Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronic Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

MPLAB 7.11 problems in ICD2

Status
Not open for further replies.

TobiasB

Junior Member level 1
Joined
Dec 13, 2005
Messages
15
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,455
Hi All,

i have an Problem with my ICD2 rebuild. I use MPLAB 7.11 an the follwing error:

ICDWarn0034: Please ensure that your system's serial FIFO buffers are disabled.
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
ICDWarn0020: Invalid target device id (expected=0x3B, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready

But the crazy thing that 2 or 3 times error "ICDWarn0020" wasnt there. Should I upload my Schematic and PCB or anyone has an idea? Schematic and PCB made with PCAD2004. I can upload PCB and Schematic as PDF?!

thx

Tobias

P.S. Sorry 4 bad english


*Edit*
I upped the schematic and the Board in Adobe PDF
 

cdallacosta

Newbie level 5
Joined
Nov 1, 2005
Messages
9
Helped
2
Reputation
4
Reaction score
0
Trophy points
1,281
Location
brazil
Activity points
1,398
icd0161: verify failed

That error means that the ICD2 did not find the expected pic on the target circuit (i.e., expected a 16F877A, found a 16F877).

In particular, the "read=0x0" means that the ICD2 was not able to read the target device identification, which means that either: a) it's not connected to a target circuit, b) the target circuit is not powered or c) the cable or a connection is faulty
 

TobiasB

Junior Member level 1
Joined
Dec 13, 2005
Messages
15
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,455
icdwarn0020

I tested the cable with the original ICD2 and the target too....Both work.... My Target Vpp of the rebuild is ca. 9V.....too low?.... But it work 1 or 2 times...i had read und erase the target...:cry:...
Should i test with serial interface (non FTDI with MAX232)?
Should i power the rebuild extern?
 

froggy

Member level 5
Joined
Jul 6, 2001
Messages
84
Helped
3
Reputation
6
Reaction score
1
Trophy points
1,288
Activity points
699
icd0161: verify failed

Check the VPP supply. it should be 12-13V 9V is way too low!

/Froggy
 

TobiasB

Junior Member level 1
Joined
Dec 13, 2005
Messages
15
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,455
mplab icd2 invalid target device id

Hello Guys
i have seen that i have an 10K Poti and not an 100K Poti at the Amp -. I have no 100k Poti here and i just made an 90k Resistor in Series ^^..... And that`s what i got in MPLAB 7.11:

MPLAB ICD 2 Ready
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
ICDWarn0020: Invalid target device id (expected=0x3B, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
Target Device PIC16F88 found, revision = b1
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Reading...
ICDWarn0038: When using auto-calculate write range, reads cover the entire memory range. Do you wish to continue?
...EEPROM
...Program Memory (0x0 - 0xFFF)
.. Config Memory
...User ID Memory
...Read Succeeded
MPLAB ICD 2 Ready
Erasing Target Device...
...Erase Succeeded
MPLAB ICD 2 Ready
Blank Checking...
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x825, Expected Val = 0x3FFF, Val Read = 0x0)
...Device not blank
MPLAB ICD 2 Ready
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
ICDWarn0020: Invalid target device id (expected=0x3B, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
ICDWarn0020: Invalid target device id (expected=0x3B, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready


U see....it worked....and then...nothing....sh**

I have no idea.....pls help me
 

TobiasB

Junior Member level 1
Joined
Dec 13, 2005
Messages
15
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,455
icdwarn0020: invalid target device id

Hi guys... i think i solved the Problem!....A very stupid Problem.... I made a short and a long cable...both worked?!.....then i changed my COM-Port of FTDI Driver >COM3 --> it doesnt work. Can this be the Problem? My Vpp and MCLR Vpp is good now. That was an error in the placement.

Ever when i choose COM-Port 2 in my FTDI Driver Settings...it work ! ! ! !
 

TobiasB

Junior Member level 1
Joined
Dec 13, 2005
Messages
15
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,455
icd2 invalid target device

:( .....hm.... Now i have Problems at Verify... Debug mode also dont work. Can anyone upload his gerber for ICD2 using FTDI? Big thx
 

TobiasB

Junior Member level 1
Joined
Dec 13, 2005
Messages
15
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,455
invalid target device id icd2

*PUSH*...Anybody has en Idea? I still have the Problems and find no Solution. Possible that Debug with FTDI dont work?

thx
 

VSMVDD

Banned
Joined
Jun 12, 2005
Messages
646
Helped
92
Reputation
184
Reaction score
34
Trophy points
1,308
Location
scotland uk
Activity points
0
icd2 problem

port B pullup
i think cts will expect this check it anyway

maybe rts is the wrong polarity also

im not debug it for you


:D

also dtr is wrong

so always device is being reset
 

TobiasB

Junior Member level 1
Joined
Dec 13, 2005
Messages
15
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,455
icd0161 verify failed

Port B Pullup? Where is Port B.....lol?

I dont find a mistake. My schem is same as Lothar Stolz / Harald Sattler! ! ! ! Proved it this morning.
 

petbos

Newbie level 3
Joined
Jul 30, 2007
Messages
4
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,312
verify failed mplab

I've tesame problem.
It seems to be a timing problem ?
First, it didn't always recognize the target pic. But then a replaced the 10K pullup resistor on the target's MCLR pin with an 100K and now it recognize always the target pic.
Now, It didn't always program and start debugging the target pic.
I've get mostly (not always) an error at the verify or start debugging stage.

Any suggestions ???

See also my other topic on edaboard that maybe gives some troubles :
https://www.edaboard.com/ftopic264563.html
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Top