This library implements the APIs required to communicate with Microchip Security device. The family of devices supported currently are:
CryptoAuth | CryptoAuth2 |
---|---|
ATECC608B | ECC204 |
ATECC608A | ECC206 |
ATECC508A | SHA104 |
ATECC108A | SHA105 |
ATSHA204A | SHA106 |
ATSHA206A | RNG90 |
The best place to start is with the Microchip Trust Platform
Online API documentation is at https://microchiptech.github.io/cryptoauthlib/
Latest software and examples can be found at:
Prerequisite hardware to run CryptoAuthLib examples:
Alternatively a Microchip MCU and Adapter Board:
For most development, using socketed top-boards is preferable until your configuration is well tested, then you can commit it to a CryptoAuth Xplained Pro Extension, for example. Keep in mind that once you lock a device, it will not be changeable.
In order to properly configured the library there must be a header file in your project named atca_config.h
at minimum this needs to contain defines for the hal and device types being used. Most integrations have an configuration mechanism for generating this file. See the atca_config.h.in template which is configured by CMake for Linux, MacOS, & Windows projects.
An example of the configuration:
There are two major compiler defines that affect the operation of the library.
Some specific options are available in the fully documented configuration files lib/calib/calib_config.h
, atca_configuration.h
, lib/crypto/crypto_config.h
, lib/host/atca_host_config.h
which is also the place where features can be selected. We provide some configurations focused on specific use cases and the checks are enabled by default.
See Release Notes
CryptoAuthLib will run on a variety of platforms from small micro-controllers to desktop host systems. See hal readme
Porting requires a time delay function of millisecond resolution (hal_delay_ms) which can be implemented via loop, timer, or rtos sleep/wait and a communication interface.
Cryptoauthlib API documentation is at https://microchiptech.github.io/cryptoauthlib/
The library is structured to support portability to:
All platform dependencies are contained within the HAL (hardware abstraction layer).
There is a set of integration tests found in the test directory which will at least partially demonstrate the use of the objects. Some tests may depend upon a certain device being configured in a certain way and may not work for all devices or specific configurations of the device. See test readme
The best place to start is with the Microchip Trust Platform
Also application examples are included as part of the Harmony 3 framework and can be copied from the Harmony Content Manager or found with the Harmony 3 Framework Cryptoauthlib_apps
The Linux HID HAL files use the Linux udev development software package.
To install the udev development package under Ubuntu Linux, please type the following command at the terminal window:
This adds the udev development development software package to the Ubuntu Linux installation.
The Linux HID HAL files also require a udev rule to be added to change the permissions of the USB HID Devices. Please add a new udev rule for the Microchip CryptoAuth USB devices.
Edit the mchp-cryptoauth.rules file and add the following line to the file: