Replace Oberon backend with uECC backend in LESC device app

Question

In my project I use nRF52832 embedded in MuRata module. I have a BLE service with capabilities very similar to NUS service.

I've managed to add support for LESC + SEC_MITM to my BLE service while using the Oberon backend. I've also managed to build a working Secure Bootloader with OTA DFU using uECC library.

The projects are built with SEGGER Embedded Studio and nRF5 SDK.

The projects are built with nRF5 SDK 16.0.0

But I am struggling to replace the Oberon backend with the uECC backend.

While using the uECC backend I get the following errors while pairing:

<info> app: BLE UART started.
<info> app: Debug logging for UART over RTT started.
<info> app:
<*> Connected

<info> app: conn_sup_timeout = 72
<info> app: min_conn_interval = 24
<info> app: max_conn_interval = 24
<info> app: slave_latency = 0
<info> app: Data len is set to 0xF4(244)
<warning> nrf_ble_lesc: Creating invalid shared secret to make LESC fail.
<info> nrf_ble_lesc: Calling sd_ble_gap_lesc_dhkey_reply on conn_handle: 0
<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Bonding, error: 136

Please help.

Ron. · Accepted Answer

Hi Vidar, 
 I failed to understand correctly your initial answer. 
 After reading again and again the crypto backends related documentation I was sure that you mentioned the compilation flags to be used while building the uECC library. But after I looked more carefully I see that the same flags have to be used also in the project using the uECC library. And that is because uECC_VLI_NATIVE_LITTLE_ENDIAN flag is also used by the micro-ecc backend which is compiled as a part of the project. 
 Please update the documentation of the backend. 
 Now while compiling my project with uECC the pairing works. 
 Thanks, 
 Ron.

Replace Oberon backend with uECC backend in LESC device app

Top Replies