ARMmbed
/
mbed-os
mirror of https://github.com/ARMmbed/mbed-os.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
mbed-os/features/cryptocell/FEATURE_CRYPTOCELL310
History
Ron Eldor cad40e1633 Rename the platform context varaiable 
Rename the generic name `ctx` of `mbedtls_platform_context`
in `platform_alt.c` to a specific name `plat_ctx`, to avoid conflicts
when used as external in crypto modules.
 		2019-01-22 13:57:32 +02:00
..
TARGET_MCU_NRF52840 Rename the platform specific crypto_platform 2019-01-22 13:56:59 +02:00
binaries Update the CC310 GCC_ARM libraries 2018-12-18 18:08:06 +02:00
include Change Cryptocell target to a feature 2018-05-21 13:40:43 +03:00
Readme.md Rename the platform specific crypto_platform 2019-01-22 13:56:59 +02:00
cc_internal.c Merge pull request #8797 from RonEld/cryptocell_ecc_errors_alt_fixes 2018-11-30 17:51:50 -06:00
cc_internal.h Modify HW accelerator drivers to new error code 2018-11-11 09:59:18 +02:00
ccm_alt.c Add the platform generic errors 2018-11-26 15:33:17 +02:00
ccm_alt.h Style fixes 2018-11-26 15:32:46 +02:00
ecdh_alt.c Change to mbedtls_platform_zeroize() 2019-01-01 13:56:58 +02:00
ecdsa_alt.c Change to mbedtls_platform_zeroize() 2019-01-01 13:56:58 +02:00
ecdsa_alt.c.mod Change Cryptocell target to a feature 2018-05-21 13:40:43 +03:00
mbedtls_device.h Change Cryptocell target to a feature 2018-05-21 13:40:43 +03:00
objects_cryptocell.h Change Cryptocell target to a feature 2018-05-21 13:40:43 +03:00
sha1_alt.c Return not supported for internal process function 2018-11-28 15:31:55 +02:00
sha1_alt.h Style fixes 2018-11-28 15:31:17 +02:00
sha256_alt.c Return not supported for internal process function 2018-11-28 15:31:55 +02:00
sha256_alt.h Style fixes 2018-11-28 15:31:17 +02:00
trng.c Rename the platform context varaiable 2019-01-22 13:57:32 +02:00

Readme.md

Guidelines for porting Cryptocell to Mbed OS

Cryptocell (CC) 310 is a hardware accelerator that can be ported to several boards, assuming these boards have CC 310 embedded in their hardware.

The CC 310 driver consists of three libraries:

  • A common core library(libcc_core.a).
  • A platform-specific TRNG library, containing TRNG-related information, for sampling sufficient entropy on the specific platform(libcc_trng.a).
  • A platform-specific library containing extra information, such as the CC register's base addresses on the specific board. (libcc_ext.a)

Library version information:

  • The CC 310 libraries were built from version arm_sw-cc310-1.1.0.1285
  • The IAR libraries were built using IAR ANSI C/C++ Compiler V7.80.1.11864/W32 for ARM with --cpu Cortex-M4f.
  • The ARM libraries were built using ARM Compiler 5.06 update 4 (build 422) with --cpu cortex-m4.
  • The GCC_ARM libraries were built using arm-none-eabi-gcc 6.3.1 20170620 (release) with -mcpu=cortex-m4.

To port your CC 310 driver to Mbed OS on your specific target, do the following:

  1. In targets.json add the following to your target:
    • MBEDTLS_CONFIG_HW_SUPPORT to macros_add key. This instructs Mbed TLS to look for an alternative cryptographic implementation.
    • CRYPTOCELL310 to feature. Use this in your common code that you need to remove from compilation in case CC exists in your board. Use #if !defined(FEATURE_CRYPTOCELL310) and #if defined(FEATURE_CRYPTOCELL310).
  2. In objects.h, include objects_cryptocell.h. You can use the FEATURE_CRYPTOCELL310 precompilation check as defined above.
  3. In features/cryptocell/FEATURE_CRYPTOCELL310/TARGET_<target name>, add your platform-specific libraries for all toolchains in TOOLCHAIN_ARM, TOOLCHAIN_GCC_ARM and TOOLCHAIN_IAR respectively.
  4. Add your CC setup code:
    • 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.