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

EK-TM4C1294XL launchpad cannot flash

Glenn Edgar
Prodigy 250 points
Other Parts Discussed in Thread: EK-TM4C1294XL, UNIFLASH, LMFLASHPROGRAMMER

1.  I started with the EK-TM4C1294XL launchpad and added USB host program.  Everything ok.

2. From step #1 I added EEPROM support.  Everything ok.

3. From step #2 I added Watchdog support.  Problem.  Once I loaded the program the launchpad board became non responsive.  Could not reflash the board even with the stand alone flash programmer.  The launchpad board is not connected to any hardware except for usb flash drive.  

4.  Two Questions:

A.  Is it possible to recover the board.

B.  What are the senarios which this problem occurs.  ( I have already bricked two boards.)  

Thanks for help.

  • 0
    Guru 27285 points

    Hi Glenn,
    point A, did you checked unbricking procedure using LMFLash utility?
    B is your program using JTAG pin as GPIO?

     Not having access of your source code nor accessing your lab to see what are you doing we cannot provide diagnose what happen.

  • 0 in reply to Roberto Romano
    Prodigy 250 points
    I tried to use the LMFlash Utility. Did not work.

    Not using the JTAG pin as GPIO , at least not on purpose.

    Will send source code shortly
  • 0 in reply to Glenn Edgar
    Guru 27285 points
    LmFlash Unbrick has a procedure did you followed as or also try uniflash too it can unbrick processor too.
    http://processors.wiki.ti.com/index.php/Category:CCS_UniFlash
  • 0 in reply to Glenn Edgar
    TI__Guru**** 244400 points
    Hello Glenn,

    There are specific steps to run the LMFlashProgrammer for Unlock Sequence

    1. Unpower the board and press reset
    2. Power the board but do not release the reset
    3. Run the unlock sequence by the "dialog box"
    4. Power Cycle the board and then do a Flash Erase Check

    Clearly there may be more to the s/w than the points mentioned. As an example some code may be "benign". However when adding the EEPROM and WD it may raise up an known errata issue. BTW, did you check the errata document. There are some conditions for the device to brick-up and we have successfully recovered the device.

    Also what is the revision of the device? You can check that by looking at the device part number which should end with a I1, I2 or I3.

    Regards
    Amit
  • 0 in reply to Roberto Romano
    Prodigy 250 points

    I tried the lmflash utility with erase option no luck.

    I noticed that there was an unlock option.  I tried the unlock option.  This solve the problem.  Somehow the processor got into a locked state.

    Thanks for your input as your suggestions helped me solve my problem.

  • 0 in reply to Glenn Edgar
    Guru 117855 points

    Glenn Edgar said:
    suggestions helped me solve my problem.

    Perhaps not - would it not prove useful for you to carefully/critically review those (most recent) code changes - which (likely) caused your plight?

    You've cured the "symptom" (locked MCU) yet "not" (yet) identified the cause - and minus that finding - issue may revisit...

    Usual suspects include improper handling of JTAG port (port C) and/or SystemClock not matching your external xtal - or mistaken parameters etc...

    KISS dictates that you introduce just ONE code change at a time - carefully noting behavior - and keeping a "code log" so that the (errant) code block is spot-lighted...

    And... while "fresh" w/board recovery method - suggest that you employ same method to recover your 2nd board - (earlier) reported in similar distress...

     

  • 0 in reply to Amit Ashara
    Guru 27285 points

    Hi Amit, this, IMHO, has to be added on first post about issues.. I check if not in place too.

  • 0 in reply to Roberto Romano
    TI__Guru**** 244400 points
    Hello Roberto,

    Yes. It a part of the Issue #5 post...

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Guru 27285 points
    HI Amit, I checked but the page is pointing to (again IMHO) is not so close to unbricking and just report press tempest and not the full procedure, I think it is better copy the instruction you wrote here to section 5 to have at hand and not search for sparse information...
  • 0 in reply to Roberto Romano
    TI__Guru**** 244400 points
    Hello Roberto,

    Thanks again. Updated it...

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Guru 117855 points
    Is it not sufficient - as one poster here (so often) suggests - to, "Do a Search?"
  • 0 in reply to cb1_mobile
    Guru 27285 points
    Right.. One more important change to forum new face maybe REMOVE this fast replay.. it is not Facebook, and forever return to a good layout (OLD ONE TOO) of full editor now require double check it. Also ADD AGAIN CLEAN file insert and not media is confusing all us.
    On spare time also is worst question of messages aka private conversation not usable as new layout. AND GRAY AND CYAN !!!!!
    Do a search.. yes it was not so simple CB1, I have to be honest and some of our guru point come from when we like to be fresh .. I fell sometimes what happen here drive to that. Our level I think can be judged by what we do not how many answer we post.
    The worst I see here Amit is the only one of this forum!!!! It is too much friendly and prepared to all, we need have someone other, possibly one of new form designer, to attack as necessary.
    [Half fresh mode off]
    Amit thank again to improve usability to all us.