Device configuration failed (Scope chip id) 0xC0

[Famartinez76]

Hi guys,

I keep getting the following message when I try to connect waveforms to my Analog Discovery 2.

"Device configuration failed (Scope chip id) 0xC0
USB: 5.02V 374mA AUX 0.00V 0mA"

The LED is blinking as if the device would be alive and kicking and the device is listed as I device i would be allowed to connect to but I cannot use any of its functions.

Is there anything that I can do to fix it?  i tried in different computers and the result is the same.

Any recommendations?

Thanks for your help.

[JColvin]

Hi @Famartinez76,

I have moved your question to a more appropriate section of the Forum.

As a confirmation, in your main computer (it looks like you are using Windows), does the AD2 show up as a USB Serial Converter in the Windows Device Manager when you connect it?

I personally haven't seen this error before, so what I would try to do is reload the data in the EEPROM since it appears that the AD2 is properly getting power from the host computer. You can do this by pressing Alt+F11 on the Device Manger screen of the WaveForms software and then clicking on the "My device is not listed" button that appears at the top to find your device and re-program it. As Attila recommends latter on in this thread, don't do this if your device is already correctly recognized.

If this does not resolve the problem though, I will need to pass you off to @attila who is much more familiar with the WaveForms software.

Thanks,
JColvin

 

[attila]

Hi @Famartinez76

Please do not try to reprogram the EEPROM, since it will not solve the problem you are facing.
The error indicates that the ID of the internal ADC IC is not read correctly.
I will try to look into this, what could cause such malfunction.

[attila]

Hi @JColvin

The FTDI EEPROM reprogramming is only and only needed when the device is not detected/recognized by the software (Adept, WaveForms, Xilinx SDK...). This happens when the content (Digilent ID, SN) was erased by another application like FTProg.
Unneeded reprogramming could lead to missprogramming the device, like programming AD as AD2 and we end up with more hassle to solve...

[JColvin]

Hi @attila,

Thank you for the information; I updated my first post to reflect this.

[attila]

Hi @Famartinez76

The software you received in private message handles the error as warning.
You can give it a try to see if despite the wrong IC ID it is working. Invalid ID could indicate damaged IC, but generally these are just 0s or 1s, 0x00 or 0xFF
Let us know what you find.

[Famartinez76]

Hi.  It is shown in windows as a USB serial converter.  Sorry for taking some time to answer.  My job keeps me very busy  i will give it a try to the SW thank you so much for your help.

[Famartinez76]

I just gave it a try.  With that test SW, it now displays the following.

[attila]

Hi @Famartinez76

Unfortunately not only the ID verification fails but further problems are detected, so it looks like the Scope ADC in the device is damaged.

[Famartinez76]

Thanks for your help guys. Is there any way for me to fix it? Any repair shop?  Or do you think I should be able to order the damaged IC and fix it myself? 

[JColvin]

Hi @Famartinez76,

Depending on when you purchased the AD2, there may be a repair or replacement option for you. I have sent you a PM about this.

Thanks,
JColvin