Build following Segger Getting Started Video fails

[gos]

I tried to follow the Video on how to use Segger (on this Page. www.nordicsemi.com/.../nRF5-SDK)

for nrF52832, but I get errors when building the Segger Solution: C:\User\nRF5_SDK_15.1.0\examples\ble_peripheral\ble_app_hrs\pca10040+

cannot find ../../../../../../external/micro-ecc/nrf52hf_armgcc/armgcc/micro_ecc_lib_nrf52.a: No such file or directory.

I found the following: https://devzone.nordicsemi.com/f/nordic-q-a/32744/15-0-sdk-eddystone-builed-failed

However, it does not explain how to "Install" "gcc-arm-none-eabi-6-2017-q2-update-win32" 

I am clueless as to how to fix this and I am "dead in the water"...

Note: I am NOT an expert at setting up environments like this. My prior experience was with MicroChip PIC system.

Please Help...

[Sigurd]

Hi,

This site here explains how to install micro-ecc. Here is a direct link to the installer for "gcc-arm-none-eabi-6-2017-q2-update-win32", just run the installer when it's finshed downloading.

BUT, micro_ecc is actually not used by the ble_app_hrs example by default, so you could actually just remove it from the project. Right click on micro_ecc_lib_nrf52.a and click on "Exclude From Build". Then try to build the project again.

[gos]

Hello,

ble_app_hrs  builds if I exclude micro_ecc_lib_nrf52.a  from the build. I do not know if it runs, since my Dev Kit (DEV KIT FOR NRF52 BLE/NFC ) is still int he mail.

My nRF5_SDK_15.1.0 is installed in folder C:\User\nRF5_SDK_15.1.0\

I downloaded and installed "gcc-arm-none-eabi-6-2017-q2-update-win32" (1) to the default folder (*) not knowing where it should be installed. (*) C:\Program Files (x86)\GNU Tools ARM Embedded\6 2017-q2-update\

However, searching the tree, there are lots of .a files there, but no instance of micro_ecc_lib_nrf52.a (2).

So, if a project do need (2), what are the steps?

Is there another .a file that should be used, and should I have installed (1) into the nRF5_SDK_15.1.0  folder at a certain level?

[Sigurd]

gos said:

So, if a project do need (2), what are the steps?

Following the list here, the next step is to make sure that make is installed. I would recommend MinGW for that. Here is a direct link to download MinGW.

Run the downloaded installer and select the folder where the MinGW toolchain will be installed. The recommended path is C:\MinGW

When the first part of the installation is finished, the MinGW Installation Manager opens. 

From the package list, select mingw32-base and msys-base. Then, click Installation -> Apply changes to install the selected items.

Then add the following paths to the PATH variable in your system:

C:\MinGW\bin and C:\MinGW\msys\1.0\bin 
To do so, right-click My computer, select Properties -> Advanced system settings -> Environment Variables and double-click the PATH variable. Then, append the existing string with the two paths, each preceded by a semicolon, for example:

…; C:\MinGW\bin;C:\MinGW\msys\1.0\bin

Then check that the make tool was installed correctly by typing make --version and pressing Enter. If there are no errors during installation, the following message is displayed:

If make is working, then at last run build_all.sh or build_all.bat located in ..\SDK15.1_folder\external\micro-ecc

micro_ecc_lib_nrf52.a will then be compiled.

[gos]

Thanks a lot Sigurd for your time and detailed explanation!