Hi Jan_Eric,

You are absolutely correct. The "software dongle" does not work
on my Windows XP box as well. I only tried 12F675 and
xwisp2 1.7.2. After successfully writing the blank chip, all
subsequent erase or go command failed.

Therefore the real dongle is still needed for 12F629/12F675.

Regards,
Xiaofan

1) Tried to erase: not really erased
E:\Coding\XWISP2172>xwisp2w port 2 erase
 xwisp2 version 1.7.02 for Windows (Sep 25 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.51 seconds

E:\Coding\XWISP2172>xwisp2w port 2 erase
 xwisp2 version 1.7.02 for Windows (Sep 25 2005, Open Watcom C 1.30)
Programmer Wisp628, firmware version 1.09
Target not found in configuration table
Target not auto-detected, please specify on commandline!
xwisp2 failed after 1.06 seconds, rc 23!

2) Tried to program with "go" command --> failed
E:\Coding\XWISP2172>xwisp2w port 2 go b675i-1.hex
 xwisp2 version 1.7.02 for Windows (Sep 25 2005, Open Watcom C 1.30)
File b675i-1.hex loaded and is Intel Hex format conforming
Programmer Wisp628, firmware version 1.09
Target not found in configuration table
Target not auto-detected, please specify on commandline!
xwisp2 failed after 1.06 seconds, rc 23!

E:\Coding\XWISP2172>xwisp2w port 2 go b675i-1.hex
 xwisp2 version 1.7.02 for Windows (Sep 25 2005, Open Watcom C 1.30)
File b675i-1.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...Wbus command failure
Write-Verify failed after 0.08 seconds, rc 21!
xwisp2 failed after 1.73 seconds, rc 21!


On 9/28/05, Jan-Erik Soderholm <jan-erik.soderholm@telia.com> wrote:
> Xiaofan Chen wrote :
>
> > 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.
>
> Hi.
>
> I've *not* been able to reproduce this on WinXP, Wisp628 1.09
> and XWisp2 1.7.02 on 12F629 and 675 (tried both).
>
> I've tried a lot of combinations of erase, write, target and go...
>
> I need to connect Wouter's dongle to be able to "lock up"
> the 12F's again after flashing b675i-2.hex from Wouters
> blink-a-led page. That hex uses both intosc and int-mclr.
>
> 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
>

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist