What are the differences between libmbedcrypto.a and libmbedcrypto-software.a?

[by1e11]

Hello,

I am wondering that what exactly are the differences between libmbedcrypto.a and libmbedcrypto-software.a?

I read through the SDK documentation about the opethread libraries part, and assuming that these two versions are interchangable.

However, I saw in the lastest SDK for thread, the cli example is using the software version and ncp example is using the hardware acc version. And I cannot build the cli example with the hardware acc version. I tried adding the cc310 lib and also the corresponding header files. Still not working.

So could anyone tell the exact usage of the two?

Thanks in advance

Best wishes

Bo

[Jørgen Holmefjord]

Hi,

This is described in the documentation: ARM CryptoCell support

What errors do you get if you try to use the other library?

Best regards,
Jørgen

[Jørgen Holmefjord]

Both NCP (UART) and CLI (UART) should be using HW version in Therad and Zigbee SDK v2.0.0. Which exact example did you use that used the software version?

[by1e11]

Hi Jorgen

I am using cli usb example in Therad and Zigbee SDK v2.0.0. And the the default library is the SW version in my downloaded package.

BTW there are errors as well when building the ncp spi example using the software version.

Thanks

Best wishes

Bo

[Jørgen Holmefjord]

Hi,

I was able to reproduce this issue. It seems that the nrf52840-sdk-usb library used by this example have been built with HW crypto support disabled. The solution is to rebuild the library with HW crypto support. This can be done by removing the flag "DISABLE_CC310=1" on line 110 and 141 of the Makefile found in "nRF5_SDK_for_Thread_and_Zigbee_2.0.0_29775ac\external\openthread\project\lib\openthread_nrf52840\sdk\usb\armgcc\Makefile", and recompile as described in above link.

For your convenience, I have attached rebuilt library that should solve the issue: libopenthread-nrf52840-sdk-usb.a

Please replace the file in "nRF5_SDK_for_Thread_and_Zigbee_2.0.0_29775ac\external\openthread\lib\gcc" with the attached file.

I have notified the developers and this issue should be resolved in next release of SDK for Thread.

Best regards,
Jørgen