SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Hung Bui — Tue, 28 Jan 2020 09:51:10 GMT

Hi Mark,

Each page of the nRF52 is 4kB so we need to count the size with page aligned.

The S132 v6.1/S132v6.2 will occupy 152kB (end address at 0x26000).

You app is 159608byte => 156kB in size.

The bootloader I assume the start address is at 0x78000 by default => Occupies 32kB. This is required because there are some storage pages for bootloader setting and backup.

So it's already occupied 152+156+32=340kB.

I assume you are using nRF52832 which has 512kB of flash. So we have 172kB left.

Even if you don't have any application data need to be reserved. It's still not enough to receive the Softdevice + BL = 152+22= 174kB (occupies 176kB).

You can do a quick check by reading the flash out using: nrfjprog --readcode and compare it with the previous hex dump before the update.

If you do a SD DFU only or BL DFU only, it should fit into the swap bank and the app should run after that.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Mark P. Mendelsohn — Tue, 28 Jan 2020 00:22:21 GMT

These are the sizes of the BL, SD, and Apps for each of SDK 14.0 and SDK 15.2

In both instances, the SD being updated is actually smaller in size than the loaded SD.

The sum of BL+SD is greater for SDK 15.2 than for SDK 14.0

Force Dual bank is disabled

#define NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES 0

SDK14.0 App Segment Size

340kB - 158784 = 189376 free

SDK 15.2 App Segment Size

328kB - 159608 = 176264 free

	SDK 14.0.0	Update
BL	23280	23280
SD 5.0.0/5.1.0	136360	123012
Sum BL+SD	159640	146292
App	158784

	SDK 15.2.0	Update
BL	23040	23040
SD 6.1.0/6.1.1	148332	147792
sum BL+SD	171372	170832
App	159608

Looks like there is room for the DUAL Bank DFU to take place.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Hung Bui — Mon, 27 Jan 2020 14:08:54 GMT

Hi Mark,

To clarify, if the SD+BL is performed with dual bank update ,and if the size of the SD is not changed, the application will be retained. If not the application will be erased. If the SD+BL size is bigger than the swap area, the singe bank update will be performed automatically (unless you configured not to use singlebank).

In the case that the application is erased, the application is only put back if you do another DFU for the app. This either be done by the DFU master automatically if you do an APP+SD+BL update or done manually if you only do DFU for SD+BL.

To avoid the case being drag for long time without solving your issue. Please summarize with bullet points on the issue(s) you currently have. Please send us any code that we can reproduce the issue here.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Mark P. Mendelsohn — Fri, 24 Jan 2020 20:07:53 GMT

devzone.nordicsemi.com/.../bootloader_5F00_debug.log

Attached is an RTT log of the buttonless DFU application with a BL + SD update with a debug Bootloader. It just hangs after the DFU finishes. The production code is based on SDK 15.2. This used to work in SDK 14.0. Although the reference you mention says that the application is saved during the DFU, it also states that the Application is put back after the DFU is completed.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Hung Bui — Wed, 22 Jan 2020 14:14:59 GMT

Hi Mark,

It's a normal behavior. The reason for that is that the application is erased when you have a successful BL+SD update or if you do single bank update. And when there is no application, the board will stay in Bootloader mode until there is a DFU of the app.
You can read more about that here: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/lib_bootloader_dfu_banks.html?cp=7_1_3_5_1_2
Single bank update is triggered if there isn't enough space for the new softdevice + BL image. You can disable this automatic switch to single bank feature.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Mark P. Mendelsohn — Tue, 21 Jan 2020 23:45:59 GMT

Some more testing shows that sending BL+SD does not return. Bootloader is still running because advertising can still be seen. The continuation timer is set to the default 10 seconds. The inactivity timer is also set to the default of 120 seconds. Running with no debugger.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Hung Bui — Mon, 20 Jan 2020 14:59:13 GMT

Could you reproduce with the stock bootloader and the DFU buttonless example?
If you could, please send us your DFU buttonless that you have your code to start WDT so we can test here.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Hung Bui — Mon, 20 Jan 2020 12:11:04 GMT

We have a case here stating that it went to the inactivity timeout handler when in debug mode but not when it's running without the debugger.
https://devzone.nordicsemi.com/f/nordic-q-a/52036/freertos-with-wdt-reset-problem-nrfjprog/212193

Could you check if it's the case for you ?

Also, as I mentioned the bootloader_reset() doesn't do reset immediately but will trigger and wait for the bootloader setting to be written in flash before the actual reset. One thing you can do is to put the reset code : NVIC_SystemReset() right into the inactivity_timeout() before the bootloader_reset() and run in normal mode and check if the board get reset ?

Do you enable reload register RR7 when you enable WDT ? We have a bug inside wdt_feed() that we don't feed the NRF_WDT_RR7 in the loop.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Mark P. Mendelsohn — Fri, 17 Jan 2020 16:46:10 GMT

The screenshot previously posted shows that the inactivity timer does get triggered.

Correction: The bootloader is advertising after the reset fails.

The SDK15.2 Bootloader will automatically feed the WDT if it is running by default.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Hung Bui — Fri, 17 Jan 2020 12:26:56 GMT

Hi Mark,

Could you check if the inactivity timeout is triggered or not ?
If the reset didn't happen, what does the bootloader do ? does it advertise ?
How do you feed the WDT inside the bootloader ?

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Mark P. Mendelsohn — Thu, 16 Jan 2020 22:13:03 GMT

Determined that the issue is related to the use of WDT. When WDT is enabled, the reset does not work. When WDT is disabled, the reset is working. We need WDT enabled. Even with WDT enabled on SDK14.0.0 Bootloader, it was still able to reset.

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Hung Bui — Wed, 09 Oct 2019 13:59:56 GMT

Hi Mark,

bootloader_reset() doesn't do the reset immediately. It will try to store the bootloader setting ( to store the DFU progress) before triggering a reset. Normally the actual reset (inside reset_after_flash_write()) should be triggered after the write command finished (a callback from softdevice). There must be something causing the callback event not to arrive.

Can you reproduce the issue every time or it only happens occasionally ?

Have you checked if you have the same problem on SDK v15.3 ?

Could you check if settings_write() inside settings_backup() return NRF_SUCCESS, and reset_after_flash_write() is called ?

RE: SDK15.2 Bootloader does not timeout even though NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set

Mark P. Mendelsohn — Tue, 08 Oct 2019 20:38:51 GMT