Compatibility of esp-cryptoauthlib with ESP32-C5 and ATECC608C

[ManelAwayter]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate.
• Provided a clear description of your suggestion.
• Included any relevant context or examples.

Issue or Suggestion Description

Hi,
I would like to know whether esp-cryptoauthlib is compatible with the ESP32-C5 and the ATECC608C secure element.

Is there official support for this combination, and if so, are there any examples or guidelines available for integration?

Thank you!

[AdityaHPatwardhan]

@ManelAwayter Thanks for the issue,
Yes the ESP32-C5 is compatible with ATECC608C, but at the moment we have not added the support in our provisioning tool for testing out the support.
We will soon add it and let you know. CC @nileshkale123
Thanks,
Aditya

[ManelAwayter]

Hi @AdityaHPatwardhan ,

Thanks for the clarification.

Now I would like to ask about the ECC608-TMNGTLS (Microchip TrustMANAGER) variant.

From the perspective of the ESP-IDF firmware using esp-cryptoauthlib and mbedTLS:

• Is the ECC608-TMNGTLS supported in the same way as the standard ATECC608C/TNG devices?

Thanks again.

[AdityaHPatwardhan]

Hi @ManelAwayter

TMNGTLS is not supported officially at the moment, but we have verified it and the TrustCustom support can be used to authenticate using the TMNGTLS device.

In TMNGTLS the main feature is the in-field provisioning through Kudelski IoT KeyStream. That is the responsibility of the application layer. Once that is done, application can pass the device certificate to esp-tls layer accordingly.

ESP-TLS shall use private key from slot 0 by default, so slot 0 needs to be used for storing the private key corresponding to the device certificate.

Additionally you need to make following configurations:

In idf.py menuconfig:

Select “ATECC608A chip type” → TrustCustom

Set ATCA_I2C_ADDRESS → 0x70

Configure the I²C pins as needed

We will soon officially support TMNGTLS, but the support wont be different than TrustCustom