# Ask the board — ask your design

> Ask the board directly: pin states, I²C addresses, how to program a part — grounded in the netlist, datasheets and BOM.

_Source: E-Sharp (esharp.se) · Probe guide_


A review finds faults. Ask the board answers questions. The same boundary applies: the answer is grounded in the actual design, and what can't be proven isn't produced.

## How to ask

1. With your assistant connected to Probe over MCP, ask the question in plain language — "How do I put the board in JTAG boot mode?", "What I²C address does the temperature sensor have?", "How do I program the configuration flash?".
2. The assistant asks Probe, which reads the netlist, datasheets and BOM and answers.
3. Every answer carries its reference: netlisted, layout position or datasheet page. Click through to the source.

## Why it's reliable

Answers that don't rest on real connectivity are rejected at the write boundary, and citations are checked against their source. You get the part's *actual* function — not the average of many datasheets. More on that boundary in [AI for design review](/en/insights/ai-for-design-review).

It speeds up bring-up: pin states, bus addresses and programming steps without digging through schematic and datasheet. [See it live](/en/book-demo).
