Request access

Capability 03 / 05

Talks to your live board.

The agents flash through your debug probe, read the serial console, halt at breakpoints and read the registers of the running chip, so every answer comes from the hardware itself.

Request access for EnLab IDE See it run
J1U1STM32F407U2LSM6DSOY1C1C2TP1TP2R1D1J2IMU NODE · REV ADEBUG PROBESWD · 4 MHzimu.c40int imu_read(void) {41 spi_xfer(0x8F);42 while (!rxne()) {}43 return SPI1->DR;44}SERIAL · 115200REGISTERSRUNNINGPC0x0800_1A3CSP0x2001_FF80SPI1_CR10x0357SPI1_SR0x0003GPIOA_ODR0x0010DMA2_S0CR0x0000watching imu_read()
enlab — live board · imu node

›

Illustrative session

See it run

The answer was in a register.

A sensor stops answering after an hour. The agents halt the running chip, read the SPI status register, find the overrun, fix the driver and prove it with an eight-hour run.

Why it matters

The answer is on the board, not in the code.

A firmware bug often only shows on the running hardware: a flag in a register, a line in the boot log, a timing that slips.

EnLab reads that state directly, while the board runs, and acts on it.

What it does

Talks to the live board, with EnLab IDE.

  • Flash and verify

    Build, flash and verify through the probe you already own.

  • Serial console

    Boot logs and device output read live, in the same session.

  • Breakpoints and registers

    Halt at a breakpoint and read peripheral registers on the real chip.

  • Probe-aware

    ST-Link, J-Link, CMSIS-DAP and Black Magic Probe.

Questions

Asked a lot.

Which debug probes does it work with?
ST-Link, J-Link, CMSIS-DAP and Black Magic Probe.
Can it read registers on a running board?
Yes. It halts at breakpoints and reads peripheral registers on the live chip.
Does it read the serial output?
Yes. Boot logs and device output are read live during the session.
How do I try it?
Request access for EnLab IDE.

All five capabilities

The whole board, start to finish.

  1. 01Schematics and PCB designReads your schematic net by net and lays out the PCB, checked against the firmware.Explore
  2. 02Board bring-upFrom first power to a running main loop, every step checked on the real board.Explore
  3. 03Talks to the live boardFlashes through your debug probe and reads the serial console and registers of the running chip.You are here
  4. 04Drives your instrumentsSets up your scope, logic analyzer and power profiler and reads the real state of the hardware.Explore
  5. 05Autonomous testing and self-healingTests the real board on its own, finds what fails, fixes the firmware and re-tests until it passes.Explore

Bring up your next board with EnLab IDE.

Request access See EnLab IDE
Request access for EnLab IDE