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.

AM263P4-Q1: Debugging using XDS110 Debug Probe - Deadlock Issue after Restart/CPU Reset/System Reset - Start debugging in a running system without reset

Part Number: AM263P4-Q1
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi,

I face some issues when debugging using XDS110 Debug Probe and the following setup:

Flash: IS25LX064 (same as at eval boards just with 64mb ram instead of 256mb)
As SW tools I am using:
CCS 12.8.1.00005 & 20.2.0.12__1.8.0
SDK 10_00_00_35
Uniflash 9.2.0.5300

Bootmode: Octal Read Mode

I basically have four Debug related questions:

  1. Let's suppose I've got a running MCU, and want to check its state with the debug probe while it is running. Can I do that without resetting the device? When I start a debug session it either starts at the beginning of the main. I've followed this guide so far: How to debug a program without a project in Code Composer Studio 
  2. Now when I launch the debugging session as in the linked video above, I'll face the following issues:
    1. When I use the Restart or CPU Reset I will be stuck in the HwiP as shown here:

    2. When I use the System Reset I will be stuck in the Core stack as shown here:
    3. So basically my question is, how can I use Restart/CPU Reset/System Reset without being stuck in some kind of deadlock and without restarting the debug session?
  3. What is the difference between Restart, CPU Reset and System Reset?
  4. How to reliably start a debug session at the reset address instead of the beginning of the main function?

I'm facing the same issues with both stated versions of CCS.

Best regards
Norbert