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.

IWR1843BOOST: Radar Software Crash in DSS with Multiple Objects (MRR Lab)

Part Number: IWR1843BOOST

I'm facing a software crash issue with our radar system in the MRR lab. Here's the breakdown:

  • FPS Dependency: As discussed in this thread the radar's frame rate (FPS) depends on the SUBFRAME_MRR_PERIODICITY_VAL parameter.
  • Current Configuration: It is set to 60ms, achieving a desirable 16.67 FPS.
  • Crash with Multiple Objects:  The software crashes in the DSS (specifically in the dss_main.c file) after a few seconds when multiple objects are present within the radar's field of view (FOV). {Testing was conducted in our basement with multiple objects placed in front of the radar. This behavior was not observed during lab testing with a limited number of objects.} The crash occurs at line 253 of dss_main.c.

/* Check if the previous frame has been completely processed. */
MmwDemo_dssAssert(dataPathObj->chirpCount != 0);





  • Reduce Maximum Objects: I understand increasing SUBFRAME_MRR_PERIODICITY_VAL can overcome this crash but this would decrease my FPS. Alternatively, could reducing the MRR_MAX_OBJ_OUT value (currently at 200) help avoid crashes while maintaining the 60ms periodicity?

    • I'd appreciate further insights on :
      • Are there other ways to prevent software crashes besides adjusting SUBFRAME_MRR_PERIODICITY_VAL or MRR_MAX_OBJ_OUT ? Are there potential optimizations within the DSS code that could improve performance with a higher object count?

    Thanks in advance for your help!

    • Hello,

      Outputting radar data can be thought of as a race, the chip has to capture all the data and process all the objects before the next frame comes in. If enough time is not given then it will crash as frames come in faster than it can handle. If you want to achieve the same FPS, you can attempt to adjust your chirp design (profileCfg) so that it finishes quicker. You can use the SensingEstimator to help edit these parameters and understand how it affects the radar chirp's performance.

      Best Regards,

      Pedrhom