HardLabs
Board simulator

Simulate whole PCBs
with firmware-in-the-loop

Upload the schematic/netlist, BOM and firmware. HardLabs builds a simulator of your board and runs the real firmware against it.

Atmos G4
Ready

Design files

  • NETatmos.netKiCad netlist
  • BOMatmos-bom.csvBill of materials
  • ELFatmos_fw.elfFirmware · 412 KB

Board model

I²C1SPI1SPI2SPI3STM32G474Cortex-M4 · 170 MHzU1DPS368BarometerICM-42688-P6-axis IMUBMP280Pressure + tempW25N01GV1 Gbit NAND
Simulation logUART2
Waiting for design files…
Pressure
—hPa
Temperature
—°C
  1. Read design
  2. Build board model
  3. Attach part models
  4. Run firmware
Built by hardware and software engineers fromNVIDIABloombergAmazonStitch Fix

How it works

See it work on our demo board

Start the board, plug in USB-C, drop it, heat it and talk to its firmware. In the browser, or from your terminal with GDB attached.

hardlabs.io/app · HardLabs demo board
demo board

What bugs does this find?

Catch an I²C timing violation in software

Replay the bus trace, inspect timing margins, and fail the firmware run when SCL violates the peripheral's contract.

Caught 4 weeks before fab on a design-partner board

Atmos G4checks · atmos_fw.elf
1 failed · 3 passed
I²C1SPI1SPI2SPI3STM32G474Cortex-M4 · 170 MHzrunning atmos_fw.elfDPS368BarometerICM-42688-P6-axis IMUBMP280Pressure + tempW25N01GV1 Gbit NANDSCL high time too short0.42 µs < 0.60 µs Fast-mode
I²C1 · SCL / SDAfail
  • SPI1ICM-42688-P WHO_AM_I0x47
  • SPI2BMP280 chip id0x58
  • I²C1DPS368 SCL t_HIGH0.42 µs
  • SPI3W25N01GV JEDEC idEF AA 21
at drivers/i2c.c:118 · pc 0x0800_1A4C
I²C clock stretchSCL t_HIGH 0.42µs < 0.60µs Fast-mode.

Headless in CI

From schematic to CI

Regression-test firmware against the simulated board on every commit.

hardlabs/atmos-firmware #142
i2c: tighten SCL high time
  • boot sequencequeued
  • spi1 WHO_AM_Iqueued
  • i2c1 SCL t_HIGHqueued
  • spi3 chip idqueued

Design-partner program

Send us your design. We'll send you a simulator.

Send schematic, netlist, BOM and firmware. We build a working board simulator you can run, debug and put in CI.

You send
  • schematic / netlist
  • BOM
  • firmware image
We send back
  • working board simulator
  • peripheral models
  • setup that runs your firmware
  • CI integration (pilot scope)

FAQ

Questions engineers ask first.

Schematic/netlist, BOM, and firmware (ELF/bin or source + toolchain). Cadence, Altium, and KiCad exports work at launch. You write no models.