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.

TM4C129XNCZAD: LMFlash hangs on Erasing when attempting download (continued)

Part Number: TM4C129XNCZAD

This question is a continuation of another which was closed when we determined we had to do a board turn to continue with the diagnosis.

Link to previous question: e2e.ti.com/.../2548977

I am trying use LMFlash to program our CPU by configuring the BOOTCFG register to enable LMFlash when a certain pin is asserted during reset.

We left off the last question having determined that RBIAS had to be tied to ground with a 4.7K resistor.

Now having a board with the resistor installed, I am attempting to download again.

Previously, LMFlash would hang with status showing 'Erasing' and eventually showing an error box with "**ERROR**: Failed to send download command!".

We are getting farther now.  The status goes through 'Erasing', transitions to 'Programming...0%" then "Programming...1%" before hanging.

It then presents either "**ERROR**: Failed to get status!" or  "**ERROR**: Failed to send packet!".

This behavior occurs either with a blank board or one that has been loaded with the BOOTCFG register programmed.

The flash does get erased to the point that it will no longer boot and has to be programmed via JTAG to get it running again.

  • After you get the error, connect with JTAG and read the contents of the flash. Is the beginning of the flash erased, still containing the original code, containing the start of the new code or containing garbage?
  • Right now, whenever I enter debug mode (press green bug) the program is automatically downloaded.
    How do I change it not to do that?
  • Hi Greg,

    One way is to delete the program load in project debug configuration tab, save the path to notepad. Alternatively uncheck load program on target connect in JTAG console tab during CCS debug, click save configuration for next time button.
  • I start a debug session from the "CCS Edit" perspective by doing "View", "Target Configurations" if that window is not already visible. Then I select a target configuration, usually one associated with a project from an example I imported. Then I right click on the target configuration file and choose "Launch Selected Configuration".

    In the debug window I right click on the "Stellaris In-Cricuit Debug Inferface ..." and select "Connect Target", or click the connect icon.

    At this point, I can examine memory locations. If I want to program and execute, I select "Run" then "Load".