Application doesn't work after update with DFU

RE: Application doesn't work after update with DFU

isdv — Tue, 28 Jan 2020 07:35:01 GMT

#define NRF_DFU_APP_DATA_AREA_SIZE 196608, solved a problem.

Thank you very much for your help.

PS.

NRF_DFU_APP_DATA_AREA_SIZE 0 -- Will delete all application data?

RE: Application doesn't work after update with DFU

Vidar Berg — Mon, 27 Jan 2020 16:06:14 GMT

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

RE: Application doesn't work after update with DFU

isdv — Sat, 25 Jan 2020 18:52:09 GMT

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

RE: Application doesn't work after update with DFU

isdv — Thu, 23 Jan 2020 09:49:13 GMT

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

RE: Application doesn't work after update with DFU

Vidar Berg — Thu, 23 Jan 2020 09:47:34 GMT

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?

RE: Application doesn't work after update with DFU

isdv — Thu, 23 Jan 2020 09:27:34 GMT

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.

RE: Application doesn't work after update with DFU

Vidar Berg — Thu, 23 Jan 2020 07:20:12 GMT

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?

RE: Application doesn't work after update with DFU

isdv — Wed, 22 Jan 2020 09:49:38 GMT

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.

RE: Application doesn't work after update with DFU

Vidar Berg — Wed, 22 Jan 2020 09:36:33 GMT

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?

RE: Application doesn't work after update with DFU

isdv — Wed, 22 Jan 2020 09:25:10 GMT

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);
};

RE: Application doesn't work after update with DFU

Vidar Berg — Wed, 22 Jan 2020 09:23:06 GMT

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?

RE: Application doesn't work after update with DFU

isdv — Wed, 22 Jan 2020 08:20:40 GMT

addr2line -e fw_aac_52832_s132.elf 0x0002656C
./components/libraries/util/app_error_weak.c:100 (discriminator 1)

Once view error:

<error> app: SOFTDEVICE: INVALID MEMORY ACCESS

RE: Application doesn't work after update with DFU

Vidar Berg — Wed, 22 Jan 2020 08:03:40 GMT

Hi,

PC: 0x0002656C is inside the application region, so the app did start in this case. Could you post the entire readout from "readregs", and also if you are able to check what your application is doing at this address (with addr2line, from *.map file, or disassembly view in IDE)?

RE: Application doesn't work after update with DFU

isdv — Wed, 22 Jan 2020 07:38:18 GMT

<info> app: Inside main
<debug> app: In nrf_bootloader_init
<debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
<debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
<debug> nrf_dfu_settings: Using settings page.
<debug> nrf_dfu_settings: Copying forbidden parts from backup page.
<info> nrf_dfu_settings: Old settings page detected. Upgrading info.
<debug> nrf_dfu_settings: Writing settings...
<debug> nrf_dfu_settings: Erasing old settings at: 0x0007F000
<debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x0007F000, len=1 pages), queue usage: 0
<debug> nrf_dfu_flash: Flash erase success: addr=0x0007F000, pending 0
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x0007F000, src=0x2000934C, len=896 bytes), queue usage: 1
<debug> nrf_dfu_flash: Flash write success: addr=0x0007F000, pending 0
<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
<debug> nrf_dfu_settings: Writing settings...
<debug> nrf_dfu_settings: Erasing old settings at: 0x0007E000
<debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x0007E000, len=1 pages), queue usage: 1
<debug> nrf_dfu_flash: Flash erase success: addr=0x0007E000, pending 0
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x0007E000, src=0x200096CC, len=896 bytes), queue usage: 1
<debug> nrf_dfu_flash: Flash write success: addr=0x0007E000, pending 0
<debug> app: Enter nrf_bootloader_fw_activate
<info> app: No firmware to activate.
<debug> app: App is valid
<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
<debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
<debug> app: Running nrf_bootloader_app_start with address: 0x00001000
<debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0

/opt/nrfjprog/nrfjprog --readregs

PC: 0x0002656C

Next problem founded:

After writing firmware with DFU and first reset i got (<debug> app: Running nrf_bootloader_app_start with address: 0x00001000) and application does not running.

After second reset all correct:

<info> app: Load.
<info> app: Load main_config.
<debug> app: Main FDS Event: 0 received
<info> app: FDS initialized

Every second reset not run app, but start bootloader with halt.

RE: Application doesn't work after update with DFU

Vidar Berg — Tue, 21 Jan 2020 15:30:34 GMT

Thanks for confirming. Have you tried to debug the application after DFU? The first thing I would check is if the program reaches main() after reset, and if not, check if the program counter (PC) register appears to get stuck at a particular address.

You can run 'nrfjprog --readregs' from the command line to read out the CPU registers.

RE: Application doesn't work after update with DFU

isdv — Tue, 21 Jan 2020 15:07:52 GMT

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

RE: Application doesn't work after update with DFU

Vidar Berg — Tue, 21 Jan 2020 12:35:37 GMT

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.