embedded-systems-development

What problem does it solve?

Embedded projects fail when teams guess at memory, timing, tooling, or verification needs instead of designing for microcontroller realities.

Core Features & Use Cases

• Hardware-accurate planning: Choose an MCU/RTOS/toolchain and define a buildable bill of materials, peripheral approach, and cost constraints for projects like sensor gateways, motor controllers, or battery-powered firmware.
• Constraint-first engineering: Produce a memory map, ISR latency budget, and power budget (active/sleep) that are measurable rather than optimistic for designs like real-time control loops and low-power telemetry.
• Verification and “done” enforcement: Define reproducible build, hardware-flash run, stack worst-case measurement, OTA with rollback rehearsal, and evidence-based completion for production readiness.

Quick Start

Use this skill to plan an ESP32 firmware approach for deep-sleep sensor sampling with a measured ISR budget and an OTA rollback strategy: “Create an embedded plan for an ESP32S3 that wakes from an external interrupt, performs a DMA-assisted sensor read, logs results, estimates a power budget, and includes a testable OTA plan with rollback.”