OPTIGA™ Trust Forum Discussions
Hello everyone,
I have been working with an Optiga Trust Mv3 for quite some time now. I have used it directly using the provided API available here (https://github.com/Infineon/optiga-trust-m) but also with an OpenSSL Engine which I developed for OpenSSL 1.1.1, based on the example provided in this repos (https://github.com/Infineon/linux-optiga-trust-m).
Now, as I am also working with an embedded device running MbedTLS and using an Optiga Trust Mv3, I would like to use the equivalent of an OpenSSL Engine for MbedTLS. I read about PSA Drivers (https://github.com/Mbed-TLS/mbedtls/blob/development/docs/proposed/psa-driver-interface.md), which seems to be what I am looking for, however I can't find any PSA driver implementation example taking advantage of a Secure Element. My goal would of course to be able to seamlessly use MbedTLS with the Optiga Trust M.
Would you have any resources on this topic, such as a repo explaining how to use a PSA driver with the Trust M ?
Thank you for your help,
Regards,
Maxime
Show LessI am trying to generate keypair using "ECC KEY 1" , "ECC KEY 2" and "RSA KEY 1" and I get the error "optiga_util_write_data/CB ==> 8007 (Access conditions not satisfied)". However, I am able to successfully generate keypairs using "ECC KEY 3" and "ECC KEY 4" and "RSA KEY 2". I am using the Shield2go TrustM secure element eval chip. What does "Access conditions not satisfied" mean and how to be able to generate using the above mentioned key slots.
I am using "optiga_crypt_ecc_generate_keypair" to generate a keypair but I get " 0x202 (CMD ERROR)". can you please let me know whats wrong here.
Here's my API.
Good day,
I want to develop an application for an academic project, and I want to use the OPTIGA Trust M chip. However, I am considering implementing it with the WLC1115 chip as the transmitter. My question is whether it's possible to make this implementation and if the application I want to develop is feasible with these two chips.
Application: I want to authenticate the transmitter with the receiver in such a way that the receiver can only be used with that transmitter and vice versa.
I also want to know if I would need to implement the OPTIGA Trust M chip both in the Tx and Rx.
Thank you for your responses.
Show Lesssh write_default_shared_secret.sh
write_default_shared_secret.sh: 2: source: not found
rm: cannot remove '*.dat': No such file or directory
Generate default shared secret
Bypass Shielded Communication.
shm_open: Permission denied
Segmentation fault
I'm trying to decide between writing the pal layer for Zephyr OS using the official Trust M library (https://github.com/Infineon/optiga-trust-m) vs using the experimental Zephyr branch for Trust M (https://github.com/Infineon/zephyr-optiga).
There have been a couple of attempts to have Trust M support added to the Zephyr repo, but didn't seem to get very far. I'm not necessarily looking to add to a public repo, but I need reliable functionality with Zephyr. Although I've briefly looked into it, I don't have a solid gauge on the effect involved in writing a pal for Zephyr. Any advise is welcome!!
Farrell
Show LessHello,
Can you please let me know the storage temperature range (MIN~MAX) for OPTIGA TRUST M SLS32AIA? This information is missing from both the ProductBrief and the datasheet.
Regards,
Martin
Show LessThere is a "fatal error: DAVE.h: No such file or directory" at the time of compilation when adding optiga-trust-m library to empty-app example.
Steps followed:
1. Choose Board Support Package: CYSBSYSKIT-DEV-01
2. Select Application Template: Empty App
3. Selected optiga-trust-m = 3.1.4 release from library manager
4. Compilation error: mtb_shared/optiga-trust-m/release-v3.1.4/examples/optiga_shell.c:38:10: fatal error: DAVE.h: No such file or directory
Show Less
Hi,
I am trying to port optiga-trust-m library for STM32 (freeRTOS). Are there any ready samples available within the community or by infineon.
Show Less