Firmware upgrade disaster!!!

[kurtus420]

OK, I will do it in 2 hours and post it, should I be handling the pic18f2550 in some sort of way to protect it from electrostatic discharge while taking it out or installing it or does it matter and does the v2.8 board protect it from discharges while programming it?

Do I just print screen and then somehow load it to a post to show this to you, sorry I'm a bit of a noob when it comes to posting images on forums, I will do this a lunch in about 4 hours if you can give me a little guidence thanks.

There is a button/command in Winpic to read the memory content and it will prompt you to save to a .hex file which you should post here.

[dmitri]

OK, I will do it in 2 hours and post it, should I be handling the pic18f2550 in some sort of way to protect it from electrostatic discharge while taking it out or installing it or does it matter and does the v2.8 board protect it from discharges while programming it?

As with all semiconductors, handle it with care.

[kurtus420]

so the use of antistatic devices such as mats and straps etc are not required? What do you mean by "handle with care"? Thanks

OK, I will do it in 2 hours and post it, should I be handling the pic18f2550 in some sort of way to protect it from electrostatic discharge while taking it out or installing it or does it matter and does the v2.8 board protect it from discharges while programming it?

As with all semiconductors, handle it with care.

[dmitri]

so the use of antistatic devices such as mats and straps etc are not required? What do you mean by "handle with care"? Thanks

Read http://en.wikipedia.org/wiki/Electrosta ... Prevention and apply common sense.

[kurtus420]

Thanks Dimitri, I let you know shortly what winpic read memory is.

[kurtus420]

is it dump buffers to hex option?

[Synthex]

LVP is not disabled in the PIC.

[kurtus420]

here's the message I get trying to reprogram

Info: Loading definitions for "PIC18F2550" from C:\PROGRAM FILES\WINPIC\devices.ini .
Info: Support for some newer PIC18F devices added by Martin v.d. Werff 2005
Couldn't find "devices\PIC18F2550.dev", please borrow/copy from MPLAB !
PIC18F: family='21'=4550, WriteLatch=32 bytes, EraseLatch=64 bytes .
Initialising PIC-Programmer: Success.
Testing: delay(500ms) took 0.50 seconds, timer_freq=1.1932 MHz ... ok
Programming...
Erasing ("bulk" or "chip") ...
Programming CODE, 0x000000..0x001692
Verifying CODE, 0x000000..0x001692
Verifying 0x000000..0x001692
Verify Error: 000000: read 00FFFF, wanted 00EF30, mask 00FFFF ==> diff=0010CF
Verify Error: 000002: read 00FFFF, wanted 00F00B, mask 00FFFF ==> diff=000FF4
Verify Error: 000004: read 00FFFF, wanted 000012, mask 00FFFF ==> diff=00FFED
Verify Error: 000006: read 00FFFF, wanted 000012, mask 00FFFF ==> diff=00FFED
More Verify Errors, unable to list all (total=2890)
Programming CONFIG, 0x300000..0x30000C
Verifying CONFIG, 0x300000..0x30000C
Verifying 0x300000..0x30000C
Verify Error: 300000: read 00FFFF, wanted 000E22, mask 00FFFF ==> diff=00F1DD
Verify Error: 300002: read 00FFFF, wanted 001E3F, mask 00FFFF ==> diff=00E1C0
Verify Error: 300004: read 00FFFF, wanted 0081FF, mask 00FFFF ==> diff=007E00
Verify Error: 300006: read 00FFFF, wanted 00FF85, mask 00FFFF ==> diff=00007A
More Verify Errors, unable to list all (total=7)
ERROR: Programming FAILED !

[kurtus420]

any thoughts on whats happening here Synthex?

[dmitri]

is it dump buffers to hex option?

The file you posted is not what you read from device. When dumped the whole memory content the resulting file for PIC18F2550 should be 92k in size.
First do Device->Read and then File->Dump buffers to hex file.