When you feel like modifying any of this example's dependencies (Mbed Crypto, Cryptoauthlib), for example to update the secure element driver interface, you'll need to make your changes across a handful of different components.
- Update SE driver interface (and tests) in Mbed Crypto (
mbed-crypto
) - Save the changes to a branch in your fork of Mbed Crypto (
mbed-crypto
) - Update Mbed OS (
mbed-os
) with your Mbed Crypto fork's SE driver changes - Save the changes to a branch in your fork of Mbed OS (
mbed-os
)cd features/mbedtls/mbed-crypto/importer
- Within the
Makefile
, editCRYPTO_RELEASE
to point to your branch - Within the
Makefile
, editCRYPTO_REPO_URL
to point to your fork make update
; if you have anmbed-crypto
in a different repo already checked out, this command can fail. Userm -rf TARGET_IGNORE/mbed-crypto/
and runmake update
againmake all
- Commit your changes on a branch in your fork
- Update the ATECC608A driver for Mbed OS (
mbed-os-atecc608a
) for the interface changes - Save the changes to a branch in your fork of
mbed-os-atecc608a
- Update the Mbed OS example for ATECC608A (
mbed-os-example-atecc608a
)- For each example subfolder you want to update:
- Point the
mbed-os.lib
file at the branch in your fork - Point the
mbed-os-atecc608a.lib
file at the branch in your fork mbed deploy
- Point the
- For each example subfolder you want to update: