Eur van Andel wrote:
> On 9 Oct 2008, at 14:06 , Rob Hamerling wrote:
>
>>> Two blink files refused to burn, I gave them a -1.
>> What exactly means 'refused to burn'? Something with the programmer?
>
>> G5-fiwihex:~/jalv2/jallib/unvalidated/sample/by_device/18f4620 eur$
>> xw go b18f4620.hex
>> XWisp 1.30, command line mode
>> hardware: Wisp628 1.23 (fast) (wisp648 firmware)
>> target: 18f4620, device code 0C00 revision bits 06
>>
>> verification failure: different data at address 300000: file=FF
>> target=0
>> ERROR
>
> Three times in a row. I have seen this before.
Ah, those damned fuses again .... always troublesome.
In the device files all fuse bits are declared with a default value of
one. It would be better if there were for every device an individual
default setting, but collecting these for every individual PIC is a time
consuming job. Therefore a chose for a 'trivial' default until there
would be time to do it better.
As programmer I use mainly a Wisp648 with my own version of Xwisp
(Xwisp2). Xwisp2 has for every supported PIC masks to correct the hex
file for fuse bits which are always 0 or always 1 when read back from
the device. This ensures that the verify works properly.
This feature of Xwisp2 explains that I do not have troubles with the
fuses. But Wouter's Xwisp seems not to have that feature, which explains
you may get verify errors.
I wonder what the Pickit2 does in this respect, I'll try that later.
Browsing through some datasets it may be better to set the default for
the 18F fuse bits to zero. Would you be so kind to test with a copy of
the 18F4620 device file (or any other giving similar trouble) with all
fuse bytes changed to 0x00? If that gives satisfactory results this
could be a provisional fix: leave the baseline and midrange fuse bits on
default all-one and change the 18Fs to default all-zero.
I must investigate if I can migrate the masks from Xwisp2 to the
'devicespecific.cmd' script for the device files with not to much work.
That would mean that about 2/3 of all the device files get an individual
fuse pattern. The remaining PICs must wait until I have collected their
patterns: datasheet reading again....
> The b18f4550 code blinks v-e-r-y s-l-o-w. If I set the freq at 20
> Mhz, it will run even slower.
Sounds to me really as fuses trouble...
> The same board (ZIF socket) works just fine with a 16F877, 16F777 and
> an 18F452.
Regards, Rob.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---