I’m trying to implement a bootloader with MCUboot on a custom board based on the nRF52840 chip.
In prj.conf I have:
CONFIG_BOOTLOADER_MCUBOOT=y CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y
and in sysbuild.conf:
SB_CONFIG_BOOTLOADER_MCUBOOT=y
When I flash this to the nRF52840DK development board:
-
The device connects to Bluetooth normally
-
DFU over BLE works without any issues
When I flash the exact same build to my custom board:
-
The device does not connect to Bluetooth at all (not visible in a BLE scanner)
-
If I remove
SB_CONFIG_BOOTLOADER_MCUBOOT=yfrom sysbuild.conf, the firmware works and connects to BLE, but DFU support is gone
So, the problem only occurs when MCUboot is enabled on the custom hardware – on the DK board it works fine.
Question:
What could cause BLE not to start when MCUboot is enabled on a custom nRF52840 board? Which hardware differences between the DK and the custom board could prevent BLE initialization during boot?
