ICD control working - Debugger not

mcurtis · Guest

All was good, untill i updated ICDU software (April 26th download) . Now the debugger gives me "can't detect target chip", however if I use the ICD control program, all works fine(passes all tests,and downloads). Seems if one works, the other should, however I'm just a hobbiest, so not all that clear on how they differ. Using ver 3.42 ide, 1.87 compilers, v2.30 icd control prrogram, 1.39 icd firmware, and ICDU40. Tried rolling back to previuos versions, but didn't help. Just to keep progress moving forward I'm using the ICD program, but it's not as much fun.

Thanks
Maynard

mcurtis · Joined: 25 May 2005 Posts: 2

Found a solution, but not an answer. Switched to a 18F452 from the 16F877 and debugger started working again. I had been running in fast mode (-5v option -Advanced tab on icd control). on start up with 18F452, got a warning this may cause problems. Tried turning it off and went back to 16F877, but still did not work. Please keep me posted if ccs responds.

-maynard

smashHIT · Joined: 28 Nov 2004 Posts: 14

Had the same problem, and asked CCS what to do:

Sir,
Try renaming the devices.dat to deviceso.dat and the devicesp.dat to devices.dat in the compiler directory.
Thanks
CCS Tech Support

That worked like a charm!

seven · Joined: 26 May 2005 Posts: 10

i do not have the file "devices.dat".

Is it available just with the lastest version? cause i'm running with the 3.222 version

mcurtis · Joined: 25 May 2005 Posts: 2

Worked for me as well. While testing, I noticed the 18F452 downloads much faster than the 16F877. Do different chips have different ICSP download speeds, or is this a CCS debugger issue.

Thanks

scanpa · Guest

Hi Guys,

I have the same problem after installation of rel 3.225: ICD is working stand alone but not as debugger.

Making a roll back to previous 3.224 all is ok.

CCS support can help us ?