Use default SysTick interrupt priority.

We really don't want SysTick_Handler, which runs the task scheduler, to
run at a higher priority than SVC_Handler, which runs supposedly-atomic
operations like mutex locking and unlocking. I've seen a mutex lock/unlock
mismatch which I think is due to interrupting rt_mut_release at a
particularly inopportune moment.

1 files changed, 0 insertions, 1 deletions

diff --git a/stm-init.c b/stm-init.c
index 0016e13..51b2ae7 100644
--- a/stm-init.c
+++ b/stm-init.c
@@ -78,7 +78,6 @@ void stm_init(void)
   /* System interrupt init*/
   /* Sets the priority grouping field */
   HAL_NVIC_SetPriorityGrouping(NVIC_PRIORITYGROUP_0);
-  HAL_NVIC_SetPriority(SysTick_IRQn, 0, 0);
 
   /* Initialize all configured peripherals */
 #ifdef HAL_GPIO_MODULE_ENABLED