You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: features/mbedtls/targets/TARGET_CRYPTOCELL310/Readme.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ The CC 310 driver consists of three libraries:
11
11
To port your CC 310 driver to Mbed OS on your specific target, do the following:
12
12
13
13
1. In `targets.json` add the following to your target:
14
-
* `MBEDTLS_CONFIG_HW_SUPPORT` to `macros_add` key. This suggests there is a hardware accelerated cryptography engine that replaces the default Mbed TLS implementation.
14
+
* `MBEDTLS_CONFIG_HW_SUPPORT` to `macros_add` key. This instructs Mbed TLS to look for an alternative cryptographic implementation.
15
15
* `CRYPTOCELL` to `device_has_add` key. Use this in your common code that you need to remove from compilation in case CC exists in your board. Use `#if !defined(DEVICE_CRYPTOCELL)` or `#if DEVICE_CRYPTOCELL`.
16
16
* `CRYPTOCELL310` to `extra_labels_add` key. The build system uses this to look for the CC 310 code and binaries.
17
17
1. In `objects.h`, include `objects_cryptocell.h`. You can use the `DEBICE_CRYPTOCELL` precompilation check as defined above.
0 commit comments