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

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

Vidar Berg — Fri, 08 Jul 2022 10:41:09 GMT

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

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

OwainIncus — Thu, 07 Jul 2022 15:29:56 GMT

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.

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

Vidar Berg — Thu, 07 Jul 2022 14:45:58 GMT

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.

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

OwainIncus — Thu, 07 Jul 2022 12:22:27 GMT

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.

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

OwainIncus — Wed, 06 Jul 2022 14:45:56 GMT

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?