Skip to main content
Associate
November 7, 2025
Solved

How to configure HSEM in STM32CubeMX

  • November 7, 2025
  • 1 reply
  • 482 views

The HSEM option is not found in "System Core" in STM32CubeMX (version 6.15), and the configuration option for HSEM interrupt is only found in NVIC. How to configure HSEM in STM32CubeMX. When I selected the LL library environment, the generated source code did not import the HSEM LL library header file. How to solve these two problems? If it is not possible to configure and import the HSEM related library files into the project file in STM32CubeMX, please let us know.

Snipaste_2025-11-07_15-12-55.png

Best answer by Mahmoud Ben Romdhane

Hello @liuxw 

Issue is fixed in the latest STM32CubeMX release 6.17.0.

You can get it through this link.

Thanks

Mahmoud

1 reply

Technical Moderator
November 7, 2025

Hello @liuxw 

 

Let me thank you for posting and welcome to the ST Community.

Your request is under investigation, and I will get back to you ASAP.

For more investigation, could you please provide your Ioc.File.

 

Thanks.

Mahmoud

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.
liuxwAuthor
Associate
November 7, 2025

Attached is my project file.

Technical Moderator
November 10, 2025

Hello @liuxw ,

 

I suggest that you take a look at this Knowledge Article. It shows how to implement inter-processor communication between CM7 and CM4 cores on the STM32H7 series using the hardware semaphore (HSEM). 

The configuration of the HSEM in STM32 devices is primarily managed through the NVIC (Nested Vectored Interrupt Controller).

For the second request, let me thank you for bringing this issue to our attention.

An internal ticket was submitted to the dedicated team (Internal Ticket Number: Ticket 221461).

I will let you know when the issue is fixed.

 

Thanks.

Mahmoud

 

 

 

 

 

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.