Jan-Erik Soderholm wrote : > It's there. Including robs adjustments. Same URL, same file. > (Shortcut : http://www.st-anna-data.se/xwisp213.zip ) > > It now downloads Edson Brusque's 32K HEX file (inluding > erase, and program/verify of all memories) in about 64 secs. Edson have reported further problems with his large HEX file. Both Rob and I have been testing this, but can not understand what is happening in Edson's hardware. I have downloaded Edson's HEX file both to a DB016 processor card fro Wouter and from a breadboard setup, with no problems. Same for Rob, I think. It "looks" like his software uses self-modifying program memory, since when programed and verifyed without a crystal, the verify runs OK, but if the PIC is started for some seconds, the verify reports a few differences (that is, using a separate "verify", not the verify that is part of the "go" command, that one runs OK in all cases...). Anyway, this has not lead to any changes of XWisp2 at the moment. I'd very much appreciate if others could also test my XWisp2 with there own applications. And I'm sure Rob would also, since errors (if any !!) could be in the common code as well as the OS specific parts. Unfortunaly I have not been able to test Edson's HEX file using the Python version, since it just hangs after reading back the code (using the latest kit from Wouter). I have not seen this before and I have notified Wouter about it... It *does* works for Edson, so, I'm lost here... Regards Jan-Erik. -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads