I’m trying to understand why configASSERT( ( portNVIC_INT_CTRL_REG & portVECTACTIVE_MASK ) == 0 ); asserts within vPortEnterCriticial. portNVIC_INT_CTRL_REG == 0x3803 and portVECTACTIVE_MASK == 0xFF I’m not calling this from an interrupt, what am I missing? The task sends a queue, then calls ul…

That looks like somehow you are calling vPortEnterCritical from within an ISR, which isn’t allowed. Look at the stack trace back from the call to see what is happening.

The configASSERT checks that the code is not executing within an interrupt or exception handler when entering a critical section. portNVIC_INT_CTRL_REG refers to the Interrupt Control and State Register (ICSR) on ARM Cortex-M. portVECTACTIVE_MASK (0xFF) extracts the VECTACTIVE field (bits 0-8), whi…

This is not being called from an ISR, I rather think this was probably the problem. [image] Debugging FreeRTOS with GDB on STM32F7 Kernel First note: I have experienced this same issue on a windows host with a separate STM32 project. This leads me to believe it could be a…

Thank you for your finding! Did this fix resolve your issue? Are you also using a Cortex-M7? If so, which core revision are you working with?

vPortEnterCritical assert cause

Kernel

friesen (Erik Friesen) February 27, 2025, 4:09pm 4

This is not being called from an ISR, I rather think this was probably the problem.

Topic		Replies	Views
Issues with configASSERT Kernel	9	1241	September 29, 2020
Error in port.c,378 Kernel debug	1	960	November 9, 2022
Help with configASSERT in vPortExitCritical Kernel	2	315	April 13, 2017
Assert failed in port.c Kernel	5	644	June 21, 2024
Stuck in vPortEnterCritical Kernel	6	1085	April 19, 2014

vPortEnterCritical assert cause

Related topics