HEADER7F / PCIe CONSOLE FREE BROWSER PREVIEW

Built for your bench. Ready for your team. ↗

Less hex.
More direction.

A board worked yesterday. Today it doesn’t.
See what changed, understand the captured state, and find your next step.

Local analysis. No install. Your dumps stay on this device.
7FPCIe workbench CAPTURE → CONTEXT → NEXT STEPv0.2

01 / INSPECT

Understand this capture.

Start with the answer. Keep every byte within reach.

GUIDED EXAMPLETry before, after, or an unreadable capture.

Switch captures to see the values move. This is captured data, never live monitoring.

Paste or import a captureSAMPLE DATA
Single-device lspci hex rows or raw hex · up to 4 KiB
⌘ / Ctrl + Enter to analyze
Need a dump? See the capture guide ↗

FROM THE BENCH TO AN ANSWER

Bring a capture.
Leave with context.

You already have the raw data. The workbench makes it easier to understand, compare and hand off.

1. Capture one device on Linux

Find its address with lspci -D, then capture the config space for that device:

sudo lspci -s 0000:01:00.0 -xxx

Replace the address with your device’s address. Extended capabilities require a supported 4 KiB capture (-xxxx). Some devices react poorly to config reads; use an existing dump or check your device documentation first. See the lspci manual ↗.

2. Paste, decode, compare

Paste the hex rows for one device. Missing bytes remain unknown. To investigate a change, compare a known-good capture with one taken after the problem appears. Compare the same device and capture method.

3. Share the evidence

Export a Markdown report or JSON for your issue tracker. Reports include observed values, offsets and limitations. A capture cannot establish root cause, prove DMA performance or reveal a vendor-specific LTSSM state.

What works today?

PCI IDs, header type, command/status, BAR values, PCIe link capability/status, selected error flags, byte-by-byte comparisons, CSV config-space field maps and local snapshots. No agent, live register access, hardware writes, cloud storage or subscription billing is included in this preview.

THE PROBLEM WORTH PAYING TO SOLVE

Stop rebuilding the story
every time a board fails.

A hex decoder helps once. A trusted baseline, a repeatable regression and evidence your whole team can use help on every release. That’s the product we’re building toward.

01 / BRING-UP

Know where you started.

Keep the working state next to the board and firmware version that produced it.

02 / REGRESSION

Catch what changed.

Compare the next build against an agreed baseline, with expected differences separated from surprises.

03 / HANDOFF

Send evidence, not guesses.

Give the firmware engineer, driver team or supplier one clear report to investigate.

START FREE. SHAPE WHAT COMES NEXT.

A useful tool today.
A shared lab tomorrow.

The browser preview is free. Paid plans below are proposed prices for features still in development. No payment is collected.

AVAILABLE NOW

Explorer

$0 / browser preview

Understand one capture. Prove a difference.

  • PCIe config decode & error flags
  • Before / after snapshot comparisons
  • CSV named fields & report exports
  • Snapshots saved in this browser
Open the free workbench ↗
PROPOSED · IN DEVELOPMENT

Lab

$149 / month · up to 5 engineers

Keep the team on the same working state.

  • Everything proposed for Pro
  • Shared boards, baselines & maps
  • Read-only Linux agent workflow
  • Team roles & activity history
Discuss the Lab pilot ↗

BUILD IT AROUND YOUR BENCH

What keeps sending you
back to the hex dump?

Tell us the recurring problem. We’ll respond about fit and scope. Early access is an enquiry, with no payment or purchase commitment.

Please leave out raw dumps and proprietary details. We use this to respond to your request. Privacy notice.