Flashing bootloader, softdevice and application issue

RE: Flashing bootloader, softdevice and application issue

Edvin — Thu, 25 Feb 2021 12:37:52 GMT

I am not sure whether using the private key is actually necessary when generating bootloader settings with the default settings in the bootloader (but I tend to include it). When testing these things, I suggest using scripts like the one attached earlier. It saves you a lot of time, and it ensures that you are testing the same every time (it is very easy to forget a step or two). If you want to use Segger Embedded Studio instead of the armgcc makefile, just replace the application .hex file that I copied into files\buttonless_app.hex.

Best regards,

Edvin

RE: Flashing bootloader, softdevice and application issue

PauDC — Thu, 25 Feb 2021 11:04:43 GMT

Thank you for this information.

This mixed with your previous reply solved the problems and my doubts.

Best regards,

Pau

RE: Flashing bootloader, softdevice and application issue

PauDC — Thu, 25 Feb 2021 11:03:36 GMT

Hello Edvin,

I was able to flash everything thanks to this answer.

The main difference I see between what you posted and what I did is that when creating the bootloader settings I didn't add the private key.

I will test more to see if this was the only reason my script was failing.

Thank you very much,

Best regards.

Pau

RE: Flashing bootloader, softdevice and application issue

Edvin — Mon, 22 Feb 2021 13:49:31 GMT

[quote user="PauDC"]I created a new folder in which I only copied the softdevice.hex, bootloader.hex and application.hex. Is this a bad practice? Could this be my mistake?[/quote]

That is fine, as long as you remember to update them. Remember that whenever you change the smallest detail in the application, it results in a new .hex file, which you need to generate a new set of settings for. You can see in the script that I delete and always copy the latest application to be flashed into the folder "files".

Please also note that you can flash the files using nrfjprog (the order doesn't matter). But if you try to debug in SES, then SES will upload a modified version of the .hex file, so the CRC will not match with the bootloader settings anymore. If you need to debug the application after you have programmed a bootloader, you should use the option: Target -> Attach Debugger:

Which will hook onto the debugger without flashing anything. In order for this to work, you need to make sure that the nRF is manually flashed with the very latest application compile.

But before you test the debugging part, make sure that you have uploaded the bootloader settings.

BR,
Edvin

RE: Flashing bootloader, softdevice and application issue

PauDC — Mon, 22 Feb 2021 08:50:35 GMT

Hello Edvin,

Thanks for your reply. I still have to test the script you attached. But I've read and analysed the rest of your reply and I have a few doubts and comments.

Q: When you merged the bootloader settings and the bootloader, did you also program that application?
A: I did in one of my trials. I also tried merging all my .hex files into one calling mergehex several times. These things didn't work, so I started from the beginning, trying to make the settings and bootloader work.

"- Replaced the dfu_public_key.c in the original location in the sdk with your personal private key.
- installed the "make" toolchain. If you are using an IDE, please compile the projects up front, and change the paths in the attached scripts. "

I did replace the key. I'm using Segger Studio as my IDE.
I created a new folder in which I only copied the softdevice.hex, bootloader.hex and application.hex. Is this a bad practice? Could this be my mistake?

Where can I find the softdevice ID? I'm asking this because I'm still using sdk 17.0.0. I found this post and I've opened the 3 files I found on tesc's answer and wasn't able to find any code similar to the one you mentioned in your notes.

Lastly, when you say
"Please note that I flash all 4 .hex files: Softdevice, Bootloader, Application and Bootloader Settings. You can merge them and program them all in one, if you like."

Do you specifically flash them in that order? Is the flashing or merging order relevant?

Best regards,

Pau

RE: Flashing bootloader, softdevice and application issue

Edvin — Fri, 19 Feb 2021 11:35:39 GMT

Can you describe what you did? If you are stuck, please try the pca10040_debug bootloader project, and monitor the RTT log. What does it say?

Did you program all the 4 files: Bootloader, Softdevice, application and bootloader settings?

Can you show me how you did it, and how you generated the bootloader settings?

Edit: I just noticed that this question was from teodf, and not the original poster. What did you do? What have you programmed on your DK? Are you using a DK? How do you perform the DFU? What is your DFU master? Are you using a phone, nRF Connect for iOS/Android? nRF Connect for Desktop? nrfutil?

BR,

Edvin

RE: Flashing bootloader, softdevice and application issue

teodf — Fri, 19 Feb 2021 09:45:23 GMT

Hi Edvin,

I arrive to flash all but my application never Start, there are just the two led of bootloader was light up.

You have a solution ?

RE: Flashing bootloader, softdevice and application issue

Edvin — Thu, 18 Feb 2021 14:54:21 GMT

Hello,

Creating these scripts is a good idea when working with a bootloader, because the bootloader will reject applications that are flashed without the correct bootloader settings.

So you are on the track of something. And you may merge the bootloader with the settings hex file, but that is not necessary. Just make sure you program them all.

Why your setup is currently not working, I am not sure. When you merged the bootloader settings and the bootloader, did you also program that application?

Let us take it from the start

Let us assume you have already:

- Replaced the dfu_public_key.c in the original location in the sdk with your personal private key.

- installed the "make" toolchain. If you are using an IDE, please compile the projects up front, and change the paths in the attached scripts.

If you copy the attached script into a .bat file (e.g. name it test.bat), place it in SDK17.0.2\examples\dfu\secure_bootloader\pca10040_s132_ble\armgcc and run it from a power shell or a command line, I believe it should work.

make -j9 
make -j9 -C ..\..\..\..\ble_peripheral\ble_app_buttonless_dfu\pca10040\s132\armgcc

set TARGET_SNR=682396787
set CONNECTIVITY_SNR=683963588

mkdir files

del files\bl_settings.hex
del files\buttonless_app.hex

copy ..\..\..\..\ble_peripheral\ble_app_buttonless_dfu\pca10040\s132\armgcc\_build\nrf52832_xxaa.hex files\buttonless_app.hex
nrfutil settings generate --family NRF52 --application files\buttonless_app.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 --key-file ..\..\..\private.key files\bl_settings.hex

nrfjprog -e --snr %TARGET_SNR%
nrfjprog --program ..\..\..\..\..\components\softdevice\s132\hex\s132_nrf52_7.2.0_softdevice.hex --verify --snr %TARGET_SNR%
nrfjprog --program _build\nrf52832_xxaa_s132.hex --verify --snr %TARGET_SNR%
nrfjprog --program files\buttonless_app.hex --verify --snr %TARGET_SNR%
nrfjprog --program files\bl_settings.hex --verify --snr %TARGET_SNR%
nrfjprog --reset --snr %TARGET_SNR%

:: if you want to also perform a DFU from another DK, uncomment the lines below, and make sure to set the serial numbers correctly.


::TIMEOUT 5

::nrfutil pkg generate --application files\buttonless_app.hex --application-version 2 --sd-req 0x0101 --hw-version 52 --key-file ..\..\..\private.key files\dfu_image_v2.zip
::nrfutil pkg generate --application files\buttonless_app.hex --application-version 3 --sd-req 0x0101 --hw-version 52 --key-file ..\..\..\private.key files\dfu_image_v3.zip
::nrfutil pkg generate --application files\buttonless_app.hex --application-version 4 --sd-req 0x0101 --hw-version 52 --key-file ..\..\..\private.key files\dfu_image_v4.zip
::nrfutil pkg generate --application files\buttonless_app.hex --application-version 5 --sd-req 0x0101 --hw-version 52 --key-file ..\..\..\private.key files\dfu_image_v5.zip


::nrfutil dfu ble -pkg files\dfu_image_v2.zip -ic NRF52 -snr %CONNECTIVITY_SNR% -n "Nordic_Buttonless"
::TIMEOUT 10
::nrfutil dfu ble -pkg files\dfu_image_v3.zip -ic NRF52 -snr %CONNECTIVITY_SNR% -n "Nordic_Buttonless"

Notes:

- Set the serial number of the programmer on your DK. The TARGET_SNR refers to the nRF52832 DK with the bootloader, and the CONNECTIVITY_SNR refers to the other DK that you will use to update the nRF52832 over the air.

- The softdevice ID of the S132 from SDK17.0.2 is 0x0101.

- Useful nrfutil commands:

nrfutil settings generate --help
nrfutil pkg generate --help
nrfutil dfu ble --help

Please note that I flash all 4 .hex files: Softdevice, Bootloader, Application and Bootloader Settings. You can merge them and program them all in one, if you like.

If you have reset the device after programming the bootloader but before programming the bootloader settings, add the flag --sectorerase to the nrfjprog command programming the bootloader settings.

Let me know if it doesn't work.

Best regards,

Edvin