cancel
Showing results for 
Search instead for 
Did you mean: 

TICK_INT_PRIORITY affected by enabling TRACE outputs

JPerr.2
Associate III

I'm working on a project based on a STM32F107VC using CubeMX V6.3.0 using STM32Cube FW_F1 V1.8.4. In this project, the Timebase Source is set to TIM7. In the original project state, the code generation defines TICK_INT_PRIORITY to 0U.

We need to remap some I/O to allow the TRACE mcu outputs to be used. When one of the pins PE2 to PE6 is assigned to the trace feature, the interrupt priority of TIM7 is automatically changed to 15, resulting in a modified  TICK_INT_PRIORITY value of 15U.

It is possible to manually reassign the preemption priority of TIM7 to 0, but I'm not sure if this will have any effect on the Trace feature. Is there a reason why the TIM7 priority is forced to 15?

0 REPLIES 0