Yes. STM32 is the largest supported family: F103, F401, F407, F411, G474, H563, H735, L073, L476, WB55 and WBA52, with ready-made Nucleo and BlackPill board configs. Compile your firmware, point LabWired at the ELF, and run it against a virtual board — no hardware on the desk.
Yes. nRF52832, nRF52840, nRF5340 and nRF54L15 are supported, including the nRF52-DK, nRF52840-DK, nRF5340-DK and nRF54L15-DK board configs.
Yes. The RP2040 is supported with a Raspberry Pi Pico board config, so Pico firmware runs as-is against the virtual board.
Yes. ESP32, ESP32-C3 (RISC-V) and ESP32-S3 (Xtensa) are supported, with devkit board configs including ESP32-WROOM-32 and ESP32-C3/S3 devkits.
ARM Cortex-M, RISC-V RV32 and Xtensa (the ESP32 family). Cortex-M is the most complete architecture today and covers the STM32, nRF and RP2040 lineups.
Yes. Zephyr is a first-class target — build with your normal Zephyr toolchain and run the resulting ELF in the Playground or in CI.
All three. LabWired runs the compiled firmware, not the framework, so Arduino sketches, ESP-IDF apps and bare-metal C, C++ or Rust all work. PlatformIO projects can be compiled by the hosted builder service.
UART, GPIO, NVIC, SysTick, RCC and Flash are the most complete. I2C, SPI, ADC and DMA coverage is growing, and USB, CAN and Ethernet are partially modeled. External components include LEDs, buttons, TMP102/LM75B sensors, SSD1306 OLED, e-paper, Nokia 5110 LCD, TM1637 displays, an MLX90640 thermal camera, an ADXL345 accelerometer and a logic analyzer.
Your compiled firmware runs unmodified against hardware models whose registers and peripherals behave like the real chip. Execution is deterministic: same firmware, same inputs, same result — every run, on every machine. That is what makes simulation results usable as a CI gate.
No. Everything runs against virtual boards, in the browser Playground and in VS Code. See LabWired Pro for the full workbench.
One line: curl -fsSL https://labwired.com/mcp.sh | sh (Windows: irm https://labwired.com/mcp.ps1 | iex). It registers the hosted MCP connector (https://api.labwired.com/mcp) with Claude Code, Codex, Cursor, VS Code, or OpenCode — or use the open LabWired Agent. Agents assemble virtual circuits, run simulations and read the results through the same API the Playground uses.
Yes. Use the GitHub Action labwired/firmware-test@v1 or the Docker image ghcr.io/w1ne/labwired. Every run produces machine-readable artifacts — result.json, .vcd waveforms and the UART log — and supports fault injection. Details on the CI page.
Yes. The extension adds DAP debugging, a register inspector and a timeline view, so you can single-step firmware and inspect peripherals without a board connected.
The simulator core is open source under MIT at github.com/w1ne/labwired-core. The hosted Playground, builder and collaboration features are commercial.
The Playground is free. Hobby is $9/month, Pro is $39/month, and Enterprise is custom. See pricing.
Yes — that is the Enterprise tier: self-hosted and air-gapped runs, custom device onboarding and co-simulation. Talk to us.