DFU from S110 (V7.1.0) to S130 (V2.0.1)

[jtredez]

Hello,

I have a device that use a NRF51822 with softdevice S110 V7.1.0 with the corresponding bootloader.

The new firmware I develop for this device is base on softdevice S130 V2.0.1 with the corresponding bootloader.

Now I would like to perform a DFU from the old software (S110 V7.1.0) currently running in production to the new one (S130 V2.0.1).

I generate a DFU package (zip file) with the new bootloader+firmware+softdevice.

I modify the two .dat files into the package to have only the CRC in 2 bytes (with this I have a CRC error).

I use nRF Toolbox to perform the DFU but I receive a "NOT SUPPORTED" response.

I have put a breakpoint into the booloader at the both places where I found the "NRF_ERROR_NOT_SUPPORTED" (in dfu_image_size_set() when the size is not multiple of 4 and in nrf_error_to_dfu_resp_val()) but I never enter into this case.

So my question is where this error come from? (is it from the softdevice?)

And more generaly is it possible to upgrade everything (bootloader+application+softdevice) with the old S110 V7.1.0 to the new S130 V2.0.1?

Thank you

Best regards

[tesc]

Hi,

It should be possible to upgrade up to SDK 11 and s130 v2.0.1. (Unfortunately it is not possible to upgrade from the bootloader in SDK 11 to the one in SDK 12, because then the size of the bootloader is increased. See the thread DFU - Updating from Legacy(SDK v11.0.0) Bootloader to SEcure(SDK v12.x.0) Bootloader.)

What SDK version is the old project based on?

What SDK version is the new project based on?

If you go from SDK 7.0 the init packet is required, and you can have a look at How to generate the INIT file for the DFU, which dates from that time.

I am not sure if a direct upgrade from SDK 7 to SDK 11 is possible, as I have not tried it before. I.e. you may need to do things in a specific order, or in two (or more) consecutive updates. I suggest that you try to:

1) Upgrade SD+BL+app to an example (or to the same app) based on the same SDK, just to confirm that you do everything correctly.

2) Upgrade SD + BL to SDK 11. If that works, consider a two-step process where you first upgrade SD and BL to SDK 11, then using the SDK 11 bootloader upgrade to the SDK 11 version of the app.

We are getting close to christmas, and many have already left for vacation. This means you may get delayed responses from Nordic employees for the next couple of weeks. I am sorry for any inconvenience. (I will leave at the end of this week, and will be back in office January 7.)

Note that since this is a public thread, other DevZone users may choose to help.

If at any time you need to share confidential information then you must either open a new private ticket (and refer to this thread) or request for this thread to go private.

Regards,
Terje

[jtredez]

Hi,

Sorry for the delay, I'm in vacation.

The OLD use a SoftDevice 110 version 7.1.0 with SDK 7.1.0. The new use SoftDevice 130 version 2.0.1 with SDK 12.3.0.

Given your comment I see it's not possible to upgrade bootloader from legacy to secure . An idea (not tested) to get around the problem, I have the source code of the secure bootloader, I can create a function which contains a call to the real (secure) bootloader start and set the address of this function (with the linker) to the old start of legacy bootloader (the UICR value), what do you thonk about this? (not sure it's compatible with the flashing of the application after).

1) I have made some tests, with the same bootloader, firmware, SDK and softdevice:

1.1) Only the application: package generated with nrfutil -> FAIL, I have the start DFU, next display 0% and nothing more. After I edit the .dat file inside the .zip to only have the CRC -> SUCCESS.

1.2) Only SD+BL: two packages, one generated with nrfutil and the same but with only the CRC in .dat file -> both FAIL with NOT SUPPORTED fail in start_data_process() p_evt->evt.ble_dfu_pkt_write.len = 0x0C.

Regards,

Jerome

[tesc]

Hi,

Sorry, I have been on vacation as well and returned yesterday.

You come with an interesting suggestion there, but I am afraid it is not that simple and that road is full of pitfalls.

It should however be very easy to port the bootloader from SDK 11 to use SoftDevice s130 v2.0.1. That way you can use the legacy bootloader, but with SDK 12.3.0 based firmware. I would highly recommend that path. The upgrade would then be two steps: First, DFU to SDK 11 bootloader and s130 v2.0.1. Second, DFU of new application.

Regards,
Terje

[jtredez]

Hi,

Thank for your comment about the possibility to use SDK 12.3.0.

But about my DFU test I have made. SD+BL return not supported and DFU application with nrf util package fail?

Thank you

[tesc]

Hi,

What is the commands that you use with nrfutil, both for generating the packages and for performing the DFU?

What version of nrfutil are you on?

Regards,
Terje

[jtredez]

Hi,

nrfutil version 4.0.0

The command for only application:

nrfutil pkg generate --hw-version 51 --sd-req 0xFFFE --application-version 0xFFFFFFFF --key-file private.key --application buzz_telec.hex RemoteV1_APP.zip

And for SD+BL:

nrfutil pkg generate --hw-version 51 --sd-req 0xFFFE --bootloader-version 0xFFFE --sd-id 0x87 --key-file private.key --bootloader bootloaderMonoBankQuartz.hex --softdevice s110_nrf51822_7.1.0_softdevice.hex RemoteV1_SD_BT.zip

Regards,

Jerome

[tesc]

Hi,

If you use the legacy bootloader (SDK 11 and earlier) then you need to use version 0.5.2 of nrfutil. (This is stated in the readme of the most recent version. The reason is that the DFU package format changed between SDK 11 and 12.) With that version the DFU packages should work fine.

Regards,
Terje

[jtredez]

Hi,

I have switched to version 0.5.2.

For only the application I have the "Invalid CRC Error" at the end of the DFU and for the SD+BL I have "Not Supported".

The command I use to generate the package are:

nrfutil.exe dfu genpkg RemoteV1_APP.zip --application buzz_telec.hex --application-version 0xffffffff --dev-revision 0xffff --dev-type 0xffff --sd-req 0xfffe

nrfutil.exe dfu genpkg RemoteV1_SD_BT.zip --bootloader bootloaderMonoBankQuartz.hex --softdevice s110_nrf51822_7.1.0_softdevice.hex --dev-revision 0xffff --dev-type 0xffff --sd-req 0xfffe

To perform the DFU I use the nRF Toobox on Android phone. The software version is 2.6.0.

Regards

[jtredez]

Hi,

Did you have another idea about my problem or something I can check?

Regards

[tesc]

Hi,

Yes, sorry. I talked to a colleague and dug a little deeper.

It turns out SDK 7.1 is so far back that things were a bit different. You must have a look at the documentation from SDK 7.1 and use scripts from that SDK release, in order to use the bootloader from that SDK to update. You can do a BL+SD update ("SdAndBl"), and from what I understand you should be able to do a direct update to the SDK 11 based bootloader. I highly recommend to first try and upgrade from the SDK 7.1 BL+SD to the same BL+SD (just with new version numbers) in order to confirm you are doing it right, though.

Regards,
Terje

[jtredez]

Hi,

The problem is that for the update we will use a mobile phone (Android or iOS) with the sdk that you provide, so a python script is not usable.

Maybe it's better to develop the new application to this old Softdevice.

Regards,

Jerome