Custom board crashes calling bt_enable

RE: Custom board crashes calling bt_enable

AndyM — Sun, 08 Jun 2025 03:50:52 GMT

Update

Traced the crash to nvs_mount wher it erases free sectors

Turns out on this board all flash outside the application area is write protected by the bootloader. When I moved the nvs parttion inside the app area crashing stopped.

The nvs partition is after the app but inside CONFIG_FLASH_LOAD_SIZE which I also had to specify
Previously it was outside.

RE: Custom board crashes calling bt_enable

AndyM — Fri, 06 Jun 2025 13:17:30 GMT

uart0 is disabled in dts. I get no build errors. The firmware runs just fine on the board until I enter a shell command that calls bt_enable . Then the board reboots. I call bt_enable() from k_work ,not shell context. It is called long after the board boots and other functionality works without problems. Anything in my .config or dts that looks suspicious?
Since I can't connect rtt I tried to redirect log traffic to the shell which uses cdc_acm_uart. I got nothing there.
My current config uses Nordic Bluetooth stack but I did try Zephyr - no improvement
Anything in my .config looks suspicious?
Thanks

RE: Custom board crashes calling bt_enable

Kazi Afroza Sultana — Fri, 06 Jun 2025 08:57:31 GMT

If you are not using UART0, make sure it is either not defined or explicitly disabled in the DTS, and that no part of your configuration (including overlays, Kconfig, or the Bluetooth stack) expects it to be present. If you do define UART0, ensure its pins do not conflict with other GPIO assignments.

You can disbale the UART0 in the devicetree ovrlay file

&uart0 {
    status = "disabled";
};

RE: Custom board crashes calling bt_enable

Kazi Afroza Sultana — Fri, 06 Jun 2025 08:02:52 GMT

Hello,

Do you have external LFXO on your custom board?