• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 87 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR2944: in CCS debug mode,dsp running abnormal

wu qiang
Prodigy 240 points
Part Number: AWR2944

Tool/software:

SDK version 4,4

I ported the tdmdemo to a ccs project.When I run project and want to get adcdata by debug mode,some thing strange happen:

It seems that there is a problem inside the DPC_ObjectDetection_execute interface of the DSP. After the log on Line 937 is output, the subsequent log is gone, and the DSP core will not run in the future, but the CCS shows that the DSP is still running. Status.
I also hit a breakpoint to see that the two member callback functions of processCallBack are also null pointers, which do not match expectations. If you continue to debug in a single step at the breakpoint, you will directly exit the current call stack, which looks like the stack has completely collapsed. Except for printing other code without modification, the compiled appimage is also running normally.
What might be the cause of the problem?

  • 0
    TI__Mastermind 20050 points

    Hi,

    I see there are multiple debug logs in the console. Printing multiple logs will cause delay in the execution of application. Due to the additional delay, application flow might break at some point.

    Also ensure there is no delay or breakpoint before DPU_RangeProcHWA_Process. Range processing is performed during the active frame time.

    Regards,

    Samhitha