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. 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. > I'm very curious to know what goes wrong with you. The blink > samples for > the 18F4620 and 18F2620 work here. I have no 18F4550, but an 18f4582 > works here too. So tend to believe there is something wrong with your > test board. The same board (ZIF socket) works just fine with a 16F877, 16F777 and an 18F452. Yes, it is weird. Could the impedance of the PLL-possible OSC pins matter here? I'll check if the PLL is default off. If the PLL is on, blinking would occur faster, not slower. --- ir EE van Andel [EMAIL PROTECTED] http://www.fiwihex.nl Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands tel+31-546-491106 fax+31-546-491107 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
