This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

What is a reason of the definite SoftDevice assertion handler: m_line_num: 811; m_p_file_name: src\ll_lm.s0.c

Hello,

We start using of our BLE devices with more or less permanent connection with our central BLE device, it was needed for Alisa connection.

BLE peripherals are old enough devices with SoftDevice S110 v7.0.0 SDK v6.0.0 on nrf51822AA, they are already in production state (that is why we can not change SoftDevice version to more newer).
Central is like a gateway from WiFi to Blutooth and vise versa. (BLE part is on nrf52832AA, S132 v2.0.0, SDK v11.0.0) 

And we found out some troubles of peripherals (resets, hangings) only after we started usage that configuration with permanent connection.
But really there are a lot of BLE disconnections with subsequent recovery a connection (we saw that with RTT Viewer). Then we deepened into the bug problem, and found out the following bug text inside our peripherals:

m_line_num: 811; m_p_file_name: src\ll_lm.s0.c

That was produced by SoftDevice assertion handler.
It was confirmed a few times on two various types of our peripheral BLE devices. To reproduce this bug we were waiting a lot of time (during a few days). 
Also we supposed, that the bug arises at the moments of connection event time.

Q: What is an exact reason of that bug text, and what are your recommnedations in our situation?

Thank you in advance.

  • Hi,
    Unfortunately, one of the tested Peripheral devices wrote at RTT Viewer the same assertion handler string after 41 hours of work:
    m_line_num: 789; m_p_file_name: src\ll_lm.s0.c
    We suppose next step with disable/enable Softdevice, as you adviced.

    .......

    It has passed 3 hours yet. And the bug happens in the second type of our Peripheral device with the same text too:

    m_line_num: 789; m_p_file_name: src\ll_lm.s0.c

Related