• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 704 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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:

Unable to get Stellaris Launchpad recognized by PC

EK-TM4C123GXL: Launchpad Debug port doesn't get detected

Karthik Raghavan
Prodigy 20 points
Part Number: EK-TM4C123GXL

The debug usb port doesn't get detected on my PC after random program run. 

Used LM flash utility to unlock the debug port and tried to update the ICDI firmware,after which it stopped working totally. Any help on fixing this would be much appreciated.

Thanks in advance

Karthik

  • 0
    TI__Guru**** 190806 points
    Hi,
    Was it working before?
    If it was working before, do you remember what you might have changed to the program that resulted in not working anymore?
    When you said it stopped working totally, what do you really mean? Can you connect to the target? Do you see any lights on the board?
    Please follow the instructions in section 5.3 of this app notewww.ti.com/.../spma075.pdf to unlock the device. After the unlock, you will need to do some power cycles.
  • 0 in reply to Charles Tsai
    Prodigy 20 points

    Hi Charles,

    Please find my response below.

    Q:Was it working before?

    A: Yes it was working before.

    Q:If it was working before, do you remember what you might have changed to the program that resulted in not working anymore?

    A:Yes,  I suspect modification to port C pin  to be cause of the issue.

    Q:When you said it stopped working totally, what do you really mean?

    A: I tried to unlock the port once and was successful( according to the debug message), but it didn't actually unlocked it. Further I tried to update the firmware and after which the USB(stellaris ICDI) is not getting listed in the device manager.

    Q:Can you connect to the target? Do you see any lights on the board?

    A:  I see lights on board, But I could no longer connect to the target as it is not getting detected.

    Q: Please follow the instructions in section 5.3 of this app notewww.ti.com/.../spma075.pdf to unlock the device. After the unlock, you will need to do some power cycles.

    A: I have followed the steps under the section 5.3, but I get an error saying that the device couldn't be connected.Attached  the screenshot.

    Thanks

    Karthik

  • 0 in reply to Karthik Raghavan
    TI__Guru**** 190806 points
    Hi Karthik,
    You repurpose the JTAG pins (PC[3:0]) for GPIO and by doing so you lose the JTAG debug capability. Please avoid doing this in the future unless you have another means (i.e. bootloader to update your firmware via serial interface) and ways to debug your device.
    I have a few suggestions but they are not guaranteed t work.
    1. Follow section 4.7 of the app note I sent you. What it is is that you can use one LaunchPad to debug another LaunchPad. This capability is only feasible if you have another working LaunchPad lying around somewhere. Even better if you have another debug probes such as XDS100 or XDS200, JLink you can use these debug probes to debug your problem board.
    2. If you can successfully connect to the problem board using method mentioned in step 1 then try to do an unlock of the device and download a simple TivaWare example such as blinky. Verify that the LED is blinking.
    3. Try to reconnect to debug USB port of the problem LaunchPad. If you still have problem connecting then it confirms that the ICDI firmware is somehow corrupted. Normally you never need to update the ICDI firmware but for whatever reason that while you were doing so, the firmware was corrupted.
    4. If step 3 fails to connect then try to update the ICDI firware again. As I said you normally don't need to do update but since it is already corrupted it doesn't hurt to update the firmware again. Hopefully it may update again. There is no guarantee in this step.
    5. If step 4 doesn't work I will suggest you either continue with step 1 if you insist keeping the problem launchPad or just abandon the problem launchPad and continue with your working launchPad for development.