# Mutex use cases

**URL:** <https://forums.freertos.org/t/mutex-use-cases/23102>\
**Category:** Kernel\
**Created:** [May 12, 2025, 10:54am UTC](https://forums.freertos.org/t/mutex-use-cases/23102 "2025-05-12T10:54:54Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![RAc](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rac/32/1389_2.png) [@RAc](https://forums.freertos.org/u/RAc)\
**Post date:** [May 28, 2025, 7:13am UTC](https://forums.freertos.org/t/mutex-use-cases/23102/20 "2025-05-28T07:13:26Z")

</div>

That may or may not work, but as Richard pointed out, it relies on some undocumented behavoir and thus may likely break with future versions of FreeRTOS.

Why not use this mechanism here

[Is there an API call (or equivalent) to tell if the scheduler is running? - Kernel - FreeRTOS Community Forums](https://forums.freertos.org/t/is-there-an-api-call-or-equivalent-to-tell-if-the-scheduler-is-running/13039/2)

so your sendchar routine uses the mutex only after the scheduler has started?

Also note that this code assumes that the USART is fully functional before the scheduler has started. That is normally not the case, in particular is it is interrupt driven.

---

_[View the full topic](https://forums.freertos.org/t/mutex-use-cases/23102)._