• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 318 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.

IWR1443BOOST: mmWave demo debugging problem

Annie Liu
Genius 10295 points
Part Number: IWR1443BOOST
Other Parts Discussed in Thread: IWR1443, CCSTUDIO

Hi Team,

Customer is debugging the VitalSigns demo on CCSv7.4.0. he used IWR1443BOOST. But whether he clicked step into, step over, step return or Resume, the program was executed in Load.c, sartsci.c, idel.c and other files. At the beginning, it was executed in the main function for a while. After entering the driver, it has been in the inside and cannot enter the main function, so the variable mmWaveNumChirps in the main function cannot be viewed. Customer would like to know how to debug, and then he is able to see the value of the variable mmWaveNumChirps?

PS: He set a breakpoint at MMWave_getNumChirps (profileHandle, &mmWaveNumChirps, &errCode), but the program did not execute to the breakpoint. At the same time, he also sent a configuration file to the IWR1443 on the GUI. The GUI can normally measure heartbeat and breathing.

  • 0
    TI__Guru 50240 points

    Hi Annie,

    This might be a CCSTUDIO problem, can customer confirm their breakpoints are enabled? With mmWave Devices in CCSTUDIO, the breakpoints must be enabled AFTER the executables are loaded on to the device but BEFORE the software starts running.

    Cheers,

    Akash