Closed zerovijay closed 4 months ago
Make sure your interrupt service routine is part of the build.
Fixed an issue where the USART6 interrupt was causing an infinite loop due to incorrect vector table alignment in the startup code.
Left one is incorrect one and right one is correct i got from stm32cubeide
External Interrupt on GPIO PA0 Not Working in STM32 VS Code Extension
Description
I have configured an external interrupt on GPIO PA0 to trigger on the falling edge via EXTI 0. The code works perfectly when using the STM32CubeIDE, but it fails to function as expected when using the STM32 VS Code extension.
I am using bare metal code, not relying on STM32 vendor libraries or CMSIS. Despite my deep dive into the registers and configurations, and numerous successful builds and uploads, the interrupt remains stubbornly non-functional in the VS Code extension environment.
Code Snippet
Steps to Reproduce
Expected Behavior
The interrupt should trigger on the falling edge of PA0 in both STM32CubeIDE and STM32 VS Code extension environments.
What I Have Tried
Additional Information
After many hours of staring at registers and flags, I think I've developed a slight case of brain damage. My coffee intake is through the roof. Any help to resolve this issue before I start talking to my microcontroller would be greatly appreciated!
Please assist me in resolving this issue.
Thank you!