Releases: Infineon/optiga-trust-m
Releases · Infineon/optiga-trust-m
OPTIGA Trust M v3.1.1
A maintenance release of the OPTIGA Trust M host library.
Changelog
v3.1.1
- 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
v3.1.0
- 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.
OPTIGA Trust M v3.1.0
A maintenance release of the OPTIGA Trust M host library.
Changelog
v3.1.0
- 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.
PR Release
v3.00.2490-ghr Update README.md
v3.00.2490
Merge branch 'development' of https://github.com/Infineon/optiga-trus…
v3.00.2484
Sync version
ES Release
v3.00.2468 v3.00.2468