Generate package to migrate SD+BL+APP from SDK15 to SDK17

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

Hung Bui — Thu, 18 Feb 2021 11:12:42 GMT

Hi Pedro,
Please try testing again using stock images (bootloader and apps)
I tested here and got no problem upgrade to SDK 17 app.
You may want to try debugging the bootloader to see if anything wrong.
I attached here the file I used. My test's steps:
1. Flash bootloader+SDK v15.2

2. DFU update app_SDK15.zip

3. DFU update sd_bl_SDK17.zip

4. DFU update app_SDK17.zip

After step 4 the device works as expected.
devzone.nordicsemi.com/.../DFU_5F00_SD_5F00_BL_5F00_18Feb.zip

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

prodrigues — Wed, 17 Feb 2021 14:37:52 GMT

Hi Hung,

[quote userid="2121" url="~/f/nordic-q-a/71576/generate-package-to-migrate-sd-bl-app-from-sdk15-to-sdk17/294874#294874"]If you do it manually (2 .zip files, one SD+BL and one APP) would it work ? [/quote]

No, I have the same problem. BL+SD dfu returns success popup and advertises as bootloader. APP, DFU after BL+SD dfu returns success popup but the APP does not boot (stays in bootloader instead).

[quote userid="2121" url="~/f/nordic-q-a/71576/generate-package-to-migrate-sd-bl-app-from-sdk15-to-sdk17/294874#294874"]Please provide the log on the phone app and let us know the app version you are using. Have you tried both nRF Toolbox and NRF Connect ? [/quote]

Yes, tried with nRF Toolbox, same problem.

Bellow you may find attached the log of NRF Connect after a DFU of BL+SD+APP.

devzone.nordicsemi.com/.../Log-2021_2D00_02_2D00_17-14_5F00_24_5F00_01.txt

Edit:
Just tried the following:

Flashed SD+BL by merging hex files and using nrfjprog
performed DFU with the same APP Zip generated earlier for the 2 zip test and worked correctly.

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

Hung Bui — Wed, 17 Feb 2021 13:34:11 GMT

Hi Pedro,

If you do it manually (2 .zip files, one SD+BL and one APP) would it work ?
We need to look into why the DFU of the APP was not executed automatically.

Please provide the log on the phone app and let us know the app version you are using. Have you tried both nRF Toolbox and NRF Connect ?

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

prodrigues — Tue, 16 Feb 2021 16:19:51 GMT

Hi,
indeed the variable FLASH_START=0x78000 was differing in both bootloader projects. Now, after DFU with Soft Device + Bootloader the device advertises as the bootloader!

However, when performing DFU with full package the Application still does not start. Instead the bootloader starts.

What could still be wrong?

Thanks,
Pedro

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

Hung Bui — Tue, 16 Feb 2021 14:06:54 GMT

Hi Perdo,

Have you made sure the start address of the 2 bootloaders are the same ? I had a quick check here with the bootloader _debug version, the one in SDK v15.2 start at address 0x72000 when the one in SDK v17.0.2 starts at address 0x71000.

They should be the same.

I attached here the file I used for testing (it worked fine).
I used this script to generate the .zip file:

nrfutil pkg generate --hw-version 52 --sd-req 0xAF --sd-id 0x0101 --softdevice s132_nrf52_7.2.0_softdevice.hex  --bootloader-version 2 --bootloader Bootloader_SDK17.hex --key-file private.key sd_bl.zip

Please unzip this:
devzone.nordicsemi.com/.../DFU_5F00_SD_5F00_BL.zip

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

Hung Bui — Tue, 16 Feb 2021 10:48:35 GMT

Thanks Pedro. There could be a change in the bootloader setting.
I will try to test doing a DFU update here and let you know if I find something.

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

prodrigues — Tue, 16 Feb 2021 10:39:07 GMT

Hi Hung,

Haven't tried everything yet but here goes some preliminary info:

1 - Yes it advertises
2- No it does not advertise if I run:

nrfjprog --program Output/sd_bl.hex --sectorerase -r

It advertises if I run:

nrfjprog -e
nrfjprog --program Output/sd_bl.hex -r

So, what is the difference?

Thanks,
Pedro

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

Hung Bui — Tue, 16 Feb 2021 10:10:45 GMT

Hi Pedro,
Regarding the issue with Linux, what you reported (error 0x802a) similar to one of the case here. You may need to disable MSD to use nrfConnect on Linux.

I would suggest to try the following:

1. Flash the stock BL+SD of SDK v15.2. Verify that it's advertising.

2. Flash the stock BL+SD of SDK v17 to the same chip (do nrfjprog --program with --sectorerase) . Verify that the new bootloader is advertising.

3. Read flash out using nrfjprog --readcode

4. Erase the chip and Redo Step 1.

5. Do DFU update of BL+SD of SDK v17 .

6. If it's not advertising try read flash out using nrfjprog --readcode

7. Compare the 2 hex dump at step 3 and step 6. I usually use Notepad++ to compare.

Please send us your files (including the private keys and public keys, the .zip file, your bootloader and softdevice in SDK v15.2 ) so that we can test here.

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

prodrigues — Mon, 15 Feb 2021 17:35:31 GMT

Hi Hung,

More info:

When I first created the post I was only trying with nRFConnect on my Android phone. When trying with nRF connect on linux I get this error:

17:22:31.417	Performing DFU with file: /home/prodrig/Documents/git/ble5_firmware/Output/5.0.0/bl_sd.zip
17:22:32.458	Attribute value changed, handle: 0x10, value (0x): 01-00
17:22:32.492	Attribute value changed, handle: 0x0F, value (0x): 02-00-00
17:22:32.494	Attribute value changed, handle: 0x0F, value (0x): 60-02-01
17:22:32.546	Attribute value changed, handle: 0x0F, value (0x): 06-01
17:22:32.562	Attribute value changed, handle: 0x0F, value (0x): 60-06-01-00-01-00-00-00-00-00-00-00-00-00-00
17:22:32.592	Attribute value changed, handle: 0x0F, value (0x): 01-01-97-00-00-00
17:22:32.607	Attribute value changed, handle: 0x0F, value (0x): 60-01-01
17:22:34.150	Received status with code 4 Unknown value, message: 'Error sending packet to target. Code: 0x802a'
17:22:35.653	Received status with code 4 Unknown value, message: 'Error sending packet to target. Code: 0x802a'
17:22:37.155	DFU failed with error: When writing 'CREATE' command to Control Point Characteristic of DFU Target: Could not write CREATE command: Failed to write to attribute with handle: 15: Error occured when writing. Errorcode: Unknown value (0x8005) .
17:22:37.159	Received status with code 4 Unknown value, message: 'Error sending packet to target. Code: 0x802a'
17:22:38.660	Received status with code 4 Unknown value, message: 'Error sending packet to target. Code: 0x802a'

[quote userid="2121" url="~/f/nordic-q-a/71576/generate-package-to-migrate-sd-bl-app-from-sdk15-to-sdk17/294443#294443"]Please use nRF Connect and check if the device after updating the BL+SD if it runs as a Bootloader and advertises anything?[/quote]

No it does not advertise.

[quote userid="2121" url="~/f/nordic-q-a/71576/generate-package-to-migrate-sd-bl-app-from-sdk15-to-sdk17/294443#294443"]Any reason why your bootloader version in your script to generate the DFU package was "--bootloader-version 0 " ? [/quote]

That was wrong at the time of the post creation. After reading my old settings.hex I realized bootloader-version was 1. So I changed and I am now generating the packages with --bootloader-version 2.

[quote userid="2121" url="~/f/nordic-q-a/71576/generate-package-to-migrate-sd-bl-app-from-sdk15-to-sdk17/294443#294443"]Please try to do SD+BL and APP DFU update separately (2 zip files) before testing with one single .zip. [/quote]

Tried this. On nRF Connect from linux I had the same issue reported above. On my phone, It sent and in the end a popup appeared saying "Application has been sent successfully". But after that the device does not advertise as expected...

Thanks,
Pedro

RE: Generate package to migrate SD+BL+APP from SDK15 to SDK17

Hung Bui — Mon, 15 Feb 2021 15:53:13 GMT

Hi Pedro,

Please use nRF Connect and check if the device after updating the BL+SD if it runs as a Bootloader and advertises anything?

Any reason why your bootloader version in your script to generate the DFU package was "--bootloader-version 0 " ?
Usually the bootloader doesn't allow update to lower or the same bootloader version.
Please try to do SD+BL and APP DFU update separately (2 zip files) before testing with one single .zip.