Deciphering bt controller assert

I'm getting this in my bt controller assert handler:

48 is the file and 260 is the line that our handler is getting.  This is on ncs 3.2.4

Parents
  • Hi

    Are you working on the nRF52840 here? This assert seems to point to the radio event manager callback not having the correct signal reported. It's hard to point to what could cause this, so I suggest you share some details on what your controller is doing exactly. Any configs on what Bluetooth controller features are used would be helpful. Also please confirm you're using the nRF52840 as is tagged on this ticket.

    If you'd like we can set this ticket to Private mode in order to keep any code snippets or configs you share private between you and Nordic employees. Let me know if that's the case and I'll get on that.

    Best regards,

    Simon

  • I believe we have this tracked to an accidental arming of timer0 when we didn't have an active radio timeslot.  Would that have caused this assert?

    we also sometimes see the assert 48, 218.  seemingly from the same timer arm.  Does that assert also line up with a timer armed when we don't have the radio?

Reply Children
No Data
Related