• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 1286 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.

TM4C123BH6ZRB: TM4C123BH6ZRB (TIVA): Recovering a locked Microcontroller => JTAG-Interface does not response

Tobi
Intellectual 320 points
Part Number: TM4C123BH6ZRB
Other Parts Discussed in Thread: UNIFLASH

Hi,

I recovered a locked TIVA microcontroller via debug port unlock sequence (by I-Jet Trace in IAR Workbench for ARM)

(s. Manual p. 199: Performing a total of ten JTAG-to_SWD and SWD-to-JTAG swith sequences while holding the microcontroller in reset to restore BOOTCFG-Register).

After PowerON-Reset flashing via JTAG or SWD is no longer possible!!!

So could you please tell me if JTAG / SWD communication must be possible after unlocking sequence?

Or is ROM-bootloader the only way for flashing?

Thanks in advance,

Tobi

  • 0
    TI__Guru**** 182656 points
    HI,

    Do you remember what did you do prior to the device being locked?

    If you have successfully gone through the unlock sequence then the JTAG communication should be possible. The question is how do you know you have unlocked the device successfully?

    Do you have other debug probe such as XDS100, XDS110 or XDS200? If you have one, then you can use the Uniflash to unlock the device.

    Do you have a TM4C123 or TM4C129 launchpad? If you have one, then you can use the the launchpad which contains the ICDI debug probe to debug your board and you can use the LM Flash Programmer to unlock the device.

    See section 5.3 and 4.6 in this app note for details.
    www.ti.com/.../spma075.pdf
  • 0 in reply to Charles Tsai
    TI__Guru**** 182656 points

    Hi Tobi,
    I have not heard back from you. I assume you are able to resolve the issue. I will close the thread for now. If you have new questions you can open a new thread or reply back to this thread with some comments if the issue persists.