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.

TMS570LS3137: Safe Mode Transition for TMDSEMU560V2STM-UE

Genius 3610 points
Part Number: TMS570LS3137
Other Parts Discussed in Thread: TMDSEMU560V2STM-UE, , UNIFLASH

Hi experts,

My customer is currently using TMS570LS3137 and TMDSEMU560V2STM-UE (Spectrum Digital) and is experiencing an error.

While using the debugger, it went into what seems to be a safe mode and the debugger can no longer be connected properly.(We confirmed from the LED and Sd560v2Config.exe that it is in safe mode.)
At first, "Error screen No.1" was displayed, and after repeated reconnections, "Error screen No.2" was displayed. As a result of checking the Memory Browser in the state of error screen No. 1, "????" was was only displayed.

Error screen No.1

Error screen No.2

As for the XDS560 side, we are trying to recover from the safe mode based on the following information, so I would like to add the result later.
:software-dl.ti.com/.../emu_xds560v2.html

For the time being, please let me check the TMS570LS3137 side.

Q1: The message seems to say that the 0xF008015C area is corrupted. Is it possible that the read-only area is rewritten by the user program?

Q2: Is there any way to restore this area to its default value (factory value)?

Q3: The program uses "F021_API_CortexR4_BE_V3D16.lib (Ver. 2.01.01)" to access the flash memory, so it does not directly access 0xF008015C. Is there any possibility that the library will rewrite this memory?

I have checked the TRM(SPNU499C), and the address "TI OTP Bank0 Package and Memory Size Information" is an area that cannot be programmed or erased according to the reference manual "5.4 Memory Map". Therefore, we do not think it can be rewritten by using software or APIs, but it would be helpful if you could give us your opinion on the causal relationship between Q1, Q2, Q3 and this problem.

Also, if you have any information about similar cases or solutions to this problem, please share them with us.

Best regards,
O.H