• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 292 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AWR2243: mmWave DFP: What does Async event handled f:80 invoked - while receiving data

Santhana Raj
Expert 1765 points
Part Number: AWR2243

Hi,

We are communicating to AWR2243 sensor using a host processor. We have successfully ported the mmWave DFP to the host processor.

While receiving raw data over CSI2 data, we occasionally get a DFP message saying Async even handled invoked f:80. Based on our search, this error means that the capturing data time is more than the frame time.

If this is the case, since we are using AWR2243, the frame period is fixed and should not vary from frame to frame to cause this error. Additionally, when using infinite frames, this doesn't seem to happen. After this message from Async handler, the CSI2 data stops streaming.

Our active frame time is a little less than 10ms while our frame time is 50ms.

Can you help us identify why this error pops up from DFP occasionally and how to handle it?

Thanks in Advance,

Santhana Raj

  • 0
    TI__Guru 69720 points

    Hi Santhana,

    Is this error code or async-event message you are recieving from AWR2243 device?

    Ideally chirp or frame duration should be more than enough to stream the adc data over CSI2 (based on selected speed). So you need to make sure that condition matched based on your calculation.

    Try increasing frame idle time.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Expert 1765 points

    Hi Jitendra,

    It's the async even message as you rightly guessed.

    I am running CSI2 in 600Msps and using four lanes. I tapped the CSI2 lines and was able to see that the data comes out for approx 10ms and the remaining 40ms remain empty.

    While trying to receive and copy the data in the host processor, I am occasionally getting this error. My understanding is that the radar active time and streaming time shouldn't depend on the capability of my host processor. I ran the AWR independently without my host processor receiving the data. In this case, I am not getting this f:80 error.

    The source of this error looks counterintuitive and confusing for me at least. Is there any situation where this can happen at any other time?

    Thanks & Regards,

    SanthanaRaj