Pin-compatible alternates
Find replacement parts for the selected component, scored against the verified gold model — footprint, interfaces, supply range, and abs-max. Drop-ins are safe swaps; “review” needs a firmware or layout change; blocked parts fail a hard constraint.
Candidates
Pin-mux planner
Declare the interfaces your board needs; the planner assigns each to conflict-free physical pins from the verified pinout and emits a locked pin-map (CSV + Zephyr pinctrl). It flags real hazards — pins shared with SWD/JTAG, crystals, or reset, and analog-only pins asked to carry a digital function — and reports anything it can't place rather than guessing.
Power tree & battery life
Per-rail current budget from the verified current-consumption data, rolled up across a duty-cycle scenario into an average draw and battery-life estimate. Built for the low-power, coin-cell world these boards live in.
Firmware scaffolding
Generate a Zephyr devicetree overlay and a C pin/address header as
bring-up scaffolding seeded from the verified pinout. Bus type, I²C address and pin numbers
are datasheet-verified; the board wiring (IRQ GPIO, chip-select, mux) is left as TODO
comments to fill in — this is generated from the MPN, not from your schematic.
Whole-board handoff
Generate an I²C board overlay, connectivity pin-map and Kconfig TODOs from the active project. Exact package-pin connectivity is preserved; GPIO controller indexes, chip-selects and unresolved address straps are never guessed.
Calculators
Same math as the xERC rules — cited, refuse-to-guess.
ldo_dissipation
divider
led_resistor
i2c_rise_time
crystal_load_caps
buck_inductor
trace_width
thermal_via_array
All 33
Design analysis
Run the full manufacturing-readiness suite — BOM health, DFM, worst-case (WCCA), compliance, the design-review gate, fab constraints and the BOM export — on a whole project board (every part) or on a single component. These are board-level analyses, so a real multi-part project is the right input. Same engine the API and xERC run.
Part data
Everything the pipeline knows about the selected verified component: live sourcing (lifecycle, RoHS/REACH, offers), the e-datasheet export with its conformance check, and the full verified component record with coverage.
Catalog search
Tolerance & search
Monte-Carlo tolerance analysis over a parametric preset (divider output, divider ratio, RC corner) plus the extreme-value bound and spec yield — and a semantic search across the verified component corpus.
Monte-Carlo tolerance
MLCC voltage/temperature derating
Semantic component search
Power tree
Build a regulator chain — a source plus buck / boost / LDO stages — and get per-stage loss + efficiency, total input power, and the end-to-end efficiency. Switchers take an efficiency; LDOs are computed from Vin/Vout/Iout (AN761).
Source
Stages
Project docs
Bring an external BOM in (paste CSV → scrubbed + resolved against the verified corpus) and build a requirements traceability matrix (RTM) — coverage per requirement, orphans, and design items nothing traces to.
BOM import
Paste CSV with a header row (e.g. mpn,qty,refdes).
Requirements traceability (RTM)
One requirement per line: rid | text | priority (priority optional). Add trace links below as rid → target to mark a requirement implemented/verified.
Simulation workbench
Configure and inspect a bounded ngspice micro-circuit run. Project context, logical revision, solver capability, artifacts, and claim limits remain visible with the result. A successful run is diagnostic evidence only and never schematic, PCB, or release signoff.
Run setup
One device per line: ref type node1 node2 value. The type must match the reference prefix. Node 0 is ground.