What is the difference between a critical section and a mutex in FreeRTOS?

A critical section masks interrupts up to configMAX_SYSCALL_INTERRUPT_PRIORITY on Cortex-M (or disables them globally on simpler architectures), providing atomic access but increasing interrupt latency. A mutex uses priority inheritance and only blocks tasks that contend for the same resource, allowing all ISRs to continue executing.

When should I use taskENTER_CRITICAL vs a mutex?

Use taskENTER_CRITICAL for very short operations (a few instructions) where interrupt latency must be minimized, such as accessing hardware registers or updating a few bytes of shared data. Use a mutex for longer critical regions, complex data structures, or when you need priority inheritance to prevent priority inversion.

How does FreeRTOS implement critical sections on ARM Cortex-M?

On Cortex-M, FreeRTOS uses the BASEPRI register to mask interrupts up to configMAX_SYSCALL_INTERRUPT_PRIORITY rather than globally disabling interrupts with PRIMASK. This allows high-priority ISRs (above the syscall threshold) to remain responsive while protecting kernel data structures.

What is the maximum time a critical section should take?

Critical sections should execute in microseconds — typically under 10 µs on modern Cortex-M cores. Longer sections degrade interrupt latency and can cause missed deadlines in hard real-time systems. If your critical section exceeds this, refactor to use a mutex or redesign the data access pattern.

Can I call FreeRTOS API functions inside a critical section?

No. Calling FreeRTOS API functions (like xQueueSend, xSemaphoreGive) inside a critical section is undefined behavior. The API functions themselves use critical sections internally and may re-enable interrupts or yield. Always use the FromISR variants in ISRs and regular API functions from tasks outside critical sections.

Home About Us Contact Us

Embedded OS
28

Operating System that runs on an embedded device control and monitors the system resources efficiently in a reliable manner. Embedded OS orchestrates execution of various applications that may run on the embedded device without conflicts.