cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeMX 6.13.0 wrong code generated for handling EXTI on STM32H747 M4 Core

peterdonchev
Associate III

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.

 

6 REPLIES 6
Ghofrane GSOURI
ST Employee

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

SofLit
ST Employee

Hello @peterdonchev ,

Kindly use </> button to paste a code. See Tips here. I'm editing your post.

Thanks

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.
PS: Be polite in your reply. Otherwise, it will be reported as inappropriate and you will be permanently blacklisted from my help/support.
Ghofrane GSOURI
ST Employee

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 :

GhofraneGSOURI_0-1736847916394.png

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

Hello @Ghofrane GSOURI ,
Can I share it with you privately?
Regards,
Peter

Hello @peterdonchev 

Yes of course .

BR,

Ghofrane

p.s.: I migrated your project to STM32Cube FW_H7 V1.12.1 and the problem reappeared!