2025-04-10 2:21 AM - edited 2025-04-10 2:51 AM
An error in the interrupt priority configuration of the STM32MP135 code generated by CubeMX will result in all interrupts being set incorrectly. For example, if you set the interrupt priority for EXTI0 to 10 in CubeMX, the code will be generated:
IRQ_SetPtiority(EXTI0_IRQn, 10);
And the correct way is to shift the priority by 3 bits:
IRQ_SetPtiority(EXTI0_IRQn, 10<<3);
Can this be fixed in future releases?