• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 316 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.

AWR6843: Deciphering error message

Lee Lemay
Prodigy 70 points
Part Number: AWR6843

Tool/software:

Dear experts,

I am receiving the following error, but I cannot figure out how to interpret it:
{module#42}: line 221: error {id:0x110000, args:[0x8015ec4, 0x90]}

I have searched through the source code and can't figure out where it is coming from, and I don't know how to interpret the values.

I am setting starting, stopping, and reconfiguring the radar many times in a row, and after a certain number of times, I receive that error.
It is repeatable - it always happens after the same number of configuration changes.

I am using a modified version of the out of the box 6843 demo.

Thank you for your help.

  • 0
    TI__Expert 4190 points

    Hello,

    Could you please let us know what all modifications you have done on out of the box 6843 demo?

  • 0 in reply to Voona Deexith
    Prodigy 70 points

    It's pretty heavily modified. I don't think I can enumerate the modifications in a meaningful way. I've tried to give you the relevant details: I'm starting, stopping, and reconfiguring the sensor many times in a row. It always occurs on the same step, the 388th time I reconfigure the sensor, and it doesn't change when I insert various different values for Task_sleep. 

    The error message is not originating from my code, and I can't find any matching strings in the SDK. Do you know where that message is coming from?

    Could you tell me what "module#42" is, what file line 221 is referring to, and what the error, id, and args are?

    I appreciate your help.

  • +1 in reply to Lee Lemay
    TI__Expert 8802 points

    Hi,

    This is an error occurring in the DSS of the device. Have you attempted to debug and step through any of the code? That would likely be the next step.

    line 221 would be in one of the DSS files, can you look in dss_main.c and see what is there?

    Regards,

    Tim

  • 0 in reply to Tim Henderson
    Prodigy 70 points

    Hi,

    This message was caused by a failed malloc, running in the MSS.
    I had a memory leak.

    Thank you for your help, stepping through the code helped me find it, it was a good suggestion.