- Add options for default configuration for MBEDTLS.
- Add shared memory pthread mutex for multi-process and multi-threads applications for Linux.
- Improve pal_os_event logging.
- Improve logging for Linux UART.
- Improve logging for Windows UART.
- Improved signature encoding for secp521r1 signature.
- Improved logging output.
- Fixed race condition in pal_os_event callback in libusb PAL.
- Added checks to signature padding check.
- Added default configuration for MBedTLS.
- Removed warnings during library compilation.
- Resolved initialization fails when triggering reset.
- Fix to allow compilation using zephyr PAL.
- Changes in README.md for host applications.
- Added missing license headers.
- New folder structure.
- Mbedtls is now configured to be used a submodule from https://github.com/Mbed-TLS/mbedtls/tree/v2.28.7.
- Added support for Zehpyr OS.
- README.md update.
- Fix Metadata configuration for OID 0xE0E8.
- Fix buffer length when reading PBS for shielded I2C connection.
- Update Documentation to match the launch of OPTIGA™ Trust M MTR
- README.md
- Datasheet v3.61
- Solution Reference Manual v3.60
- Config Guide v2.2
- Include new Shields and Get-Started (PSoC62S2)
- Fix Typo in Protected-Update Documentation & Parser
- PSoC PALs were removed from the PALs directory and shall be now part of the application
- Fixed 62S2 Pin assignment for the Power Control
- Fixed wrong ASN.1 ECDSA Signature size (r and s components) calculation.
- Datasheet Update
- (Linux PAL) Fixed the Segmentation fault for 64bits Linux system
- (Linux PAL) Added libgpiod support
- Fix i2c initialization routine for the PSoC6 FreeRTOS component
- Add the OPTIGA™ Trust IoT Security Development Kit link to the readme
- After the 3.01.2558 release of the core, I2C address structure member in the PAL changed its place, this release fixes it.
- Fix building "Error[Pe513]: a value of type "void (*)(void *, uint16_t)" cannot be assigned to an entity of type "void *"" Error in the optiga/comms/ifx_i2c/ifx_i2c_physical_layer.c file
- Based on the 3.01.2558 release of the core communication stack plus additional tools and PALs
- Missing of error handling for pal_i2c_init failure keeps the local host application in hung state when optiga_util_open_application is invoked.
- ifx_i2c_context structure and other structure members are not arranged in the descending order of their sizes, leading to incorrect memory access in case of few compilers.
- Re-entrancy issues in execution handler of OPTIGA™ command layer and ifx_i2c layer in linux environment, when the CPU load is high.
- In Protected update tool, unicast option is considered as Octet string instead of hex array, creating an invalid Manifest.
- Few of the resources created/initialized as part of optiga_util_create / optiga_crypt_create / optiga_util_open_application are not de-allocated / destroyed as part of optiga_util_destroy / optiga_crypt_destroy / optiga_util_close_application, creating problems in multi-process linux execution environment.