App will not launch after updating Bootloader with BLE DFU

RE: App will not launch after updating Bootloader with BLE DFU

Sigurd — Thu, 26 Aug 2021 12:47:32 GMT

Hi,

Q1)
Is this log from the bootloader?

00> <info> app: Inside main
00> <debug> app: In nrf_bootloader_init
00> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
00> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
00> <debug> nrf_dfu_settings: Using settings page.
00> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
00> <debug> app: Enter nrf_bootloader_fw_activate
00> <debug> app: Valid BL
00> <debug> app: Verifying BL: Addr: 0x000F1000, Src: 0x00059000, Len: 0x0000C598
00> <debug> app: No bootloader copy needed, bootloader update complete.
00> <warning> nrf_dfu_settings: Settings write aborted since it tries writing to forbidden settings.
00> Received a fault! id: 0x00004002, pc: 0x00000000, info: 0x2003ffa0

Q2)

If yes on Q1, then it seems like NRF_DFU_IN_APP somehow must be incorrectly set to 1 in the bootloader.
Could you double check the value of NRF_DFU_IN_APP ?

[quote user=""]I also have the ability to add additional log messages to the bootloader. [/quote]

Maybe you could print/log the value of NRF_DFU_IN_APP ?

RE: App will not launch after updating Bootloader with BLE DFU

csulz — Fri, 20 Aug 2021 16:31:14 GMT

To be clear, the in-app DFU is working once the correct bootloader is in place. This is not the issue to be focusing on.

The app includes a bluetooth DFU service and I am able to initiate and complete an app update with an android phone. However when I attempt to update the bootloader with this exact same process it fails every time.

RE: App will not launch after updating Bootloader with BLE DFU

Sigurd — Fri, 20 Aug 2021 12:50:20 GMT

Are you able to put the device into normal bootloader mode, and do a non in-app/background DFU ?

RE: App will not launch after updating Bootloader with BLE DFU

csulz — Thu, 19 Aug 2021 16:11:42 GMT

Bootloader project:

#define NRF_DFU_IN_APP 0

(also #define NRF_BL_DFU_ALLOW_UPDATE_FROM_APP 1)

Application project:

#define NRF_DFU_IN_APP 1

Do you think this means that the app is running and just crashing here? What is the app trying to write to the settings page? Anyway to change what is being written?

RE: App will not launch after updating Bootloader with BLE DFU

Sigurd — Thu, 19 Aug 2021 13:51:22 GMT

The code that prints this:

00> <warning> nrf_dfu_settings: Settings write aborted since it tries writing to forbidden settings.

Looks like this:

    if (NRF_DFU_IN_APP && !settings_forbidden_parts_equal_to_backup((uint8_t *)&s_dfu_settings))
    {
        NRF_LOG_WARNING("Settings write aborted since it tries writing to forbidden settings.");
        return NRF_ERROR_FORBIDDEN;
    }

NRF_DFU_IN_APP is documented as this:

// <q> NRF_DFU_IN_APP  - Specifies that this code is in the app, not the bootloader, so some settings are off-limits.
 

// <i> Enable this to disable writing to areas of the settings that are protected
// <i> by the bootlader. If this is not enabled in the app, certain settings write
// <i> operations will cause HardFaults or will be ignored. Enabling this option
// <i> also causes postvalidation to be disabled since this is meant to be done
// <i> in the bootloader. NRF_BL_DFU_ALLOW_UPDATE_FROM_APP must be enabled in the bootloader.

#ifndef NRF_DFU_IN_APP
#define NRF_DFU_IN_APP 0
#endif

What did you set NRF_DFU_IN_APP to in your bootloader project?

RE: App will not launch after updating Bootloader with BLE DFU

csulz — Thu, 12 Aug 2021 16:44:49 GMT

nRF5 SDK 15.3.0

nRFutil version 6.0.1

RE: App will not launch after updating Bootloader with BLE DFU

Sigurd — Thu, 12 Aug 2021 14:07:52 GMT

What version of nrfutil did you use?

I see that e.g. we have this statement, here, that might be relevant:
"¹Use nRF Util v5.0.0 or later when creating update packages of bootloaders compiled from nRF5 SDK 15.3.0 or later to ensure the correct size of generated packages."

RE: App will not launch after updating Bootloader with BLE DFU

csulz — Tue, 10 Aug 2021 16:33:56 GMT

The 'in-app/background' DFU process does not work with 'bootloader v1' which is the reason for the upgrade.

The DFU process to attempt the upgrade from 'bootloader v1' to 'bootloader v2' was performed by connecting to the device via Bluetooth nRF Connect Android application while the device was running the application code, which includes a DFU service. The process appears to finish correctly and there is a verification message from the android app, but when the device reboots the application does not run. This same process works for application updates but not for bootloader updates.

RE: App will not launch after updating Bootloader with BLE DFU

Sigurd — Mon, 09 Aug 2021 20:57:19 GMT

Hi,

[quote user="csulz"]The DFU process appears to complete but the app still does not seem to boot after this[/quote]

Was this DFU process a "in-app DFU"/ background DFU process , or was it done when the device was in "regular" bootloader mode ?

RE: App will not launch after updating Bootloader with BLE DFU

csulz — Thu, 29 Jul 2021 19:10:58 GMT

Any other ideas?

RE: App will not launch after updating Bootloader with BLE DFU

csulz — Mon, 26 Jul 2021 21:04:41 GMT

I generated a bootloader package with this command and loaded it onto a device running our app and our bootloader v1. The DFU process appears to complete but the app still does not seem to boot after this. There appears to be no change with this new command.

RE: App will not launch after updating Bootloader with BLE DFU

Marjeris Romero — Sun, 25 Jul 2021 13:57:11 GMT

Hi,

Can you try to generate the bootloader packet using the following command:

nrfutil pkg generate --bootloader secure_bootloader.hex --bootloader-version 2 --hw-version 52 --sd-req 0xB6 --key-file private.pem BL2.zip

The --sd-id is the new softdevice ID to be used as --sd-req for the application update in case the ZIP contains a Softdevice and an application. Since the ZIP contains only a bootloader then this setting is not needed.

Best regards,

Marjeris