Skip to main content
Use these guides when a task spans several stages of development. Each one walks through defining success, checking the starting behavior, making changes, and verifying the result on the intended hardware.

Choose a workflow

Rapid bring-up

Establish startup, verify the first peripheral transaction, and save a repeatable board check.

Driver development

Build a peripheral driver from its datasheet and board connections, then verify normal and failure paths.

Debugging and RCA

Distinguish hardware and software causes, test a correction, and preserve the evidence behind it.

Automated testing

Build repeatable host, target, and bench checks with reviewable evidence.

Platform migrations

Preserve behavior and board constraints while moving firmware to new hardware.

RTOS migrations

Move firmware between real-time operating systems while preserving application behavior.

Performance optimization

Measure speed, memory, or power, make a bounded change, and compare again.

Work in small, verifiable steps

Start with one result you can test, then repeat these steps as the project grows:
1

Define the outcome

State one observable milestone or metric and the constraints the work must preserve.
2

Establish a baseline

Record the current build, test, target behavior, or measurement before changing the implementation.
3

Make a bounded change

Use Plan mode when the work has meaningful trade-offs, then implement the smallest useful increment.
4

Verify on the intended target

Repeat the same test or measurement and preserve the output needed for review.

Prepare your project

Quickstart

Install Embedder, initialize the repository, and verify your first change.

Core concepts

Learn how modes, approvals, sessions, skills, memory, and delegation work.

Monitor and debug

Collect serial, debugger, signal, power, trace, and coverage evidence.

Supported hardware

Check platform, peripheral, probe, transport, and instrument support.
Last modified on September 18, 2026