ICD-U40 does not work. ICD-2 does

Hans Wedemeyer · Joined: 15 Sep 2003 Posts: 226

I've been battling an issues with the ICD-U40 (two of them) for some time.
Today the issue got so bad I can no longer program chips with either of the units I have.

I have tried upgrading the firmware to whatever is the latest, and in fact to a special firmware that was supplied by CCS.

After programming a units the ICD-U40 reports a verification error.
So I tried programming different units, with the same results.

Then I downgraded the firmware to an older version in an attempt to see if the new (and special) firmware was the problem.
The result is the same.

So I fired up MPLAB V7.51 and ICD-2 and it programmed and verified the units OK....

Has anyone else had this problem with the CCS- ICD-U40 ?

Douglas Kennedy · Joined: 07 Sep 2003 Posts: 755 Location: Florida

The ICD-U40 I have has worked flawlessly. The only issue I ever had was having too long a cable between the unit and the target chip. About 6 ins is fine alot more than 6 ins and it starts to fail.

treitmey · Joined: 23 Jan 2004 Posts: 1094 Location: Appleton,WI USA

Also check the pull-up on mclr.
icd-u40 says 47k and no cap

Ringo42 · Joined: 07 May 2004 Posts: 263

I've had the same issue. I have 2 programmers and 1 of them got so bad I could not use it. 1 programmer worked great, the other always had verify errrors. I sent it to CCS and they could find nothing wrong with it. I just got it back today and have not had any problems yet tonight with it. I had problems on at least 6 different boards.
_________________
Ringo Davis

Andreas · Joined: 25 Oct 2004 Posts: 136

Hi,

Sounds very familiar to me, had a lot of proböems inthe last months, got new software, had to make chances on the ICD Hardware......

All I wanted was to be able to programm J-Type Procs.

And all of the time the ICD2 had no problems at all !!!!!

Finally after about 3 - 4 weeks mailing with CCS I got the great answer maybe You should buy a new one, we made some major changes in the last released ICD's.

Has somebody of You seen any message about releases or changes to ICD Hardware ??

Had also made upgrades to the firmware by reflashing the chip with a hexfile supplied y CCS.

Result: Still not having 2 ICD40U with which I can programm all my projects !

best regards
Andreas

Neutone · Joined: 08 Sep 2003 Posts: 839 Location: Houston

I have also destroyed a few ICD-U40's with a high voltage spike caused by switching a high current load while I was debugging code.

mcman · Joined: 23 Jan 2007 Posts: 8 Location: Corvallis, OR

I have an ICD-U40 that I, too, could not get to work. If I remember correctly, the problem had to do with USB connectivity. The ICD-U40 has an FTDI USB device. My development system also included an FTDI USB device. The CCS IDE would get confused when trying to connect. Basically, a poorly written 'open' method on the part of CCS. It isn't difficult to connect to a specific device based on fields configured on the USB device such as VID, PID, Mfg, Description. In fact, the ICD-U40 has all those fields configured:

VID: 0403
PID: F9D1
Mfg: CCS
Desc: CCS ICD-U40

Even so, as soon as I would plug my other FTDI based USB device in, the CCS compiler would freak out and try to connect with it instead. So, I dropped the CCS IDE and went with MPLAB instead, along with the ICD-2. No problems with that.

treitmey · Joined: 23 Jan 2004 Posts: 1094 Location: Appleton,WI USA

My solution to the mcman problem was to change my PID/VID/description
for my dev system(mprog). Then in production the correct one is used.

If your using an FTDI device,...please open it the right way.
btw I think the current software is opening it the right way, I haven't
seen any of those problems for a while.