Change softdevice version on DFU (sd version failure)

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Mon, 04 Mar 2024 20:49:39 GMT

[quote user="Andre N"]If I understand it correctly, it says I cant change the bootloader start address over DFU.
But you (and some other employee in another ticket) said otherwise.[/quote]

Sorry, I misunderstood your question.

I mean you can modify the bootloader address at the first/original bootloader on the device, and then use the same address for the later to update. The address of the bootloader cannot be updated over DFU as that note stated.

RE: Change softdevice version on DFU (sd version failure)

Andre N — Mon, 04 Mar 2024 20:15:36 GMT

Thanks!

you see in the link you sent me there is this in the bottom of the page.

If I understand it correctly, it says I cant change the bootloader start address over DFU.
But you (and some other employee in another ticket) said otherwise.

regarding the overlaps, i checked with nrfConnect Programmer and the allocated memory is way bigger than the actual used memory so i should be fine.

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Mon, 04 Mar 2024 19:58:05 GMT

Hi,

[quote user="Andre N"]Is it possible to move the addresses of mbr_params_page, bootloader_settings_page, and bootloader?[/quote]

If you use SES, you can modify the addresses of mbr_params_page and bootloader_settings_page in flash_placement.xml.

[quote user="Andre N"]i think i saw somewhere in this forum that we cant change bootloader address on DFU is that true?[/quote]

No, you can modify the Bootloader address by the FLASH_START in the SES bootloader project option.

Modifying those addresses might cause memory overlap errors. You have to handle it by yourself. Here is the Memory layout of the different chips with current SoftDevices.

-Amanda H.

RE: Change softdevice version on DFU (sd version failure)

Andre N — Fri, 01 Mar 2024 11:45:24 GMT

Hi again

Is it possible to move the addresses of mbr_params_page, bootloader_settings_page, and bootloader?
because i noticed that mbr_params_page and bootloader_settings_page have 1000 bytes reserved each but only use 300 each.

i noticed that if i reseve only the necessary space and move them up a bit, i should have enough space for my dfu.
i have already managed to move bootloader_settings_page but not mbr_settings_page
also i think i saw somewhere in this forum that we cant change bootloader address on DFU is that true?

regarding the crypto solution, security is not really a problem for this device. it is just a small sensor

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Fri, 23 Feb 2024 13:59:46 GMT

Hi,

I will not suggest you disable NRF_CRYPTO due to the security. To protect the target device against malicious attackers who try to impersonate the rightful sender of the firmware update, the init packet of the firmware package must be signed.

You could use the secure_bootloader without debug version to get the smaller size. If this still cannot help, I would suggest considering another nRF52 chip with large memory space.

-Amanda H.

RE: Change softdevice version on DFU (sd version failure)

Andre N — Fri, 23 Feb 2024 11:42:05 GMT

Hello
thx again for you help

I realised that i am only 4kB short in memory and so i tried to make a smaller bootloader.

I am wondering if i can disable NRF_CRYPTO because the bootloader would be 11KB instead of 22KB.

I tried disabling NRF_CRYPTO but i get this error between the two parts of the DFU:

Remote DFU error: INVALID OBJECT. SD busy? Retrying...

I assume the 1st part of the DFU is when we change the BL+SD and the 2nd part is when we change the APP.
I get the error after BL+SD are transfered.

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Wed, 14 Feb 2024 20:05:07 GMT

Hi,

[quote user="Andre N"]Is it possible to do a single bank OTA BLE DFU for the BL + SD?[/quote]

The figure in the Single-bank updates documentation illustrates the single-bank OTA BLE DFU for the BL + SD when there is an application. You need NRF_DFU_SINGLE_BANK_APP_UPDATES set to 1 in your bootloader's sdk_config.h.

You also can check the code nRF5_SDK_17.1.0_ddde560\components\libraries\bootloader\dfu\nrf_dfu_validation.c

[quote user="Andre N"]In the meantime im looking into dualbank DFU via external flash. that should work right?[/quote]

See this post.

-Amanda H.

RE: Change softdevice version on DFU (sd version failure)

Andre N — Tue, 13 Feb 2024 23:33:49 GMT

Hello
No problem.

I am already doing single bank updates (for the app)
Is it possible to do a single bank OTA BLE DFU for the BL + SD?

In theory it sounds impossible to me since i need the BL and SD to do it

In the meantime im looking into dualbank DFU via external flash. that should work right?

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Tue, 13 Feb 2024 18:20:05 GMT

Hi,

Sorry for the delay.

You could try the Single-bank updates. See Dual-bank and single-bank updates.

-Amanda H.

RE: Change softdevice version on DFU (sd version failure)

Andre N — Fri, 09 Feb 2024 10:56:00 GMT

Looking at the actual layout after flashing, (with app data and all those things)
The only space i have available for DFU is from 0x19000 to 0x35000
So i have 114688 bytes available and my new BL+SD is 130504
I assume i must flash both at the same time because i had to adjust BL parameters for this SD

Is it possible to optimise the current memory layout?
because the application data only takes a few bytes but is is allocating thousands of bytes
the same goes for mbr params and bootloader settings, they only need 800 bytes each but they are allocating 4096 each

RE: Change softdevice version on DFU (sd version failure)

Andre N — Fri, 09 Feb 2024 10:40:44 GMT

If i update SD only:
The sd is actually trasnfered but i get an error after transfer

If i update Bootloader + SD :
I get insufficient resources error
here is my memory layout

If i update Bootloader + SD + APP: i get SD version error

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Fri, 09 Feb 2024 06:33:50 GMT

Hi,

Could you try to test just only update SD / SD+BL / SD+BL+APP?
nrfutil pkg generate --hw-version 52 --sd-req 0x0103 --sd-id 0x0102 --softdevice s113_nrf52_7.2.0_softdevice.hex --key-file private.pem output_file.zip

nrfutil pkg generate --hw-version 52 --sd-req 0x0103 --sd-id 0x0102 --softdevice s113_nrf52_7.2.0_softdevice.hex --bootloader bootloader.hex --bootloader-version 3 --key-file private.pem output_file_1.zip

Are those packages uploaded successfully?

RE: Change softdevice version on DFU (sd version failure)

Andre N — Thu, 08 Feb 2024 19:44:39 GMT

On a phone app all i get is this: SD version failure (code = 7)

with pc-ble-driver-py and a dongle, i get this:

Traceback (most recent call last):
File "/home/andre/projects/debug-dfu_sd/main.py", line 56, in <module>
dfu.dfu_send_images()
File "/home/andre/projects/debug-dfu_sd/nordicsemi/dfu/dfu.py", line 124, in dfu_send_images
self._dfu_send_image(self.manifest.application)
File "/home/andre/projects/debug-dfu_sd/nordicsemi/dfu/dfu.py", line 95, in _dfu_send_image
self.dfu_transport.send_init_packet(data)
File "/home/andre/projects/debug-dfu_sd/nordicsemi/dfu/dfu_transport_ble.py", line 526, in send_init_packet
self.__execute()
File "/home/andre/projects/debug-dfu_sd/nordicsemi/dfu/dfu_transport_ble.py", line 607, in __execute
self.__get_response(DfuTransportBle.OP_CODE['Execute'])
File "/home/andre/projects/debug-dfu_sd/nordicsemi/dfu/dfu_transport_ble.py", line 682, in __get_response
raise NordicSemiException('Extended Error 0x{:02X}: {}'.format(resp[3], data))
pc_ble_driver_py.exceptions.NordicSemiException: Extended Error 0x07: The array of supported SoftDevices for the update does not contain the FWID of the current SoftDevice.

and i get this error when the old SD id is not included on --sd-id list.
i know it makes no sense. --sd-id is not even supposed to be a list of ids.

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Thu, 08 Feb 2024 19:40:43 GMT

Could you post the error log and command again?

RE: Change softdevice version on DFU (sd version failure)

Andre N — Thu, 08 Feb 2024 19:32:26 GMT

yes thats the version

i just retried that and i still get the error

also could it be linked to the bootloader settings file?
i never touched it but now we are changing the bootloader so maybe we should ?

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Thu, 08 Feb 2024 19:26:04 GMT

What is the SD version on the device now? Is it s112_nrf52_7.2.0? If so, try to set --sd-req 0x0103 and --sd-id 0x0102.

RE: Change softdevice version on DFU (sd version failure)

Andre N — Thu, 08 Feb 2024 19:16:35 GMT

exactly but i get the error when i do that too

if i put several id on --sd-req it is because the doc of nrfutil says i can do it (and im antecipating further updates)

here is a breakdown of how i create a package
nrfutil pkg generate
--hw-version 52
--sd-req 0x0103,0x0102        (id of current softdevice)
--sd-id 0x0102                       (id of new softdevice)
--softdevice s113_nrf52_7.2.0_softdevice.hex
--bootloader bootloader.hex
--bootloader-version 3           (bumped bootloader version)
--application myapplication.hex
--application-version 18         (bumped application version)
--key-file private.pem
output_file.zip

also it is weird that the error disapears if i include the ID of current softdevice on --sd-id and not on --sd-req
(again, the error disappears but the device doesnt work after the dfu)

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Thu, 08 Feb 2024 19:09:11 GMT

It 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. See this blog post for more details.

RE: Change softdevice version on DFU (sd version failure)

Andre N — Thu, 08 Feb 2024 18:36:49 GMT

Hi again.
I checked my bootloader and there was indeed a problem. i forgot to update the RAM on the linker file like i did on the application linker file.
And i couldnt see the RAM error beacause the logs ware deactivated on the bootloader
So now i dont have the insufficient resources problem anymore. Thanks for that

However, i still have the SD version error.
I have the same error everywhere (DFU app, nrfConnect app, pc-ble-driver + dongle)

this is the error i get:
Extended Error 0x07:
The array of supported SoftDevices for the update does not contain the FWID of the current SoftDevice.

it says the array of supported SD doesnt containt the current SD but as you can see, i did put both SD on my array:
--sd-req 0x0103,0x0102 as i said on my ticket

is this the right syntax?

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Tue, 30 Jan 2024 16:49:08 GMT

Hi,

Maybe you could try to move BL's start address a little back to get more free space for the updated package. Here is the Memory layout for SD+BL+APP. Although there is no one for nRF52820 s112/s113, it could give some inspiration.

-Amanda H.

RE: Change softdevice version on DFU (sd version failure)

Andre N — Tue, 30 Jan 2024 16:30:25 GMT

Hi
we are changing to s113 because we need to transfer data as fast as possible.
s113 is very close to our current SD but it supports Data packet length extension.
with s112 we are limited to 200kbps but with s113 we can reach 1000kbps.

We should have enough flash space though:
our old application APP 89044 + SD 98284 + BL 64000 (total 251328)
our new application APP 75556 + SD 107692 + BL 64000 (total 247248)

could it be related to RAM? because i had to change that too with the new SD

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Tue, 30 Jan 2024 15:38:52 GMT

Hi,

The error indicates that one or more of the new FW images are too big to fit in flash. Any special reason to update to s113? s112 is smaller than s113. You can check the release notes under nRF5_SDK\components\softdevice\s113\doc.

Maybe you could try the BL without debugging information to get a smaller size.

-Amanda H.

RE: Change softdevice version on DFU (sd version failure)

Andre N — Tue, 30 Jan 2024 10:25:29 GMT

I tested some other things and i am getting weird results.

- i tried to do a DFU with nrfConnect Desktop and i get a different error: "INSUFFICENT RESOURCES"

- i flashed my device with the example s113 secure bootloader and it seemed to work.
then i made a DFU package and the dfu fails with 'INSUFFICIENT RESOURCES' too
(it was just BL + SD, no APP)

RE: Change softdevice version on DFU (sd version failure)

Andre N — Mon, 29 Jan 2024 21:55:00 GMT

Thanks

I just tested this and indeed the device doesnt advertise. it kinda looks like it keeps rebooting
I just changed the softdevice on my bootloader's makefile and got this.

Does this mean that i just forgot to change some things? like the linker script?

Does this mean that my this SD is not compatible with the BL and i will never be able to change it ?

RE: Change softdevice version on DFU (sd version failure)

Amanda Hsieh — Mon, 29 Jan 2024 21:04:15 GMT

You could program the SD and BL on the board to see if they can work together as expected or not.