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.

Debug CM3 core when emulator is suspended

Hi,

In 3.2 TI SDK kernel once MPU is suspended we are not able to connect the emulator to the CM3 core. Is this an expected behavior or we need to change any settings in the CCS debugger ?  We would like to debug how CM3  core handles the GPIO0 interrupt and wakes up the MPU. 

Incase we cannot connect debugger to CM3 core when MPU is suspended. Can we driver UART0 directly from CM3 core to print debug messages?

Please find the CCS error message mentioned below,

CS_DAP_M3: Error: (Error -275 @ 0xFFFFFEED) The attempt to poll a target device exceeded its timeout limit. The utility or debugger has requested that a target device be repeatedly accessed for a specific data or status value. This has failed because the built-in limit for the maximum number of attempts when polling the JTAG scan-path has been exceeded. (Emulation package 5.0.623.0)

M3_wakeupSS_0: Error: (Error -1045 @ 0xFFFFFEED) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.623.0)
CS_DAP_M3: Error: (Error -5002 @ 0xFFFFEC76) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.623.0)
M3_wakeupSS_0: Trouble Halting Target CPU: (Error -1044 @ 0xFFFFEC76) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.623.0)

Regards

Yogavanan M