Migration Guidance: Implementing TinyCrypt-equivalent functionality in NCS v3.2.1

[Himanshu111]

Hello DevZone Team,

I would like to express my appreciation for the excellent support and the collaborative community platform you provide for nRF developers.

We are currently in the process of migrating our project from nRF Connect SDK (NCS) v3.0.2 to the latest v3.2.1 release. While the majority of the application is functioning as expected, we have encountered a challenge regarding the TinyCrypt library.

Our project relies on this library. As TinyCrypt is being deprecated/removed in newer SDK versions, we are seeking guidance on the recommended migration path. Specifically:

• Are there existing reference samples in v3.2.1 for migrating ECC or AES operations from TinyCrypt to the PSA Crypto API?

• What are the mandatory Kconfig changes required to enable the modern security stack (Mbed TLS/PSA) to maintain compatibility with our existing mobile authentication logic?

Migration guide link:  is not having any update regarding the TINYCRYPT update.

Any documentation or technical references you can provide to help us bridge this gap would be greatly appreciated.

Best regards,

Himanshu Pachauri

[Edvin]

Hello,

It is correct that TinyCrypt is being deprecated. 

Is there any particular reason why you are porting this application to v3.2.1? The reason I ask is that there are many changes in the latest SDK updates, but they don't bring any new features to the nRF52 series. My recommandation is that if your application is dependent on TinyCrypt, you should stay on v3.0.2, if that works for your application.

But please let me know if you have a particular reason to move to v3.2.1. It would be useful to know.

Best regards,

Edvin