STSAFE-A120 authentication chip (part number: STSAFA120S8SPL05).

[Dan Gabbay]

We are interested in incorporating the STSAFE-A120 authentication chip (part number: STSAFA120S8SPL05) into our current design. However, the available datasheet lacks the necessary details for firmware development. We would highly appreciate your help and guidance on this matter.

 

[db16122]

For security device, most information is confidential and should sign NDA for further information. You may need to check with FAE for detail

[Moktar SELLAMI]

Hello ​@Dan Gabbay, 
For firmware development  with STSAFE-A120 ST provides:

• X-CUBBE-STSE01, a software expansion for STM32Cube that provides examples for STSAFE-A110/STSAFE-A120/STSAFE-L010 that comes with a user manual UM3490 Getting started with the X-CUBE-STSE01 software package. 
• STMicroelectronics Secure Element Library (STSELib) a middleware that provides a set of APIs and interface function to interact with the STSAFE-A secure element 
• STSAFE-A Software Development Kit (stsafe-a-sdk) offers a collection of application examples and demonstrations on how to use the STSAFE-A secure element along with a dedicated wiki page. 

Best Regards

[Dan Gabbay]

Hi Onizuka09,
Thank you for trying to help me. Yes, I have cloned the following repository: https://github.com/stmicroelectronics/stsafe-a-sdk and tried to add the stselib library to my project, but I could not build it cleanly.
I ran into so many compilation errors that I couldn't resolve them, so I eventually gave up. For context, we are using the STM32H733 MCU with STM32CubeIDE, alongside ChibiOS RTOS version 21.11.4.
I guess the fact that we use ChibiOS makes life a bit more difficult here.
Thanks,
Dan
 

[Moktar SELLAMI]

Hello ​@Dan Gabbay 

Sorry to hear about the current issue you are having.

For community guidelines, I recommend that you post your new issue about the STSElib implementation in your current project, and provide as much detail as possible, especially the type of errors you are seeing.

For now, I would suggest starting by running the current examples provided and seeing how they work.

Best regards

 

[Dan Gabbay]

I am trying to get the STSAFE-A120 to generate a true 256-BIT random number and by looking at the I2C protocol analyzer it seems to be working at least partially but I am getting the following error status STSE_SERVICE_FRAME_CRC_ERROR. Can somebody help me to understand the format of the messages exchanged between the MCU and the chip. I is important for me to try to understand the format first before trying to fix the issue.
From the I2C protocol analyzer I see three frames as shown below:
0x 40 W 0x02 00 24 14 52
0x41 R 0x00 00 26 73 CF~A
0x41 R 0x00 00 26 73 CF followed by 34 bytes (that keeps changing each time the oscilloscope triggers.
Please help me to parse the frames and understand the data fields. This may help me to fix the issue I am seeing.

Thank you for your help and time.
 

[db16122]

it is kind of MIFARE protocol according to the AI feedback

[Pavel A.]

> I guess the fact that we use ChibiOS makes life a bit more difficult here.

So why can’t you make just a minimal example without any OS? Using the ST HAL for I2C, or whatever the examples use?