ICD2 cannot program my 16F877

[Marcel Tschopp]

Hi<p>
My Problem is following (listing from MPLAB):<p>
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
<b>ICDWarn0020: Invalid target device id (expected=0x4D, read=0x0)</b>
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Programming Target...
...Erasing Part
...Programming Program Memory
...Loading DebugExecutive
...Programming DebugExecutive
...Programming Debug Vector
...Programming Configuration Bits
Verifying...
...Program Memory
<b>ICD0161: (CMemory::Verify) Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x3000, Val Read = 0x0)
...Verify Failed (and stopped)
...Verify Failed (and stopped)</b>
...Programming failed
MPLAB ICD 2 Ready
<p>
I have MPLAB 6.13, PCM 1.13 and ICD2, which i use over USB.<br>
I checked the connections from and to the 16F877 and they seems to be correct.<br>
Please, can you help me?<p>

Thanks!
___________________________
This message was ported from CCS's old forum
Original Post ID: 13675

[mcafzap]

:= Verifying...
:= ...Program Memory
:= <b>ICD0161: (CMemory::Verify) Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x3000, Val Read = 0x0)


FWIW I've had similar results from time to time. It seems that the write protection bits become set and hence the 'Val Read = 0x0'. The only solution I've found is to program the processor with an external programmer, then replace it in your development board where it will once again work OK.

Steve
___________________________
This message was ported from CCS's old forum
Original Post ID: 13677

[Marcel Tschopp]

:=:= Verifying...
:=:= ...Program Memory
:=:= <b>ICD0161: (CMemory::Verify) Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x3000, Val Read = 0x0)
:=
:=
:=FWIW I've had similar results from time to time. It seems that the write protection bits become set and hence the 'Val Read = 0x0'. The only solution I've found is to program the processor with an external programmer, then replace it in your development board where it will once again work OK.
:=
:=Steve

Thanks for your fast reply.

I don't believe that this is the problem, because I tried to program two new and "fresh" PICs. Why should the configuration bits have changed?

If I have no other chance then I will try to get an Pro Mate II. Or does anybody know a cheaper external programmer for 16F877 PICs?

Marcel Tschopp
___________________________
This message was ported from CCS's old forum
Original Post ID: 13679

[jds-pic]

> ICDWarn0020: Invalid target device id (expected=0x4D, read=0x0)

this message usually means one of the following:
1) Vcc is not on, or the ICD2 can't supply enough current
2) the ICD2 <-> PGD/PGC/MCLR connections are miswired
3) other logic on the PGD or PGC pins is causing contention
4) the PGM pin is pulled high
5) you have some other problem related to the electrical config

until that error message is solved, nothing after it should be expected to work in any deterministic way.

jim
___________________________
This message was ported from CCS's old forum
Original Post ID: 13697

[Chip Jansen]

:=
:=> ICDWarn0020: Invalid target device id (expected=0x4D, read=0x0)

:=4) the PGM pin is pulled high

I ran across the same problem with an ICD 2 / 18f720 --
I had stuff wired up to port B and consequently pin B5
which was the PGM pin and the switch happened to be pulled high.

Thank you!
~chip
___________________________
This message was ported from CCS's old forum
Original Post ID: 144515435