Oberon Security Drivers for nRF54L15

Hello,

Does the nrf_oberon library support the nRF54L series parts? In the technical documentation, it appears that M33 parts are supported:

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/libraries/security/nrf_security/doc/drivers.html#nrf-oberon-driver

I am able to build my code (SDK/Toolchain version 2.9.0) for nRF52840 successfully using the nrf_oberon libraries, but the build fails for nRF54L15 targets with this error:

fatal error: ocrypto_aes_eax.h: No such file or directory
2 | #include <ocrypto_aes_eax.h>

If nrf_oberon does support the full range of M33 parts, are there any additional KConfigs necessary for the L15?

Thanks!

Parents
  • Hi Grant,

    In the meantime, could you let me know which crypto functionality you need.? What do you want to achieve.? 

    Regards,

    Swathy

  • Hi Swathy,

    I was able to get the Oberon libraries to compile in using the Kconfig PSA_CRYPTO_DRIVER_OBERON and everything appears to work properly on the nRF54l15. I have a couple other questions about this topic:

    1) Using the PSA APIs with the CRACEN backend introduces a pretty sizable performance hit and adds a decent amount of overhead to the memory required for task stacks. For a wireless protocol, are there advantages that I am not seeing to using the PSA APIs and CRACEN? From my testing, it is roughly 4x slower than using Oberon APIs directly.

    2) The best performance I have seen is using the ECB hardware. It is currently not supported by ConnectSDK for the nrf54l15, but I found this thread with a patch to add support -  Doing AES/ECB encryption in nRF54L15 board. Is there any plan to integrate this patch into mainline ConnectSDK?

    Thanks!

    Grant 

Reply
  • Hi Swathy,

    I was able to get the Oberon libraries to compile in using the Kconfig PSA_CRYPTO_DRIVER_OBERON and everything appears to work properly on the nRF54l15. I have a couple other questions about this topic:

    1) Using the PSA APIs with the CRACEN backend introduces a pretty sizable performance hit and adds a decent amount of overhead to the memory required for task stacks. For a wireless protocol, are there advantages that I am not seeing to using the PSA APIs and CRACEN? From my testing, it is roughly 4x slower than using Oberon APIs directly.

    2) The best performance I have seen is using the ECB hardware. It is currently not supported by ConnectSDK for the nrf54l15, but I found this thread with a patch to add support -  Doing AES/ECB encryption in nRF54L15 board. Is there any plan to integrate this patch into mainline ConnectSDK?

    Thanks!

    Grant 

Children
No Data
Related