UBEMX generated EXTI IRQ handler with wrong symbolC

[FColl.1]

I have two gpios enabled one as an output another as a interrupt input. PA11 and PI11 respectively. There are two pin defines generated by CUBEMX, for argument call them MYPINA_Pin and MYPINB_Pin respectively.

For the interrupt handler CUBE generates code like this...

void EXTI15_10_IRQHandler(void)
{
 /* USER CODE BEGIN EXTI15_10_IRQn 0 */
 /* USER CODE END EXTI15_10_IRQn 0 */
 HAL_GPIO_EXTI_IRQHandler(MYPINA_Pin);
}

While this results in correct machine code because MYPINA_Pin == MYPINB_Pin, it is quite alarming and reduces my confidence in CUBEMX. Not to mention confusing. If I want to track down some code and I search for MYPINB_Pin I will not find the interrupt handler.

Has anyone else seen this and/or reported it to ST?

[TDK]

> Has anyone else seen this and/or reported it to ST?

Yes, it's been reported a handful of times.

https://community.st.com/s/question/0D53W00001FQUu1SAH/cubeide-incorrectly-generates-the-initial-code-of-exti-handlers-namely-it-substitutes-the-wrong-names-with-user-labels

https://community.st.com/s/question/0D53W00001K2AvVSAV/bug-report-on-code-generation-for-stm32h745-using-stm32cubemx-v640

[FColl.1]

Thanks for that. It is a hard issue to come up with a good search query string!

[Zaher]

Oh yeah, I've been struggling with interrupts on STM32L552ZE since yesterday. I just figured out that the EXTI handlers generated from STM32CubeMX 6.4.0 had wrong GPIO Pin names. I just replaced the names for the EXTI handlers to get interrupts working.

One more thing to add, the edge detector didn't detect the interrupt when the signal goes through line driver buffer. I used the buffer as a 5v <> 3v translator, along with a 16-bit bus transceiver. I wanted to ensure complete bus isolation on a given device while reading/writing another one that shares the same bus/IO. signals. I had to use a jumper wire and assign a different EXTI for direct connection between the external interrupt signal and the STM32.

[Sara BEN HADJ YAHYA · Accepted solution]

Hello @FColl.1​ , @Zaher​ ,

This issue is fixed from CubeMX v6.5.0.

Sara.

[Zaher]

Hello @Sara BEN HADJ YAHYA​ ,

Thank you very much for letting me know. I will update CubeMX pretty soon!

Rgs,

Zaher