AnsweredAssumed Answered

LL code from CubeMX not clearing interrupts

Question asked by Dave Jones on Jul 15, 2017
Latest reply on Jan 15, 2018 by Jeanne Joly

I'm using CubeMX to generate the initial code for a custom board using an STM32L452. I've tried a couple of variations of settings, including using HAL for all the peripherals, and using a mix of HAL and LL.

 

When I use HAL for the EXTI pins, Cube creates an interrupt handler that includes a line in it that calls a generic EXTI GPIO handler that in turn clears the interrupt flag.

 

But when I have it use LL for the EXTI, it creates an empty interrupt handler with no calls to generic handlers, and no code to clear the interrupt flag.

 

I know asking for it to make LL code is asking for it to make a slim set of code, but leaving out anything to clear that flag seems a bit too slim. I would think that without clearing that flag, once that interrupt happens, it will happen constantly over and over again.

 

Shouldn't Cube have at least stuck in something simple to clear the interrupt?

Outcomes