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

CCS/RM42L432: LAUNCHXL RM42 EVAL and RM42L432

Lloyd Allen
Prodigy 30 points
Part Number: RM42L432

Tool/software: Code Composer Studio

enabling the ESM (Error Signaling Module) on the LAUNCHXL RM42 EVAL running the RM42L432 MCU caused the ESM to be latched. Once latched resetting the target does not remove the error; indicated by the Red LED on the target EVAL bd. Can't remove the ESM error because the host PC can't connect to the target while the error persists. 

The ESM ERROR is apparently latched internally and does not respond to resets. If anyone knows how to remove the ESM device error, please reply.

Lloyd Allen

SMT ENGINEERING

work;    920.954.8324

cell;      318.719.2927

  • 0
    TI__Guru 65520 points

    Lloyd,

    ESM errors will persist through warm reset and need to be cleared by the CPU,  but not through a power on reset.

    If you have an ERROR LED on even after power cycling then you have a source of error that persists through the power cycle, but

    it is actually detected again and indicated again after each cycle.  This sounds likely too if you also are having a difficulty connecting to the MCU.

    Sometimes putting particularly bad code in the Flash can cause this because the flash contents persist and the part can execute the bad code

    very quickly after startup to sometimes make it difficult to just connect JTAG again.

    We used to refer to this as 'bricking' the EVMs or HDKs but it's not really that bad just a little trickier to get control of the CPU again.
    There are some instructions on the forum I think for the unbrick but would need to search.

  • 0
    TI__Guru 59540 points
    Hello Lloyd,

    As Anthony mentioned, it may be that you have entered a very tight loop in your software and are simply unable to break in via JTAG. In this thread, a similar issue is discussed with several ways that could potentially be used catch the program before the problematic code begins execution.

    e2e.ti.com/.../1918205