nrf52833 s113 DFU Package generation

RE: nrf52833 s113 DFU Package generation

Vidar Berg — Wed, 05 Aug 2020 08:42:01 GMT

[quote user="Olfox"]App start only after uploading the zip file via dfu[/quote]

This indicates that the generated settings page doesn't contain the correct information needed by the bootloader to validate and boot the application. The settings page is updated by the bootloader when you do DFU, so that explains why that part works.

Are you referring to "boot-validation" when you say "signed image", or that the update itself has to be signed? I would recommend to just disable boot validation when debugging, it makes it so that you don't have to update the settings page every time you make a change to the application.

Generate and program settings page without app boot validation:

nrfutil settings generate^
  --app-boot-validation NO_VALIDATION^
  --family NRF52^
  --application-version-string "1.0.0"^
  --bootloader-version 1^
  --bl-settings-version 2^
  --application <APPLICATION>.hex^
  settings.hex
  
  nrfjprog --program settings.hex --sectorerase -r

RE: nrf52833 s113 DFU Package generation

Olfox — Mon, 03 Aug 2020 12:55:26 GMT

Hi Vidar ! thank you. I have generated my setting page. without it i can t start my app. How to proceed to have debug mode with ses when signed image is used please ? Is it possible ? Also i don t know why bootloader doesn t start my signed application when it is flashed at the same time than bootloader setting page and soft device. App start only after uploading the zip file via dfu.

RE: nrf52833 s113 DFU Package generation

Vidar Berg — Mon, 03 Aug 2020 09:49:33 GMT

Hi,

[quote user="Olfox"]So with the option i can at least upload, and appllication strt only after uploading with dfu ble and not when application has been written by wire.[/quote]

This option is required if you've built the bootloader with NRF_BL_APP_SIGNATURE_CHECK_REQUIRED enabled in sdk_config.h. And when you programing everything through the debug interface (Softdevice+bootloader+app) you also need to generate and program the settings page to inform the bootloader that a valid app exists. See "Generating and displaying bootloader settings" for steps to generate the settings page.

RE: nrf52833 s113 DFU Package generation

Olfox — Thu, 30 Jul 2020 13:04:41 GMT

Hi Vidar Berg thanks for the reply,

here is the command i'have used to generate the zip:

nrfutil pkg generate --hw-version 52 --sd-req 0xCC --application-version 2 --application myapp.hex --key-file private_key.pem myapp_inc_signed.zip --app-boot-validation VALIDATE_ECDSA_P256_SHA256

Without --app-boot-validation VALIDATE_ECDSA_P256_SHA256, after programming , it reset, i see dfuTarg advertising, i connect click dfu button dl the myapp_signed.zip , it try to upload, 1time , 2time , 3 times and disconnect, i reconnect , it disconnect, and continu to advertise dfu targ but application doesn't start.

So with the option i can at least upload, and appllication strt only after uploading with dfu ble and not when application has been written by wire. And without the option, even upload doesn't work.

Ok concerning speed, it is a samsung 7 so quiet recent. SO this speed is normal :)

RE: nrf52833 s113 DFU Package generation

Vidar Berg — Wed, 29 Jul 2020 09:15:17 GMT

Hello,

Could you post the commands you use to generate the bootloader settings page (Generating and displaying bootloader settings)?

1. It sounds like a problem with the bootloader settings page. Please try to generate the settings page without the enabling boot validation of the app (--app_boot_validation) and see if you get the same result (the bootloader falls back to dfu mode if this validation fails).

2. It may be slightly faster or slower depending on the phone you use, but 8.3 kB (bytes?) is pretty quick. I got 9-10 kB/s with my iPhone 8 for comparison, and with this transfer rate, it will only take a few seconds to update a regular-sized SDK app.

RE: nrf52833 s113 DFU Package generation

Olfox — Fri, 24 Jul 2020 15:33:27 GMT

Hi ,

I found the good documentation, sorry to have have search enough before to ask on the forum :

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.3.0%2Flib_bootloader_dfu_validation.html&anchor=lib_bootloader_signatures

So I start from zero. Create private , public key, put it in secure bootloader, and then flash with nrfConnect 3.4.0 the four files : softdist.hex myApplication.hex, bootloader.hex and the bootloader setting page.

I needed to add an option to generation packqge to have it working: --app_boot_validation VALIDATE_ECDSA_P256_SHA256.

Q1)

But when i flash like this, bootloader is not able to start normally my application. I can do the dfu via le of my zipped signed package. But the application flashed at " production step" is not started because not signed i guess. How to allow my initial application to start after flashing the four files please? Is it just a matter of not signed app?

Q2)

I have an upload rate of 8.3kB ( i was at 50cm from the devBoad), is it normal ? It seems to be slow .

Thank you