• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 392 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

EK-TM4C123GXL: Board Will Not Show Up in Device Manager

EK-TM4C123GXL: nothing showing in device manager after using dfuprog

Colin
Prodigy 120 points
Part Number: EK-TM4C123GXL

Hi. This is the second board I've "destroyed" by attempting to flash a program using DFU. After using dfuprog.exe to switch to DFU mode and then flashing a program, the device disappears from device manager and I can't do anything with the device. The device has power, but I cannot use dfuprog or LM Flash Programmer since the board is not showing up in device manager. Below are the steps I did at a command prompt before the device disappeared:

  1. typed "dfuprog.exe -e" and received a response that 1 device was found.
  2. typed "dfuprog.exe -m" and received "Switching to DFU mode".
  3. typed "dfuprog.exe -v -f program.bin -a -r"

After the above steps, the device disappeared from device manager. Again, this is the second board I've done this with. Please help. Thank you.

--Colin

  • 0
    TI__Guru**** 159325 points

    Hi Colin,

      The very first time you type dfuprog.ex -e, you should see two devices. Below is an example of what you should see. 

    As you can see from the above picture, there are two DFU-capable devices. The first one is the ICDI (In-Circuit Debug Interface) and the other is the Device Firmware Upgrade. You MUST be very careful that you select the correct device to perform the firmware upgrade because the ICDI is DFU-capable as well. By default the dfuprog.exe -m will select the first device which is the ICDI as in my case from the picture above. In my above picture the ICDI happens to be the first device. What likely happened is that you perform the firmware upgrade on the ICDI device instead. The ICDI is the on-board debug probe. Once the ICDI is erased and programmed with an incorrect firmware it lost its capability to function as a debug probe. In this case, you cannot connect to the target anymore. If you go to the Windows Device Manager, you will not see the ICDI anymore. That should confirm the theory.  

    If you see two devices, it is strongly recommended that you disconnect ICDI debug port from the PC, and power the board either with a 5V external power brick or any usb wall charger which is not plugged in your pc. This way, your PC is connected to the board only through USB OTG port.

    If IDCI debug port is disconnected from your PC, you should see only one device from dfuprog -e, and its index should be 0, and should be named as ``Device Firmware Upgrade''. If for any reason that you cannot provide the power to the board without connecting ICDI debug port to your PC,  please take careful note of the index for the device `Device Firmware Upgrade'', it could be 0 or 1, we will need this index number for the -m command.


    Entering the following command will switch this device into DFU mode and leave it ready to receive a new firmware image:

    dfuprog -i index -m</tt>

    After entering this command, you should notice that the device disconnects from the USB bus and reconnects again. Running dfuprog -e a
    second time will show that the device is now in DFU mode and ready to receive downloads. At this point, either LM Flash Programmer or dfuprog may be used to send a new application binary to the device.

       

  • 0 in reply to Charles Tsai
    Prodigy 120 points

    Hi Charles. Thank you for your reply. I did indeed program the ICDI device. Is there a way I can recover this board so that I can use the ICDI device again? Thank you.

  • 0 in reply to Colin
    TI__Guru**** 159325 points

    Hi Colin,

      As it is now in your case, the ICDI is not capable for DFU anymore. Unfortunately, there is no economical way to recover the ICDI. If you look at the back of the EK-TM4C123GXL board, on the side close to the ICDI chip you will see TC2050-IDC-NL. This is a connector to the ICDI. I did some Google search and the TC2050-IDC-NL connector will cost much more than buying another launchPad board. Even if you have the TC2050-IDC-NL, you will need an external debug probe and do some wire connection to the TC2050-IDC-NL. If this is done correctly you can program the ICDI firmware to the ICDI debug probe via the standard JTAG interface. I truly believe this is not worth your time and money. I've not done this myself and can't really support you in this approach. 

  • 0 in reply to Charles Tsai
    Guru 117850 points

    Hello Charles,

    Staff & I both rate your diagnosis here absolutely, 'Top Cabin!'

    It is wondered if this poster noted the, 'screen detail' which followed his keying in: dfuprog.ex -e?

    Or - perhaps more importantly - if the DFU's printed instructions properly alerted readers to, 'Key in: dfuprog.ex -e' and then read & well note this (very) critical detail?

    When any (potential) outcome proves 'so brutal' - high (even repeated) emphasis would be most welcome.     (And in this poster's case  - board saving!)

    If my group may - now may be an 'advantaged time' to migrate to a 'J-Link' JTAG/SWD Probe - which can SAVE BOTH of poster's boards!    (after slight board modification to accept it)    J-Link's are available at great discount via the 'educational version' (one does not have to 'pretend' to be a student or educator) - which is full powered & vendor agnostic - while accepting many different IDEs...