Application doesn't work after update with DFU

[isdv]

Hi!

SDK 16.0

I use secure bootloader from SDK with button.

1. Single app written from Segger Studio work fine.

2. Firmware (bootloader with app) written from script below work fine.

However App package (app_dfu_package.zip) updated from nrfConnect for Android start fail.

3. When bootloader written from Segger Studio and app_dfu_package.zip updated from nrfConnect for Android, all work fine.

Why can't write full package and then update app with DFU?

# write bootloader, softdevice and app

OUTPUT_DIR=Output

mergehex=/opt/mergehex/mergehex
nrfjprog=/opt/nrfjprog/nrfjprog
nrfutil=nrfutil

SOFTDEVICE=../../../components/softdevice/s132/hex/s132_nrf52_7.0.1_softdevice.hex
BOOTLOADER=../secure_bootloader/pca10040_s132_ble/ses/Output/Release/Exe/secure_bootloader_ble_s132_pca10040.hex

PRIVATE_KEY=private.pem
APP=../fw/pca10040/s132/ses/Output/Release/Exe/fw_aac_52832_s132.hex
APP_VERSION=1

NRF_FAMILY=NRF52
HW_VERSION=52

BOOTLOADER_SETTINGS=$(OUTPUT_DIR)/bootloader_settings.hex
BOOTLOADER_VERSION=1
BOOTLOADER_SETTINGS_VERSION=1


MERGED_BOOTLOADER_SETTINGS=$(OUTPUT_DIR)/m_bootloader_settings.hex
MERGED_APP_BOOTLOADER_SETTINGS=$(OUTPUT_DIR)/m_app_bootloader_settings.hex

#make bootloader settings
nrfutil settings generate --family $(NRF_FAMILY) --application $(APP) --application-version $(APP_VERSION) --bootloader-version $(BOOTLOADER_VERSION) --bl-settings-version $(BOOTLOADER_SETTINGS_VERSION) $(BOOTLOADER_SETTINGS)

#add softdevice to bootloader with settings
$(mergehex) -m $(SOFTDEVICE) $(BOOTLOADER_SETTINGS)  $(BOOTLOADER) -o $(MERGED_BOOTLOADER_SETTINGS)

#add app
$(mergehex)  -m  $(MERGED_BOOTLOADER_SETTINGS) $(APP) -o $(MERGED_APP_BOOTLOADER_SETTINGS)

#flash into device
$(nrfjprog) --family $(NRF_FAMILY) --recover
$(nrfjprog) --family $(NRF_FAMILY) --program $(MERGED_APP_BOOTLOADER_SETTINGS)  --chiperase  --verify
$(nrfjprog) --family $(NRF_FAMILY) --reset

#make package for DFU updating
$(nrfutil) pkg generate --hw-version $(HW_VERSION) --application-version $(APP_VERSION) --application $(APP) --sd-req 0xCB --sd-id 0xCB  --key-file $(PRIVATE_KEY) $(OUTPUT_DIR)/app_dfu_package.zip

[Vidar Berg]

Hi,

Does the the application update fail at the beginning of the transfer (around 0%)? That would indicate the the pre-validation check is failing (version and signature checks). I suggest you try to bump $(APP_VERSION) when you create the package as "downgrade prevention" is enabled by default.

[isdv]

Transfer comes to an end successfully.

sdk_config.h

#ifndef NRF_DFU_APP_ACCEPT_SAME_VERSION
#define NRF_DFU_APP_ACCEPT_SAME_VERSION 1
#endif

[Vidar Berg]

Thanks. So the error indicates that the application is trying to access a memory region reserved to the Softdevice (NVMC, POWER, CLOCK, RADIO,..). Can you think of anything that the application does differently on the first boot after DFU? 

[isdv]

Simple program have same problem:

log_init();
NRF_LOG_INFO("Load.");
NRF_LOG_FLUSH();
while (true) {
      NRF_LOG_INFO("--");
      NRF_LOG_FLUSH();
      nrf_delay_ms(2000);
};

[Vidar Berg]

I can't be the same problem if you're not enabling the Softdevice. Does this simple program also fail on the first run, but run fine on the next?

[isdv]

Yes.

1.  Run fail

<info> app: Inside main
<debug> app: In nrf_bootloader_init
...

<debug> app: Running nrf_bootloader_app_start with address: 0x00001000
<debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0

2. Run fine

<info> app: Load.
<info> app: --
<info> app: --

When app run fine bootloader  don`t write log output.

I don`t understand why bootloader starts without button pressed.

[Vidar Berg]

Are you only using logging to check if the 'simple' app is running fine? The reason I ask is that RTT clients will usually fail to retrieve log messages after the transition from bootloader to application because the RTT RAM buffer holding the log data gets moved around (client must scan RAM again to find out where the buffer is located). Can you try using a LED or the UART logger backend for indication instead?

[isdv]

Modify example/peripheral/blinky and example/peripheral_ble/ble_app_blinky

nrf_gpio_cfg_output(0);
int on=1;
for (;;){
            on=!on;
            nrf_gpio_pin_write(0,on);
            nrf_delay_ms(500);
}

This work fine.

[Vidar Berg]

So the simple application boots fine on first run, it was just the logging that didn't work.  Can you repeat this with your actual application? 

[isdv]

I remove from own app code that used FDS and disable peer_manager, then app started after upload DFU.

[isdv]

The peer_manager application stops with an error:

<error> peer_manager_pds: Could not initialize flash storage. fds_init() returned 0x860A.
<error> peer_manager: pm_init failed because pds_init() returned NRF_ERROR_STORAGE_FULL.
<error> app: Fatal error

[Vidar Berg]

The error indicates that the flash page allocated to FDS pages have become corrupted (ie overwritten). Please make sure you have reserved the entire FDS region in your bootloader (see DFU_APP_DATA_RESERVED define - it should correspond to the number of FDS pages used by the app).

Memory layout