Start the receive of ETB-based trace automatically.

Yulin,

When the device is powered off CCSv5 cannot be connected to it; therefore you can't collect trace data at this point. Even if ETB could be activated at power up time, the ETB data collection is circular and therefore previous data would be overwritten when the trace buffer reached its limit.

What people usually do is insert a forever loop at the very beginning of the boot code, which allows time to connect CCS to the device and then debug the boot process. That would also allow connecting to the ETB to collect trace data.

Hope this helps,

Rafael

Rafael,

Yes, IF this is a issue that occurs every time after the device is released from reset.

However, the issue (crashed somewhere in UBL) I faced happens less than 1 in 100 rounds of reset stability test.
(DM365 triggers a HW reset after it leaves UBL and enters the test code)