• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 1445 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.

Unlock procedure EK-TM4C123GXL

Johannes Seifert
Prodigy 30 points
Other Parts Discussed in Thread: UNIFLASH, EK-TM4C123GXL, SEGGER

Hello I cannot  unlock  for my EK-TM4C123GXL board despite it is recognized in the device manager and in the shell:  ls /dev/serial/by-id: usb-Texas_Instruments_In-Circuit_Debug_Interface_0E21058E-if00. uniflash doesn't show the unlock topic and in LM flash programmer the procedure doesn't change anything, still getting error: CORTEX_M4_0: Error connecting to the target... is the board damaged? thx for help

  • 0
    TI__Guru 72500 points

    Just to double check your connections, can you verify your USB cable is connected as shown, with the select switch in the "Debug" position, that is to the the right?

    You should see this in the device manager:

    This picture is from a Windows 7 machine. What operating system are you using? Is the Launchpad new, or one that may have been previously programmed?

  • 0 in reply to Bob Crosby
    Prodigy 30 points
    Hi yes the launchpad is connected that way... I'm using windows 10 and ubuntu 16.04. LTS and can see the stellaris ICDI in the device manager that way, the launchpad was programmed before and worked without failure until a few days ago. i didn't upload new code that could cause the failure, i used the code as before just tried to test a not working connection to a motor driver... uniflash and lm flash prorammer always show "cannot connect to target" after the unlock procedure...
  • 0 in reply to Johannes Seifert
    TI__Guru 72500 points
    Unfortunately that does sound like the part was damaged.
  • 0 in reply to Bob Crosby
    Prodigy 30 points

    Hi That's bad.. despite of all thx!

  • 0 in reply to Johannes Seifert
    Guru 117855 points

    May I note that while you've suffered "misfortune" ... "All may not be as bad - as thought."

    Our findings - working w/well over 100 client-users of TM4C (and past LM3S, LX4F) - is that RARELY are (BOTH) the ICDI MCU and User/Target MCU (again both) harmed. Under the conditions you note - it seems (most) likely that the ICDI MCU has suffered - which means - that if care is taken - there's a reasonable chance that the "User/Target MCU" has escaped damage.

    In such case - it is suggested that you "Sever the connections" between ICDI and Target MCU. You will then need to implement the means to introduce, "other than the board's ICDI MCU" - to program & debug. Firm/I "avoid the ICDI" for "just this reason" - we employ a "J-Link" (from Segger) and introduce the J-Link signals (JTAG or SWD) via an, "added, 7 pin header" located just beneath the ICDI MCU.

    Staff reports having done such - more than 10x - with total success! (they ARE skilled - and (perhaps) lucky, too...) Beats "trashing the board" - I'd say...   And - should you acquire a "J-Link" @ "Educational Discount" - your board is most likely to "outperform" the (departed) ICDI - perhaps leading to more such, ICDI dispatchings!     (note that I am NOT encouraging such action...)