How to Detect and Prevent Race Conditions in Embedded Firmware

Embedded firmware bugs such as race conditions and non‑reentrant functions are hard to reproduce, but by understanding their causes, using atomic operations, mutexes, and clear naming conventions, developers can systematically identify, avoid, and mitigate these hidden errors in RTOS‑based systems.

Best PracticesRTOSnon-reentrant

0 likes · 7 min read

How to Detect and Prevent Race Conditions in Embedded Firmware

360 Zhihui Cloud Developer

Sep 18, 2018 · Backend Development

How to Implement Non‑Reentrant Functions in Go: Mutex and Atomic Solutions

This article explains what a non‑reentrant function is, why it matters in concurrent Go programs, and demonstrates two practical implementations—using a sync.Mutex and an atomic flag—to ensure a function runs only once at any given time.

ConcurrencyGoGoroutine

0 likes · 5 min read

How to Implement Non‑Reentrant Functions in Go: Mutex and Atomic Solutions