Problem Programming PIC18F2550

[Firelord]

The facts.

- Using a MD built from scratch (PCB's from the current schematics), currently testing the digital board (with the all the IC's) without the analogue board, keyboard or LCD connected;
- ATMega324P programmed ok, however I cannot test it since the LCD seems dead (upon connecting one of the protected IC's on its circuit is starting to heat up);
- PIC uses a 12MHz crystal and I programmed it with pic18f2550usb_12MHz.hex (from the downloads section of the website), also tried a shorter programming cable with no luck.

I will recheck the board once again and if I encounter a dumbass mistake or short or whatever, I will let you know via this thread.

[dmitri]

You should have used "File->Dump buffers to hex file" to save the read memory content.

[Firelord]

You should have used "File->Dump buffers to hex file" to save the read memory content.

All right, I will post that tomorrow.

[Firelord]

Here's the dump (no pun intended).

[dmitri]

Here's the dump (no pun intended).

The code memory content is correct. Can you read the device again and then go to "Config Memory" tab and make a screenshot?
After this try programming it again but do "Device->Erase" and "Device->Blank check" first.

[Firelord]

Here's the dump (no pun intended).

The code memory content is correct. Can you read the device again and then go to "Config Memory" tab and make a screenshot?

First thing tomorrow.

After this try programming it again but do "Device->Erase" and "Device->Blank check" first.

I've performed various combinations of procedures, featuring those somewhat similar to the one described, but to no avail. Of course, I will try it again anyway.

I wonder, why isn't CONFIG being written properly? Tried programming PIC several times, and program code always verified ok, but these two errors within the CONFIG memory block are rather persistent.

[Firelord]

Ok, here's the screen and the erase-blank check log.

Code: Select all

Erasing chip using algorithm "PIC18F" .
Device has been erased.
Reading 0x3FFFFE - 0x3FFFFF ...
Reading 0x300000 - 0x30000D ...
  Config memory is not blank at addr 0x300000 : read=0x0500, mask=0xFFFF .
Reading 0xF00000 - 0xF000FF ...
Reading 0x000000 - 0x007FFF ...
Device is NOT blank.

[dmitri]

Your PIC is correctly programmed. Your problem is elsewhere.

[dmitri]

- ATMega324P programmed ok, however I cannot test it since the LCD seems dead (upon connecting one of the protected IC's on its circuit is starting to heat up);

I once had this problem and the cause was that I accidentally swapped odd and even wires going to LCD by soldering a pin header on the wrong side of the LCD, i.e. 1 went to 2, 2 went to 1, 3 went to 4, 4 went to 3 and so on.

[Firelord]

- ATMega324P programmed ok, however I cannot test it since the LCD seems dead (upon connecting one of the protected IC's on its circuit is starting to heat up);

I once had this problem and the cause was that I accidentally swapped odd and even wires going to LCD by soldering a pin header on the wrong side of the LCD, i.e. 1 went to 2, 2 went to 1, 3 went to 4, 4 went to 3 and so on.

I double checked that (at least I thought I did). But I guess it doesn't matter anymore, since one of the chip on the LCD is definitely dead. Going to get another LCD module (all pins aligned in a single row and it's harder to make a mistake).

One more question on PIC18F2550. Is it supposed to be recognized by the OS right after it's flashed, even if ATMega and optocoupler IC are not in their sockets and nothing else is connected to the digital board (keyboard, LCD, etc.)?