migration to sdk2.0, BLE, MBEDTLS, OBERON and CC3XX?

[OwainIncus]

Hi,

I am trying to migrate a moderaely complicated nrf5340 app from sdk 1.9.1 to sdk 2.0 and having a few issues with getting the right crypto configuration.

Original app was working using the following MBEDTLS config...

CONFIG_MBEDTLS=y
CONFIG_MBEDTLS_BUILTIN=y
-# This one for AES CBC 128
CONFIG_MBEDTLS_CIPHER_AES_ENABLED=y
-# This one for SHA256
CONFIG_MBEDTLS_MAC_SHA256_ENABLED=y

My broken firmware config is....

CONFIG_NORDIC_SECURITY_BACKEND=y
CONFIG_OBERON_BACKEND=y

I am pretty sure my security config is wrong and is crashing in bluetooth stack startup when bt_rand() calls a function tc_hmac_dcprng_generate(); whilst doing some intialisation for BLE advertising to do with getting a random address.

I have been trying to follow....


https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/nrfxlib/nrf_security/doc/backend_config.html#nrf-security-legacy-config

as I assume a legacy config is what I need. But what configuration do I need?
What is Oberon and CC3XX and which do I need? It says MBEDTLS backend is nolonger suppcorted.


Anyone any Ideas?

[OwainIncus]

looks like its in a function tc_sha256_init() when it blows up; is this not tinycrypt; I thought I would be using mbedtls functions?

[OwainIncus]

I have compiled up one of the nordic heart rate central/periheral examples for out board; and this has no sepecific Security config or MBEDTLS or anythig else. This runs OK on our board. I checkout the defualt security config the project got when built.

I then removed all security config from our project; and this appears to be working for bluetooth; although I must now try and pull back in some oter third party libs that use MBEDTLS.

Looking much better.

[Vidar Berg]

Thank you for the update! I did not really get time to review the changes between 1.9.x and v2.0.0. Today. Please let me know if you encounter the build errors when you start pulling in your third party libraries again.

[OwainIncus]

I have added the third party libs back in their integration notes they say o enable various zephyr EMBEDTLS options; but I built OK with same config as per heart rate relay example (defaults) and hese libraries seem to be running all good.

Looking in the .config generated for the BLE example; a raft of TLS related config seems to land in the project and that seems enough.

[Vidar Berg]

I'm glad to hear to hear that the legacy configurations get correctly selected automatically. Thanks for the update.