How Bringup works

The editor runs in the browser at /app. No account is needed to start; circuits stay in your browser until you save them to an account.

1. Pick a part in the library on the left, then click on the sheet to place it. Hold Shift to place several.
2. Draw wires with the wire tool: click a pin, click the corners, finish on a pin or an existing wire (or double-click).
3. Select a part to change its values in the inspector on the right. Right-click it to rotate, mirror or delete it, open its code or this documentation.
4. Start the simulation with ▶ Simulate. Hover over a wire or a pin to read voltage and current, place probes for the oscilloscope.
5. Switch between Schematic, PCB, Scene and Code at the top.

Circuits are drawn from parts of the library on one or more sheets. Every part carries its simulation model, its pins and, where known, a land pattern for the board. A circuit can be saved as a part of its own and used like any other part (hierarchical component).

The analog engine sets up the modified nodal analysis (MNA) of the circuit and solves it with Newton-Raphson: first the DC operating point, then a transient analysis in time steps. Diodes, transistors and the other nonlinear parts are limited between iterations as in SPICE.

Digital parts (Verilog, synthesized with Yosys) and microcontrollers run as digital agents next to it. A mixed-signal bridge exchanges pin levels with the analog solver after every accepted step: outputs drive the nodes through a driver resistance, inputs read the node voltages with thresholds. So analog parts, logic and firmware share one run.

Each part page in this documentation states which model the part uses: a built-in element, a SPICE subcircuit, Verilog, a behavioural model of a chip, or a microcontroller with real firmware.

Microcontroller parts run the binary you would flash, on an emulated CPU core. Write the code in the code view (Arduino sketch, bare-metal C or Zephyr, depending on the chip) and compile it, or load your own ELF / Intel HEX / BIN file in the inspector.

Probes, the oscilloscope and the logic analyzer read the running simulation. The heat map colours parts by dissipated power and estimated temperature, in the schematic and on the board in 2D and 3D. Parts driven beyond their ratings are marked as overloaded.

The power analysis evaluates recorded time windows of a current probe on a Li-ion cell: charge, peaks and an estimated runtime.

The Raspberry Pi Pico W connects to a simulated Wi-Fi network. Its firmware uses its real TCP/IP stack (lwIP); the router, the broker and the test server are part of the simulation. The Network panel shows all traffic.

Placement and routing are generated from the schematic, with rules per net type. Check the design rules, look at the board in 3D and export Gerber X2, drill files, BOM, placement file or a KiCad board. The files are not tied to one manufacturer.

Every part page shows the land pattern the generator uses and whether it is verified, a draft to check, a generic package or an off-board connector.

The 3D view shows the generated or imported board with its parts, and can colour it with the heat map. The Scene view arranges several boards as devices in space: antennas couple by distance and orientation.

The learning path loads one circuit per lesson and checks each task against the running simulation. The examples menu opens finished circuits, from an RLC circuit to a CPU built from 74xx chips.

An MCP server gives Claude Code and other MCP clients the same tools as the editor. There is no built-in chat; you use the agent you already have.

library_search

Finds parts and their pins

circuit_edit

Places and connects parts; the changes appear in the open editor

circuit_check

Finds wiring and supply mistakes

firmware_compile

Compiles firmware and loads it into the chip

circuit_simulate

Runs the circuit, measures with scope and logic analyzer, reads displays, steps through code

Without an account the editor works in the browser. An account stores projects and your own parts. Plans set the limits of the work done on the server: number of projects and parts, private projects, builds per day, Zephyr builds, fabrication and KiCad export, PDN analysis, more than two copper layers, MCP agents, API keys and commercial use. Where a feature is locked, the editor names the plans that include it; the account dialog lists the current offer.

Every part of the library has its own page, generated from the same definition the editor and the simulation use. In the editor, right-click a part or use the book icon in the library and the inspector to open it.

• Built-in circuit element 41
• SPICE subcircuit 20
• Verilog (digital engine) 29
• Microcontroller with real firmware 12
• Application processor booting Linux 2
• Behavioural mixed-signal model 52
• Hierarchical part (sub-schematic) 3
• No electrical model 2