Skip to content

Commit 2b2aa0f

Browse files
Ron EldorRon Eldor
authored andcommitted
Rephrase meaning of MBEDTLS_CONFIG_HW_SUPPORT
Rephrase the label, to make it more clearer.
1 parent e68815e commit 2b2aa0f

File tree

1 file changed

+1
-1
lines changed
  • features/mbedtls/targets/TARGET_CRYPTOCELL310

1 file changed

+1
-1
lines changed

features/mbedtls/targets/TARGET_CRYPTOCELL310/Readme.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ The CC 310 driver consists of three libraries:
1111
To port your CC 310 driver to Mbed OS on your specific target, do the following:
1212

1313
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.
1515
* `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`.
1616
* `CRYPTOCELL310` to `extra_labels_add` key. The build system uses this to look for the CC 310 code and binaries.
1717
1. In `objects.h`, include `objects_cryptocell.h`. You can use the `DEBICE_CRYPTOCELL` precompilation check as defined above.

0 commit comments

Comments
 (0)