Firmware & runtime logs
Analyze boot sequences, assertion failures, watchdog resets, HardFault traces, RTOS messages, and application diagnostics.
Product
A diagnostic copilot for embedded failures.
DebugArc gives engineers a structured first-pass investigation across firmware output, peripheral failures, runtime events, and hardware symptoms.
Peripheral & bus faults
Reason about I²C, SPI, UART, GPIO, sensor initialization, timing symptoms, and common hardware/software boundary failures.
Compiler & integration errors
Use source-level clues, build errors, configuration context, and board constraints to produce a focused investigation plan.
Input
Give DebugArc the context you already have.
The MVP accepts text-based evidence so an investigation can start immediately without a device agent or SDK.
✓UART / serial console output
✓Crash traces and fault registers
✓Compiler or linker output
✓Sensor and protocol symptoms
✓Plain-language issue descriptions
target: STM32
environment: FreeRTOS
input: UART log
[ERROR] I2C timeout at 0x68
[ERROR] WHO_AM_I = 0x00
[WARN] sensor retry failed
Output schemaSTRUCTURED
Classification
Subsystem · severity · confidence
Reasoning output
Likely root cause · supporting evidence · alternative causes
Action
Recommended checks · next measurement
Output
Predictable reports instead of free-form chat.
Claude Structured Outputs keep the result machine-readable, making it easier to render consistently, test output quality, and build future workflows around the same diagnostic schema.
Try the current MVP.
Start with a sample log, then replace it with your own embedded-system issue.
Open demo →