Weird ICD-U40 behaviour

[icefield]

Three weird things happen with the 2 ICD-U40's we have:

(1) You have to have the U40 plugged into the same USB port that it was in when the software was installed.

(2) Sometimes the PC "looses" the ICD and when you try to program a pic, you get a dialog prompting for serial port number and baud rate. Unpugging the U40 and plugging it in again fixes the problem.

(3) When debugging, the unit often fails and you get a communication error about the clock not starting. This is working with an 18LF6722 and 16LF876A.

Should any of these be a concern? We have two I40's which work fine in case (3), but we can't use them below 5V Vdd.

[PCM programmer]

I have seen issues like this with the Microchip ICD2 and also flash drives.
It was related to an external hub used with a USB add-on card. I think
my external USB 1.1 hub died, so I put on a new USB 2.0 hub. Then
I had to re-install the ICD2 software. I still have occasional problems
with a flash drive that doesn't get detected when I plug it in to the hub.

I think the basic idea is to not mix versions of an external hub and
mainboard USB controllers. You will get problems if you do.

[icefield]

The problem with the USB port happens between the two physical ports on a laptop. There is no hub involved.

But, really this is just an annoyance (albeit something no other USB device I have has problems with).

What is more of a concern are the debugging issues and the "resetting" issues.

[treitmey]

In regards to the USB disapearing and then reapearing that is probably an issue with the USB cable to ICD-U40 connection. The conection is probably loose. If you bump it the device disapears. Bump it again and you hear the ding-dong of a USB device being added to the computer again. This is what I think is causing it.

I've been meaning to cut off the USB wire and solder right to the ICD-U40. This would verify if my hunch is correct.