Specialized hardware interfaces and system reliability for Zephyr RTOS. Covers LVGL GUI development, Audio I2S/Codecs, Watchdog timers, and Fault Injection. Trigger when building human-machine interfaces (HMI), audio devices, or high-reliability mission-critical systems.
Scanned 9/1/2026
Install to Claude Code
npx -y skills add beriberikix/zephyr-agent-skills --skill specialized --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Specialized?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/beriberikix-specialized)More formats (shields.io, HTML) on the badges page.
---
name: specialized
description: Specialized hardware interfaces and system reliability for Zephyr RTOS. Covers LVGL GUI development, Audio I2S/Codecs, Watchdog timers, and Fault Injection. Trigger when building human-machine interfaces (HMI), audio devices, or high-reliability mission-critical systems.
---
# Zephyr Specialized Hardware & Reliability
Integrate complex peripherals and build resilient systems that recover gracefully from unexpected failures.
## Core Workflows
### 1. LVGL GUI Development
Build sophisticated graphical user interfaces for LCD and TFT displays.
- **Reference**: **[lvgl_gui.md](references/lvgl_gui.md)**
- **Key Tools**: Widgets, Styles, Double Buffering, `native_sim` simulator.
### 2. Audio I2S & Codecs
Implement high-quality digital audio streaming and codec management.
- **Reference**: **[audio_i2s.md](references/audio_i2s.md)**
- **Key Tools**: `CONFIG_I2S`, DMA streaming, Ping-pong buffering.
### 3. Watchdog & Reliability
Ensure your system never hangs in the field using hardware watchdog timers.
- **Reference**: **[watchdog_reliability.md](references/watchdog_reliability.md)**
- **Key Tools**: `wdt_feed()`, Windowed watchdog, Health checks.
### 4. Fault Injection & Resilience
Test your system's ability to recover from unexpected software and hardware errors.
- **Reference**: **[fault_injection.md](references/fault_injection.md)**
- **Key Tools**: Chaos testing, `k_oops()`, Reset reason diagnostics.
## Quick Start (Watchdog Feed)
```kconfig
# Enable watchdog support
CONFIG_WATCHDOG=y
```
```c
// Feed the dog in your main loop
while (1) {
// Perform application work
wdt_feed(wdt_dev, wdt_channel);
k_sleep(K_MSEC(1000));
}
```
## Professional Patterns (Reliability & UX)
- **Safe Boot Animation**: Use a simple, non-interactive LVGL screen to show system status while critical subsystems (e.g., cloud connectivity) are initializing.
- **Zero-Pop Audio**: Always use volume ramping when starting or stopping I2S streams to protect hardware and improve user experience.
- **Bitmask Health Monitoring**: Use a bitmask to track the health of all background threads; the watchdog monitor only feeds the timer if ALL bits are set periodically.
## Automation Tools
- **[watchdog_window_check.py](scripts/watchdog_window_check.py)**: Verify feed interval timing against watchdog window constraints.
## Examples & Templates
- **[watchdog_health_map_template.h](assets/watchdog_health_map_template.h)**: Starter health-bit definitions for watchdog supervision.
## Validation Checklist
- [ ] GUI render loop maintains target frame behavior without starving control tasks.
- [ ] I2S audio stream starts/stops without underruns or audible artifacts.
- [ ] Watchdog feed policy resets the system when health criteria are not met.
- [ ] Fault-injection scenarios produce expected reset reason and recovery behavior.
## Resources
- **[References](references/)**:
- `lvgl_gui.md`: GUI widgets and performance tuning.
- `audio_i2s.md`: Audio streaming and DMA patterns.
- `watchdog_reliability.md`: Watchdog setup and health checks.
- `fault_injection.md`: System resilience and chaos testing.
- **[Scripts](scripts/)**:
- `watchdog_window_check.py`: Feed-window timing checker.
- **[Assets](assets/)**:
- `watchdog_health_map_template.h`: Health-mask template header.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!