From ac27aa0c4e8a948b1c41072edb9c019e97363cc1 Mon Sep 17 00:00:00 2001 From: Simon Beaudoin Date: Sun, 19 Jul 2020 22:23:23 -0400 Subject: [PATCH] Update port.c Forgot an * while writing comment.. --- portable/GCC/ARM_CR5/port.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/portable/GCC/ARM_CR5/port.c b/portable/GCC/ARM_CR5/port.c index 656d79a98..0658218a0 100644 --- a/portable/GCC/ARM_CR5/port.c +++ b/portable/GCC/ARM_CR5/port.c @@ -514,7 +514,7 @@ uint32_t ulPortSetInterruptMask( void ) * and 'vPortClearInterruptMask'. At the time of calling those functions, the interrupt mask is not set in the interrupt controller, thus the only protecting barrier * against the CPU traping into recursive interrupt was the IRQ Enable bit in the CPSR. By not taking it into acount, the very code that protects the CPU against * critical section violation just enabled it to happen : A SysTick was waiting to happen, and calling 'portCPU_IRQ_ENABLE' would enable it to occur... Thus triggering a - * switch of context while already performing a switch context. / + * switch of context while already performing a switch context. */ if(!wasIRQDisabled) portCPU_IRQ_ENABLE();