Problem with PIC18F2550 ICSP

[dmitri]

Read it again TWICE and post both files here.

[jonga]

Ok, here they go. It took a while because for some reason the reading is really slow...

[dmitri]

Seems strange that reading the same PIC twice produces different results, doesn't it?
Try this: disconnect the ICSP cable and try reading flash twice again, as if the cable still connected, and post both files here again.

[jonga]

Now, on both readings I got

Reading 0x3FFFFE - 0x3FFFFF ...
Reading 0x300000 - 0x30000D ...
Reading 0xF00000 - 0xF000FF ...
Reading 0x000000 - 0x007FFF ...
Reading PIC ok.

I then simulated a programming with no cable plugged in. The messages during the programming were:


Programming...
Erasing ("bulk" or "chip") ...
Programming CODE, 0x000000..0x007FFE
Verifying CODE, 0x000000..0x007FFE
Verifying 0x000000..0x007FFE
Verify Error: 000010: read 000000, wanted 005156, mask 00FFFF ==> diff=005156
Verify Error: 000012: read 000000, wanted 006F58, mask 00FFFF ==> diff=006F58
Verify Error: 000014: read 000000, wanted 006B59, mask 00FFFF ==> diff=006B59
Verify Error: 000016: read 000000, wanted 0090D8, mask 00FFFF ==> diff=0090D8
More Verify Errors, unable to list all (total=8)
Programming DATA, 0xF00000..0xF000FF
Verifying DATA, 0xF00000..0xF000FF
Verifying 0xF00000..0xF000FF
Programming CONFIG, 0x300000..0x30000C
Verifying CONFIG, 0x300000..0x30000C
Verifying 0x300000..0x30000C
Verify Error: 300000: read 000000, wanted 000E32, mask 00FFFF ==> diff=000E32
Verify Error: 300002: read 000000, wanted 001E3F, mask 00FFFF ==> diff=001E3F
Verify Error: 300004: read 000000, wanted 0080FF, mask 00FFFF ==> diff=0080FF
Verify Error: 300006: read 000000, wanted 00FF85, mask 00FFFF ==> diff=00FF85
More Verify Errors, unable to list all (total=7)
ERROR: Programming FAILED !


And finally simulated two readings with same messages:

Reading 0x3FFFFE - 0x3FFFFF ...
Reading 0x300000 - 0x30000D ...
Reading 0xF00000 - 0xF000FF ...
Reading 0x000000 - 0x007FFF ...
Reading PIC ok.

It's really strange....

[dmitri]

Now take PIC18F2550 out of the socket, connect the ICSP cable and simulate reading memory again twice.

[jonga]

Here it goes... it seem blank, right?

[dmitri]

Here it goes... it seem blank, right?

It is. I now inclined to think that your PIC is now bust. If only you had another PIC... As a last test, put the PIC back in the socket, program it with proper V2 USB MIDI firmware, straight after that read the memory back and post it here.

[jonga]

I wish i had bought 2 of these

At least now the readings are equal. Could you tell me what they mean?

[jonga]

Just one more question: the WinPic should recognize the PIC only with USB powered on or only the COM cable is enough (I mean, not to programm it, just to be initialized by WinPic)?

[dmitri]

Not sure what you meant by "recognize the PIC", but you have to power the board whenever you want read/write your PIC.
If you meant the warning "Could not initialize programmer!" then with this ICSP cable this warning is due to the fact that it is not a real JDM programmer.
Now, about your last dumps:

Code: Select all

:02000000E3FF1C
:0E000000DAFFFFFFFFFFFFFFFFFFFFFFFFFF25
:00000001FF


First two lines are in conflict to each other. Basically the first line says that at the address 0x0000 you have (reversed on the device) FFE3, while the second line says you FFDA at the same address. How can it be I wonder?

Another question, since you were asking about powering over USB, do you have +5 on pin 20 when you try to program your PIC?