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.

IWR6843AOP: What could cause Transfer Controller Error 0x09 during runtime?

Part Number: IWR6843AOP

Tool/software:

Hi TI team,

We're working on a project based on the IWR6843AOP and using a slightly modified version of the OOB demo from the mmWave SDK.

During runtime (after a few seconds to a few hours of operation), we encounter an EDMA Transfer Controller error. The error is captured by our callback function and seen in CCS, and I’ve attached a screenshot showing the exact error details.

We also used EDMA_getStatusInfo() to further investigate, and I’ve attached a second screenshot with the queue status.

But we did add an additional task for SCI data transmission, but it runs at a lower priority than the DPM task, so it shouldn't preempt or interfere with EDMA-related operations.

I’d like to understand:

  1. What could typically cause error code 0x09 (Transfer Request Error) on EDMA?

  2. Is it likely related to queue overflow, or improper chaining configuration?

  3. What runtime signals should we monitor to help confirm the root cause?

  4. Do you recommend any strategies to monitor or mitigate this kind of EDMA error at runtime?

Any insights would be greatly appreciated. Let me know if you'd like us to share the full paramSet contents or runtime logs.

Thank you so much!

Best regards,
Alan Cheng.

  • Hi Alan, 

    Thanks for the information. We'll look into your questions and get back to you in the next 1-2 days. Thanks for your patience. 

    Best regards,

    Josh

  • Hi Josh,

    Thanks for the update!

    Just checking in — if there’s been any progress or additional thoughts on the issue, I’d really appreciate it if you could let me know. I’m still looking into it on my end as well.

    Thanks again for your support!

    Best regards,
    Alan Cheng

  • Hi Alan, 

    I apologize for the delay and lack of update from my side. After looking into this further, it's not a common problem that we have encountered in the past so I don't have any quick explanation as to what could be the exact cause right now. It might help me out a bit if you could expand a bit on the extent of the modifications that you have made to the demo application. Are the changes only related to adding a new task as you mentioned or the changes also involve additional or modified EDMA transfers? 

    I think it couldn't hurt if you could also share the paramset contents as you suggested. One other point, I noticed from your screenshot that the error actually appears to be a bus error rather than transfer request error. 

    Best regards,

    Josh