Need help getting started with STSAFE-A110 (X-NUCLEO-SAFEA1B) on STM32H503 Custom Board

[Paul632]

Hello everyone,

I am looking for some help getting started with the STSAFE-A110 in a new project.

My Setup:

• MCU: Custom board using STM32H503CBT6

• Secure Element: X-NUCLEO-SAFEA1B expansion board

• Software: STM32CubeIDE with the X-CUBE-SAFEA1 middleware added via CubeMX

• Output: I am using the USB CDC Virtual COM port (Classic Middleware) for my output. I have not enabled and am not using UART.

The Problem:
I am completely stuck trying to get the initial communication working. I cannot seem to establish communication between the STM32H5 and the STSAFE-A110 through I2C, and I cannot get StSafeA_Init() to initialize the STSAFE properly.

I have tried reading the user manual (UM2646 - Getting started with the X-CUBE-SAFEA1), but I find it extremely confusing. It does not clearly outline the necessary steps that I need to take to start the project properly from code generated by CubeMX.

What I need help with:
Could someone provide a clear, step-by-step guide on how to actually bring up the STSAFE-A110 from a blank CubeMX project? Specifically:

1. What exactly needs to be configured in CubeMX for the X-CUBE-SAFEA1 middleware to work?

2. What is the exact sequence of initialization calls required in main.c to start talking to the chip?

Any guidance or a minimum working example would be greatly appreciated.

Thank you!

[Grom]

Hello ​@Paul632 ,

X-CUBE-SAFEA1 is an older package that will soon be deprecated.

I would recommend using the new Cube package:  X-CUBE-STSE01 | Product - STMicroelectronics..

Please note that this package is based on the Secure Element Library (STSELib), which is maintained on GitHub and updated monthly. Its release cadence differs from that of the Cube package because of the additional framework integration testing required.

All the information needed to get started with the STSAFE-A product family and STSELib can be found in the following SDK wiki: stsafe-a-sdk Wiki . While this documentation is primarily intended for bare-metal implementations outside CubeMX, it is still relevant for the Cube package, even if the embedded library version may be slightly older.

Please do not hesitate to reply on this thread if you need any further support.

Best regards.