This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TM4C129XNCZAD: device not recognised by windows 10 - Unknown USB device (Invalid Configuration Descriptor)

Part Number: TM4C129XNCZAD
Other Parts Discussed in Thread: EK-TM4C1294XL

i have some boaurd that were manufacturered over a year ago and never used - we no longer have access to the software / hardware team who developed them and about half the boards (35) are not recognised by windows with the message above.

the other boards all plug in - are recognised - get a firmware update by the setup application and just work ..... and then show up as HIDs

can someone point me at a solution please.

cheers

  • Hi,

    i have some boaurd that were manufacturered over a year ago and never used - we no longer have access to the software / hardware team who developed them and about half the boards (35) are not recognised by windows with the message above.

    The error message "device not recognized by windows 10 - Unknown USB device (Invalid Configuration Descriptor)" seems to suggest it fails the USB enumeration. During enumeration, the device is supposed to send to the host the device descriptor, configuration descriptor, interface descriptor and etc so the host knows what Windows driver to use. 

     Do you know if the failure boards and good boards all supposed to have the same firmware in them? If they have the same firmware then it is possible a board level problem. Can you do a ABA swap test? Swap the failure MCU to the good board and swap the good MCU to the bad board? Does the good board continue to work? Does the failure board continue to fail?

     If after the swap the good board continues to work and the failure board continues fail then it is not a MCU problem. You need to investigate the board.  

     If after the swap the good board does not work anymore or the failure board becomes working again then it is a MCU problem. If this is the case, I will suggest you reprogram the firmware via JTAG interface. I supposed your board have JTAG connector and you have access to the IDE and the firmware.

     Of course, you can reprogram the the failure MCU before doing the swap and see if it works. That will be the first step I will do. 

  • Thanks for the quick reply Charles. i cant swap the MCU as its soldered to the board - i do have a TIVA development board but no software (or experience) 

    i expected all boards to be the same - when initially plugged in to a PC they appear in device manager as tivaware stellar firmware updater and then our app pushes the firmware to it - so maybe these board failed in that process and are in an unknown state.

    i wil look into setting up the development kit on a PC and seeing if i can get some software. hopefuly i can "blank" the units using the jtag - and start again.

  • Hi Adrian,

    There is a USB DFU example at C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c1294xl\boot_demo_usb. You can load this example through JTAG interface and then run it. Once running, it will enumerate as a DFU device. On the Windows device manager you should see below image.  You can use your own PC app to download your firmware or use C:\Program Files (x86)\Texas Instruments\Tiva\usb_examples\dfuprog utility to download your firmware.

  • Thanks Charles, i will get teh development board sorted out with software and giv ethat a go.

    Thsnka again.

  • ok, let us know your findings.