That is good news. Only 12F629 and 12F675 cause problem. I've only played with 12F629/675/635 and 16F684 and I find there is no problem with 12F635 and 16F684. You must have played with more chips than I. Even better news is that the "software dongle" seems to work (erase first before write). I am now testing Rob's latest Xwisp2 1.7.2 version and the "go" command is working without the hardware dongle. If more people can confirm that the "software dongle" is working for 12F629/12F675, there is no more need for hardware dongle. We just beed to use the most often used "go" command now. Maybe you (Jan-Eric) can try out this as well to see if this is the case for 12F629/675 on Windows. I will test it later as well on Windows. Regards, Xiaofan ***********Test on Linux for xwsip2 1.7.2 test 2 version***************** 1) using write command will sometimes fail because of the INTOSC and internal /MCLR. mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2172$ ./xwisp2u port /dev/ttyS1 write state6752.hex xwisp2 version 1.7.02 for Linux (Sep 22 2005, Open Watcom C 1.30) File state6752.hex loaded and is Intel Hex format conforming Programmer Wisp628, firmware version 1.09 Detected target: 12F675 revision 03 (ID=0FC3) Transferring image to 12F675 via Wisp628 Transferring program memory...Wbus command failure Write failed after 0.14 seconds, rc 21! xwisp2 failed after 1.13 seconds, rc 21! 2) Erase and then write will work from my testing mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2172$ ./xwisp2u port /dev/ttyS1 erase xwisp2 version 1.7.02 for Linux (Sep 22 2005, Open Watcom C 1.30) Programmer Wisp628, firmware version 1.09 Detected target: 12F675 revision 03 (ID=0FC3) Target erased xwisp2 terminated successfully in 1.33 seconds mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2172$ ./xwisp2u port /dev/ttyS1 write state6752.hex xwisp2 version 1.7.02 for Linux (Sep 22 2005, Open Watcom C 1.30) File state6752.hex loaded and is Intel Hex format conforming Programmer Wisp628, firmware version 1.09 Detected target: 12F675 revision 03 (ID=0FC3) Transferring image to 12F675 via Wisp628 Transferring program memory...OK! Transferring ID memory........OK! Transferring data memory......OK! Transferring fuses memory.....OK! Write terminated successfully in 1.27 seconds xwisp2 terminated successfully in 2.25 seconds 3) "go" command is doing erase first for this version. I have not tested the old versions mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2172$ ./xwisp2u port /dev/ttyS1 go state6752.hex xwisp2 version 1.7.02 for Linux (Sep 22 2005, Open Watcom C 1.30) File state6752.hex loaded and is Intel Hex format conforming Programmer Wisp628, firmware version 1.09 Detected target: 12F675 revision 03 (ID=0FC3) Target erased Transferring image to 12F675 via Wisp628 Transferring program memory...OK! Verifying program memory......OK! Transferring ID memory........OK! Verifying ID memory...........OK! Transferring data memory......OK! Verifying data memory.........OK! Transferring fuses memory.....OK! Verifying fuses memory........OK! Write-Verify terminated successfully in 1.62 seconds Putting target in run mode On 9/24/05, Jan-Erik Soderholm wrote: > > And to add to that, the *only* devices that I have had to use > the dongle with are the 12F629/675. I have had the same > experience with the F88 as Rob (re-programmed OK using > both intosc and int-mclr without the dongle). > > Regards, > Jan-Erik. > -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist