Skip to main content
Associate
March 20, 2026
Solved

X-NUCLEO-ESE02A1 I2C configuration

  • March 20, 2026
  • 2 replies
  • 191 views

Hello,

I have started evaluation of X-NUCLEO-ESE02A1 shield with NUCLEO-F401RE board, and used STM32CubeMX for project generation according to PDF inside X-CUBE-SAFEA1 package.

However, I can't get any demo running, and both these generated demos, as well as my attempt, fail with error code 0x01 which maps to STSAFEA_COMMUNICATION_ERROR. I have tried putting jumpers for I2C lines pullup on the shield, jumpers P4 and P5, but it did not help. Then I read in the product User manual UM3579 about additional RST PIN so I tried also putting a jumper on P3 connector but still nothing. However then I traced it to PB5/D4 PIN which is actually not used and not advised to be initialized in the Getting started document.

So my question is: Do I need to use this pin, and if so, how exactly should it be used, to enable communication with STSAFEA110? Everything other, related to I2C, USART, expansion package itself is enabled, project compiles and app shows logs after flashing to Nucleo, but only unsuccessful logs.

Regards,
Tomasz

Best answer by Saket_Om

Hello @TomaszKucma 

The X-CUBE-SAFEA1 package does not support the STSAFE-L device (secure element embedded in X-NUCLEO-ESE02). You should use the X-CUBE-STSE01 v2.0 available on our website:

X-CUBE-STSE01 | Product - STMicroelectronics

2 replies

Saket_OmBest answer
Technical Moderator
March 30, 2026

Hello @TomaszKucma 

The X-CUBE-SAFEA1 package does not support the STSAFE-L device (secure element embedded in X-NUCLEO-ESE02). You should use the X-CUBE-STSE01 v2.0 available on our website:

X-CUBE-STSE01 | Product - STMicroelectronics

"To give better visibility on the answered topics, please click on ""Accept as Solution"" on the reply which solved your issue or answered your question.Saket_Om"
Associate
March 30, 2026

Ohhh I messed that up. I downloaded the right package and everything works good now. Thank you!