ARMmbed
/
mbed-os
mirror of https://github.com/ARMmbed/mbed-os.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Explaining how to opt in modules 

Add a section in the CC Readme file explaining how to enable the optional module.
pull/10991/head
Ron Eldor 2019-07-08 18:43:39 +03:00
parent cd4283e5fb
commit a08b150546
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
features/cryptocell/FEATURE_CRYPTOCELL310/Readme.md
View File

@ -26,3 +26,13 @@ To port your CC 310 driver to Mbed OS on your specific target, do the following:
* Implement `crypto_platform_setup()` and `crypto_platform_terminate()` to enable CC on your platform, in case you have board-specific setup functionality, required for CC setup. You MUST call 'SaSi_LibInit()` and 'SaSi_LibFini()' respectively in these functions.
* Define `crypto_platform_ctx` in `crypto_device_platform.h` in a way that suits your implementation.
## Enabling optional alternative drivers
There are three additional modules that have alternative implementation support, which are not enabled by default.
The reason is to allow backwards compatability, as these modules don't have full functionality, and return `MBEDTLS_ERR_PLATFORM_FEATURE_UNSUPPORTED` for some features.
The modules are:
* `AES` which only supports 128 bit key size, in opposed to previous suipport for all key sizes.
* `CMAC` which only supports AES 128 bit key size, in opposed to previous supporting DES and all key sizes.
* `SHA512` which only supports SHA512, in opposed to previously supporting SHA384 as well.
In order to enable these modules, you should define `MBEDTLS_AES_ALT`, `MBEDTLS_CMAC_ALT` and `MBEDTLS_SHA512_ALT` respectively, either in `mbed_app.json` or in your `MBEDTLS_USER_CONFIG_FILE` to have hardware accelerated module with reduced RAM size, on the expense of full functionality.