FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Clarification on IEC 60730 Class B compliance for STM32G031xx and use of X-CUBE-CLASSB-G0 library

Aayush
Associate

‎2025-10-07 11:18 PM - last edited on ‎2025-10-14 6:29 AM by

Hello,

I’m currently working on an application using the STM32G031xx MCU and need to ensure IEC 60730 Class B compliance for safety-critical software. I found the X-CUBE-CLASSB-G0 (v4.0.0) library and have a few questions:

  1. Is X-CUBE-CLASSB-G0 v4.0.0 the correct library to use for Class B compliance with the STM32G031xx series?

  2. Does the library already include all the required safety routines (e.g., CPU register tests, RAM tests, clock tests, stack/PC tests), or do I still need to implement additional safety code manually, such as the March-C test for RAM?

  3. Are the provided function prototypes in the library sufficient to meet compliance if I integrate and call them as recommended in the documentation, or should I modify or extend them to achieve full Class B certification?

  4. For example, the function is declared as
    STL_Status_t STL_SCH_InitRam(STL_TmStatus_t *pSingleTmStatus);
    but there is no visible definition. Do we need to implement this function ourselves, or is the definition (including the March-C test implementation) already provided in the library? How can we confirm that a definition is associated with this declaration?

Any official guidance or examples for integrating this library into an STM32G0 project would be greatly appreciated.

Thank you!

0 Kudos
1 REPLY 1
Petr Sladecek
ST Employee

‎2025-10-14 7:29 AM

Hello,

I believe that most of the questions can be answered by proper reading of dedicated UM3083. Integration example source code give you additionally practical correct implementation way how the library should be integrated into user application.

Chpt 3.2. replies #1; all the G0 subfamily are supported.

Chpt 4.1. replies #2, #3, #4; The FW includes test modules to test generic MCU parts like Core registers, RAM functionality and Flash content integrity including scheduler of these modules. You can learn about mandatory steps to perform these modules correctly there, too. Chpt 7 describes details about all the APIs, functions and user configuration structures associated with these modules which are certified and fully cover requirements of the standard as visible from Table 35 at chpt 10. Clock test is part of the FW integration example as noted at chpt. 9 summarizing as well other application specific test to be added by end user (not included at ST solution).

Hopefully this can help you to integrate the FW correctly at your application.

Best regards,

Petr

0 Kudos
Top