michaelh/zephyr
1
0
Fork 0
Code Releases Activity

arm: ensure SysTick IRQ level is set unconditionally

Browse source 
When the SoC implements SysTick, but the system
does not use it as the driver for system timing
we still need to set its interrupt level. This
is because the SysTick IRQ is always enabled,
so we must ensure the interrupt priority is set
to a level lower than the kernel interrupts (for
the assert mechanism to work properly) in case
the SysTick interrupt is accidentaly raised.

Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
This commit is contained in:
Ioannis Glaropoulos 2021-06-16 15:41:11 +02:00 • committed by Christopher Friedt
commit 6981b84550
1 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
arch/arm/include/aarch32/cortex_m/exc.h
View file

@ -145,6 +145,19 @@ static ALWAYS_INLINE void z_arm_exc_setup(void)
* SecureHardFault in a PE without the Main Extension.
*/
#endif /* ARM_SECURE_FIRMWARE && !ARM_SECURE_BUSFAULT_HARDFAULT_NMI */
#if defined(CONFIG_CPU_CORTEX_M_HAS_SYSTICK) && \
!defined(CONFIG_CORTEX_M_SYSTICK)
/* SoC implements SysTick, but the system does not use it
* as driver for system timing. However, the SysTick IRQ is
* always enabled, so we must ensure the interrupt priority
* is set to a level lower than the kernel interrupts (for
* the assert mechanism to work properly) in case the SysTick
* interrupt is accidentally raised.
*/
NVIC_SetPriority(SysTick_IRQn, _EXC_IRQ_DEFAULT_PRIO);
#endif /* CPU_CORTEX_M_HAS_SYSTICK && ! CORTEX_M_SYSTICK */
}
/**