agency-embedded-firmware-engineer

To design an RTOS task architecture avoiding priority inversion, outline your target MCU and memory budget first, then apply deterministic task patterns with proper stack sizing and safety-critical error handling to ensure predictable real-time behavior.

The best way to implement non-blocking ISRs in embedded firmware is to apply platform-specific conventions across ESP-IDF, STM32, or Nordic platforms, satisfying static analysis requirements and keeping interrupt service routines deterministic for constrained devices.

Yes, this embedded firmware approach works with ESP-IDF, STM32 LL/HAL, and Zephyr/Nordic platforms, providing platform-specific guidance to ensure maintainability, testability, and robust peripheral driver implementation across different MCU families.

To build robust peripheral drivers for UART, SPI, and I2C with safe error handling, implement non-blocking patterns and apply safety-critical error handling protocols tailored to your specific MCU family to ensure production-grade reliability.

RTOS firmware deadlocks on constrained devices often stem from poorly structured task synchronization; applying static analysis and proper stack sizing during the design phase helps identify and prevent these timing and resource conflicts early.