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.

CCS/TMS320F28027: real time debug issue

Part Number: TMS320F28027


Tool/software: Code Composer Studio

Hi, I'm using F28027 launchpad and CCS7.2 to do some test about the real time debug under the guidance of workshop of CCS5(C2000). (CCS7 workshop does not have anything about real time debug).

1. In the training material, it's said that by enabling real time debug mode, we can access to memory and registers while the processor is running. Traditional debugging requires the processor to be completely halted to access memory and registers

But I can also access to memory and registers while the processor is running even with the traditional debugging. I say this because when I run the code, the register's value is changing when I enable the continuous refresh of the register window. The same applies to variables in memory browser when I run the code in traditional debugging mode.

I'm using Example_2802xEPwmRealTimeInt project in F2802x example project folder, the variable EPwm1TimerIntCount, and register EPwm1Regs.TBCTR is changing the same way no matter in traditional debug mode or real time debug mode.

2. It's said in SPRU430F: In the real-time emulation mode, if DBGM = 1, the CPU ignores halt requests or hardware breakpoints until DBGM is cleared. DBGM does not prevent the CPU from halting at a software breakpoint.

But when I insert a software breakpoint in an interrupt in real time debugging mode, CCS ask me to switch to rude real time debug mode. Only by entering rude real time debug mode, the code can halt at the breakpoint I insert in the interrupt.

3.  It's said in SPRU430F: In the real-time emulation mode, if DBGM = 1, the CPU ignores halt requests or hardware breakpoints until DBGM is cleared. DBGM does not prevent the CPU from halting at a software breakpoint.

Halt request could be clicking the suspend icon in the tool bar, right? So halt means the same as suspend when debugging with CCS, right?

4. I cannot change the value of DBGM in ST1 register by modifying its value in register window in real time debug mode, no matter the code is suspended or not. So I can only change it's value by adding code lilke "asm(" setc DBGM")" in the code, right? By adding such code I can make part of the program code time critical and not halted by the debugger, right?

Thanks in advance.