Softdevice assertion: nRF54L15

I have observed a Softdevice assertion, built from the v3.1.0 commit. https://github.com/nrfconnect/sdk-nrfxlib/tree/v3.1.0

#define CONFIG_MPSL_LIB_DIR "nrf54l"
#define CONFIG_MPSL_LIB_FLOAT_ABI_DIR "soft-float"
#define CONFIG_BT_LL_SOFTDEVICE_MULTIROLE 1

The assertion was seen through Memfault, I believe the `file` and `line` parameters have been overwritten, but I have the backtrace through the obfuscated symbols.

Parents
  • Ah, sorry, missed the obvious.

    We need to know the file and line to check the mapping we have internally about the assert handlers.

    Is there any way you can help us reproduce the error? Could it be a stack overflow? Could you try to calibrate some thread stack sizes by increasing them from what you have by default?

  • I am a bit confused, the screenshot has the complete list of functions the interrupt transitions through from `mpsl_radio_isr_wrapper` to `sdc_assertion_handler`, how can the filename and line number be required to find where the assertion is?

    > Is there any way you can help us reproduce the error?
    Not really, the fault has only occurred once.

    > Could it be a stack overflow?
    In an interrupt handler? I'm not sure how that would work.

Reply
  • I am a bit confused, the screenshot has the complete list of functions the interrupt transitions through from `mpsl_radio_isr_wrapper` to `sdc_assertion_handler`, how can the filename and line number be required to find where the assertion is?

    > Is there any way you can help us reproduce the error?
    Not really, the fault has only occurred once.

    > Could it be a stack overflow?
    In an interrupt handler? I'm not sure how that would work.

Children
No Data
Related