Programming bootloader with segger studios?

[Luke.L]

I am going through the steps for building a secure bootloader

https://devzone.nordicsemi.com/b/blog/posts/getting-started-with-nordics-secure-dfu-bootloader

However I couldn't find the

B1. Compile the uECC library.

Step for segger studios

Going through the infocenter, I can only find the following:

Programming using Segger Embedded Studio

No additional action is required since softdevice and UICR are programmed implicitly by Segger Embedded Studio when bootloader application is flashed.

So what are the steps required to build a secure DFU?

[AndreasF]

Hi.

B1. Compile the uECC library.

 You have to run the build_all file found in the folder external\micro-ecc.

This will build the library.

Best regards,

Andreas

[sharu102]

I am having some trouble in step B1 Compile the uECC library to build the bootloader. We have been using nrf52 and Segger Embedded Studio for development.

The picture shows the list of IDE options available in the ..\external\micro-ecc\ folder to compile uECC and I wasn’t able to find my IDE. Any suggestions on how to overcome this would be very helpful.

[Einar Thorsrud]

Hi,

This list doe snot necessarily covered all IDEs, but it does cover all supported compilers (for instance Segger Embedded STudio use armgcc). So if you are using a supported toolchain or IDE in the SDK, then you should be covered after successfully running build_all.bat.

[Nicholas Lee]

This does NOT work for SEGGER users with the armgcc toolchain, as the required make command is not included in the path by the SEGGER installation.
The resulting failure looks like this:

C:\Nordic_Semi\nRF5_SDK_16.0.0_98a08e2\external\micro-ecc>build_all
'make' is not recognized as an internal or external command,
operable program or batch file.
'make' is not recognized as an internal or external command,
operable program or batch file.
'make' is not recognized as an internal or external command,
operable program or batch file.
'make' is not recognized as an internal or external command,
operable program or batch file.
'make' is not recognized as an internal or external command,
operable program or batch file.
'make' is not recognized as an internal or external command,
operable program or batch file.
'make' is not recognized as an internal or external command,
operable program or batch file.
'make' is not recognized as an internal or external command,
operable program or batch file.
'make' is not recognized as an internal or external command,
operable program or batch file

To resolve this, see : https://devzone.nordicsemi.com/f/nordic-q-a/29067/installing-micro-ecc-issue

[Einar Thorsrud]

Hi,

That is correct. The SDK only includes Makefiles intended to be used with GCC for building the micro-ecc library, so the idea is that you should make sure to have a GCC toolchain in place for building this. The simplest way to get that is to install Gow (or similar) and gcc-arm-none-eabi. You can refer to the micro_ecc backend documentation for more details. Whit this in place you just need to run build_all.bat, and you will have binary libraries that can be used with all supported toolchains.