Re: xwisp2 1.7.01 released

Sorry if you received this email twice.
It seems all my recent post to GNUPIC list
using my gmail account did not go through.
Therefore I resend the post again.

---------- Forwarded message ----------
From: Xiaofan Chen <xiaofanc AT gmail.com>
Date: Sep 17, 2005 9:26 PM
Subject: Re: [gnupic] xwisp2 1.7.01 released
To: [email protected]

The compilation/building on Ubuntu is perfect: not even a warning message!

The initial test on 12F635/16F684 shows that the binary I built works.
The verification of 12F629 shows error message but the

Regards,
Xiaofan

1) building
mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2171s$ cp xwisp2_gu.mak Makefile
mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2171s$ make clean
rm -f xwisp2bus.o xwisp2cfg.o xwisp2cmd.o xwisp2com.o xwisp2dat.o
xwisp2hex.o xwisp2mis.o xwisp2tgt.o xwisp2os.o
rm -f xwisp2.o xwlist.o
rm -f xwisp2u xwlistu
mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2171s$ make
Compiling xwisp2.c
Compiling xwisp2bus.c
Compiling xwisp2cfg.c
Compiling xwisp2cmd.c
Compiling xwisp2com.c
Compiling xwisp2dat.c
Compiling xwisp2hex.c
Compiling xwisp2mis.c
Compiling xwisp2tgt.c
Compiling xwisp2os.c
Linking xwisp2u
Compiling xwlist.c
Linking xwlistu

2) test on 16f684 using adapted PICkit 1 lesson 2 --> okay
mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2171s$ ./xwisp2u port
/dev/ttyS1 write state6842.hex
 xwisp2 version 1.7.01 (Sep 17 2005, GCC 3.3)
File state6842.hex loaded and is Intel Hex format conforming
Programmer Wisp628, firmware version 1.09
Detected target: 16F684 revision 03 (ID=1083)
Transferring image to 16F684 via Wisp628
Transferring program memory...OK!
Transferring ID memory........OK!
Transferring data memory......OK!
Transferring fuses memory.....OK!
Write terminated successfully in 1.44 seconds
xwisp2 terminated successfully in 2.22 seconds
mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2171s$ ./xwisp2u port
/dev/ttyS1 verify state6842.hex
 xwisp2 version 1.7.01 (Sep 17 2005, GCC 3.3)
File state6842.hex loaded and is Intel Hex format conforming
Programmer Wisp628, firmware version 1.09
Detected target: 16F684 revision 03 (ID=1083)
Verifying program memory......OK!
Verifying ID memory...........OK!
Verifying data memory.........OK!
Verifying fuses memory........OK!
Verify terminated successfully in 0.28 seconds


3) To test 12F629 without a Wisp628 dongle, I erase the chip to avoid 
the Vdd-before-Vpp problem (12F629/675 require Vpp-before-Vdd). 
The programming seems to be okay and the chip is indeed working. 
However the verification gives error. I need to check this again.

mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2171s$ ./xwisp2u port
/dev/ttyS1 erase  xwisp2 version 1.7.01 (Sep 17 2005, GCC 3.3)
Programmer Wisp628, firmware version 1.09
Detected target: 12F629 revision 15 (ID=0F8F)
Target erased

mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2171s$ ./xwisp2u port
/dev/ttyS1 write state629.hex
 xwisp2 version 1.7.01 (Sep 17 2005, GCC 3.3)
File state629.hex loaded and is Intel Hex format conforming
Programmer Wisp628, firmware version 1.09
Detected target: 12F629 revision 15 (ID=0F8F)
Transferring image to 12F629 via Wisp628
Transferring program memory...OK!
Transferring ID memory........OK!
Transferring data memory......OK!
Transferring fuses memory.....OK!
Write terminated successfully in 1.25 seconds
xwisp2 terminated successfully in 2.23 seconds

mcuee@ubuntu:~/Desktop/build/xwisp2/xwisp2171s$ ./xwisp2u port
/dev/ttyS1 verify state629.hex
 xwisp2 version 1.7.01 (Sep 17 2005, GCC 3.3)
File state629.hex loaded and is Intel Hex format conforming
Programmer Wisp628, firmware version 1.09
Detected target: 12F629 revision 15 (ID=0F8F)
Verifying program memory......OK!
Verifying ID memory...........OK!
Verifying data memory.........OK!
Verifying fuses memory........failed at 00400E, expected: '8C3F', found:
'8C11'
Verify failed after 0.29 seconds, rc 21!
xwisp2 failed after 1.27 seconds, rc 21!