CC2340R5: How to check restart reason using CCS

YW Lin

Part Number: CC2340R5

Hi TI members,

Below is my building environment:

Software	Version
Code Composer Studio	12.4.0.202306011800
SimpleLink SDK	7.20.1.10
XDCtools	3.62.1.16_core

We have been developing a project with data_stream and ptm functioning.

Recently, we observed our device constantly restarted due to unknown reason.

We would like to check the reason within CCS, but we can only see below message once device got restarted:

Cortex_M0P: JTAG Communication Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD request. Clear the error the condition, and try the SWD request again. (Emulation package 9.12.0.00150)

How can we use CCS debug features to check this issue?

Thanks.

BR,

YuWen

over 2 years ago

0 Ryan Brown1 over 2 years ago

TI__Guru**** 223677 points

Hi YuWen,

You can save the PMCTLGetResetReason return in a variable, launch a target configuration in CCS to start a debug session with the device, and load the symbols of your project to locate and obtain the variable in question. Or you can output the aforementioned API return to a print log terminal or UART interface.

Regards,
Ryan

0 YW Lin over 2 years ago in reply to Ryan Brown1

Intellectual 540 points

Dear Sir,

Thanks for the advice.

I'm still a bit curious about how shall we use the API PMCTLGetResetReason.

I supposed our program was restarted while running through some functions in app parts, but not sure what exact function it was running in.

Should I put the PMCTLGetResetReason API in a new thread and keep checking it in the background

or where would you recommend us to call it while we weren't quite sure of when the restart would take place?

Thanks.

BR,

YuWen

0 Ryan Brown1 over 2 years ago in reply to YW Lin

TI__Guru**** 223677 points

PMCTLGetResetReason will return the following sources from the last reset performed:

If you desire further granularity or debugging, you must utilize debug tools to what occurs in your code during runtime which causes the restart. You can use while forever loop traps, debug output hints, and step-by-step modifications from working code to further determine the issue.

Regards,
Ryan

0 YW Lin over 2 years ago in reply to Ryan Brown1

Intellectual 540 points

Dear Sir,

I would like to print the reset reason to the LogSinkBuf, but it seemed that I could only print the number of the result of PMCTLGetResetReason().
Currently, I wrote somthing like this to see the output of reset reason:

uint32_t reset_Reason = NULL;
reset_Reason = PMCTLGetResetReason();

Log_printf(LogModule_App1, Log_DEBUG, "%d", reset_Reason);

I tried to print other known reset reasons like "PMCTL_RESET_WATCHDOG", and I saw it showed 54.

Where should I refer to the number corresponding to the reset reason?

Or how to print the exact sring (like the PMCTL_RESET_WATCHDOG) in the LogSinkBuf?

Thanks.

BR,

YuWen

0 Ryan Brown1 over 2 years ago in reply to YW Lin

TI__Guru**** 223677 points

Decimal 54 is 0x36 which is (PMCTL_RSTSTA_SYSSRC_WDTEV | PMCTL_RSTSTA_RESETSRC_SYSRESET) = (0x30 + 0x06) = PMCTL_RESET_WATCHDOG. All of this is deduced from the pmctl API and hw_pmctl definitions. Thus, in order to accomplish your application requirement you will need to do the same for all PMCTL_* definitions create a table which converts decimal values to their string PMCTL_* representation and displays them with the Log function accordingly.

Regards,
Ryan

Bluetooth®︎

Bluetooth forum

CC2340R5: How to check restart reason using CCS