AnsweredAssumed Answered

Is there a way to get CubeMX to link interrupts to a GPIO pin but have the interrupt start DISABLED in the areas of the code it manages?

Question asked by Ed Maynard on Sep 14, 2017
Latest reply on Sep 15, 2017 by Vangelis Fortounas

Using CubeMX 4.21.0

 

I have  GPIO that is attached to an EXTI interrupt. (Pin Configuration page)

On the NVIC Configuration page, the EXTI interrupts are Enabled

The EXTI interrupts are checked to generate IRQ handler (Code Generation)

With this configuration, I get the handler and the GPIO_Init() routines enables the interrupt

 

If I do not check the Enabled box on the NVIC configuration page, I don't get the interrupt handler emitted when the code is generated.

 

Using the init sequencing moves the interrupt enables to their own file but it is still within the sections of code overwritten by CubeMx. Thus, I would need to keep making changes every time i emit code from CubeMx.

 

Is there a way to have cubemx generate the interrupt handler and have the interrupt start disabled that does not require post processing the code?

Outcomes