nfr bootloader bl-settings-version

RE: nfr bootloader bl-settings-version

Hieu — Fri, 05 May 2023 13:55:57 GMT

Hi LSz,

What specific version of nRF SDK v15 did you use? If I understand correctly, the bootloader on the device is still from that SDK v15.x.0 version, right?

From the Generating and displaying bootloader settings page of the nRF Util documentation:

The --bl-settings-version depends on the SDK version:

SDK version	BL settings version
<=12.0	1
>=15.3.0	2

Table 2. SDK and BL settings versions

The DFU bootloader settings version supported and used by your selected SDK is listed in the nrf_dfu_types.h file in the bootloader library. Even though bootloaders compiled from an nRF5 SDK 15.3.0 or later can only use version 2, they can be configured to support a version 1 settings page. When a new bootloader with a version 1 settings page boots, the bootloader translates the settings page to version 2 before booting. If a version 2 settings page is used, boot validation for SoftDevice and Application can be generated with the settings page using the --sd-boot-validation and --app-boot-validation commands.

Please take a dive into nrf_dfu_types.h of your bootloader SDK version and see if settings version 1 is supported. If you still have any questions, please let me know and I will investigate with you. I am out of office for the next three working days so it will have to be around the later half of next week. My apology for the inconvenience.

Hieu

RE: nfr bootloader bl-settings-version

mrono — Thu, 04 May 2023 12:50:29 GMT

I checked my old commits and see now that what I did was a different mistake. I forgot to update NRF_DFU_SETTINGS_VERSION when migrating my bootloader project to the newer SDK. That got me in trouble.

Here is the bootloader code for handling an old settings version:

    if (NRF_DFU_SETTINGS_COMPATIBILITY_MODE && !NRF_DFU_IN_APP && (s_dfu_settings.settings_version == 1))
    {
        NRF_LOG_INFO("Old settings page detected. Upgrading info.");

        // Old version. Translate.
        memcpy(&s_dfu_settings.peer_data, (uint8_t *)&s_dfu_settings + DFU_SETTINGS_BOND_DATA_OFFSET_V1, NRF_DFU_PEER_DATA_LEN);
        memcpy(&s_dfu_settings.adv_name,  (uint8_t *)&s_dfu_settings + DFU_SETTINGS_ADV_NAME_OFFSET_V1,  NRF_DFU_ADV_NAME_LEN);

        // Initialize with defaults.
        s_dfu_settings.boot_validation_softdevice.type = NO_VALIDATION;
        s_dfu_settings.boot_validation_app.type        = VALIDATE_CRC;
        s_dfu_settings.boot_validation_bootloader.type = NO_VALIDATION;
        memcpy(s_dfu_settings.boot_validation_app.bytes, &s_dfu_settings.bank_0.image_crc, sizeof(uint32_t));

        s_dfu_settings.settings_version = NRF_DFU_SETTINGS_VERSION;
    }

So it auto-updates the settings page. Only some validation options are set to default values.

RE: nfr bootloader bl-settings-version

LSz — Thu, 04 May 2023 12:22:50 GMT

I updated everything except the bl-settings-version 1.
There aren't any problems that I can see.

RE: nfr bootloader bl-settings-version

mrono — Thu, 04 May 2023 11:51:48 GMT

I made the same mistake when I first upgraded to SDK17. There was a serious problem, but I have forgotten what exactly.

Just to clarify, have you also updated the bootloader to the one from SDK17? I think this is where you'll run into issues. For instance check if you are now able to update the bootloader again.