ble_stack_init fails when trying to run secure DFU bootloader example

RE: ble_stack_init fails when trying to run secure DFU bootloader example

Simonr — Mon, 13 Nov 2023 13:11:13 GMT

I just tested this on my end as well with the stock secure BLE example, but it seems to work correctly on my end, and the RAM start shouldn't change like this when entering the bootloader mode.

Can you confirm you made no changes to the sample except generating and adding a DFU key? Worth noting that this is not necessary if you did the debug version of the example.

What version of SEGGER Embedded Studios (SES) are you using for development? I know there has been some issues with using other (mainly newer) SES versions than what has been used for testing and verification on our end. You should use v5.42a of SES if possible.

Best regards,

Simon

RE: ble_stack_init fails when trying to run secure DFU bootloader example

mraposo1 — Fri, 10 Nov 2023 20:46:04 GMT

Using the latest NRF52 SDK 17.1.0
Using the bootloader as is from the DFU examples.
It does not work in either the DK or my board.

After some investigation, found out that the issue happens when calling sd_ble_enable.
It returns NRF_ERROR_NO_MEM.

Also, the value for p_ram_start changes from 0x2003ffb0 (where *p_ram_start=20005978) to 0x00000047 (???)

RE: ble_stack_init fails when trying to run secure DFU bootloader example

Simonr — Thu, 09 Nov 2023 15:02:13 GMT

What nRF5 SDK version are you using for development here? Have you made any specific changes to the secure bootloader sample, and just to make sure, you're testing this on an nRF52840 DK, correct, or are you using custom hardware?

Also, have you done any debugging to see if there is any useful error messages or log info from the application that tells you what exactly is going wrong? Seems like sd_mbr_command should provide a return value that points to what's wrong.

Best regards,

Simon