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.

AWR1843BOOST: How to do halt debug in real time?

Part Number: AWR1843BOOST

Tool/software:

Hi,

I'm developing it by referring to the MRR demo project.

And I'm using the CCS v12.1 and radar toolbox 1.10.00.13, mmwave_sdk_03_06_00_00-LTS.

Real-time halt debugging is required to develop and debug algorithms,

There is a phenomenon that occurs in mss to abort when a break is applied during radiation.

On this issue, the TI proposes two options.(https://buly.kr/3NGaUPd)

The first one is to write only one frame.

The second is to break before the frame starts.

Setting the number of frames to 1 has the hassle of having to rebuild every time I debug it, so I'm trying the second way.

At which point do I have to set the break to stop before the frame starts in the MRR demo project?

It was confirmed that it is impossible within the frame start interrupted callback function in MSS.

  • Hello John,

    There is no feature where you can set it up before the start of frame interrupt.
    There are multiple reasons for this:

    1) Even if you halt the MSS, the frame is controlled over by the RSS firmware. Setting a breakpoint on the MSS is not going to halt the RSS. So even if you halt at any function before, the RSS will still be functional.

    2) The only time you can put this is before the start of first frame and that is if you put a break point before sensor start (won't really help you at all).

    3) That is why if you see the thread you mentioned, they moved forward with the single frame debugging as you the other option is not viable.

    4) To make it more understandable, once you provide the sensor start from the MSS to RSS, then via hardware the RSS based on your chirp, frame, profile will configure and send all the chirps and frames. The MSS does not need to configure it anymore. So, any break point in the MSS< is not going to help your case in any way. The only option is single frame debug.

    Regards,
    Saswat Kumar