CCS/AM5728: Debugging DSP cores using CCS

chandrashekhar S

Part Number: AM5728

Tool/software: Code Composer Studio

Hello everyone,

I'm using GLSDK-7.04 setup. I'm trying to debug DSP cores from CCS but when i load the symbols i'm getting following error.

procedure i followed is:

i) Launch the debugger by providing .ccxml file path.

ii) I will connect to DSP cores.

iii) once the connection is successful i will load the symbols.

Please help me out to solve this problem ?

over 7 years ago

0 Ki over 7 years ago

TI__Guru**** 475261 points

Hello,
Your screenshot did not get posted properly. Can you try again?

Thanks
ki

0 chandrashekhar S over 7 years ago in reply to Ki

Intellectual 350 points

Hi,

I updated the post, please go through it.

0 Ki over 7 years ago in reply to chandrashekhar S

TI__Guru**** 475261 points

Thanks. That is not really an error but more of a message. For more details, please see:
processors.wiki.ti.com/.../Debug_Handbook_for_CCS

Thanks
ki

0 chandrashekhar S over 7 years ago in reply to Ki

Intellectual 350 points

Hello,

Thanks for your suggestion and I gone through that link, they are saying like we can ignore such kind of messages(The message itself is harmless and can be ignored).

We added a Break-point inside while loop in mainProcessCommand() function, But the Break-point is not hitting. We resume that DSP operation but it is starting from begging(main) instead of continuing its operation from where it is halted.

The calling sequence of mainProcessCommand() function as follows.

main() -> RCP_MAIN() -> mainProcessCommand()

One more thing, After connecting to the Target Board the DSP execution was halted/suspended but after disconnecting, the DSP is not resuming its operation ?

I don't know what went wrong ?

Regards,

chandrashekhar

0 Ki over 7 years ago in reply to chandrashekhar S

TI__Guru**** 475261 points

chandrashekhar S said:
We added a Break-point inside while loop in mainProcessCommand() function, But the Break-point is not hitting.

The reasons why a breakpoint is not being triggered is usually one of the below:

- the instruction that the breakpoint is set is not being reached

- a standard Eclipse breakpoint is being set instead of a CCS breakpoint (https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/715288/2637149#2637149)

- the debugger is configured to skip all breakpoints (see: https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/684276/2520879#2520879)

chandrashekhar S said:
One more thing, After connecting to the Target Board the DSP execution was halted/suspended but after disconnecting, the DSP is not resuming its operation ?

The target may not auto-resume execution upon disconnect. The behavior of this depends on the target and debug probe use. In your case, try manually resuming execution before disconnecting

Thanks

Code Composer Studio™︎

Code Composer Studio forum

CCS/AM5728: Debugging DSP cores using CCS