RE: Trouble in configuring nrf_ble_lesc.c for PEER MANAGER

STE — Fri, 12 Nov 2021 16:24:51 GMT

Dear Simonr,

thanks for your help.

I've see the suggested app because was addressed by many thread through the forum.

After some attempt finally I was successfully in configuring this feature but was principally a trial and error procedure, so take a look at the compiler error messages and then include the necessary files.

About the file main.c I've followed what reported at this link:

https://devzone.nordicsemi.com/f/nordic-q-a/44658/communication-problems-between-ble_peripheral-and-ble_central-in-nrf52-project/176907#176907

and used the peripheral part to modfify my main.c code.

Other than the source .c files is also necessary add related include path inside the common option of the project then:

select the Common profile:

then select Preprocessor and then select the User include Directories:

so by comparing the example design and the own design add the necessary path, in my case was the following ones:

../../../../../../components/libraries/crypto

../../../../../../components/libraries/crypto/backend/cc310

../../../../../../components/libraries/crypto/backend/cc310_bl

../../../../../../components/libraries/crypto/backend/cifra

../../../../../../components/libraries/crypto/backend/mbedtls

../../../../../../components/libraries/crypto/backend/micro_ecc

../../../../../../components/libraries/crypto/backend/nrf_hw

../../../../../../components/libraries/crypto/backend/nrf_sw

../../../../../../components/libraries/crypto/backend/oberon

../../../../../../components/libraries/crypto/backend/optiga

...

../../../../../../components/libraries/stack_info

...

../../../../../../external/nrf_cc310/include

../../../../../../external/nrf_oberon

../../../../../../external/nrf_oberon/include

../../../../../../external/nrf_tls/mbedtls/nrf_crypto/config

and may be some other ones that actually I can not remember, check by comparing with the example file what you have to add and by the error message from the compilation stage.

Next step was add the "libnrf_cc310_0.9.13.a lib" to my project source file, this lib is at the following path "..\nRF5_SDK_17.0.2_d674dde\external\nrf_cc310\lib\cortex-m4\hard-float"

and everty time that an error arise check what source file was missing and add it sequencially.

For the ble_nus service, inside the function ble_nus_init() change the following rows:

    //add_char_params.read_access  = SEC_OPEN;
    //add_char_params.write_access = SEC_OPEN;
    add_char_params.read_access  = SEC_JUST_WORKS;
    add_char_params.write_access = SEC_JUST_WORKS;
    
    ........
    
    //add_char_params.read_access       = SEC_OPEN;
    //add_char_params.write_access      = SEC_OPEN;
    //add_char_params.cccd_write_access = SEC_OPEN;
    add_char_params.read_access       = SEC_JUST_WORKS ;
    add_char_params.write_access      = SEC_JUST_WORKS ;
    add_char_params.cccd_write_access = SEC_JUST_WORKS ;

Inside the config file set:

PEER_MANAGER_ENABLED

PM_LESC_ENABLED

FDS_ENABLED

add following lines to the config files:

in order to include the nrf_ble_lesc.c file also add the following line to the sdk_config.h file:

It is not possible to add inside the doc for every SDK the necessary dependency file to use? it would be more simple and no time consuming follow the instruction for each module so include the needed file and enable the right switch into the config file, just a suggest.

Thanks and best regards.

RE: Trouble in configuring nrf_ble_lesc.c for PEER MANAGER

Simonr — Fri, 12 Nov 2021 14:29:37 GMT

Hello

When it comes to BLE and security, it is generally easier to choose one of the examples already implementing the BLE protocol and peer manager, and then add the peripheral functionalities you would like to use.

I would suggest checking out the glucose application for instance which already implements LESC, and add UART and ADC to that one instead.

Best regards,

Simon