Secure bootloader example doesn't build

RE: Secure bootloader example doesn't build

JGusler — Thu, 13 Oct 2022 14:16:35 GMT

Using SES 5.42a with a clean copy of the entire secure bootloader folder worked immediately

RE: Secure bootloader example doesn't build

Einar Thorsrud — Thu, 13 Oct 2022 14:00:38 GMT

[quote user="JGusler"]Maybe the build_all.bat file pulled them in[/quote]

Yes, it does. Then this part is OK.

RE: Secure bootloader example doesn't build

JGusler — Thu, 13 Oct 2022 13:56:58 GMT

Every single file in that repo I am looking at right now in the sdk under sdk/external/micro-ecc/micro-ecc

Maybe the build_all.bat file pulled them in

RE: Secure bootloader example doesn't build

Einar Thorsrud — Thu, 13 Oct 2022 13:52:42 GMT

Not sure what you mean, but micro-ecc does not ship with the SDK. That is why you have these instructions that I linked to.

RE: Secure bootloader example doesn't build

JGusler — Thu, 13 Oct 2022 13:51:26 GMT

The whole thing already exists in the SDK, all the files from the repo, in the micro-ecc folder

RE: Secure bootloader example doesn't build

Einar Thorsrud — Thu, 13 Oct 2022 13:42:42 GMT

You don't need to modify the sample, it builds right out of the box. So there is something else wrong here. Did you remember to check out and build micro-ecc as explained under Installing micro-ecc?

RE: Secure bootloader example doesn't build

JGusler — Thu, 13 Oct 2022 13:34:47 GMT

Ah, the pca10056_s140_ble project. I added the following includes to nrf_dfu_validation.c to remove a bunch of errors

#include "nrf_crypto_ecc.h"
#include "nrf_crypto_ecdsa.h"
#include "nrf_crypto_hash.h"

I then had to remove the size limitation for .text and .rodata in the flash_xml (not a new issue)

Now I'm just getting issues in nrf_crypto_ecc.o and ecdsa.o that all also mention some location in .rodata

RE: Secure bootloader example doesn't build

Einar Thorsrud — Thu, 13 Oct 2022 13:16:56 GMT

[quote user="JGusler"]The project "secure bootloader".[/quote]

There are many example projects under this folder (different configurations, different toolchains and different ICs). Which exact project are you using?

[quote user="JGusler"]I'm using version 6.34a at them moment.[/quote]

I saw that in the log. Please revert to SES 5.42a just to have a know base. That is used for release testing this SDK release and the projects will build out of the box, if not, there is a high likelihood that there is an error with your setup or that you have modified something in the SDK by accident (which is why I suggested to extract a fresh copy of the whole SDK, not just the bootloader project)

RE: Secure bootloader example doesn't build

JGusler — Thu, 13 Oct 2022 13:00:55 GMT

The project "secure bootloader". I'm using version 6.34a at them moment. Okay, I'll start messing with this then just to get it to work, I didn't want to while it was 'supposed to work'

RE: Secure bootloader example doesn't build

Einar Thorsrud — Thu, 13 Oct 2022 08:50:41 GMT

I see. Which exact example project are you using? Also note that you should expect some issues (though not these) if you use a too recent Segger Embedded Studio version. SDK 17.1.0 was release tested using SES 5.42a, so I suggest you try to build with that first to limit the number of unknowns. (You can always port the project to a newer release later).

RE: Secure bootloader example doesn't build

JGusler — Wed, 12 Oct 2022 14:11:04 GMT

Okay so I built and compiled it, added the nrf52hf uECC lib to my project, enabled the corresponding backends and disabled the others, added micro-ecc/micro-ecc to the common preprocessor defines, all with a fresh copy of the secure bootloader example, and I'm still getting those errors

RE: Secure bootloader example doesn't build

JGusler — Wed, 12 Oct 2022 13:08:23 GMT

Oh, I built but didnt compile, I'm stupid. You can delete this ticket

RE: Secure bootloader example doesn't build

Einar Thorsrud — Wed, 12 Oct 2022 08:03:31 GMT

I am not able to explain this without more information. All example bootloaders for other devices than the nRF52840 use micro-ecc by default, and as long as you have checked out and built mico-ecc as explained under Installing micro-ecc, it builds out of the box. Which exact example project are you using? And have you made any other changes in the SDK files? Can you try to download a fresh copy of the SDK, clone and build micro-ecc, and then see what happens?