AWR1843: AWR1843 MRR DSS Exception

Rajesh Dubey

Part Number: AWR1843

Hi,

we are working on MRR demo from Automotive toolbox. we are getting error on UART console as - DSS Exception: ../dss_main.c, line 221, and system hangs.

if I commenting line no 221(MmwDemo_dssAssert(dataPathObj->chirpCount != 0). it works fine. Just want to know the reason for this and how to resolve this issue?

over 2 years ago

0 Aniket Mahajan over 2 years ago

TI__Genius 14846 points

Hi,

This happens if you run the lab in CCS debug and start the MSS core before the DSS core. Could you try starting the DSS first, and then the MSS?

(I am slightly hazy on this issue, correct order of starting the cores might also be reversed, it would be worth trying starting MSS first, then DSS and seeing which of the two gives the error).

Regards,

Aayush

0 Rajesh Dubey over 2 years ago in reply to Aniket Mahajan

Prodigy 250 points

Hi Aayush, I am not debugging the code in CCS. it is running on AWR1843 custom board. it is not happening immediately after the system starts. I was looking on MATLAB GUI found that whenever more number of objects appears on the GUI it gives this error. I have added some more features in ReadTask of MSS FYI.

0 Aniket Mahajan over 2 years ago in reply to Rajesh Dubey

TI__Genius 14846 points

Hi Rajesh,

I understand. If the code has been modified, it is possible this issue comes from the device not having enough time to process data.

The line where the error comes from (the assertion) is meant to occur if the previous frame hasn't completed processing and the next frame's chirps start coming in.

Could you just measure the amount of time your extra bit of code is taking, and add that time to the frame time of the configuration? The configurations are in .h files in the src/common folder.

Regards,

Aayush

0 Rajesh Dubey over 2 years ago in reply to Aniket Mahajan

Prodigy 250 points

Hi Aayush,

Thank you for the information. I got it and gonna implement that. before doing that what if simply I comment that line. what will Happen, is it going to impact on the detection accuracy or something?

0 Aniket Mahajan over 2 years ago in reply to Rajesh Dubey

TI__Genius 14846 points

Hi Rajesh,

If the frame processing exceeds the frame time and this line is commented out, the data will get corrupted. At a high level, then next frame's chirps will start coming in, and would either get dropped or overwrite the older frame's data.

Regards,

Aayush

0 Rajesh Dubey over 2 years ago in reply to Aniket Mahajan

Prodigy 250 points

Hi,

Thank you for the help. so increasing frame time and idle time should resolve this issue

0 Aniket Mahajan over 2 years ago in reply to Rajesh Dubey

TI__Genius 14846 points

Hi Rajesh,

From what I can make of it, even the idle time doesn't need to be changed at it is the time in between chirps.

You would need to increase SUBFRAME_USRR_PERIODICITY_VAL, SUBFRAME_MRR_PERIODICITY_VAL in the .h files in src/common to increase the interframe margin time available for processing.

Regards,

Aayush

0 Rajesh Dubey over 2 years ago in reply to Aniket Mahajan

Prodigy 250 points

Sure. thank you for your help.

0 Rajesh Dubey over 2 years ago in reply to Rajesh Dubey

Prodigy 250 points

Hi Aayush, one last question . does MRR and USSR frames come at same time or one by one..?

0 Aniket Mahajan over 2 years ago in reply to Rajesh Dubey

TI__Genius 14846 points

Hi Rajesh,

They come one by one in an alternating manner. You can see more details on this in the developer guide/user guide of the lab.

Regards,

Aayush

Sensors

Sensors forum

AWR1843: AWR1843 MRR DSS Exception