Frank
Moderator
Registered: July 31, 2005
Posts: 1,401
|
| | Sept 14, 2007 at 06:39 PM | Reply with quote | #1 |
|
The latest (and last) FREE upgrade to the DIY programmers (K128, K149, K150, K182) has been released and is available for download from
http://www.ozitronics.com/download/DIYpack25ep.zip
It will be uploaded to the DIY website once they re-open for business in one week's time.
No installation required - simply unzip into the folder of your choice.
The following is a list of supported PICs in this new release. Many thanks to 'bfoz' for compiling this list (see http://www.websitetoolbox.com/tool/post/diykit/vpost?id=2154125&trail=30)
10F200 16C65 16C84 16F87 18F2320 18F8520
10F202 16C65A 16F54 16F88 18F2321 18F8525
10F204 16C65B 16F57 16F818 18F2331 18F8621
10F206 16C66 16F59 16F819 18F2410
10F220 16C67 16F627 16F870 18F2420
10F222 16C620 16F627A 16F871 18F2431
12C508 16C620A 16F628 16F872 18F2450
12C508A 16C621 16F628A 16F873 18F2455
12C509 16C621A 16F630 16F873A 18F2480
12C509A 16C622 16F631 16F874 18F2510
12F509 16C622A 16F648A 16F874A 18F2520
12CE518 16C71 16F676 16F876 18F2550
12CE519 16C71A 16F677 16F876A 18F2580
12C671 16C72 16F684 16F877 18F4220
12C672 16C72A 16F685 16F877A 18F4221
12CE673 16C73 16F687 16F913 18F4320
12CE674 16C73A 16F688 16F914 18F4321
12F629 16C73B 16F689 16F916 18F4331
12F675 16C74 16F690 16F917 18F4410
12F683 16C74A 16F72 18F242 18F4420
16C505 16C74B 16F73 18F248 18F4431
16C554 16C76 16F74 18F252 18F4450
16C558 16C77 16F76 18F258 18F4455
16C61 16C710 16F77 18F442 18F4480
16C62 16C711 16F737 18F448 18F4510
16C62A 16C712 16F747 18F452 18F4520
16C62B 16C716 16F767 18F458 18F4550
16C63 16C745 16F777 18F1220 18F4580
16C63A 16C765 16F83 18F1320 18F6520
16C64 16C773 16F84 18F2220 18F6525
16C64A 16C774 16F84A 18F2221 18F6621
It is highly recommended that you read the 'readme-ep' PDF document for details on firmware/software changes plus unsupported PICs.
This latest upgrade is the result of many, many hours of hard work by Jim Robertson.
This upgrade is for use with GENUINE DIY programmers only.
|
| Loading... | |
Solexious
Registered: Sept 11, 2007
Posts: 6
| |
PIClover
Registered: June 05, 2007
Posts: 9
|
| | Sept 15, 2007 at 12:32 AM | Reply with quote | #3 |
|
Thank you VERY! much for this upgrade, but while unpacking this zip, McAfee tells me that in fixhex2.exe and microbrn.exe is a trojan horse (New Malware.eb)...???
Grtzz PIClover |
| Loading... | |
Solexious
Registered: Sept 11, 2007
Posts: 6
|
| | Sept 15, 2007 at 01:55 AM | Reply with quote | #4 |
|
Hello,
I'm running avg virus scanner with no reports of any viruses...
sol
|
| Loading... | |
newfound
Registered: Aug 06, 2005
Posts: 497
|
| | Sept 15, 2007 at 08:25 AM | Reply with quote | #5 |
|
Quote: Originally Posted by PIClover
Thank you VERY! much for this upgrade, but while unpacking this zip, McAfee tells me that in fixhex2.exe and microbrn.exe is a trojan horse (New Malware.eb)...???
Grtzz PIClover
Both files have been compressed with an exe packer. I did a web search I could not find any evidence to support that the packer is actually a trojan horse. I suspect it is a mistake by the McAfee virus scan.
I have a few different virus scan programs myself and I will also double check with these.
If this turns out to be a major problem I may need to find a new EXE packer but for now I will wait and see if another search on the web turns up nothing.
|
| Loading... | |
Ernie
Registered: Aug 14, 2007
Posts: 12
|
| | Sept 15, 2007 at 11:07 AM | Reply with quote | #6 |
|
| Thanks Jim for all the work you have put into this. I have completed this update and everything seems to be working well. The best thing about having a K128 is knowing it is safe to change the oscillator on my Warp13 because I have a backup. Having a second programmer and avoiding the bridge firmware path helped too. Both programmers are now fully up to date, as are the respective applications. Maybe now I can get to tinkering. I also ran the ep through AVG, no infections found. Could it be the nature of this software that it can look suspicious to some protection software? (I'm not trying to be sarcastic of condescending, I'm just curious.)
Thanks,
EEP |
| Loading... | |
Frank
Moderator
Registered: July 31, 2005
Posts: 1,401
|
| | Sept 15, 2007 at 03:21 PM | Reply with quote | #7 |
|
I am running ZoneAlarm Security Suite - it didn't find any problems either.
|
| Loading... | |
PIClover
Registered: June 05, 2007
Posts: 9
|
| | Sept 15, 2007 at 06:20 PM | Reply with quote | #8 |
|
The problem is McAfee, i tried other files also packed with Npack (like Microbrn and Fixhex2) and i get the same trojan warning...
I have to find a workaround for this as McAfee keeps deleting these files.  |
| Loading... | |
miix
Registered: Sept 15, 2007
Posts: 1
| |
bfoz
Registered: Jan 27, 2006
Posts: 27
|
| | Sept 16, 2007 at 05:02 AM | Reply with quote | #10 |
|
I'm glad to see this update has finally made it into the wild. Congrats.
A few questions though...
1. By stating that this is the last free update are you implying that there will there be no more updates, or that you're switching to an update-for-a-fee model?
2. The documentation lists a set of parts that aren't supported, but I'm not seeing the list of supported parts. Did I miss it?
3. The docs indicate that P18A is a closed protocol. Am I forbidden from adding support to QProg?
__________________
http://bfoz.net |
| Loading... | |
Frank
Moderator
Registered: July 31, 2005
Posts: 1,401
|
| | Sept 16, 2007 at 10:49 AM | Reply with quote | #11 |
|
1. This upgrade is a substantial improvement on the previous DIYpack25 and provides very good support for a wide variety of commonly used PICs.
This is the last free upgrade for these programmers - it is just not possible for DIY to keep funding all the work involved forever.
The other problem is that, due to the limitations of the Windows application and the problems previously mentioned, it is simply not possible to keep 'upgrading' as new PICs are released. At some point in the near future a complete re-write of the software/firmware will be necessary.
So, there may be other upgrades in the future but it is uncertain whether these will be provided by DIY or by a third party. In any case they will certainly not be free. However the price will be very reasonable, similar to most 'shareware' software.
2. Jim would be best to answer this question. My understanding is that the 'supported' parts are those that were supported under DIYpack25, with the exception of those PICs specifically listed as not being supported (if that makes sense).
3. Once again, Jim is best equipped to answer this question. However the reason is quite clearly stated in the 'readme-ep' file - "Due to the widespread misuse of the intellectual property of DIY ....."
|
| Loading... | |
bfoz
Registered: Jan 27, 2006
Posts: 27
|
| | Sept 16, 2007 at 11:19 AM | Reply with quote | #12 |
|
Quote: Originally Posted by Frank
1. This is the last free upgrade for these programmers - it is just not possible for DIY to keep funding all the work involved forever.
Understood.
Quote: Originally Posted by Frank
2. Jim would be best to answer this question. My understanding is that the 'supported' parts are those that were supported under DIYpack25, with the exception of those PICs specifically listed as not being supported (if that makes sense).
It might be more user-friendly to publish a canonical list somewhere instead of listing the diffs. I know to look through the cid file, but not everyone is so inclined. And I like to think I'm not the only one who hasn't memorized the chip list from pack25. 
Quote: Originally Posted by Frank
3. Once again, Jim is best equipped to answer this question. However the reason is quite clearly stated in the 'readme-ep' file - "Due to the widespread misuse of the intellectual property of DIY ....."
I saw that rationale in the text and it worries me a bit. After reading it a few times I'm getting the feeling that QProg is considered a misuse. I'm not privy to everything that's transpired, so maybe I'm missing something.
Just out of curiosity...Why is Jim the best one to ask when the text says "...misuse of the intellectual property of DIY...". Does the IP belong to Jim or DIY?
__________________
http://bfoz.net |
| Loading... | |
newfound
Registered: Aug 06, 2005
Posts: 497
|
| | Sept 16, 2007 at 02:04 PM | Reply with quote | #13 |
|
Hi Brandon, please rest assured that you are welcome to extend the usefulness of the DIY programmers. As you said you have not read everything and you are missing some details. I am personally sad that I cannot help and I have spent so time wondering how this can be changed.
It would be great if I could publish the details of P18A (and even the one of two things about P018 that you and Bob missed) so you can continue your good work. Sadly, there are factories churning out clones using the DIY software and/or firmware. At the very least it is time to slow them up. There are some traps included in the expansion pack that hopefully will cause them headaches when they least suspect it. To that ends I have not offered details of what exactly has and hasn't changed. The matter is rather strategic, anything I say may offer clues, or it may be a complete bum steer.
If and when the issue of pirating is brought under control I may promote the new protocol (if I am still on the scene) so people can write matching software. My final point on this matter would be that Stu who wrote Donkey Prog was not exactly happy that it too was "lifted" as used by pirates without permission. You may or may not feel the same way if your QProg is likewise taken advantage of.
On the matter of there being no list of supported PICs, this may well be because there is a difference between "included" and "supported" PICs. The readme contains a list of PICs that cannot be supported (i.e. don't waste your time) and also a basic nudge in the direction of users adding new parts themselves. This was always the intention of the open chipinfo file. It was NEVER going to be my job to add all the possible programmable PICs though in fact I have added many more parts than I agreed to. My agreement was to fix the problems with the 10Fxxx parts and make it possible to program the later 18Fxxxx PICs. That I have done and a lot more too.
Finally, as I understand it, both DIY and myself now jointly own the IP and can act together or independently. It is a matter of trust between us.
|
| Loading... | |
Frank
Moderator
Registered: July 31, 2005
Posts: 1,401
|
| | Sept 16, 2007 at 04:46 PM | Reply with quote | #14 |
|
Quote: Originally Posted by Frank
<snip>
Just out of curiosity...Why is Jim the best one to ask when the text says "...misuse of the intellectual property of DIY...". Does the IP belong to Jim or DIY?
I meant that Jim would be best to answer about why the P18A spec is 'closed', which he has since answered.
And yes, the IP belongs to both DIY and Jim.
|
| Loading... | |
bfoz
Registered: Jan 27, 2006
Posts: 27
|
| | Sept 17, 2007 at 02:34 AM | Reply with quote | #15 |
|
Quote: Originally Posted by newfound
(and even the one of two things about P018 that you and Bob missed) so you can continue your good work.
You're the second person to mention that I missed something in P018 without telling me what it is. This is driving me nuts.
Quote: Originally Posted by newfound
My final point on this matter would be that Stu who wrote Donkey Prog was not exactly happy that it too was "lifted" as used by pirates without permission. You may or may not feel the same way if your QProg is likewise taken advantage of.
One of the nice things about releasing something as OSS is not having to worry much about such issues; especially with such a permissive license as the BSD. I'm happy if people think QProg is good enough to be distributed.
__________________
http://bfoz.net |
| Loading... | |
