Browse
STMicroelectronics Community
FAQs
Sign In
Product forums
STM32 MCUs
STM32 MCUs Products
STM32 MCUs Boards and hardware tools
STM32 MCUs Software development tools
STM32 MCUs Embedded software
STM32 MCUs TouchGFX and GUI
STM32 MCUs Motor control
STM32 MCUs Security
STM32 MCUs Wireless
STM32 MPUs
STM32 MPUs Products
STM32 MPUs Boards and hardware tools
STM32 MPUs Embedded software and solutions
STM32 MPUs Software development tools
MEMS and sensors
MEMS (sensors)
Imaging (sensors)
Automotive and Transportation
Automotive MCUs
AutoDevKit Ecosystem
GNSS positioning
Edge AI
Interface and connectivity ICs
Power management
ST25 NFC/RFID tags and readers
STM8 MCUs
Others: hardware and software
Analog and audio
Knowledge base
STM32 MCUs
STM32 MPUs
MEMS and sensors
Analog and audio
EMI filtering and signal conditioning
Interface and connectivity ICs
Power management
Quality & reliability
Academy
About
Community guidelines
Feedback forum
Community blog
Developer news
Frostlike7646
Associate
since
2021-08-02
2023-06-14
User statistics
1
Posts
0
Solutions
0
Kudos given
0
Kudos received
STMicroelectronics Community
About Frostlike7646
Options
Report User
User Activity
Posts
Replies
No posts to display.
Re: Hello, I am using the B-L475E-IOT01A2 board and I am trying to adapt the STSAFE-A110 secure element to it. Independent of the input I2C message, I always receive the same message from the slave (see details).
2021-08-04
Just wanted to say thank you for updating with your findings, this was key to getting me on the right track. It certainly does look like `STSAFEA_CRC_SUPPORT` is hardcoded to 1 (enabled) in stsafea_core.c, and never changed.
