// Similar for read, delay, etc.
Unlike general-purpose microcontrollers, the MaxQ1065 isolates sensitive cryptographic keys (like device private keys) from the host MCU. Even if the main processor is compromised, the keys stored in the MaxQ1065 remain secure.
By adopting the SDK, you move from "hoping your software crypto is safe" to "hardware-guaranteed security." Whether you are building a smart lock, a glucose monitor, or an industrial PLC, the MaxQ1065 SDK gives you the API scaffolding to deploy robust, provable security without being a cryptographer. maxq1065 sdk
Connect the MaxQ1065 to your host MCU via I²C. Typical wiring:
The SDK includes a seamless integration with mbedTLS through the interface. You replace the software crypto backend: // Similar for read, delay, etc
The SDK includes Python scripts to inject keys into blank MaxQ1065 units during manufacturing:
However, a host processor cannot simply "wish" the hardware to perform tasks. It requires a structured set of libraries, drivers, and APIs to communicate with the chip. This is the fundamental role of the MaxQ1065 SDK. By adopting the SDK, you move from "hoping
MAXQ1065 SDK is a development suite designed to facilitate the integration of the
// In your mbedTLS config.h #define MBEDTLS_ECP_ALT #define MBEDTLS_ECDSA_ALT #define MBEDTLS_ECDH_ALT
The SDK is available on Analog Devices’ GitHub and through their portal. A community forum and application notes provide additional examples.
#include "maxq1065.h"