You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title says, EXTI config for maxim and aducm3029 needs an additional no_os_gpio_direction_input() call compared to stm32 which does this in the HAL generated code, as specified in the .ioc.
Now there are 2 solutions which we should discuss here:
Automatically perform this call for aducm3029 and maxim (and possibly others?) by adding this new feature.
I'd argue that setting the GPIO as input is normal for any EXTI on any platform and probably there is no harm in recommending performing the step for stm32 too, but this has to be tested.
The text was updated successfully, but these errors were encountered:
As the title says, EXTI config for maxim and aducm3029 needs an additional no_os_gpio_direction_input() call compared to stm32 which does this in the HAL generated code, as specified in the .ioc.
Now there are 2 solutions which we should discuss here:
The text was updated successfully, but these errors were encountered: