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

Question

During a DFU on SDK15.2 the BLE connection is terminated. The NRF_BL_DFU_INACTIVITY_TIMEOUT_MS is set to 120000. 
 After 2 minutes, the device still has not reset and started running the application again. 
 This same test on SDK14.0.0 will restart the device after 2 minutes of inactivity. 
 Using the Keil Debugger, confirmed that inactivity_timeout() is being called after two minutes 
 but the call to bootloader_reset() does not recover the device. 
 
 Screenshot attached.

Hung Bui · Accepted Answer

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.

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

Top Replies