DFU update with SD+BL+APP

RE: DFU update with SD+BL+APP

bama — Thu, 16 Jan 2020 07:41:27 GMT

Thank you Hung Bui!

With the information with the options i have to set before I generate my update file and the information regarding the start address, I was now able to do the update successfully.

regards
markus

RE: DFU update with SD+BL+APP

Hung Bui — Tue, 07 Jan 2020 16:02:25 GMT

It's normal Markus. The bootloader wouldn't allow an update of the same version. If you want to test you would need to increase the bootloader version when creating the .zip file.

RE: DFU update with SD+BL+APP

bama — Tue, 07 Jan 2020 14:58:13 GMT

Hi,

I have checked the Start address of the old and new booloader and you are right these addresses was different. I have now build the new bootloader with the same start address like the old Bootloader. Now I was able to update the Device with the *.zip file.

But now i want to checkl if the new updated device can be also update in futurte I have tried to load the same *.zip file again on the Tag. but there i will then get the message Result code 11 extended erro code 5 (fw_version_failure)

Do you have a idea how to prevent this ? I also have tried to load this *.zip file with the --debug-mode set on the new updated tag but with the same result

thank your regards markus

RE: DFU update with SD+BL+APP

Hung Bui — Thu, 02 Jan 2020 14:19:33 GMT

Hi Markus,

Could you clarify the DEBUG option you mentioned on the old bootloader, did you used the _debug project example in the SDK ?

If you did, the new bootloader should have the start address at the same place as the old bootloader (0x73000).

Could you get any logging from the bootloader ? And get a sniffer trace ?

When testing, you can try testing to update just the SD+BL first (generate the DFU packet with just the SD and BL)

RE: DFU update with SD+BL+APP

bama — Thu, 02 Jan 2020 08:09:34 GMT

Hi,

I have now tired ot make my package with this two possibilities:

nrfutil pkg generate --hw-version 52 --key-file C:\Entwicklung\BeverageMetrics\Firmware\BevMetTag\key\private.pem --application-version 2 --application ble_app_BevMetTag.hex --sd-req 0x98,0xCA --softdevice s132_nrf52_7.0.1_softdevice.hex --sd-id 0xCA --bootloader secure_bootloader_ble_s132_pca10040.hex --bootloader-version 2 BevMetTag_package.zip

nrfutil pkg generate --hw-version 52 --debug-mode --key-file C:\Entwicklung\BeverageMetrics\Firmware\BevMetTag\key\private.pem --application-version 2 --application ble_app_BevMetTag.hex --sd-req 0x98,0xCA --softdevice s132_nrf52_7.0.1_softdevice.hex --sd-id 0xCA --bootloader secure_bootloader_ble_s132_pca10040.hex --bootloader-version 2 BevMetTag_package_debug.zip

And for both *.zip files I get the same Connection timeout error after SD+BL was transfered to the Device.

Do you think it has something todo with a possible DEBUG option in the old Bootloader?

regards

markus

RE: DFU update with SD+BL+APP

Hung Bui — Fri, 27 Dec 2019 16:54:21 GMT

Hi Markus,

When you update the softdevice, the original bootloader won't be able to work with this new softdevice, so you need to update the SD+BL+APP.

In your script to generate the .zip file, it seems that you would need to set --hw-version to 52 (by default it's 52 if you use nRF52) and you would need to increase the bootloader version to 2 for example. The bootloader won't update if the new version is not higher than the current version.

Please try capture a sniffer trace when you do DFU update. Also any log from the bootloader and DFU master would be useful.