Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem


Desinherit after different mutex is given

Posted by Benjamin Meier on April 10, 2013
Hi all,

whilst analyzing my software i found something that concerned me.
I was wondering why the priority of the control-task is set back at this point in time.
But first things first.

The image below shows a part of a trace captured with percepio. There are no events hidden.
There are mainly three active tasks.
- Display (Priority 1)
- Radio (Priority 2)
- Control (Priority 3)

To share some resources with tasks (some were not active during the capture) there are mainly two mutexes:
- SPI Mutex
- Radio Mutex

Any task communicating with the display has to have the SPI mutex first.
Any task communicating with the radio needs to get the Radio mutex and then the SPI mutex.

Even though it isn't very pretty the control-task attempts to get the Radio-mutex and blocks.
This leads to the inheritance of the priority of the Radio-task, which has the radio mutex during the whole capture.

Somewhat later the priority of the radio-task is returned to its original priority (2).
This right after the radio-task returns the other mutex (SPI).

I cannot see any reason why this should be. The Radio-mutex is still owned by the radio-task.

Thanks for any idea, I'm quite confused right now...

RE: Desinherit after different mutex is given

Posted by Benjamin Meier on April 10, 2013
Also should to my opinion the control-task get active if the priority of the radio task was actually returned to 2.

RE: Desinherit after different mutex is given

Posted by Richard on April 10, 2013
The priority inheritance mechanism is very simply and does not stack inherited priorities - it assumes only one mutex is held at a time.


[ Back to the top ]    [ About FreeRTOS ]    [ Privacy ]    [ Sitemap ]    [ ]

Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

FreeRTOS v10.2.0 is available for immediate download. MIT licensed, and including RISC-V and ARMv8-M (Cortex-M33) demos.

NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.

View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.


FreeRTOS and other embedded software careers at AWS.

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Cadence Tensilica Cortes

Espressif ESP32

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers





STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS

Xilinx Microblaze and Zynq partner