BLE DFU update

RE: BLE DFU update

RichardHdrd — Fri, 18 Feb 2022 12:01:01 GMT

Hi Amanda,

I could try the

MSDDisable

It solved the issue.

Thank you!

RE: BLE DFU update

Amanda Hsieh — Fri, 18 Feb 2022 11:23:57 GMT

Hi,

[quote user="RichardHdrd"]Important: After executing B, the *DK* contains S132 v5.1.0, the EB somehow crashes.[/quote]

Are you using the same EB in A and B flows? Try to erase the kit before programming the Secure Bootloader & SD S140 (7.2.0) (merged by mergehex) to EB.

[quote user="RichardHdrd"]>>It should update SD+BL+AD to run the new app with the new SD[/quote]

If the updated app uses the same SD version on the device, you don't need to update the SD.

-Amanda

RE: BLE DFU update

RichardHdrd — Fri, 18 Feb 2022 10:58:30 GMT

Hello Amanda,

Thank you for the reply. I never experienced problems using the JLink before, but will try the command:

MSDDisable

Now for the following I'm confused by your instructions/explanations:

Just to be sure, that we have same understanding of what I do:

Upload Secure Bootloader & SD S140 (7.2.0) (merged by mergehex) to EB:

Works: [Linux PC/nrfjprog] --[USB]-->DK --[DebugCable]-->EB

Upload Signed App.zip (compiled for S140 7.2.0) to EB:

A) Works: [Smartphone/nrfToolbox-DFU] >>>> [BLE] >>>> EB

B) Works not: [Linux PC/nrfUtil] --[USB]-->DK >>>> [BLE] >>>> EB

Important: After executing B, the *DK* contains S132 v5.1.0, the EB somehow crashes.

As the update of App.zip (containing app.hex and none of SD or BL) is possible with [Smartphone/nrfToolbox-DFU], i cannot see, why it shouldn't work with nrfUtil.

>>It should update SD+BL+AD to run the new app with the new SD

Why? The EB already contains SD 7.2.0 +BL, I only want to DFU-BLE update the app.

Best regards,

Richard

RE: BLE DFU update

Amanda Hsieh — Fri, 18 Feb 2022 10:21:23 GMT

Hi,

For Error code: NRF_ERROR_SD_RPC_NO_RESPONSE, Have a look at this post.

[quote user=""]SoftDevice detected, id 0xA5 (S132 v5.1.0)[/quote]

You cannot just only update the app which requires Softdevice S140 (v.7.2.0). It should update SD+BL+AD to run the new app with the new SD. Please be aware that

While updating with the new SD, the command requires two different SD IDs. The first update requires --sd-req to be set to the ID of the old SD. The APP update requires the ID of the new SD. The new ID must be set using --sd-id parameter. This parameter was added in nRF Util v3.1.0 and is required since v3.2.0 in case the package should contain SD (+ BL) + APP. Also, the new ID is copied to --sd-req list so that in case of a link loss during the APP update the DFU process can be restarted. In this case, the new SD would overwrite itself, so --sd-req must contain the ID of the new SD. See DFU package combinations.

Regards,
Amanda