DFU bootloader -- NRF_ERROR_SVC_HANDLER_MISSING

[lee-marc]

Module:	ilumi H52 BLE module (nRF52832)
SDK:	nRF5_SDK_15.3.0_59ac345
Softdevice:	132_nrf52_6.1.1_softdevice.hex
Compiler:	gcc version 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907] (15:7-2018-q2-4)

My objective is to be able to update the whole flash of the Nordic device over the air.

I've compiled the secure bootloader according to "Getting started with Nordic's Secure DFU bootloader, a step by step guide" without errors.

But, as we are using the "ilumi H52 BLE" module, which contains an external power amplifier, I need to implement additional code.

err_code = sd_ble_opt_set(BLE_COMMON_OPT_PA_LNA, &opt);
APP_ERROR_CHECK(err_code);

This command leads to following error message:

<error> app: Received an error: 0x00000001!

According to ntf_error.h 0x00000001 means NRF_ERROR_SVC_HANDLER_MISSING. What does that mean? How can I solve that problem?

[Vidar Berg]

Hi,

Did you call sd_ble_opt_set(BLE_COMMON_OPT_PA_LNA, &opt); after enabling the Softdevice in nrf_dfu_ble.c->ble_stack_init()? Softdevice APIs may return this error if the Softdevice is not enabled. 

[lee-marc]

I started sd_ble_opt_set(BLE_COMMON_OPT_PA_LNA, &opt); before nrf_bootloader_init(dfu_observer);.
That's why it didn't work. Thank you for the hint.

[RVM]

Is there any mechanism to register a callback that can be executed at the right time to take this action?
I really do not want to be modifying the stock SDK -- tracking becomes a nightmare if I open up this can of worms.

Cheers
RMV