Re: xwisp2 1.7.01 released

Rob Hamerling <[email protected]>
Newsgroups gmane.comp.hardware.microcontrollers.gnupic
Message-ID <[email protected]>
Hi Wayne,

Wayne Topa wrote:

>   You forgot the Makefile and ISTR you were going to put the
>   xwisp2.cfg file in the source package, XWISP2171S.ZIP.

Huh? Have you downloaded the right package? I just checked again:
(1)
There are 6 makefiles in xwisp2171s.zip called 'xwisp2_pq.mak', in which 
'p' represents the compiler (g-GCC, v = IBM-VAC, w = Watcom) and 'q' 
represents the target platform (2 = OS/2, w = W32, u = linUx'). So for 
compiling xwisp2 under linux you'll probably use xwisp2_gu.mak.
(2)
xwisp2.cfg is also in xwisp2171s.zip....


[from you other message]
> I copied the xwisp2.cfg from the binary zip file.  The changes.txt
> file mentions the 'fix for the 12F635,683, and the 16F684,688 etc'
> as removing the FuseFixedZero and FuseFixedOne specifications from 
> xwisp2.cfg.  xwlistu still has them listed tho.

Probably a misunderstanding: I removed only the part of the calibration 
words. The masks for the config word (fuses) itself should remain.
Note, xwisp2 uses these mask only to prevent write/verify errors when 
the hex-file contains an incorrect bit pattern. For example: the hex 
file contains for the fuses a '1'-bit on an 'unused' position which 
always reads back as '0'-bit.

To Xiaofan: with verify-only xwisp will report errors in your hex-file 
to my opinion rightly: the hex file is in error, not the bits in the PIC.

>  The XWISP2171.ZIP, binary package, does indeed work as advertised!
> 
>  Very nice job Rob.  You sure did the fixup fast.  Now I really have
>  to consider the Wisp6[2|4]8 again.

Thanks for the compliments!

Regards, Rob.

-- 
Rob Hamerling, Vianen, NL phone +31-347-322822
homepage: http://www.robh.nl/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.