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.

AWR1642BOOST: Error: MMWDEMO_DSS_FRAME_PROC_DEADLINE_MISS_EVT. xWR16xx Demo is flashed on AWR.

Part Number: AWR1642BOOST

Hi,

I am trying to run one chirp per subframe as seen in the below image of my CLI Script. When I run this, everything loads in correctly (as I can see the yellow DS3 light up), but it does not run completely. I only gain retrieve 16510 bytes of data.

Additionally, below is the error i get and it points to MMWDEMO_DSS_FRAME_PROC_DEADLINE_MISS_EVT.

If I run 2 chirps per subframe as seen below, it runs completely through with no errors and I get all the data. 

Any advice on how to get the one chirp to run through completely would be greatly appreciated! The reason for this is because I am doing a crude way of distributed BPM with 3 radars in the network each transmitting certain CLI scripts so I can backtrack and resolve their own chirps. I do not need any on board DSS processing to occur. 

Thanks!

George

  • Hello George,

    I need to try same experiment at my end to find the cause of it. 

    Somehow DSS is not getting sufficient time to process the data during the frame and hit this error.

    Meanwhile, if you don't need any on board DSS processing then you can use mmWave Studio to configure the device and capture the raw adc data using DCA1000.

     

    Regards,

    Jitendra

  • Hi Jitendra,

    Thank you so much! Yeah just very odd how 2 chirps works like a charm, just not one (and one chirp is less time than 2).

    And yes, no on board DSS processing necessary. I looked through the mmWave Studio User Guide and I did not see much about how to run that bin file (image) on the AWR directly, instead mostly GUI functionality. Is there some documentation I could follow? Mostly, I am looking for what the configuration script for the radar would be like given the image flashed on the AWR is the mmWave Studio rather than the demo. 

    Thank you so much!

    George

  • Hello George,

    You need to use device in SOP-2 mode while connecting with mmWave Studio.

    Refer section 6 from mmwave_studio_user_guide.pdf (C:\ti\mmwave_studio_02_01_01_00\docs) to find right step (SOP-2 & firmware selection) for this experiment.

     

    Regards,

    Jitendra

  • Jitendra,

    Great, I saw those steps. So, correct me if I am wrong.

    I have 3 AWRs that I would like to run at the same time in a network. Therefore, to get them ready for that, I will

    1) connect each AWR up my laptop with the mmWave Studio GUI downloaded

    2) follow the firmware download steps on page 23 of the user guide (in SOP-2 mode)

    3) Disconnect them and connect them to their Raspberry Pis where they will be disbursed through the room.

    I am unsure after this point how to configure the radars without the mmWave GUI. When I ran the AWRs in demo mode (flashed on AWR), I used the attached python file to start the test and load in the configuration script. How would you configure and start the test when the mmWave Studio firmware is downloaded on the AWR?

    start_AWR.docx

    Additionally, is there a limit on the number of chirps one can configure for the mmWave studio? I found these two files that may be able to help direct the conversation on how to load these into the AWR remotely and configure the AWRs. As a reminder, I do have the network of three AWRs hardware triggered to start together. There is a way in the configuration CLI script for the demo image to configure this hardware start. Is there the same way to do it on the AWR with the mmWave Studio?

    5417.ProfConfigData.csv

    3146.ChirpConfigData.csv

    Thanks!

    George

  • I figured it out, thank you!