nRF52820 softdevice DFU

RE: nRF52820 softdevice DFU

DANG CONG TAO — Sat, 05 Nov 2022 03:48:41 GMT

Hi, I Cannot find the macro "NRF_DFU_APP_DOWNGRADE_PREVENTION" in the header "sdk_config.h".
I'm using nRF SDK version 15.3.0

Could you help me how to find it?

RE: nRF52820 softdevice DFU

Louis_263 — Thu, 06 Oct 2022 14:28:55 GMT

Hi Vidar,

the softdevice+application DFU worked with nrfutil version 6.1.7. Thank you for your help.

RE: nRF52820 softdevice DFU

Louis_263 — Fri, 30 Sep 2022 12:27:57 GMT

I can confirm that with nrfutil version 6.1.7 the FWID 0x00 does not appear in the output from 'nrfutil pkg display 'ZIP_FILE' command. I didn't manage to test the DFU today, but I will get back to you on this next week ;-)

RE: nRF52820 softdevice DFU

Vidar Berg — Fri, 30 Sep 2022 07:52:31 GMT

I don't see any problems with what you have done so far.

The only way the application update will be allowed to overwrite the Softdevice is if the signed init command for the app contains 0x00 in its SD FWID list as shown below.

Output from 'nrfutil pkg display 'ZIP_FILE' command:

RE: nRF52820 softdevice DFU

Louis_263 — Thu, 29 Sep 2022 13:59:54 GMT

Hi Vidar,

Thanks for the quick reply, I will try it and get back to you.

Maybe I'll list here again all the steps I've done so far, then maybe you can check if everything is correct.

I took the UART secure bootloader project as is, and used the following preprocessor symbols for me:
- CONFIG_GPIO_AS_PINRESET
  FLOAT_ABI_SOFT
  NRF52820_XXAA
  BOARD_PCA10100
  NRF_DFU_SINGLE_BANK_APP_UPDATES=1
  NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES=0
  NRF_DFU_SETTINGS_VERSION=2
  SVC_INTERFACE_CALL_AS_NORMAL_FUNCTION
  __HEAP_SIZE=0
  uECC_ENABLE_VLI_API=0
  uECC_OPTIMIZATION_LEVEL=3
  uECC_SQUARE_FUNC=0
  uECC_SUPPORT_COMPRESSED_POINT=0
  uECC_VLI_NATIVE_LITTLE_ENDIAN=1
I generate the bootloader settings for my project, consisting of softdevice, app and bootloader, with the following command:
- nrfutil settings generate --family NRF52QFAB --application app.hex --application-version 1 --bootloader-version 1 --bl-settings-version 2 settings.hex
With a custom command I jump from the application into the bootloader (GPREGRET method) and thus trigger a DFU
I generate the DFU package with the following command:
- nrfutil pkg generate --hw-version 52 --application app.hex --application-version 1 --sd-req 0x00,0x100 --sd-id 0x100 --softdevice s140_nrf52_7.2.0_softdevice.hex --key-file private_key.pem app_sd_dfu_package.zip
During the DFU the old softdevice and the old application should be deleted and replaced 1 to 1 at the same location in flash memory by the new softdevice and the new application

RE: nRF52820 softdevice DFU

Vidar Berg — Thu, 29 Sep 2022 10:53:49 GMT

Hi Louis,

Thanks. I see from your command that you are correctly setting the FWID requirements so you are likely experiencing this bug that was addressed in nrfutil v6.1.7: https://github.com/NordicSemiconductor/pc-nrfutil/releases

Please upgrade nrfutil and try again.

RE: nRF52820 softdevice DFU

Louis_263 — Thu, 29 Sep 2022 10:37:28 GMT

Hi Vidar,

this is the command I used:

nrfutil pkg generate --hw-version 52 --application app.hex --application-version 1 --sd-req 0x00,0x100 --sd-id 0x100 --softdevice s140_nrf52_7.2.0_softdevice.hex --key-file private_key.pem app_sd_dfu_package.zip

Louis

RE: nRF52820 softdevice DFU

Vidar Berg — Thu, 29 Sep 2022 10:10:44 GMT

Hi Louis,

The init command for the application update must include the FWID of the Softdevice the app was built for (i.e. 0x0100 if you still use s140 v7.2.0), and not 0x00. When the FWID is 0x00, it tells the bootloader that the application is meant to run without the Softdevice, so it will overwrite it.

Can you post the command you used to make the combined Softdevice+application update package?

RE: nRF52820 softdevice DFU

Louis_263 — Wed, 28 Sep 2022 12:17:51 GMT

Hi Vidar Berg ,

I have tried the solution approach and the transfer of the DFU also works without problems, I get displayed: "Device programmed".
However, after the DFU (App+Softdevice), the application no longer starts. I looked at the memory after the DFU and discovered an anomaly, see the image below:

There is a "gap" in the softdevice and I don't know why it is there. Maybe it means that the application is no longer being called.
Maybe you can help me.

Update:

I found out that the actual application is written to the beginning of the softdevice (see the following pictures). How can this happen?
Can't the memory area of the softdevice simply be deleted and then the new softdevice be written there? And the same with the application. I don't understand why the application is written to the beginning of the softdevice area.

This is the log of the DFU of the application (executed after the DFU of the softdevice):

devzone.nordicsemi.com/.../log_5F00_wrong_5F00_dfu.txt

There you can see that somehow this does not work as I imagined. The cache_address is initially set to 0x27000 (i.e. the start of the application) and is then set to 0x1000 (i.e. the start of the softdevice).

Louis

RE: nRF52820 softdevice DFU

Vidar Berg — Wed, 07 Sep 2022 07:00:04 GMT

Hello Louis,

I am sorry for the confusion. I meant to say that you had to "disable NRF_DFU_APP_DOWNGRADE_PREVENTION", not to enable it. It makes sense that you can't overwrite the SD with NRF_DFU_APP_DOWNGRADE_PREVENTION enabled.

Best regards,

Vidar

RE: nRF52820 softdevice DFU

Louis_263 — Mon, 05 Sep 2022 14:08:58 GMT

Hello Vidar,

thanks for your response. With the above adjustments, I get the following error:

Extended Error 0x07: The array of supported SoftDevices for the update does not contain the FWID of the current SoftDevice.

If I omit the NRF_DFU_APP_DOWNGRADE_PREVENTION and use as command

nrfutil pkg generate --hw-version 52 --sd-req 0x00 --softdevice s140_nrf52_7.2.0_softdevice.hex --key-file private.pem app_dfu_package_sd_s140.zip

then it works. Does that make sense?

Best regards,

Louis

RE: nRF52820 softdevice DFU

Vidar Berg — Mon, 05 Sep 2022 13:16:16 GMT

Hello Louis,

In addition to having NRF_DFU_SINGLE_BANK_APP_UPDATES, please try to enable disable NRF_DFU_APP_DOWNGRADE_PREVENTION and add 0x00 to your --sd-req list. This should allow you to overwrite an existing softdevice.

nrfutil pkg generate --hw-version 52 --sd-req 0x00, 0x100 --softdevice s140_nrf52_7.2.0_softdevice.hex --key-file private.pem app_dfu_package_sd_s140.zip

Best regards,

Vidar