Explorer
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
HEADER7F / PCIe CONSOLE FREE BROWSER PREVIEW
Built for your bench. Ready for your team. ↗A board worked yesterday. Today it doesn’t.
See what changed, understand the captured state, and find your next step.
01 / INSPECT
Start with the answer. Keep every byte within reach.
Switch captures to see the values move. This is captured data, never live monitoring.
02 / COMPARE
A working baseline beside the capture you’re investigating.
03 / NAMED FIELDS
Apply your CSV field map to the capture from Inspect. Offsets refer to PCI config space, not BAR memory.
04 / SAVED SNAPSHOTS
Keep up to 20 captures on this browser. Give them names that tell their story.
FROM THE BENCH TO AN ANSWER
You already have the raw data. The workbench makes it easier to understand, compare and hand off.
Find its address with lspci -D, then capture the config space for that device:
sudo lspci -s 0000:01:00.0 -xxxReplace 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 ↗.
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.
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.
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
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.
Keep the working state next to the board and firmware version that produced it.
Compare the next build against an agreed baseline, with expected differences separated from surprises.
Give the firmware engineer, driver team or supplier one clear report to investigate.
START FREE. SHAPE WHAT COMES NEXT.
The browser preview is free. Paid plans below are proposed prices for features still in development. No payment is collected.
Understand one capture. Prove a difference.
Turn an investigation into a repeatable check.
Keep the team on the same working state.
BUILD IT AROUND YOUR BENCH
Tell us the recurring problem. We’ll respond about fit and scope. Early access is an enquiry, with no payment or purchase commitment.