Skip to content

OPTIGA Trust M v3.1.3
Compare
Choose a tag to compare
@ayushev ayushev released this 29 Jun 13:48
· 94 commits to develop since this release
release-v3.1.3
3b2a33c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changelog

v3.1.3

  • Fix i2c initialization routine for the PSoC6 FreeRTOS component
  • Add the OPTIGA Trust IoT Security Development Kit link to the readme

v3.1.2

  • After the 3.01.2558 release of the core, I2C address structure member in the PAL changed its place, this release fixes it.

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.
Assets 2
Loading