• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 30 subscribers
  • Views 521 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.

Need help with locked LM4F232

Stefan Ineichen
Prodigy 20 points


Hi everyone,

I've accidentally changed a pin (PC0) belonging to the JTAG interface to be used as a GPIO on my evaluation kit (http://www.ti.com/tool/ek-lm4f232) with a LX4F232H5QD chip.
Now I'm locked out. I tried to unlock it by using "Debug Port Unlock" in the LM Flash Programmer utility.
For this procedure I connected pin 10 of the JTAG connector to ground.
In the LM Flash Programmer I've selected "Fury, DustDevil, and Blizzard Classes".

Nothing helps, all I get is: "**ERROR**: Failed to unlock connected device!"

I also tried using a XDS100v2 instead of the onboard ICDI interface.

Can anybody help?

Thank you,
Stefan

  • 0
    Guru 117855 points

    Cross-post!   Note - original post stated Sandstorm class device - has subsequently been changed...  Poster at least is consistent - having locked himself now out of 2 Stellaris.

    LX4 devices are, "Blizzard" - should select that using LMI Flash Programmer and follow exact Unlock Procedure...

    http://e2e.ti.com/support/microcontrollers/stellaris_arm_cortex-m3_microcontroller/f/471/t/225049.aspx

    Response w/in reference...

  • 0 in reply to cb1_mobile
    Prodigy 20 points

    Sounds like a good idea to halt the MCU, unfortunately I don't think it will help in my case as I do the configuration of GPIOs right at the beginning.

    Any other ideas?

  • 0 in reply to Stefan Ineichen
    Guru 47900 points

    Still unclear if yours is an LX4F or LM3S-Sandstorm.  Those early class (Sandstorm) parts - as I understand - did not include any facility to, "unlock."  If instead - as your Subject now states - yours is LX4F - the normal Utility "unlock" w/in the flash programmer should quickly restore.

    Theory (and we/others have done this w/success) is to force the Sandstorm MCU to "hang" prior to reaching the errant JTAG instruction.  If that instruction is the earliest - you may well have to remove/replace that MCU. 

    Prevention trumps cure dept: "written notice - re: Port_C and Sandstorm - is prominent @ all our workstations..."  

  • 0 in reply to cb1
    Prodigy 20 points

    It's an LX4F. I just wrote to customer service about the problem. If they're able to help I'll post the solution here.

  • 0 in reply to Stefan Ineichen
    Guru 47900 points

    Stefan Ineichen said:
    I'll post the solution here.

    Such is always appreciated - will likely return you faster and more considered response on future posts.

    Blizzard class does appear on newer LMI Flash Programmer Tool.  Suggest that you upgrade to newest version - select Blizzard and attempt unlock procedure.  Suppose that if yours is lunchpad or eval - possibly "unlock" not fully implemented - but have yet to encounter dreaded, "lock-out" on LX4F family...

    Do post end results and good luck...

  • 0 in reply to cb1
    Prodigy 20 points

    Thanks for the suggestion.
    The blizzard classes already appeared in the LM Flash Programmer version I had installed.
    I've updated to the newest version regardless and the problem is still the same.
    Hopefully the people from customer support answer quick...