• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 235 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.

AWR1843AOPEVM: Inter-frame debugging exit because CHIRP PROCE DEADLINE MISS EXCEPTION

Geogia
Prodigy 170 points
Part Number: AWR1843AOPEVM

Hi， I'm trying to step into the interFrameProcessing function in obstacle_detection_aop DEMO, but it always exit due to "CHIRP PROCE DEADLINE MISS EXCEPTION". What should I do, is there any way to step into inter-frame function ? 

  • 0
    TI__Mastermind 35785 points

    Hello Geogia,

    So, you might be not able to debug it as the interframe time you may have configured is very less, due to which by the time you are trying to debug and step in, the processing is already completed. You can try to increase the frame time and try it or also you can keep a single chirp in the frame and then try to debug and see if it works for you.

    Regards,
    Saswat Kumar

  • 0
    TI__Guru*** 149044 points

    Hi,

    You can set up a breakpoint in the function. There will be an exception from the mss code but you will still be able to step through the dss code. Also make sure you re-build the dss code with no optimization. This will disable any compiler optimizations which could introduce jumps through the code.

    Another way is to change the frame configuration and run only 1 frame instead of infinite frames.

    In thus way there is no more exception.

    Thank you

    Cesar