Porting LESC in serialization application processor, not found any guide to port peer manager and backend for nrf_crypto_rng_vector_generate()

[pin2]

Hi,

SDK - nRF5_SDK_15.2.0_9412b96

HW - nRF52840 connectivity chip,  other controller for application chip

We are tried to port serialization application on other than nordic chip where connectivity application is running on nRF52840, we are able to use ble with open connection (without LE legacy & LESC).

when we are enabling LESC in sdk_config.h by changing setting below macro to 1

#define NRF_BLE_LESC_ENABLED 1

#define PM_LESC_ENABLED 1

We are using crypto backend as micro-ecc because application controller don't have CC310 Hardware  we are getting compilation error for random vector generator is there only two way for RNG is CC310 and NRF HW but our application chip don't have either is there any software RNG available for serialization.

NRF_CRYPTO_BACKEND_MICRO_ECC_ENABLED 1

Looking forward to here from you, as I am not able to found any documents regarding LESC porting in serialization.

In HRS example located at examples/ble_peripheral/ble_app_hrs/pca10056/ser_s140_uart/ses

When I am seeing this section in project file for below section, I am wonder as per serialization document porting of components/serialization/application/ and components/serialization/common is enough but below section say there is need of other files also, Please help us to identify number of files porting required other than availble in serialization.

  <folder Name="nRF_BLE">
      <file file_name="../../../../../../components/ble/peer_manager/auth_status_tracker.c" />
      <file file_name="../../../../../../components/ble/common/ble_advdata.c" />
      <file file_name="../../../../../../components/ble/ble_advertising/ble_advertising.c" />
      <file file_name="../../../../../../components/ble/common/ble_conn_params.c" />
      <file file_name="../../../../../../components/ble/common/ble_conn_state.c" />
      <file file_name="../../../../../../components/ble/common/ble_srv_common.c" />
      <file file_name="../../../../../../components/ble/peer_manager/gatt_cache_manager.c" />
      <file file_name="../../../../../../components/ble/peer_manager/gatts_cache_manager.c" />
      <file file_name="../../../../../../components/ble/peer_manager/id_manager.c" />
      <file file_name="../../../../../../components/ble/nrf_ble_gatt/nrf_ble_gatt.c" />
      <file file_name="../../../../../../components/ble/peer_manager/nrf_ble_lesc.c" />
      <file file_name="../../../../../../components/ble/nrf_ble_qwr/nrf_ble_qwr.c" />
      <file file_name="../../../../../../components/ble/peer_manager/peer_data_storage.c" />
      <file file_name="../../../../../../components/ble/peer_manager/peer_database.c" />
      <file file_name="../../../../../../components/ble/peer_manager/peer_id.c" />
      <file file_name="../../../../../../components/ble/peer_manager/peer_manager.c" />
      <file file_name="../../../../../../components/ble/peer_manager/peer_manager_handler.c" />
      <file file_name="../../../../../../components/ble/peer_manager/pm_buffer.c" />
      <file file_name="../../../../../../components/ble/peer_manager/security_dispatcher.c" />
      <file file_name="../../../../../../components/ble/peer_manager/security_manager.c" />
    </folder>

Thanks in Advance,

Pintu Sakariya

[Jared]

Hi,

Using the CC310 hardware with serialization is not a feature that is supported by our API. It might be possible but unfortunately, this is something that you would have to do yourself. 

Best regards

Jared