2022-03-02 08:54 PM
2022-03-03 08:56 AM
As @TDK mentioned: hovering the disabled box shows The corresponding GPIO pin is left as "Free" and ....
So you need to assign the pin context to the Cortex-M7. To do that:
Does it answer your question?
Regards
/Peter
2022-03-02 11:33 PM
Simply tick the relevant box on EXTI Line, in this case EXTI Line [15:10]. A corresponding interrupt function is then generated by CubeMX or the CubeIDE.
You can read about the respective EXTI lines in the reference manual for the respective STM32 family.
Does it answer your question?
Regards
/Peter
2022-03-03 12:10 AM
2022-03-03 06:03 AM
There's probably a reason it's disabled. Hover over it and see if a note pops up. If that's not it, attach the IOC.
2022-03-03 06:45 AM
Disclaimer: I have no direct experience with dual-core STM32 CPUs, but... Do you need to map that EXTI pin to one of the cores first?
2022-03-03 08:56 AM
As @TDK mentioned: hovering the disabled box shows The corresponding GPIO pin is left as "Free" and ....
So you need to assign the pin context to the Cortex-M7. To do that:
Does it answer your question?
Regards
/Peter
2022-03-03 05:45 PM
I saw a popup hover over it
that talk "The corresponding GPIO pin is left as "Free" and not used by any middleware or pack."
Thanks to you, I was able to solve the problem.
2022-03-03 05:46 PM