RM57 HDK does not work

Hi Wonjae,

  I'm able to also see that the LED turned on when the debugger is connected to the target. When the LED is turned on, my ESM status registers shows that there is a CPU compare error. Please look at ESM Stat2 register to see if you are getting a value of 0x00000004. For my case, the reason for the error is that the debugger operations place the CPU in a halting debug state where the code execution is halted. Since the halting debug events are asynchronous, there is a possibility for debug requests to cause loss of lock. In RM48 type of devices, the CCM module will disable the compare between the two CPUs' outputs upon detection that the CPU is in the halting debug state. The signal that indicates the CPU is in debug state is broadcasted to the rest of the system. However, in RM57 device, the signal that indicates the CPU is in debug state is first connected to CTI (Cross Trigger Interface) module. The CTI debug architecture in RM57 allows a programmable triggering capability that enables the CPU's halting request to propagate to certain modules but not to others at user's choice. However, by default after reset, the CTI module is in a disable state. This means that when the CPU is in the halting debug state, the signal that indicates as such is blocked at the CTI module. Therefore, the rest of the system including the CCM module does not know the CPU is in a halting debug state. The CCM will continue to compare while the CPU is in debug state. As mentioned earlier, the two CPU could be out of lockstep when in debug state. We will need to clarify this behavior in our next errata. Once you clear the LED, it will not have CPU compare error anymore.

If you run into the situation where you see the LED right after you connect to the target, please clear the LED by writing 0x5 to the Error Key (ESMEKR) register. In your case, you might have started to perform some program/erase operation to the flash. The flash loader will perform a debugger reset to the target. This reset is like a system reset which actually resets some of the ESM's internal registers. When this happens, you can not clear the LED by writing 0x5. You either need to go through a power up reset to clear the LED or by first writing 0xA to the ESMEKR register followed by another write of non 0xA value such as 0x0 to the ESMEKR register.

For your Demo problem, could you elaborate what errors you are getting. Could you download the Demo from the below link http://www.ti.com/tool/hercules_safety_mcu_demos again and try to reflash the HDK with the Demo software?

Hi Wonjae,

  I will try to send you the uniflash privately.