This folders are used to demonstrate basic functionality of the security chip.
The list of available Host Applications, Platform and current status can be found in the table below :
Host application | Operating System | Status |
---|---|---|
OPTIGA™ Trust M Cryptography | Native | Active |
OPTIGA™ Trust M MQTT Client | FreeRTOS | Active |
OPTIGA™ Trust M Power management | Native | Active |
OPTIGA™ Trust M Data management | Native | Active |
OPTIGA™ Trust M TLS with mbedTLS | Native | Active |
OPTIGA™ Trust M AWS FreeRTOS | FreeRTOS | Active |
OPTIGA™ Trust M Microsoft Azure IoT | FreeRTOS | Active |
OPTIGA™ Trust M PKCS#11 interface | Linux | Active |
OPTIGA™ Trust M Matter integration | Linux | Active |
OPTIGA™ Trust M Zephyr PAL & Application | Zephyr | Active |
Some of the examples, for instance example_optiga_util_read_data
calls
// OPTIGA Comms Shielded connection settings to enable the protection
OPTIGA_UTIL_SET_COMMS_PROTOCOL_VERSION(me, OPTIGA_COMMS_PROTOCOL_VERSION_PRE_SHARED_SECRET);
OPTIGA_UTIL_SET_COMMS_PROTECTION_LEVEL(me, OPTIGA_COMMS_RESPONSE_PROTECTION);
Which afterwards raises the 0x107 handshake error. In most of the cases it happens because the Pairing didn't happen. In this case you need either to remove these two lines of the code, or pair your device with the secure element.