Re: [Usbpicprog-technical] Through-hole UPP testing

[Francesco M. <f18...@ya...>]

Hi,

Frans Schreuder ha scritto:
 > Hi,
 >> I have programmed my other two PIC18F2550 with the UPP bootloader. UPP 
(v.1.1) autodetected them correctly and when I clicked Actions->Program the 
programming seems successful.
 >> However if I click Actions->Verify for both those PICs I get "Verify config 
failed at 0x300004. Read 0x00. Expected 0xFF".
 >> If I understand it correctly, the bits are relative to the watchdog timer 
(WDTPS2-WDTPS0 e WDTEN).
 >>
 > There's nothing wrong with your usbpicprog, it's just normal that it can't 
verify this locations since it is not implemented in the pic and always reads as 
0x00.
ah, good!

 > I should still add some kind of mask in the software for which configuration 
bits to verify and which not. But since it differs for every PIC it is a lot of 
work to do that, so it will probably take a while.
I've seen that Piklab has in "piklab/src/devices/pic/xml_data" all datas 
available for lots of PICs; the XML files there should contain all required info 
for implementing those masks... since they release Piklab under GPL I think it 
would be ok to reuse those files.

Btw, I read on the website about the old piklab plugin; is the new one being 
developed?

I'm ready to give an hand with patches/implementation work :)

 > You can disable the verify function for config memory in the preferences panel!
I'll do so in the meanwhile, then.

Bye,
Francesco

--