Skip to content

Commit 069c596

Browse files
Ron EldorRon Eldor
authored andcommitted
Fix typo in Readme
Fix typo `DEBICE_CRYPTOCELL ` - > `DEVICE_CRYPTOCELL`
1 parent 8f44cdf commit 069c596

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
@@ -14,7 +14,7 @@ To port your CC 310 driver to Mbed OS on your specific target, do the following:
1414
* `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.
17-
1. In `objects.h`, include `objects_cryptocell.h`. You can use the `DEBICE_CRYPTOCELL` precompilation check as defined above.
17+
1. In `objects.h`, include `objects_cryptocell.h`. You can use the `DEVICE_CRYPTOCELL` precompilation check as defined above.
1818
1. In `features/mbedtls/targets/TARGET_CRYPTOCELL310/TARGET_<target name>`, add your platform-specific libraries for all toolchains in `TOOLCHAIN_ARM`, `TOOLCHAIN_GCC_ARM` and `TOOLCHAIN_IAR` respectively.
1919
1. Add your CC setup code:
2020
* Implement `cc_platform_setup()` and `cc_platform_terminate()` to enable CC on your platform, in case you have board-specific setup functionality, required for CC setup. You can implement these functions as empty functions.

0 commit comments

Comments
 (0)