• State Verified Answer
  • Replies 2 replies
  • Subscribers 74 subscribers
  • Views 563 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 239551
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Nordic security module port as SES project ?

AKYR

Hello Nordic team,

I'm currently developping a project that uses the nrf52840 as an HTTP server/client on top of its Bluetooth functionnalities. 

I'm looking into implementing the Transport Layer Security (TLS) using the CC310 crypto-cell to lighten CPU charge.

I've read the documentation about the Nordic Security Module, from nrfxlib git repository : https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrfxlib/nrf_security/doc/nrf_security.html

It looks like the perfect module for my needs but my entire project uses Segger Embedded Studio organisation in the same way the nRF5 SDK v15.3.0 examples do.

Questions: 

Do you have an example for the Nordic Security Module for Segger Embedded Studio ? 

If not do you have any tips on how to add the CMake example from https://github.com/NordicPlayground/nrfxlib/tree/master/nrf_security into an existing Segger project ? 

Thanks in advance ! 

Aloïs KYROU.

Parents
  • +1

    This is not something we have ready, but I have asked the SDK team and here are the main pointers on how to build the crypto library in NCS and include it in nRF5 SDK:

    • nrf_security must be enabled in an "empty project" in NCS
    • Once configured and built the libraries and headers must be copied from the zephyr folder. There are some scripts to facilitate combining the libraries for a better convenience here:

    https://github.com/KaSroka/fw-nrfconnect-nrf/commits/ot-crypto-lib-build

      • Check the last two commits. It should be good enough to understand what to copy from the build directory. extract_libs.sh and update_libs.sh (They are very OpenThread centric and some paths are true only on my PC - some improvements are needed here, but should be helpful.)
    • The configuration file (nrf-config.h) and the appropriate headers (generated_includes) must be used in the nRF5 SDK project
    • Note: There is no need to set mutex-support for a nRF5 SDK usage unless you plan to run FreeRTOS
      • If the FreeRTOS integration is needed specific APIs to set the FreeRTOS mutexes must be called before initializing the library

     

Reply
  • +1

    This is not something we have ready, but I have asked the SDK team and here are the main pointers on how to build the crypto library in NCS and include it in nRF5 SDK:

    • nrf_security must be enabled in an "empty project" in NCS
    • Once configured and built the libraries and headers must be copied from the zephyr folder. There are some scripts to facilitate combining the libraries for a better convenience here:

    https://github.com/KaSroka/fw-nrfconnect-nrf/commits/ot-crypto-lib-build

      • Check the last two commits. It should be good enough to understand what to copy from the build directory. extract_libs.sh and update_libs.sh (They are very OpenThread centric and some paths are true only on my PC - some improvements are needed here, but should be helpful.)
    • The configuration file (nrf-config.h) and the appropriate headers (generated_includes) must be used in the nRF5 SDK project
    • Note: There is no need to set mutex-support for a nRF5 SDK usage unless you plan to run FreeRTOS
      • If the FreeRTOS integration is needed specific APIs to set the FreeRTOS mutexes must be called before initializing the library

     

Children
Related
Terms of service