STM32CubeMX 6.13.0 wrong code generated for handling EXTI on STM32H747 M4 Core
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-13 1:31 PM - last edited on ‎2025-01-14 12:53 AM by mƎALLEm
STM32CubeMX 6.13.0.
MCU - STM32H747.
LL library selected.
Generating the EXTI2_IRQHandler for the M4 core:
void EXTI2_IRQHandler(void)
{
/* USER CODE BEGIN EXTI2_IRQn 0 */
/* USER CODE END EXTI2_IRQn 0 */
if (LL_EXTI_IsActiveFlag_0_31(LL_EXTI_LINE_2) != RESET)
{
LL_EXTI_ClearFlag_0_31(LL_EXTI_LINE_2);
/* USER CODE BEGIN LL_EXTI_LINE_2 */
/* USER CODE END LL_EXTI_LINE_2 */
}
/* USER CODE BEGIN EXTI2_IRQn 1 */
/* USER CODE END EXTI2_IRQn 1 */
}
The generated code uses LL_EXTI_IsActiveFlag_0_31 and LL_C_EXTI_ClearFlag_0_31 instead of LL_C2_EXTI_IsActiveFlag_0_31 and LL_C2_EXTI_ClearFlag_0_31 for CORE2.
- Labels:
-
Bug-report
-
Interrupt
-
STM32CubeMX
-
STM32H7 series
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-14 12:45 AM
Hello @peterdonchev
First let me thank you for posting.
I'm currently checking this internally and will get back to you as soon as possible.
THX
Ghofrane
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-14 12:53 AM
Hello @peterdonchev ,
Kindly use </> button to paste a code. See Tips here. I'm editing your post.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-14 1:47 AM
Hello @peterdonchev
Actually I tried to reproduce the issue mentioned above but I found that CubeMX 6.13.0 works just fine and this is my generated code :
I am sharing my IOC with you to double check my configuration.
I would appreciate it if you could provide your IOC to continue the investigation.
I will be waiting for your feedback.
THX
Ghofrane
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-14 2:13 AM
Hello @Ghofrane GSOURI ,
Can I share it with you privately?
Regards,
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-14 2:17 AM
Hello @peterdonchev
Yes of course .
BR,
Ghofrane
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-14 2:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-15 12:44 AM
Hello @peterdonchev
This issue has been raised to the development team to correct this behavior internal ticket number 200413 .
If there are any updates, I'll keep you posted.
THX
Ghofrane
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-05-20 6:21 AM
Hello @peterdonchev
The issue is fixed in the latest release of the STM32CubeMX (6.14.0).
KR,
Semer.
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.
