DFU Failure updated from SDK14.1 to SDK17

RE: DFU Failure updated from SDK14.1 to SDK17

Amanda Hsieh — Wed, 27 Oct 2021 06:18:42 GMT

Hi,

The test file has an updated package with s132_nrf52_7.2.0_softdevice, SDK 17.0.2 bootloader and app.

First, run the Command.bat under 278167_DFU_SDK14.1_to_SDK17\SDK_14.0.0 to program s132_nrf52_5.0.0_softdevice.hex and SDK 14.1.0 bootloader, and then run generate_pkg.bat under 278167_DFU_SDK14.1_to_SDK17\SDK_17.0.2 to generate the package. Update with this package.

Regarding the hardware version error, Please kindly answer the following questions to help me understand more about your issue.

Are you using SDK 14.1.0 bootloader example? If it is the modified bootloader, what do you modify?

Can you provide the debug log on the device?

-Amanda

RE: DFU Failure updated from SDK14.1 to SDK17

Dave_couling — Tue, 26 Oct 2021 16:44:05 GMT

Unfortunately your DFU Package does not work either, with a "Cannot read property 'asynch' of null" Error

RE: DFU Failure updated from SDK14.1 to SDK17

Dave_couling — Tue, 26 Oct 2021 16:41:24 GMT

Could you provide a test file that is just the SD1327.2 and the SDK17.0.2 bootloader?

RE: DFU Failure updated from SDK14.1 to SDK17

Amanda Hsieh — Tue, 26 Oct 2021 08:38:40 GMT

Hi,

Do you program s132_nrf52_5.0.0_softdevice.hex and SDK 14.1.0 bootloader on nRF52DK to update with the package with s132_nrf52_7.2.0_softdevice, SDK 17.0.2 bootloader and app? If so, I cannot reproduce the issue with the command provided by me. Here is my test file. devzone.nordicsemi.com/.../278167_5F00_DFU_5F00_SDK14.1_5F00_to_5F00_SDK17.zip

Are you using SDK 14.1.0 bootloader example? If it is the modified bootloader, what do you modify?

Can you provide the debug log on the device?

-Amanda

RE: DFU Failure updated from SDK14.1 to SDK17

Dave_couling — Mon, 25 Oct 2021 17:13:50 GMT

Yes I used the --hw-version 52 as your instructed. However I still get the same error as seen in my original post

RE: DFU Failure updated from SDK14.1 to SDK17

Amanda Hsieh — Mon, 25 Oct 2021 07:50:13 GMT

Hi,

Good to know you fix the command issue.

Do you use "--hw-version 52" in the command? In your last command, I see the hw version config is wrong.

-Amanda

RE: DFU Failure updated from SDK14.1 to SDK17

Dave_couling — Wed, 20 Oct 2021 16:48:58 GMT

Re-installing Python 3.7 seemed to fix this particular error. However when I try and upload the *.zip file I get the error shown in my original post. Any ideas?

RE: DFU Failure updated from SDK14.1 to SDK17

Dave_couling — Wed, 20 Oct 2021 16:45:02 GMT

Thanks for the reply, but I get the same error. Error: no such option: --sd-id

RE: DFU Failure updated from SDK14.1 to SDK17

Amanda Hsieh — Wed, 20 Oct 2021 06:50:52 GMT

Hi,

Try this:

nrfutil pkg generate --hw-version 52 --key-file dfu_private.pem --application-version 2 --application "C:\Application_Firmware\custom_board\s132\armgcc\_build\nrf52832_xxaa.hex" --sd-req 0x9D --sd-id 0x0101 --softdevice "C:\SDK_17\components\softdevice\s132\hex\s132_nrf52_7.2.0_softdevice.hex" --bootloader-version 2 --bootloader "C:\Bootloader_Firmware\s132_ble\armgcc\_build\nrf52832_xxaa_s132.hex" SD_APP_BOOT_Package.zip

-Amanda

RE: DFU Failure updated from SDK14.1 to SDK17

Dave_couling — Tue, 19 Oct 2021 23:30:14 GMT

nrfutil pkg generate --hw-version 2 --key-file "dfu_private.pem" -application-version 2 "C:\Application_Firmware\custom_board\s132\armgcc\_build\nrf52832_xxaa.hex" --sd-req 0x9D --sd-id 0x0101 --softdevice "C:\SDK_17\components\softdevice\s132\hex\s132_nrf52_7.2.0_softdevice.hex" --bootloader-version 2 --bootloader "C:\Bootloader_Firmware\s132_ble\armgcc\_build\nrf52832_xxaa_s132.hex" SD_APP_BOOT_Package.zip

RE: DFU Failure updated from SDK14.1 to SDK17

Amanda Hsieh — Tue, 19 Oct 2021 06:03:01 GMT

Hi,

[quote user="Dave_couling"]I've tried the --sd-id command, however nrfutil rejects this command with the following error: Error: no such option: --sd-id[/quote]

Can you post the command?

-Amanda

RE: DFU Failure updated from SDK14.1 to SDK17

Dave_couling — Mon, 18 Oct 2021 17:06:23 GMT

Yes I am trying to update the S132v5 to S132 V7

I've tried the --sd-id command, however nrfutil rejects this command with the following error: Error: no such option: --sd-id

I'm using nrfutil version: 6.1.0

RE: DFU Failure updated from SDK14.1 to SDK17

Amanda Hsieh — Mon, 18 Oct 2021 11:18:39 GMT

Hi,

Are you updating from s132_nrf52_5.0.0 to s132_nrf52_7.2.0? If so, see DFU package combinations:

However, the two SDs may have different 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.

[quote user=""]nrfutil pkg generate --hw-version 2 --key-file legacy_dfu_private.pem --sd-req 0x9D --softdevice s132_nrf52_7.2.0_softdevice.hex --bootloader-version 2 --bootloader new_bootloader_nrf52832_xxaa_s132.hex SD_BOOT_Package.zip[/quote]

Try to add --sd-id 0x0101.

Regards,
Amanda