TMDX570LC43HDK: nERROR LED always on after PORRST

Hi Johan,

This behavior may be caused by the HW bug described in DEVICE#56 in device Errata. You can clear the error by writing 0x5 first, then 0x00 to ESMEKR register.

DEVICE#56 nERROR assertion on debugger connect
Severity 4-Low
Expected Behavior: No errors should be detected when connecting to the device by JTAG
Issue: Sometimes a CPU compare error (ESM Group 2 channel 2) is generated when the debugger connects to device.
Condition: Upon a debugger initially connecting to the device.
Implication(s): The nError pin will toggle upon initial connection with the debugger.
Workaround(s): Clear the nERROR by writing 0x5 to the ESMEKR key register in the ESM module and ignore the nERROR pin toggle which happens immediately upon the debugger connecting.

Hi,
Correct me if I'm wrong, but this happens even if I don't have any mini-USB connected on the development board, so I would expect that there is no debugger connected to the board at this time, right ?
Thank you for your help

You are absolutely correct. Is there any code programmed to the device before? The LED will be turned on when there is an error on the channel of ESM group 2 and 3.

The ESM (Error Signaling Module) monitors on-chip device errors and determines whether an interrupt or external Error pin/ball (nERROR) is triggered when a fault is detected.

Please connect JTAG to the device, and check ESM status registers.

CCS-->View-->Registers-->ESM-->stat2  and stat3 and shdwdtat2

Hi,
Here are the two configurations I am having when the MCU is reaching the main() function call:
1: 
2: 
Currently, there is only an empty main function.

I am struggling to find more information about the ESM errors that can occur, could you share with me the reference document for that ?

Hello,

The table 6-45 in device datasheet has detailed description:

Bit 3 of Stat1 indicates: Cortex-R5F Core - All fatal bus error events. [Commonly caused by improper or incomplete ECC values in Flash.]

Actually, after I reprogrammed the chip with other programs, the issue is back, even when I am using the same program I had no issue with before. Same error with the Bit 3 of Stat2. Would you have some input to correct that ?