Upgrade from s140 to s340

RE: Upgrade from s140 to s340

Aftab — Fri, 29 Nov 2024 12:47:43 GMT

Found the solution of it by:

First upload the modified bootloader (only) file
Upload the modified bootloader + new SD + new app

To create new bootloader package this command is used: nrfutil pkg generate --bootloader bootloader.hex --bootloader-version 1 --hw-version 52 --sd-req 0x00 --key-file private.pem dfu_bootloader_package.zip

To create new BL+SD+APP package, this command is used: nrfutil pkg generate --bootloader bootloader.hex --bootloader-version 2 --application app.hex --application-version 2 --application-version-string "1.0.0" --hw-version 52 --sd-req 0x00 --sd-id 0xB9 --softdevice ANT_s340_nrf52840_6.1.1.hex --key-file private.pem Converter_package.zip

This process was done to convert normal BLE (SD = s140_nrf52_7.0.1_softdevice.hex) devices into ANT capable devices (SD = ANT_s340_nrf52840_6.1.1.hex).

The new bootloader changes were as follows:

Removed the softdevice compatibility to make s340 work
NRF_DFU_APP_ACCEPT_SAME_VERSION 0, to accept firmware with different version
NRF_DFU_APP_DOWNGRADE_PREVENTION 0 for ANT/BOOST
#define NRF_DFU_EXTERNAL_APP_VERSIONING 0 for ANT/BOOST

RE: Upgrade from s140 to s340

Aftab — Thu, 06 Jun 2024 14:51:08 GMT

[quote userid="4240" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486896"]

Aftab said:
When writing 'CREATE' command to Control Point Characteristic of DFU Target: Operation code 1 (CREATE) failed on DFU Target. Result code 3 (INVALID_PARAMETER).

It's difficult to say as the error does not say what the parameters were. When do you experience this, and are you still using the built-in DFU library in the nRF Connect for desktop app?

[/quote]

It happens when I try to upload the bl+sd (340) + app bundle/zip file, here is the log:

https://drive.google.com/file/d/1eJsnySkHJa9xZuJbk6xhsGh439tM3vFA/view?usp=sharing

Before this, I upload the modified bootloader (s140 based) zip file which uploads correctly on a non-modified s140 bootloader. I could see the modified advertising name of the device. That means the required bootloader upgrade was complete.

RE: Upgrade from s140 to s340

Vidar Berg — Fri, 31 May 2024 12:17:42 GMT

[quote user="Aftab"]When writing 'CREATE' command to Control Point Characteristic of DFU Target: Operation code 1 (CREATE) failed on DFU Target. Result code 3 (INVALID_PARAMETER).[/quote]

It's difficult to say as the error does not say what the parameters were. When do you experience this, and are you still using the built-in DFU library in the nRF Connect for desktop app?

[quote user="Aftab"]The old bootloader advertised with name DfuTarg, the new one is with Dfu_ABCD_X, does this affect anything? Also if I with download the bootloader onto barebone device, it quickly starts advertising. Not sure what is missing[/quote]

I need more information to speculate where it might be failing. Are you able to attach a debugger to the target?

RE: Upgrade from s140 to s340

Aftab — Fri, 31 May 2024 09:25:23 GMT

What causes this error?

When writing 'CREATE' command to Control Point Characteristic of DFU Target: Operation code 1 (CREATE) failed on DFU Target. Result code 3 (INVALID_PARAMETER).

RE: Upgrade from s140 to s340

Aftab — Fri, 31 May 2024 07:27:33 GMT

The old bootloader advertised with name DfuTarg, the new one is with Dfu_ABCD_X, does this affect anything? Also if I with download the bootloader onto barebone device, it quickly starts advertising. Not sure what is missing here.

RE: Upgrade from s140 to s340

Vidar Berg — Fri, 31 May 2024 07:21:40 GMT

Yes, but you were not getting the NRF_DFU_RES_CODE_INSUFFICIENT_RESOURCES error on your last attempt either.

RE: Upgrade from s140 to s340

Aftab — Fri, 31 May 2024 07:20:03 GMT

The build does not fail with the flash_placement.xml file you provided

RE: Upgrade from s140 to s340

Vidar Berg — Fri, 31 May 2024 07:15:08 GMT

There was an error in the linker configuration for the bootloader in SDK 16 that allowed the bootloader code to grow into the MBR param and BL settings page without raising any errors at link time..

You can replace your flash_placement.xml with the one attached below to ensure that the build will fail if your bootloader becomes too big.

devzone.nordicsemi.com/.../8688.flash_5F00_placement.xml

RE: Upgrade from s140 to s340

Aftab — Fri, 31 May 2024 07:07:32 GMT

SDK v16.0

RE: Upgrade from s140 to s340

Vidar Berg — Fri, 31 May 2024 07:05:49 GMT

Bootloader updates always require a higher version number. The bootloader will not accept a bootloader update of the same version or lower, and the error response if the version requirement is not met should be NRF_DFU_RES_CODE_EXT_ERROR + NRF_DFU_EXT_ERROR_FW_VERSION_FAILURE.

NRF_DFU_RES_CODE_INSUFFICIENT_RESOURCES should only be returned if the data object is too big or if the new bootloader is too big to fit in the allocated bootloader region.

Which SDK version are you on?

RE: Upgrade from s140 to s340

Aftab — Thu, 30 May 2024 13:32:32 GMT

These the project settings of both the bootloaders, they are same:

Old bootloader
FLASH_PH_START=0x0
FLASH_PH_SIZE=0x100000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x40000
FLASH_START=0xf8000
FLASH_SIZE=0x6000
RAM_START=0x20005968
RAM_SIZE=0x3a698

New bootloader
FLASH_PH_START=0x0
FLASH_PH_SIZE=0x100000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x40000
FLASH_START=0xf8000
FLASH_SIZE=0x6000
RAM_START=0x20005968
RAM_SIZE=0x3a698

RE: Upgrade from s140 to s340

Vidar Berg — Thu, 30 May 2024 13:18:39 GMT

[quote userid="76817" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486683"]Result code 4 (INSUFFICIENT_RESOURCES[/quote]

This suggests that the new bootloader has a different start address in flash. Please ensure all the bootloaders you are using are linked to the same start address. Using different start address will either cause the bootloader to reject the update with the INSUFFICIENT_RESOURCES error, or accept the update and cause the device to become bricked.

RE: Upgrade from s140 to s340

Aftab — Thu, 30 May 2024 13:17:58 GMT

I changed the --bootloader-version 1 to --bootloader-version 2, it caused the bootloader to upload successfully but device stops advertisement and cannot be scanned even after power cycle.

RE: Upgrade from s140 to s340

Aftab — Thu, 30 May 2024 13:14:14 GMT

Sorry, this is the command with which I generate the bootloader file:

nrfutil pkg generate --bootloader bootloader.hex --bootloader-version 1 --hw-version 52 --sd-req 0xB9 --sd-id 0xCA --key-file private.pem FW_Hotshot_hv_fv_bootloader_only.zip

When I try to upload this file, it gives me error:

DFU failed with error: When writing 'EXECUTE' command to Control Point Characteristic of DFU Target: Operation code 4 (EXECUTE) failed on DFU Target. Result code 4 (INSUFFICIENT_RESOURCES).

RE: Upgrade from s140 to s340

Vidar Berg — Thu, 30 May 2024 13:03:32 GMT

[quote userid="76817" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486677"]This is the command:[/quote]

This creates a combined sd+bl+app update, not BL only.

[quote userid="76817" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486677"]The intermediate bootloader plus s340 softdevice uploads successfully but after power cycle, the device cannot be scanned.[/quote]

The intermidate bootloader was to allow the s340 to be updated in the first place. The S340 SoftDevice, bootloader, and app can be updated after updating to the intermediate bootloader.

RE: Upgrade from s140 to s340

Aftab — Thu, 30 May 2024 12:54:34 GMT

This is the command:

nrfutil pkg generate --bootloader bootloader.hex --bootloader-version 1 --application app.hex --application-version 2 --application-version-string "2.0.0" --hw-version 52 --sd-req 0xB9 --sd-id 0xCA --softdevice s140_nrf52_7.0.1_softdevice.hex --key-file private.pem FW_Hotshot_hv_fv_3_files.zip

[quote userid="4240" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486667"]The intermediate bootloader does not need to be compatible with the S340 API (the S140 SoftDevice will be present on the DFU target at this point), as the new bootloader for S340 should be updated along with the S340 SoftDevice.[/quote]

The intermediate bootloader plus s340 softdevice uploads successfully but after power cycle, the device cannot be scanned.

[quote userid="4240" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486646"]You mean s340 based application + the S340 Softdevice? This will only work if the bootloader currently present on your device has been patched to allow the Softdevice variant to be changed.[/quote]

Exactly what changes are required in this case?

RE: Upgrade from s140 to s340

Vidar Berg — Thu, 30 May 2024 12:33:32 GMT

[quote userid="76817" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486664"]I tried that and it gives error 3, INVALID PARAMETER error.[/quote]

This should work. Maybe there was an issue with the init command. Can you show the nrfutil command you used to create this update?

[quote userid="76817" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486664"]That was the original idea, I previously did many things including re-compiling the bootloader against the s340 API headers (details here: BLE Bootloader example). This helped me device advertise with DfuTarg name. But uploading the s340 based app again gives error 3 INVALID_PARAMETER.[/quote]

The intermediate bootloader does not need to be compatible with the S340 API (the S140 SoftDevice will be present on the DFU target at this point), as the new bootloader for S340 should be updated along with the S340 SoftDevice.

RE: Upgrade from s140 to s340

Aftab — Thu, 30 May 2024 12:27:56 GMT

[quote userid="4240" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486646"]So, isn't it sufficient to only upgrade the bootloader in the intermdiate step?[/quote]

I tried that and it gives error 3, INVALID PARAMETER error.

[quote userid="4240" url="~/f/nordic-q-a/111644/upgrade-from-s140-to-s340/486646"]Can you attach a debugger to the board to find out if the program may have crashed, or does it continue to advertise?[/quote]

I haven't attached debugger yet bit it does not advertise any longer.

That was the original idea, I previously did many things including re-compiling the bootloader against the s340 API headers (details here: BLE Bootloader example). This helped me device advertise with DfuTarg name. But uploading the s340 based app again gives error 3 INVALID_PARAMETER.

RE: Upgrade from s140 to s340

Vidar Berg — Thu, 30 May 2024 11:29:52 GMT

Hello,

[quote user=""]Before uplaoding the s340 based app, there is an intermediate step where I upload s140 based app but with modified bootloader which allows the s340 based app to be uploaded. The s140 bootloader by default does not allow to firmware to be replaced by an s340 based app. It i son this step where I'm facing problems.[/quote]

Maybe I'm forgetting some details, but my recollection is that this limitation only applied to the SoftDevice, not the app. The bootloader has no way of knowing what SoftDevice an app upgrade was built for. So, isn't it sufficient to only upgrade the bootloader in the intermdiate step?

[quote user=""]I am using the same bootloader project as before and following the same steps. But the first half of upload is complete (bl+sd), the app.hex does not upload. The nRFConnect app gets stuck after bl+sd upload successful and then gives time out error.[/quote]

Can you attach a debugger to the board to find out if the program may have crashed, or does it continue to advertise?

[quote user=""]SN: Is there a way to directly replace an s140 based app to s340 one?[/quote]

You mean s340 based application + the S340 Softdevice? This will only work if the bootloader currently present on your device has been patched to allow the Softdevice variant to be changed.

Best regards,

Vidar