RE: MPSL Fault upon connection when using nRF Connect Desktop BLE App

Parker Lloyd — Fri, 19 Apr 2024 18:15:46 GMT

Our application is using LVGL and we were running the lvgl_task_handler in the system workqueue. After moving the lvgl_task_handler to a dedicated thread this problem went away. We are still not entirely sure what the cause of the issue was.

RE: MPSL Fault upon connection when using nRF Connect Desktop BLE App

Edvin — Wed, 17 Apr 2024 08:33:19 GMT

Hello,

So does the issue occur every time you try to connect using nRF Connect for Desktop -> Bluetooth Low Energy, or only some of the times?

What hardware are you running on? Is it an nRf52833 DK, or is it custom HW? If it is custom, does it have an LFXTAL? If so, which one? And does it also happen if you run the same application on a DK?

The obvious answer is that the application on the nRF crashes, and the connection from nRF Connect on Desktop times out. But we need to find the reason for the crash.

There is a clue in the log from the nRF, in the line saying "ZEPHYR_FATAL_ERROR 26: ...". Can you check what is on that address? Please note that this address may change every time you build the application. So please run it again, to get the latest, up to date, addres, and then run the following command using your build folder:

arm-none-eabi-addr2line -e build\zephyr\zephyr.elf 0x<address>

Please note that arm-none-eabi-addr2line is an external tool, but you may have it if you have installed the GNU arm embedded toolchain on your computer. If not, you can try to run arm-zephyr-eabi-addr2line using the same parameters, but you need to run it from an environment where the zephyr toolchain is loaded. Does it point to somewhere in the MPSL part of your application?

Best regards,

Edvin