@@ -26,33 +26,24 @@ Follow the `readme.txt` for detailed installation instructions.
26
26
27
27
``` sh
28
28
git clone git@github.com:ARMmbed/mbed-os-example-atecc608a.git
29
- cd mbed-os-example-atecc608a/
29
+ cd mbed-os-example-atecc608a/atecc608a
30
30
source ~ /venvs/mbed/bin/activate
31
- mbed new .
32
31
mbed deploy
33
32
mbed compile -t GCC_ARM -m K64F --flash --sterm
34
33
```
35
34
36
35
### PSA Crypto driver development
37
36
38
- Add any driver files (none created so far) to the mbed-os-atecc608a folder. It
39
- is backed by the
37
+ Driver files are located in the atecc608a/ mbed-os-atecc608a folder.
38
+ It is backed by the
40
39
[ mbed-os-atecc608a] ( https://github.com/ARMmbed/mbed-os-atecc608a/tree/mbed-cryptoauthlib )
41
- repo , which any application wanting to use Mbed OS and the ATECC608A will
40
+ repository , which any application wanting to use Mbed OS and the ATECC608A will
42
41
depend on (same as how this example depends on it).
43
42
44
43
Any Mbed Crypto changes needed to support your driver work should be done in
45
44
` mbed-os/features/mbedtls/mbed-crypto/importer/TARGET_IGNORE/mbed-crypto ` , and copied
46
45
into Mbed OS's idiosyncratic file layout before use using the importer.
47
46
48
- For the first-time setup only, if you need to make any Mbed Crypto changes,
49
- perform the following operations:
50
-
51
- ``` sh
52
- cd mbed-os/features/mbedtls/mbed-crypto/importer
53
- make update
54
- ```
55
-
56
47
For every change you make in Mbed Crypto (which you'd make inside
57
48
` mbed-os/features/mbedtls/mbed-crypto/importer/TARGET_IGNORE/mbed-crypto ` ),
58
49
update Mbed OS with those changes by performing the following operations.
0 commit comments