A waveform screenshot can help an assistant discuss a stall, and an image of a report may be convenient when text is unavailable. However, the image may omit signal names, sample edges, units or the interval where the failure began. A fluent explanation of a cropped image is still a hypothesis. Supply machine-readable source data when available and permitted.
Input | Include | Do not infer |
|---|---|---|
Waveform | Clock edge convention, signal names, radix, reset interval, time scale and relevant protocol rule. | That post-edge display values necessarily equal the values sampled on that same edge. |
Timing report | Text report, clock definition, units, path type and constraints. | That a cropped negative number identifies the root cause or justifies a timing exception. |
Congestion image | Layer/metric legend, placement/routing stage and comparable run settings. | That a bright region proves a particular block caused congestion. |
Specification table | Heading, row/column labels, footnotes and document revision. | That an isolated cell applies without its conditions. |
Synthetic values sampled immediately before each rising edge
edge valid ready data
1 1 0 A
2 1 0 A
3 1 1 A
4 0 1 X (not meaningful)
rule: a transfer occurs on a rising edge with valid AND ready
observation: one transfer, at edge 3; no conclusion about later internal processingAsk the assistant to identify the sampled transfer edge and cite the rule, not merely describe a shape. Independently count the conjunction from the supplied table. If a screenshot appears to show data changing on an edge, inspect the simulator's sampling convention and raw trace before declaring a stability violation. A missing signal is a reason to request more evidence, not to invent it.
A screenshot shows valid high and ready low, but contains neither a clock nor a time scale. An assistant claims a five-cycle stall and a dropped packet. Which observations are supported, and what should the follow-up request contain?
The displayed region suggests backpressure, but cycle count and packet loss are not established. Request clock/sample convention, time scale, packet boundaries, the producer's data and the relevant capture interval. Check the raw waveform or a small exported table before acting.