DFU

RE: DFU

bjorn-spockeli — Fri, 14 Feb 2020 07:44:08 GMT

See Bootloader Settings page in our documentation. It basically contains information that tells the bootloader if there is a valid application and softdevice present in addition to the progress of the firmware update and the progress of the firmware activation.

Best regards

Bjørn

RE: DFU

Sunil vignesh — Fri, 14 Feb 2020 05:43:50 GMT

can you tell what is the role of BLE settings bl_settings

why need to create the bl_settings.hex hex file?

RE: DFU

bjorn-spockeli — Thu, 13 Feb 2020 19:08:42 GMT

See the Firmware version section under Acceptance rules for versions in our Bootloader documentation.

RE: DFU

Sunil vignesh — Thu, 13 Feb 2020 13:36:08 GMT

Thank you,

I have a doubt that

i have run the application with SDK_15.3 and respective SD.

now i need to change it to SDK_16.0 with respective SD.

through DFU

How can i do

i have refer this link

got error like this

RE: DFU

bjorn-spockeli — Tue, 11 Feb 2020 12:53:55 GMT

Its --bl-settings-version, not --ble-settings-version.

RE: DFU

Sunil vignesh — Tue, 11 Feb 2020 12:30:59 GMT

Hi,

I tried to implement BLE_UART_DFU.

in process i got stuck in nrfutil settings generate.

I am using SDK_16

but in settings generate is upto SDK_15.3.0. i am using nrfutil 6.0.1

D:\HEXFILE>nrfutil settings generate --help
Usage: nrfutil settings generate [OPTIONS] HEX_FILE

Options:
--family [NRF51|NRF52|NRF52QFAB|NRF52810|NRF52840]
nRF IC family: NRF51 or NRF52 or NRF52QFAB
or NRF52810 or NRF52840 [required]
--application TEXT The application firmware file. This can be
omitted ifthe target IC does not contain an
application in flash.Requires --application-
version or --application-version-string.
--application-version INTEGER The application version.
--application-version-string TEXT
The application version string, e.g.
"2.7.31". Will be converted to an integer,
e.g. 207031.
--bootloader-version INTEGER The bootloader version. [required]
--bl-settings-version INTEGER The Bootloader settings version.Defined in
nrf_dfu_types.h, the following apply to
released SDKs:
|SDK12.0.0 - SDK15.2.0|1|
|SDK15.3.0 - |2| [required]
--start-address INTEGER Custom start address for the settings page.
If not specified, then the last page of the
flash is used.
--no-backup Do not overwrite DFU settings backup page.
If not specified, than the resulting .hex
file will contain a copy of DFU settings,
that will overwrite contents of DFU settings
backup page.
--backup-address INTEGER Address of the DFU settings backup page
inside flash. By default, the backup page
address is placed one page below DFU
settings. The value is precalculated based
on configured settings address
(<DFU_settings_address> - 0x1000).
--app-boot-validation [NO_VALIDATION|VALIDATE_GENERATED_CRC|VALIDATE_GENERATED_SHA256|VALIDATE_ECDSA_P256_SHA256]
The method of boot validation for
application.
--sd-boot-validation [NO_VALIDATION|VALIDATE_GENERATED_CRC|VALIDATE_GENERATED_SHA256|VALIDATE_ECDSA_P256_SHA256]
The method of boot validation for
SoftDevice.
--softdevice FILE The SoftDevice firmware file. Must be given
if SD Boot Validation is used.
--key-file FILE The private (signing) key in PEM format.
Needed for ECDSA Boot Validation.
--help Show this message and exit.

D:\HEXFILE>nrfutil settings generate --family NRF52 --application ble_app_uart_dfu.hex --application-version 0 --bootloader-version 0 --ble-settings-version 2 bl_setting.hex
Usage: nrfutil settings generate [OPTIONS] HEX_FILE
Try "nrfutil settings generate --help" for help.

Error: no such option: --ble-settings-version

RE: DFU

bjorn-spockeli — Wed, 05 Feb 2020 12:59:06 GMT

[quote user="Sunil vignesh"]If the device is Fitness tracker (Health care product) which one you suggest Button DFU or Buttonless DFU or Background DFU.[/quote]

I would recommend the Buttonless DFU solution.

[quote user="Sunil vignesh"][/quote]

I tried to implement Buttonless DFU to BLE_UART or BLE_Blinky it has build but the problem

But after successive upload into the device it doesn't work.

Can you provide a detailed description on how you added the DFU service to the BLE_UART and BLE_Blinky applications? By upload to you mean flashing the application code with the DFU service added ? Or do you mean that you were able to perform DFU, but the application did not start after the DFU finished?

If its the latter, then please provide the log output from the bootloader ( make sure that you use the debug version of the bootloader in our SDK) as well as the logs from the nRF Connect mobile app if you are using this to perform the update.

Best regards

Bjørn

RE: DFU

Sunil vignesh — Tue, 04 Feb 2020 15:56:34 GMT

Bjorn are you there?

RE: DFU

Sunil vignesh — Mon, 03 Feb 2020 11:45:45 GMT

Hi,

i need your opinion that, i need to do DFU

In Button DFU - Works, but the problem is after sleep when it wake up with button press it enter into DFU mode (note: device has one button)

Buttonless DFU and Background DFU as different means . and code reference for background DFU.

If the device is Fitness tracker (Health care product) which one you suggest Button DFU or Buttonless DFU or Background DFU.

I tried to implement Buttonless DFU to BLE_UART or BLE_Blinky it has build but the problem

But after successive upload into the device it doesn't work.

do you have any BLE_UART_DFU code (buttonless) reference .

RE: DFU

bjorn-spockeli — Thu, 30 Jan 2020 09:31:10 GMT

[quote user=""]Is Buttonless DFU as same as Background DFU or both are different[/quote]

Buttonless DFU means that you can trigger the nRF52xxx device to enter bootloader mode by writting to one of the characteristics in the DFU service. The nRF52xxx will then reset into the bootloader and the bootloader that receives the new firmware image and when the entire image is received it will replace the old image with the new one. In other words, the

Background DFU is different. Here its the application that receives the new firmware image while it is continuing to perform the regular application tasks. Once the entire firmware image has been received the nRF52xxx will reset into bootloader mode and replace the old application with the new one.

So the main difference is that with regular buttonless DFU the device will not function as "normal" when the firmware image is being received, but if the update is done in the background in the application, i.e. Background DFU, then the only downtime will be the time it takes to replace the old application with the new one.

[quote user=""][/quote]

I have done Button DFU.

But while running Buttonless DFU for my application. the application doesn't work. i don't know how to debug my application

Are you using the _debug version of the bootloader as suggested by my colleague in https://devzone.nordicsemi.com/f/nordic-q-a/51844/ble_app_buttonless_dfu-my-application

Please describe in detail what that is not working with your application. Are you not able to perform DFU? Doesnt the nRF52xxx device enter the bootloader when you write to the DFU characteristic? Do you get an error when you try to perform DFU?

Best regards

Bjørn