• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 1140 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.

CCS/IWR1642: Problem in setting the breakpoints while debugging the mmWave Demo of IWR1642

S. Bae
Intellectual 560 points

Part Number: IWR1642

Tool/software: Code Composer Studio

Hello, 

I am facing a troublesome in setting the breakpoints while debugging the mmWave Demo of IWR1642.

My environments are given below.

First I flashed xwr16xx_ccsdebug.bin in C:\ti\mmwave_sdk_01_01_00_02\packages\ti\utils\ccsdebug.

And I loaded and run two images "xwr16xx_mmw_mss.xer4f" and "xwr16xx_mmw_dss.xe674" built in CCS project.

The Demo runs normally and all the radar parameters are well configured.

The problem starts here.

Even though I set some breakpoints  in mss_main(), all the breakpoints are ignored. So I cannot investigate the code with a step-by-step.

I confirmed breakpoints in dss_main() are well paused.

I saw a thread( ) related to this issues in TI E2E and tried that. But the results are not encouraging. 

Please let me know how to set properly breakpoints in the code of mss_main() and other parts of mmWave Demo.

  • 0
    TI__Guru**** 152104 points
    Hi

    Please try to set hardware breakpoints instead of software breakpoints and check if it works.

    Please note that you will not be able to use breakpoints to analyze the code step by step. Since the demo is running in a multicore environment when you set a breakpoint in the code executing on one of the cores, the other core and the RF front end will continue running and the code will crash.

    If you want to analyze the code step by step you can modify the demo profile to configure the RF front end for a single frame.

    Please see the definition of "frameCfg" in the mmWave SDK UG.

    Sample Configuration for single frame:
    frameCfg 0 3 128 1 160 1 0

    Sample Configuration for infinite frames
    frameCfg 0 3 128 0 160 1 0

    Thank you
    Cesar
  • 0 in reply to Cesar
    TI__Genius 11415 points
    As Cesar mentioned, debugging real time code with breakpoints is never an option.

    If user needs to study the processing chain only, we suggest to use the dsp_edma test which uses exact same code as mmW demo and is non real time/DSP only. See under ti/drivers/test/dsp_edma.

    Regards,
    Michelle
  • 0 in reply to Cesar
    Intellectual 560 points

    Thank you Cesar.

    Actually, I am not intending to debug during radar is working but want to look into the deep inside of the code where the radar parameter settings are done.

    I solved this problem by re-installing the mmw_mss_16xx from Resource explorer. Now the debugger stops the breakpoints where I want to see.

    I think your tip would help my work. 

    Have a good day.