• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 631 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/IWR1642BOOST: 1642 DEBUG

HAIGANG ZHAO
Intellectual 780 points
Part Number: IWR1642BOOST

Tool/software: Code Composer Studio

Why does the 1632 DEMO stop at a place after debugging debug, the program stops after the breakpoint, but after a few seconds, the program will run away? This caused me to be unable to debug the program continuously. How can I solve it?

  • 0
    TI__Mastermind 30405 points

    Hello,

    In order to correctly debug the application in CCS, please ensure that you are following the below points:

    1. Make sure you have flashed ccs_debug.bin on your IWR1642BOOST EVM before running the code in CCS debug mode as explained in the mmWave SDK user guide.
    2. Note that by default, the binaries (both for R4F and DSP i.e. .xer4f and .xe674) have -O3 level optimization enabled. This applies to the pre-compiled binaries provided in the SDK as well as the ones compiled either using makefiles in the SDK or with the CCS projectspecs provided in mmWave Industrial Toolbox. -O3 optimization  does not allow statement level debugging as the code is optimized.
      1. Remove this flag from the CCS projectspec (or the SDK common makefile) or change it to level 0 i.e. -O0 and re-compile the code to build the binaries for statement level debugging. You will need to do this for separately for the R4F and DSP binaries in the respective CCS projects, re-import and re-build the projects.
      2. Or, if using the SDK makefile based build, change the R4F_CFLAGS and C64X_CFLAGS defines in C:\ti\mmwave_sdk_02_01_00_04\packages\ti\common\mmwave_sdk.mak and re-build the new binaries.
      3. Note that this may increase the memory requirements and/or break real-time behavior because of un-optimized compilation.

    Regards

    -Nitin