nrf52 SDK Example Project Error - FYI

[mjscottinnc]

Using CrossStudio and SES project and session files, I'm unable to successfully link the project due to a filling library file or missing compile option.

The project path is: 'nRF5_SDK_15.0.0_a53641a\examples\ble_central_and_peripheral\experimental\ble_app_interactive\pca10040\s132\ses',

the error is:

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

I did a complete search of the hard drive and micro_ecc_lib_nrf52.a does not exist anywhere.

The file micro_ecc_lib_nrf52.a is listed under folder 'nRF_micro-ecc' in the IDE

The preprocessor defines are:

__SES_ARM
BOARD_PCA10040
CONFIG_GPIO_AS_PINRESET
FLOAT_ABI_HARD
INITIALIZE_USER_SECTIONS
MBEDTLS_CONFIG_FILE="nrf_crypto_mbedtls_config.h"
NO_VTOR_CONFIG
NRF52
NRF52832_XXAA
NRF52_PAN_74
NRF_CRYPTO_MAX_INSTANCE_COUNT=1
NRF_SD_BLE_API_VERSION=6
S132
SOFTDEVICE_PRESENT
SVC_INTERFACE_CALL_AS_NORMAL_FUNCTION
SWI_DISABLE0
uECC_ENABLE_VLI_API=0
uECC_OPTIMIZATION_LEVEL=3
uECC_SQUARE_FUNC=0
uECC_SUPPORT_COMPRESSED_POINT=0
uECC_VLI_NATIVE_LITTLE_ENDIAN=1

[Stian Røed Hafskjold]

Hi, you need to compile the library first. Please look at this guide: http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.0.0/lib_crypto_backend_micro_ecc.html

[iQd]

Hi,

Would it be possible to get the library pre-compiled somewhere, I have been trying to get this done for two days and got basically nowhere. I had no idea there is a hurdle like this to cross for getting this one functionality to work.

I am at a point where I have the micro-ecc folder with the Git project data in place, but cannot compile them, as no 'make' is in my system although I think I have installed everything needed for it. Most stuff is for Linux, I am running on Windows.

Would be just simple if I could find the necessary files ready-made, copy them in the right folders - done.
Why it cannot be like that?

Thanks.

[Stian Røed Hafskjold]

It's because of licensing. The micro-ecc library is a third party product. We require that people download the source code and compile the library themselves.

Make sure that the path for the toolchain/Make is in the PATH environment variable.

[nszmnsky]

While the licensing argument makes sense, why does it need to be compiled outside of the normal nRF52 development environment? Is there a way to compile for instance within an SES project?

[awneil]

There's nothing to stop you setting it up in your own project ...