• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 32 subscribers
  • Views 1163 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.

Recovering a "Locked" microcontroller from uvision 4 IDE

Daniele Guidi
Prodigy 80 points
Other Parts Discussed in Thread: LMFLASHPROGRAMMER, EK-TM4C123GXL, SEGGER

Hi,

for a new project, we are planning to use the TM4C1290 microcontroller. For the development and the debugging of application code, we will use the uvision 4 IDE and the ulink 2 as USB to JTAG debugger both from KEIL. I have a question about the recovering sequence described in the datasheet (document SPMS429B) chapter 4.3.4.3, page 207.

Is there any way to recover a locked microcontroller using the IDE and the debugger above indicated? Can you please explain me the sequence to be done?

We will do the same question also to KEIL support service but, maybe, you already know the answer.

My request comes from mass production needs. If, for any reason, the microcontroller gets locked at the end of line, I need the possibility to recover the part; on the board, there is the JTAG connector. 

If, with our tools, is not possible to recover the part, do you know if there are some other tools (maybe from texas instruments) to recover the microcontroller throug the jtag connector?

Tank you. Best regards.

Daniele

  • 0
    TI__Guru**** 244380 points
    Hello Daniele,

    Look at Issue #3 in the post

    e2e.ti.com/.../374640

    You would need to Wire a LaunchPad for TM4C123 to your board for unlocking.

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Intellectual 840 points
    Amit,
    I'm also interested in which JTAG tools can be used for "Recovering a 'Locked' Microcontroller" (SPMS440B Sec. 4.3.4.3.) Please provide details on "wiring a LaunchPad for TM4C123 to your board for unlocking". I don't see anything about that in Issue #3 of your other post.
  • 0 in reply to henlee
    TI__Guru**** 244380 points
    Hello Henlee,

    Please search the TM4C Forum. I have on numerous occassion put up an image which shows how to wire a EK-TM4C123GXL to another TM4C device and then use LMFlashProgrammer to unlock the target TM4C device.

    Regards
    Amit
  • 0
    Guru 27665 points

    Consider also the commercial JTAG suppliers.  IIRC Segger claims to support unlocking (it would be worth asking).

    No offense to Amit's drawings but a solid commercial tool is preferable to something cobbled together with wire-wrap wire as far as I'm concerned.

    Robert

  • 0 in reply to Robert Adsett
    TI__Guru**** 244380 points
    Hello Robert

    None taken :-). And I agree too. Having the same in one solid HW+SW combo is any day superior.

    Regards
    Amit
  • 0
    Guru 27665 points
    Another thing to keep in mind. It may be cheaper to throw the locked board out. Consider if it happens in one board out of a thousand and the board cost $100 to make then throwing it out is a cost of $0.10 per board.

    To recover the board you need to budget for tools that may sit idle and training and re-testing. Also the time to recover the boards. The hidden costs add up pretty quickly.

    Robert
  • 0 in reply to Robert Adsett
    Intellectual 840 points
    This is a new TM4C129 design. There are only 2 boards. I'll look through the DK-TM4C129X manual and see if I can figure out how to connect its ICDI to our board.
  • 0 in reply to henlee
    Guru 27665 points
    You did say it was a mass production issue, that implies to me a lot more than 2 boards.

    I'm not sure I'd worry about it at all, I've not had a board lock. OTOH I don't attempt to re-use the JTAG pins either.

    Robert
  • 0 in reply to Robert Adsett
    Intellectual 840 points
    That was the original poster, not me. I'm trying to recover one of our new boards which is bricked.