Single bank DFU update in SDK16 fails

RE: Single bank DFU update in SDK16 fails

Shruuts — Thu, 28 Jul 2022 18:28:31 GMT

Hey Terje,

I am currently changing the code as follows to get single bank update to work. Please let me know if you see any issues with this. Thanks.

nrf_dfu_result_t postvalidate(uint32_t data_addr, uint32_t data_len, bool is_trusted)

.
else
{
if (ret_val == NRF_DFU_RES_CODE_SUCCESS)
{
// Mark the update as complete and valid.
s_dfu_settings.bank_1.image_crc = crc32_compute((uint8_t *)data_addr, data_len, NULL);
s_dfu_settings.bank_1.image_size = data_len;
#if NRF_DFU_SINGLE_BANK_APP_UPDATES
s_dfu_settings.bank_0.image_crc = s_dfu_settings.bank_1.image_crc;
s_dfu_settings.bank_0.image_size = data_len;
#endif // NRF_DFU_SINGLE_BANK_APP_UPDATES
}
.

return ret_val;
}

RE: Single bank DFU update in SDK16 fails

Shruuts — Mon, 25 Jul 2022 23:44:48 GMT

Hey Terje,

Any update on this? Thanks.

RE: Single bank DFU update in SDK16 fails

Shruuts — Tue, 19 Jul 2022 21:37:42 GMT

Hey Terje,

I set the --sd-req to 0xCD (I am using s112 v7.0.1) and I incremented the application version with the exact same outcome.

Before:

nrfjprog --memrd 0x7E000 --n 128 --family nrf52
0x0007E000: D8D55457 00000002 00000001 00000002 |WT..............|
0x0007E010: 00000000 00000000 0004625C C5DFD660 |........\b..`...|
0x0007E020: 00000001 00000000 00000000 00000000 |................|
0x0007E030: 00000000 00000000 00000000 00000000 |................|
0x0007E040: 00000000 00000000 00000000 00000000 |................|
0x0007E050: 00000000 00000000 00000000 FFFFFFFF |................|
0x0007E060: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF |................|
0x0007E070: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF |................|

After:

nrfjprog --memrd 0x7E000 --n 128 --family nrf52
0x0007E000: C66D1D39 00000002 00000002 00000002 |9.m.............|
0x0007E010: 00000000 00000000 00000000 00000000 |................|
0x0007E020: 00000001 0004625C FFDD4169 00000000 |....\b..iA......|
0x0007E030: 00000000 00000000 00000000 00000000 |................|
0x0007E040: 00000000 00000000 00019000 00000000 |................|
0x0007E050: 00000000 00000000 00000000 FFFFFFFF |................|
0x0007E060: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF |................|
0x0007E070: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF |................|

I am also setting NRF_BL_DFU_ALLOW_UPDATE_FROM_APP to 1. Although setting it to 0 does not make a difference either.

RE: Single bank DFU update in SDK16 fails

tesc — Tue, 19 Jul 2022 15:15:01 GMT

Hi,

Have you tried setting the --sd-req to the SoftDevice used (or is this serial DFU / no SoftDevice installed)?

Also, application version, has it strictly increased from what was already stored?

Regards,
Terje

RE: Single bank DFU update in SDK16 fails

Shruuts — Fri, 15 Jul 2022 20:03:28 GMT

Here is my command to generate the application package:

nrfutil pkg generate --hw-version 52 --sd-req 0x00 --key-file private.pem --application-version 0x01 --application main.hex app_dfu_package.zip

Version for nrfutil: v6.1.3.

Btw, if I ignore the error from nrf_bootloader.c and let the application code boot anyway, it works. So the code is written to the correct place.

RE: Single bank DFU update in SDK16 fails

tesc — Fri, 15 Jul 2022 14:44:53 GMT

Hi,

Yes, this looks a bit strange. What is the full command you used for generating the DFU package, and with what version of nrfutil?

Regards,
Terje

RE: Single bank DFU update in SDK16 fails

Shruuts — Thu, 14 Jul 2022 21:49:28 GMT

Hey Terje,

I am seeing a failure with my code. I am setting NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES to 0.

I send a DFU package (zip file created by nrfutil) using nRFConnect app. Before the update, when reading the MBR and Bootloader settings I get:

nrfjprog --memrd 0x7E000 --n 128 --family nrf52
0x0007F000: B77F69C5 00000002 00000001 00000002 |.i..............|
0x0007F010: 00000000 00000000 0004625C FFDD4169 |........\b..iA..|
0x0007F020: 00000001 00000000 00000000 00000000 |................|
0x0007F030: 00000000 00000000 00000000 00000000 |................|
0x0007F040: 00000000 00000000 00019000 00000000 |................|
0x0007F050: 00000000 00000000 00000000 FFFFFFFF |................|
0x0007F060: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF |................|
0x0007F070: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF |................|

Here, bank 0 has the correct details of size and crc. After the update, I get

nrfjprog --memrd 0x7E000 --n 128 --family nrf52
0x0007F000: 2869FC68 00000002 00000001 00000002 |h.i(............|
0x0007F010: 00000000 00000000 00000000 00000000 |................|
0x0007F020: 00000001 0004625C FFDD4169 00000000 |....\b..iA......|
0x0007F030: 00000000 00000000 00000000 00000000 |................|
0x0007F040: 00000000 00000000 00019000 00000000 |................|
0x0007F050: 00000000 00000000 00000000 FFFFFFFF |................|
0x0007F060: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF |................|
0x0007F070: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF |................|

Here bank 0 is the active bank, but the size of code is 0. This makes the check for valid application fail in line 301 in nrf_bootloader.c:

else if (!boot_validate(&s_dfu_settings.boot_validation_app, nrf_dfu_bank0_start_addr(), s_dfu_settings.bank_0.image_size, do_crc))

My file size before and after the update is the same since I am only changing a version number as a test.

RE: Single bank DFU update in SDK16 fails

tesc — Thu, 14 Jul 2022 14:19:54 GMT

Hi,

The references to bank 1 that you refer to are to the value stored in the DFU settings. From what I understand, those settings will contain the correct values for when doing single bank DFU, so that the functionality of the DFU bootloader is correct for that scenario. (E.g. containing same data for both bank_0 and bank_1 when single bank is used.)

Setting NRF_DFU_SINGLE_BANK_APP_UPDATES should ensure single-bank update is used for the application.

In addition, there is an NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES (which may conflict with NRF_DFU_SINGLE_BANK_APP_UPDATES), please check that you have not set that one as well.

Apart from that, do you see any error or is it failing in any way, or is your inquiry based only on code inspection?

Regards,
Terje