Probe E# — E-Sharp AB
Probe is made by E# (E-Sharp AB) in Sweden. Want your own boards reviewed like this? Book a meeting

TIMIQ CPU

OHWR0060 · revision R1

TIMIQ CPU (OHWR0060 R1) is an open-hardware circuit board from the CERN Open Hardware Repository, designed in KiCad EDA: a 8-layer board of 160 × 160 mm with 338 components and 456 nets, published under CERN-OHL-1.2.

review 82% walked · 22 findings: 12 major · 10 minor (206 items)

Open in the interactive viewerRead the full review

TIMIQ CPU (OHWR0060 R1) circuit board, top view: copper, silkscreen and components
Top view, rendered by Probe from the design's own fabrication data.

Design review

Probe recorded 22 findings: 12 major · 10 minor (206 items) on this design. Each is shown here with its reasoning; the full review links every one to the pins, nets and datasheet pages it rests on.

  1. observationOBS-147majorOpen

    FPGA PROG_B reset needs BOTH the supervisor and the FPGA's own RST_FPGA to assert: the two pull-down FETs on Q8's gate form an AND, so neither reset source works alone

    FPGA PROG_B reset needs BOTH the supervisor U22 and the FPGA's own RST_FPGA to assert: the two pull-down FETs Q4/Q5 on Q8's gate form an AND, so neither reset source works alone.

    The circuit

    ``mermaid flowchart LR U22["U22 LTC2908 RST<br/>R129 10k pull-up"] --> Q5["Q5 BSN20"] RST["RST_FPGA, U12 C15<br/>R128 10k pull-up"] --> Q4["Q4 BSN20"] Q4 -- "R131 0R" --> G["Q8 gate node<br/>Net-(Q5-Pad3)<br/>R133 10k to 3V3"] Q5 -- "pulls low" --> G G --> Q8["Q8 BSN20"] -- "R136 / R138 0R" --> PB["PROG_B_FPGA<br/>U12 T2, R135 4.7k pull-up"] ``

    • Q8 pulls PROG_B_FPGA low (FPGA reconfigure) only when its gate node Net-(Q5-Pad3) is high through R133 10k.
    • Q5 is on, pulling that node low, whenever U22 RST is high (supplies good).
    • Q4 is on, pulling it low through R131 0R, whenever RST_FPGA is high.
    • Q8 therefore turns on only when U22 RST is low and RST_FPGA is low.

    What that means

    SituationResult
    Supplies good, FPGA pulls RST_FPGA lowQ5 still holds Q8 off: the FPGA cannot reset itself
    A rail drops, RST_FPGA high or floating on R128 (its state before and during configuration)Q4 holds Q8 off: U22 cannot assert PROG_B

    Why it matters

    The sheet block is titled 'Power monitor & FPGA reset': each source is evidently meant to reset the FPGA on its own (a wired-OR of reset requests). As drawn the supervisor output is masked for exactly the cases it exists for (brown-out, unconfigured FPGA), and the FPGA's self-reset only works during a supply fault. Fix: make the two requests OR onto Q8, e.g. drive Q8's gate from a diode-OR / two parallel FETs pulling PROG_B directly, or invert the RST_FPGA sense so Q4 and Q5 act in series.

  2. observationOBS-613majorOpen

    LP3883ES-1.2 went end-of-life (Obsolete)

    Vendor (DigiKey) lifecycle for LP3883ES-1.2 (Texas Instruments's listing) changed from "Active" to "Obsolete" since this board was reviewed. Placed as U25. A sourcing/longevity risk; consider a replacement before production.

  3. concernCON-001majorOpen

    [eol:LP3883ES-1.2:Obsolete] LP3883ES-1.2 lifecycle changed from "Active" to "Obsolete" since this board was reviewed: OHWR0060 R1 TIMIQ CPU. A sourcing and longevity risk. Should this be replaced before the next build?

  4. ReferencePlaneDiscontinuitymajorOpen

    123 nets change reference between 3V3 and GND at 153 vias, none with a reference that continues across (fastest: /TOP/FPGA_configuration//CF_FPGA at 100 ps 10-90 %, ASSUMED)

    At 153 via(s), on 123 net(s), the signal leaves a layer referenced by one of 3V3 and GND for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 153 with none. 153 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether 3V3 and GND are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

    • '/TOP/Ethernet_PHY/1000_LED' at (174.23, -115.93), L1_TOP -> L8_BOTTOM: GND on L2_GND to 3V3 on L7_PSU; pure, no reference continues across; stitching none, 102.4 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/1000_LED' at (177.32, -115.93), L1_TOP -> L8_BOTTOM: GND on L2_GND to 3V3 on L7_PSU; pure, no reference continues across; stitching none, 102.4 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/1000_LED' at (189.15, -114.7), L1_TOP -> L8_BOTTOM: GND on L2_GND to 3V3 on L7_PSU; pure, no reference continues across; stitching none, 102.4 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/1000_LED' at (189.16, -111.29), L1_TOP -> L8_BOTTOM: GND on L2_GND to 3V3 on L7_PSU; pure, no reference continues across; stitching none, 102.4 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/PHY_INT' at (178.14, -94.29), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 94.8 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/PHY_RXD2' at (184.46, -149.67), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 91.4 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/PHY_RXD2' at (193.88, -149.67), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 91.4 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/PHY_RXD5' at (184.46, -148.8), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 89.2 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/PHY_RXD5' at (193.77, -148.8), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 89.2 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/PHY_RXDV' at (184.46, -150.43), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 76.6 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/PHY_RXDV' at (193.87, -150.43), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 76.6 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • '/TOP/Ethernet_PHY/PHY_RXD1' at (179.87, -135.91), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 76.1 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
    • and 141 more

    Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=refchange%3A3V3%7CGND serves each with its own layer_image region; all of them lie in x 113.46..242.85, y -221.92..-83.17 mm (board frame, Y up).

    The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    At refchange:3V3|GND

  5. DecapViaFanoutmajorOpen

    DecapViaFanout: 19 components×19

    Checked by the review, stands · Claude walker W1 (Cern session) — Checked: fan-out lengths read from the copper stand (23 capacitors); the 0.5 nH limit is Probe's starting value, not a Spartan-6 or LP39xx requirement, and no PDN target is stated. Left for the owner.

    At C114, C115, C117, C28, C36, C37 and 13 more

    Each finding, with its own headline
    • C114C114 on '5V': its rail pad reaches its via over 2.45 mm of track, adding about 0.88 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C114 on '5V': its rail pad reaches its via over 2.45 mm of track, adding about 0.88 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C114.1 (rail) runs 2.45 mm along its copper to its nearest via, 1.45 mm past the 1 mm beside the pad: 0.88 nH; C114.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.88 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.39 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.65 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C115C115 on '5V': its rail pad reaches its via over 2.47 mm of track, adding about 0.89 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C115 on '5V': its rail pad reaches its via over 2.47 mm of track, adding about 0.89 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C115.1 (rail) runs 2.47 mm along its copper to its nearest via, 1.47 mm past the 1 mm beside the pad: 0.89 nH; C115.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.89 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.39 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.65 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C117C117 on '3V3': its rail pad reaches its via over 2.43 mm of track, adding about 0.86 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C117 on '3V3': its rail pad reaches its via over 2.43 mm of track, adding about 0.86 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C117.1 (rail) runs 2.43 mm along its copper to its nearest via, 1.43 mm past the 1 mm beside the pad: 0.86 nH; C117.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.86 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.47 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.78 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C28C28 on '3V3': its rail pad reaches its via over 2.22 mm of track, adding about 0.74 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C28 on '3V3': its rail pad reaches its via over 2.22 mm of track, adding about 0.74 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C28.1 (rail) runs 2.22 mm along its copper to its nearest via, 1.22 mm past the 1 mm beside the pad: 0.74 nH; C28.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.74 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.47 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.78 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C36C36 on '3V3': its rail pad reaches its via over 3.78 mm of track, adding about 1.68 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C36 on '3V3': its rail pad reaches its via over 3.78 mm of track, adding about 1.68 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C36.1 (rail) runs 3.78 mm along its copper to its nearest via, 2.78 mm past the 1 mm beside the pad: 1.68 nH; C36.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.68 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.47 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.78 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C37C37 on '3V3': its rail pad reaches its via over 3.88 mm of track, adding about 1.45 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C37 on '3V3': its rail pad reaches its via over 3.88 mm of track, adding about 1.45 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C37.1 (rail) runs 3.88 mm along its copper to its nearest via, 2.88 mm past the 1 mm beside the pad: 1.45 nH; C37.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.58 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.45 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.08 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.78 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C41C41 on '1V2': its rail pad reaches its via over 2.32 mm of track, adding about 0.67 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C41 on '1V2': its rail pad reaches its via over 2.32 mm of track, adding about 0.67 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C41.1 (rail) runs 2.32 mm along its copper to its nearest via, 1.32 mm past the 1 mm beside the pad: 0.67 nH; C41.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.58 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.67 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.00 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.65 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C43C43 on '3V3': its rail pad reaches its via over 5.12 mm of track, adding about 2.08 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C43 on '3V3': its rail pad reaches its via over 5.12 mm of track, adding about 2.08 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C43.1 (rail) runs 5.12 mm along its copper to its nearest via, 4.12 mm past the 1 mm beside the pad: 2.08 nH; C43.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.58 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 2.08 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.77 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.26 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C46C46 on '3V3': its rail pad reaches its via over 3.17 mm of track, adding about 1.09 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C46 on '3V3': its rail pad reaches its via over 3.17 mm of track, adding about 1.09 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C46.1 (rail) runs 3.17 mm along its copper to its nearest via, 2.17 mm past the 1 mm beside the pad: 1.09 nH; C46.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.58 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.09 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.77 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.26 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C53C53 on '3V3': its rail pad reaches its via over 6.00 mm of track, adding about 2.52 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C53 on '3V3': its rail pad reaches its via over 6.00 mm of track, adding about 2.52 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C53.1 (rail) runs at least 6.00 mm along its copper to its nearest via, 5.00 mm past the 1 mm beside the pad: 2.52 nH; C53.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.58 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 2.52 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.77 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.26 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C54C54 on '3V3': its rail pad reaches its via over 6.00 mm of track, adding about 2.53 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C54 on '3V3': its rail pad reaches its via over 6.00 mm of track, adding about 2.53 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C54.1 (rail) runs at least 6.00 mm along its copper to its nearest via, 5.00 mm past the 1 mm beside the pad: 2.53 nH; C54.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.59 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 2.53 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.77 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.26 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C55C55 on '3V3': its rail pad reaches its via over 4.06 mm of track, adding about 1.54 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C55 on '3V3': its rail pad reaches its via over 4.06 mm of track, adding about 1.54 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C55.1 (rail) runs 4.06 mm along its copper to its nearest via, 3.06 mm past the 1 mm beside the pad: 1.54 nH; C55.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.58 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.54 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.77 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.26 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C56C56 on '1V2': its rail pad reaches its via over 2.40 mm of track, adding about 0.85 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C56 on '1V2': its rail pad reaches its via over 2.40 mm of track, adding about 0.85 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C56.1 (rail) runs 2.40 mm along its copper to its nearest via, 1.40 mm past the 1 mm beside the pad: 0.85 nH; C56.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.85 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.23 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.39 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C59C59 on '1V2': its rail pad reaches its via over 2.98 mm of track, adding about 1.20 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C59 on '1V2': its rail pad reaches its via over 2.98 mm of track, adding about 1.20 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C59.1 (rail) runs 2.98 mm along its copper to its nearest via, 1.98 mm past the 1 mm beside the pad: 1.20 nH; C59.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.20 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.39 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.65 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C61C61 on '3V3': its rail pad reaches its via over 2.05 mm of track, adding about 0.63 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C61 on '3V3': its rail pad reaches its via over 2.05 mm of track, adding about 0.63 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C61.1 (rail) runs 2.05 mm along its copper to its nearest via, 1.05 mm past the 1 mm beside the pad: 0.63 nH; C61.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.63 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.47 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.78 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C62C62 on '3V3': its rail pad reaches its via over 3.14 mm of track, adding about 1.08 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C62 on '3V3': its rail pad reaches its via over 3.14 mm of track, adding about 1.08 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C62.1 (rail) runs 3.14 mm along its copper to its nearest via, 2.14 mm past the 1 mm beside the pad: 1.08 nH; C62.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.59 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.08 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.77 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.26 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C66C66 on '3V3': its rail pad reaches its via over 3.75 mm of track, adding about 1.39 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C66 on '3V3': its rail pad reaches its via over 3.75 mm of track, adding about 1.39 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C66.1 (rail) runs 3.75 mm along its copper to its nearest via, 2.75 mm past the 1 mm beside the pad: 1.39 nH; C66.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.59 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.39 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.77 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.26 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C84C84 on '2V5': its rail pad reaches its via over 3.60 mm of track, adding about 1.31 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C84 on '2V5': its rail pad reaches its via over 3.60 mm of track, adding about 1.31 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C84.1 (rail) runs 3.60 mm along its copper to its nearest via, 2.60 mm past the 1 mm beside the pad: 1.31 nH; C84.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.58 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.31 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.84 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.39 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C88C88 on '2V5': its rail pad reaches its via over 5.32 mm of track, adding about 2.18 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C88 on '2V5': its rail pad reaches its via over 5.32 mm of track, adding about 2.18 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C88.1 (rail) runs 5.32 mm along its copper to its nearest via, 4.32 mm past the 1 mm beside the pad: 2.18 nH; C88.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.58 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 2.18 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.84 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.39 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

  6. FiducialMissingmajorOpen

    FiducialMissing: 2 boards×2

    Checked by the review, stands · Claude walker (cern session) — Stands: none of the 338 placed components is a fiducial (no FID footprint or refdes), and OBS-159 already records no fiducials on either side despite a 1 mm BGA and 0.5 mm-pitch parts. Left for the owner.

    At bottom, top

    Each finding, with its own headline
    • bottomThe bottom side carries 58 SMT component(s) and no fiducial was found on it

      The bottom side carries 58 SMT component(s) but no fiducial was found on it — a placement machine has no optical reference to align to. Probe found no pad labelled .pad_usage=g_fiducial/l_fiducial (basis pad_usage); no single-pad, netless, undrilled component whose 0.5-3 mm round pad has a concentric solder-mask opening at least 1.5x its diameter with no other copper inside it (basis geometry); and no component whose refdes starts FID or whose part or package name contains FIDUCIAL (basis footprint-name). If your library names fiducials something Probe does not recognise, mark this benign — disposition_finding(rule='FiducialMissing', entity='bottom', status='benign', reason=…) — the name match only ever silences this check, it never asserts anything. If the side really has no fiducial, say so with status='confirmed': that answers the finding and keeps it gating release.

    • topThe top side carries 67 SMT component(s) and no fiducial was found on it

      The top side carries 67 SMT component(s) but no fiducial was found on it — a placement machine has no optical reference to align to. Probe found no pad labelled .pad_usage=g_fiducial/l_fiducial (basis pad_usage); no single-pad, netless, undrilled component whose 0.5-3 mm round pad has a concentric solder-mask opening at least 1.5x its diameter with no other copper inside it (basis geometry); and no component whose refdes starts FID or whose part or package name contains FIDUCIAL (basis footprint-name). If your library names fiducials something Probe does not recognise, mark this benign — disposition_finding(rule='FiducialMissing', entity='top', status='benign', reason=…) — the name match only ever silences this check, it never asserts anything. If the side really has no fiducial, say so with status='confirmed': that answers the finding and keeps it gating release.

  7. FloatingInputmajorOpen

    FloatingInput: 10 nets×10

    e.g. “U14.6 on 'Net-(R48-Pad1)' has no driver and no pull” · 10 different statements

    At Net-(R10-Pad1), Net-(R48-Pad1), Net-(R7-Pad1), Net-(R8-Pad1), Net-(R9-Pad1), Net-(U1-Pad1) and 4 more

    Each finding, with its own headline
    • Net-(R10-Pad1)U6.2 on 'Net-(R10-Pad1)' has no driver and no pull

      Net 'Net-(R10-Pad1)': input(s) U6.2 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

    • Net-(R48-Pad1)U14.6 on 'Net-(R48-Pad1)' has no driver and no pull

      Net 'Net-(R48-Pad1)': input(s) U14.6 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

    • Net-(R7-Pad1)U3.2 on 'Net-(R7-Pad1)' has no driver and no pull

      Net 'Net-(R7-Pad1)': input(s) U3.2 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

    • Net-(R8-Pad1)U4.2 on 'Net-(R8-Pad1)' has no driver and no pull

      Net 'Net-(R8-Pad1)': input(s) U4.2 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

    • Net-(R9-Pad1)U5.2 on 'Net-(R9-Pad1)' has no driver and no pull

      Net 'Net-(R9-Pad1)': input(s) U5.2 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

    • Net-(U1-Pad1)U1.1 on 'Net-(U1-Pad1)' has no driver and no pull

      Net 'Net-(U1-Pad1)': input(s) U1.1 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor. U1.1 (NC): the function NAME reads as a not-connect, which is a clue and not a fact, so the pin is kept. If the datasheet's type column says NC, file that cell (submit_pin_behavior pinType=nc, quoting the cell and citing the page) and the pin leaves this finding.

    • Net-(U3-Pad1)U3.1 on 'Net-(U3-Pad1)' has no driver and no pull

      Net 'Net-(U3-Pad1)': input(s) U3.1 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor. U3.1 (NC): the function NAME reads as a not-connect, which is a clue and not a fact, so the pin is kept. If the datasheet's type column says NC, file that cell (submit_pin_behavior pinType=nc, quoting the cell and citing the page) and the pin leaves this finding.

    • Net-(U4-Pad1)U4.1 on 'Net-(U4-Pad1)' has no driver and no pull

      Net 'Net-(U4-Pad1)': input(s) U4.1 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor. U4.1 (NC): the function NAME reads as a not-connect, which is a clue and not a fact, so the pin is kept. If the datasheet's type column says NC, file that cell (submit_pin_behavior pinType=nc, quoting the cell and citing the page) and the pin leaves this finding.

    • Net-(U5-Pad1)U5.1 on 'Net-(U5-Pad1)' has no driver and no pull

      Net 'Net-(U5-Pad1)': input(s) U5.1 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor. U5.1 (NC): the function NAME reads as a not-connect, which is a clue and not a fact, so the pin is kept. If the datasheet's type column says NC, file that cell (submit_pin_behavior pinType=nc, quoting the cell and citing the page) and the pin leaves this finding.

    • Net-(U6-Pad1)U6.1 on 'Net-(U6-Pad1)' has no driver and no pull

      Net 'Net-(U6-Pad1)': input(s) U6.1 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor. U6.1 (NC): the function NAME reads as a not-connect, which is a clue and not a fact, so the pin is kept. If the datasheet's type column says NC, file that cell (submit_pin_behavior pinType=nc, quoting the cell and citing the page) and the pin leaves this finding.

  8. PartLifecyclemajorOpen

    LP3883ES-1.2 on U25: the distributor catalogue reports "Obsolete" for Texas Instruments's LP3883ES-1.2

    LP3883ES-1.2 on U25: the distributor catalogue reports "Obsolete" for Texas Instruments's LP3883ES-1.2 — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names National Semiconductor, and that is one line with Texas Instruments: Texas Instruments completed its acquisition of National Semiconductor on 2011-09-23. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/LP3883ES-1.2/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). THE LAST BUY DATE HAS PASSED (2024-03-18, 972 day(s) ago), so this is a substitution rather than a buy. The distributor reports 10,915 left. No approved alternate is recorded for this position.

    At U25

  9. PartLifecyclemajorOpen

    PartLifecycle: 4 part numbers×4

    2 Not For New Designs, 2 Obsolete · on 4 placements

    At C118, C123, U15, X1

    Each finding, with its own headline
    • C118EEEFC1A101P on C118: the distributor catalogue reports "Not For New Designs" for Panasonic Industry's EEE-FC1A101P

      EEEFC1A101P on C118: the distributor catalogue reports "Not For New Designs" for Panasonic Industry's EEE-FC1A101P — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. That is the maker this board's BOM names (Panasonic). A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/EEEFC1A101P/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). No approved alternate is recorded for this position.

    • C123EEEFC1C100R on C123: the distributor catalogue reports "Not For New Designs" for Panasonic Industry's EEE-FC1C100R

      EEEFC1C100R on C123: the distributor catalogue reports "Not For New Designs" for Panasonic Industry's EEE-FC1C100R — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. That is the maker this board's BOM names (Panasonic). A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/EEEFC1C100R/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). No approved alternate is recorded for this position.

    • U15XCF04SVOG20C on U15: the distributor catalogue reports "Obsolete" for AMD's XCF04SVOG20C

      XCF04SVOG20C on U15: the distributor catalogue reports "Obsolete" for AMD's XCF04SVOG20C — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names Xilinx, and that is one line with AMD: AMD completed its acquisition of Xilinx on 2022-02-14. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/XCF04SVOG20C/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). THE LAST BUY DATE HAS PASSED (2021-06-30, 1,964 day(s) ago), so this is a substitution rather than a buy. The distributor reports NONE left. No approved alternate is recorded for this position.

    • X17B-25.000MEEQ-T on X1: the distributor catalogue reports "Obsolete" for TXC CORPORATION's 7B-25.000MEEQ-T

      7B-25.000MEEQ-T on X1: the distributor catalogue reports "Obsolete" for TXC CORPORATION's 7B-25.000MEEQ-T — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. That is the maker this board's BOM names (TXC). A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/7B-25.000MEEQ-T/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). THE LAST BUY DATE HAS PASSED (2021-09-30, 1,872 day(s) ago), so this is a substitution rather than a buy. The distributor reports NONE left. No approved alternate is recorded for this position.

  10. ReferencePlaneDiscontinuitymajorOpen

    ReferencePlaneDiscontinuity: 93 boards×93

    Checked by the review, stands · Claude walker W1 (Cern session) — Checked: splits, voids and reference changes read from the copper stand as reported (166 sites over the FPGA, PHY and BeagleBone nets). They are layout-practice findings with Probe's default limits; no datasheet or app note on file sets one for these nets. Not refutable with a citation; left for the owner.

    At along@L5_PSU:1V2|5V, refchange:1V2|GND, refchange:5V|GND, split@L4_DIGITAL:2V5|GND, split@L5_PSU:1V2|5V, void:1V2@L5_PSU:172.79,-177.5 and 87 more

    Each finding, with its own headline
    • along@L5_PSU:1V2|5V'/TOP/Ethernet_PHY/PHY_RXD7' runs ALONG the split between the 1V2 and 5V planes on L5_PSU at 1 place, the longest 0.58 mm; the impedance rises from 55 ohm to 72 ohm there at worst, 13.3 % of each edge reflected (fastest: /TOP/Ethernet_PHY/PHY_RXD7 at 1 ns 10-90 %, suggested by its name)

      On L5_PSU the 1V2 and 5V planes part, and '/TOP/Ethernet_PHY/PHY_RXD7' runs down the slot between them at 1 place(s), rather than across it. This is not a crossing: the return still follows the track, in the plane on its other side and in the slot's edges, so it does not detour. What changes is the track's own impedance. With the plane gone from under it on this side for that length, its field reaches further, to the slot's edges and to the next plane beyond, so its capacitance falls and its impedance rises; every edge travelling down it is partly reflected where it enters the stretch and again where it leaves, by (Z2 - Z1)/(Z2 + Z1). The longer the stretch against the edge's rise, the more of the edge sees the full step. A crossing is generally the worse fault; a mismatch is not free. Over solid plane each track is 55 ohm; along the slot 72 ohm, reflecting up to 13.3 % of each edge (a method-of-moments field solve of the cross-section, one dielectric; were the slot's edges to carry none of the return, up to 74 ohm). No place stays within 10 %, the tolerance controlled impedance is commonly built to (the stackup states none), so the finding is a warning. One decision covers the split line's slot: whether these tracks may run down it, or should be moved over solid plane.

      • '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL at (182.73, -121.54), 4.58 mm, running ALONG the split for 0.58 mm, not across it, 55 ohm over solid plane, 72 ohm along it: 13.3 % of each edge reflected; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=along%40L5_PSU%3A1V2%7C5V serves each with its own layer_image region; all of them lie in x 181.22..183.73, y -124.98..-118.62 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • refchange:1V2|GND27 nets change reference between 1V2 and GND at 36 vias; 2 of them partial (fastest: /TOP/Spartan6_FPGA/EXTS0 at 100 ps 10-90 %, ASSUMED)

      At 36 via(s), on 27 net(s), the signal leaves a layer referenced by one of 1V2 and GND for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 36 with none. 36 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether 1V2 and GND are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. 2 of them are partial: another reference continues across through a stitching via of its net, so only part of the return has nowhere to go. The pure ones are listed first, then the partial ones with the farthest stitching via first.

      • '/TOP/Ethernet_PHY/PHY_INT' at (178.14, -94.29), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 94.8 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXD2' at (184.46, -149.67), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 91.4 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXD2' at (193.88, -149.67), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 91.4 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXD5' at (184.46, -148.8), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 89.2 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXD5' at (193.77, -148.8), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 89.2 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXDV' at (184.46, -150.43), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 76.6 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXDV' at (193.87, -150.43), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 76.6 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXD1' at (179.87, -135.91), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 76.1 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXD1' at (184.46, -134.58), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 76.1 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXCLK' at (191.52, -164.5), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 76.1 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXD6' at (179.19, -135.09), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 73.8 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • '/TOP/Ethernet_PHY/PHY_RXD6' at (185.59, -133.75), L1_TOP -> L6_DIGITAL: GND on L2_GND to 1V2 on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 73.8 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • and 24 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=refchange%3A1V2%7CGND serves each with its own layer_image region; all of them lie in x 173.56..235.01, y -202.39..-92.29 mm (board frame, Y up).

      The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • refchange:5V|GND9 nets change reference between 5V and GND at 9 vias, none with a reference that continues across (fastest: Net-(J12-Pad1) at 100 ps 10-90 %, ASSUMED)

      At 9 via(s), on 9 net(s), the signal leaves a layer referenced by one of 5V and GND for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 9 with none. 9 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether 5V and GND are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

      • '/TOP/Ethernet_PHY/ACT_LED' at (173.57, -85.17), L3_DIGITAL -> L6_DIGITAL: GND on L2_GND, 2V5 on L4_DIGITAL to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 63.0 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'Net-(J12-Pad2)' at (133.13, -104.36), L1_TOP -> L6_DIGITAL: GND on L2_GND to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 44.0 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'Net-(J12-Pad6)' at (133.2, -99.27), L1_TOP -> L6_DIGITAL: GND on L2_GND to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 42.2 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'Net-(J12-Pad8)' at (134.55, -95.96), L1_TOP -> L6_DIGITAL: GND on L2_GND to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 41.3 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'Net-(J12-Pad7)' at (139.46, -94.25), L1_TOP -> L6_DIGITAL: GND on L2_GND to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 36.5 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'Net-(J12-Pad5)' at (140.1, -98.06), L1_TOP -> L6_DIGITAL: GND on L2_GND to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 36.0 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'Net-(J12-Pad4)' at (140.94, -96.68), L1_TOP -> L6_DIGITAL: GND on L2_GND to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 35.1 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'Net-(J12-Pad3)' at (141.54, -98.68), L1_TOP -> L6_DIGITAL: GND on L2_GND to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 34.6 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'Net-(J12-Pad1)' at (143.83, -101.21), L1_TOP -> L6_DIGITAL: GND on L2_GND to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching none, 31.7 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=refchange%3A5V%7CGND serves each with its own layer_image region; all of them lie in x 131.13..175.57, y -106.36..-83.17 mm (board frame, Y up).

      The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@L4_DIGITAL:2V5|GND10 nets cross the split between the 2V5 and GND planes on L4_DIGITAL at 10 places; 9 with a plane on the track's other side (fastest: /TOP/Spartan6_FPGA/SW0 at 100 ps 10-90 %, ASSUMED)

      On L4_DIGITAL the 2V5 and GND planes part, and 10 nets cross from one to the other at 10 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 9 of the 10 crossing(s) the track's other neighbour carries a plane, which the return can use there. 9 of the 10 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • '/TOP/Digital_interface/SPARE3' on L3_DIGITAL at (193.36, -183.47), 3.03 mm; other side: no plane on L2_GND
      • '/TOP/BeagleBone_connectors/BBB_CLKOUT2' on L3_DIGITAL at (173.67, -80.37), 2.77 mm; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/BeagleBone_connectors/BBB_SPI1_CLK' on L3_DIGITAL at (165.33, -80.64), 2.16 mm; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/BeagleBone_connectors/BBB_SPI1_CS0' on L3_DIGITAL at (160.26, -80.46), 2.04 mm; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/Spartan6_FPGA/SW0' on L3_DIGITAL at (205.32, -183.44), 2.83 mm; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/Spartan6_FPGA/SW1' on L3_DIGITAL at (205.95, -183.44), 2.83 mm; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/Spartan6_FPGA/SW2' on L3_DIGITAL at (206.47, -183.44), 2.83 mm; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/Spartan6_FPGA/SW3' on L3_DIGITAL at (207.08, -183.44), 2.83 mm; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/Spartan6_FPGA/SW4' on L3_DIGITAL at (207.66, -183.44), 2.83 mm; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/Spartan6_FPGA/SW5' on L3_DIGITAL at (208.26, -183.44), 2.83 mm; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=split%40L4_DIGITAL%3A2V5%7CGND serves each with its own layer_image region; all of them lie in x 159.26..210.26, y -186.35..-78.44 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@L5_PSU:1V2|5V14 nets cross the split between the 1V2 and 5V planes on L5_PSU at 14 places; 8 with a plane on the track's other side (fastest: Net-(J12-Pad1) at 100 ps 10-90 %, ASSUMED)

      On L5_PSU the 1V2 and 5V planes part, and 14 nets cross from one to the other at 14 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 8 of the 14 crossing(s) the track's other neighbour carries a plane, which the return can use there. 8 of the 14 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL at (175.18, -121.57), 3.64 mm; other side: no plane on L7_PSU
      • '/TOP/Ethernet_PHY/PHY_HPD' on L6_DIGITAL at (180.29, -121.57), 3.55 mm; other side: no plane on L7_PSU
      • '/TOP/Ethernet_PHY/PHY_MDC' on L6_DIGITAL at (172.68, -121.57), 3.53 mm; other side: no plane on L7_PSU
      • '/TOP/Ethernet_PHY/PHY_RXD1' on L6_DIGITAL at (183, -121.57), 3.5 mm; other side: no plane on L7_PSU
      • '/TOP/Ethernet_PHY/PHY_RXD3' on L4_DIGITAL at (177.96, -121.57), 3.6 mm; other side: no plane on L3_DIGITAL
      • '/TOP/Ethernet_PHY/PHY_TXD7' on L4_DIGITAL at (183.09, -121.57), 3.8 mm; other side: no plane on L3_DIGITAL
      • 'Net-(J12-Pad1)' on L6_DIGITAL at (159.21, -101.21), 2 mm; other side: 3V3 on L7_PSU, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU
      • 'Net-(J12-Pad2)' on L6_DIGITAL at (159.21, -102), 2 mm; other side: 3V3 on L7_PSU, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU
      • 'Net-(J12-Pad3)' on L6_DIGITAL at (159.21, -98.68), 2 mm; other side: 3V3 on L7_PSU, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU
      • 'Net-(J12-Pad4)' on L6_DIGITAL at (159.21, -96.68), 2 mm; other side: 3V3 on L7_PSU, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU
      • 'Net-(J12-Pad5)' on L6_DIGITAL at (159.21, -98.27), 2 mm; other side: 3V3 on L7_PSU, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU
      • 'Net-(J12-Pad6)' on L6_DIGITAL at (159.21, -99.45), 2 mm; other side: 3V3 on L7_PSU, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU
      • and 2 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=split%40L5_PSU%3A1V2%7C5V serves each with its own layer_image region; all of them lie in x 157.21..184.09, y -124.47..-93.25 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:172.79,-177.59 nets cross where the GND plane on L2_GND, the GND plane on L3_DIGITAL, the GND plane on L4_DIGITAL and the 1V2 plane on L5_PSU is drawn back round copper of /TOP/Digital_interface/FD0_BYP, /TOP/Digital_interface/PLL_DATA, /TOP/Digital_interface/PLL_LE, /TOP/Digital_interface/SPARE0, /TOP/Digital_interface/SPARE1, /TOP/Spartan6_FPGA/LED_G, /TOP/Spartan6_FPGA/LED_R, Net-(R55-Pad2), Net-(R62-Pad2), Net-(R64-Pad2), at 1 place, the longest 22.19 mm (fastest: /TOP/Spartan6_FPGA/LED_G at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/Spartan6_FPGA/LED_G' on L3_DIGITAL, the GND plane on L4_DIGITAL has 22.19 mm under the track with copper of Net-(R55-Pad2), Net-(R62-Pad2), Net-(R64-Pad2), not a plane, at (163.04, -179.87), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 9 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 5.55 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -222.44..-86.44 and of the pour at x 177.88..178.83, y -179.3..-178.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 11 of the 26 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 26 reference layers: '/TOP/Digital_interface/FD0_BYP' on L3_DIGITAL at (168.6, -181.1), 15.55 mm, running ALONG the bare copper for 3.79 mm, not across it over copper of Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Digital_interface/PLL_DATA' on L3_DIGITAL at (172.44, -181.9), 9.07 mm, running ALONG the bare copper for 3.99 mm, not across it over copper of Net-(R62-Pad2), Net-(R55-Pad2), Net-(R64-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Digital_interface/PLL_LE' on L3_DIGITAL at (172.84, -186.07), 0.45 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/Digital_interface/PLL_LE' on L3_DIGITAL at (172.84, -182.48), 9.3 mm, running ALONG the bare copper for 5.55 mm, not across it over copper of Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, to the end of the track; other side: no plane on L2_GND / '/TOP/Digital_interface/PLL_LE' on L3_DIGITAL at (172.84, -186.07), 0.45 mm over no copper; other side: no plane on L2_GND / '/TOP/Digital_interface/SPARE0' on L3_DIGITAL at (174.41, -182.67), 6.51 mm, running ALONG the bare copper for 5.21 mm, not across it over copper of Net-(R62-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/LED_G' on L3_DIGITAL at (163.04, -179.87), 22.19 mm, running ALONG the bare copper for 4.27 mm, not across it over copper of Net-(R55-Pad2), Net-(R62-Pad2), Net-(R64-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/LED_R' on L3_DIGITAL at (163.69, -180.27), 20.69 mm, running ALONG the bare copper for 3.53 mm, not across it over copper of Net-(R64-Pad2), Net-(R62-Pad2), Net-(R55-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / 'Net-(R55-Pad2)' on L4_DIGITAL at (175.66, -173.44), 1.51 mm over no copper; other side: no plane on L5_PSU / 'Net-(R55-Pad2)' on L4_DIGITAL at (175.66, -175.44), 6.34 mm, running ALONG the bare copper for 1.86 mm, not across it over copper of /TOP/Digital_interface/PLL_LE, /TOP/Digital_interface/PLL_DATA, /TOP/Digital_interface/FD0_BYP, /TOP/Spartan6_FPGA/LED_R, /TOP/Spartan6_FPGA/LED_G, not a plane; other side: no plane on L5_PSU / 'Net-(R55-Pad2)' on L4_DIGITAL at (178.46, -179.55), 0.86 mm over copper of /TOP/Digital_interface/SPARE1, not a plane, to the end of the track; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R55-Pad2)' on L4_DIGITAL at (175.66, -172.94), 2.51 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(R55-Pad2)' on L4_DIGITAL at (175.66, -175.59), 1.81 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(R55-Pad2)' on L4_DIGITAL at (177.21, -178.97), 3.09 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(R62-Pad2)' on L4_DIGITAL at (171.34, -175.26), 1.66 mm over copper of /TOP/Spartan6_FPGA/LED_R, /TOP/Spartan6_FPGA/LED_G, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R62-Pad2)' on L4_DIGITAL at (171.34, -178.83), 1.65 mm over copper of /TOP/Digital_interface/FD0_BYP, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R62-Pad2)' on L4_DIGITAL at (173.83, -180.44), 6.82 mm, running ALONG the bare copper for 1.86 mm, not across it over copper of /TOP/Digital_interface/SPARE0, /TOP/Digital_interface/PLL_LE, /TOP/Digital_interface/PLL_DATA, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R62-Pad2)' on L4_DIGITAL at (177.03, -180.94), 2.44 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(R64-Pad2)' on L4_DIGITAL at (172.36, -175.26), 1.66 mm over copper of /TOP/Spartan6_FPGA/LED_R, /TOP/Spartan6_FPGA/LED_G, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R64-Pad2)' on L4_DIGITAL at (176.87, -179.29), 8.15 mm, running ALONG the bare copper for 3.83 mm, not across it over copper of /TOP/Digital_interface/FD0_BYP, /TOP/Digital_interface/PLL_LE, /TOP/Digital_interface/PLL_DATA, /TOP/Digital_interface/SPARE1, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R64-Pad2)' on L4_DIGITAL at (178.96, -182.25), 1.53 mm over no copper; other side: no plane on L5_PSU / 'Net-(R64-Pad2)' on L4_DIGITAL at (179.85, -183.69), 1.84 mm over no copper; other side: no plane on L5_PSU / 'Net-(R64-Pad2)' on L4_DIGITAL at (172.79, -177.5), 1.71 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(R64-Pad2)' on L4_DIGITAL at (177.96, -180.23), 1.64 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(R64-Pad2)' on L4_DIGITAL at (178.96, -182.25), 1.53 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(R64-Pad2)' on L4_DIGITAL at (179.85, -183.69), 1.84 mm over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A172.79%2C-177.5 serves each with its own layer_image region; all of them lie in x 157.76..181.3, y -187.29..-170.69 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:175.66,-165.1211 nets cross where the GND plane on L3_DIGITAL, the GND plane on L4_DIGITAL and the 1V2 plane on L5_PSU is drawn back round copper of /TOP/BeagleBone_connectors/BBB_I2C1_SCL, /TOP/BeagleBone_connectors/BBB_I2C1_SDA, /TOP/BeagleBone_connectors/BBB_I2C2_SCL, /TOP/BeagleBone_connectors/BBB_I2C2_SDA, /TOP/BeagleBone_connectors/BBB_SPI1_CLK, /TOP/BeagleBone_connectors/BBB_SPI1_CS0, /TOP/BeagleBone_connectors/BBB_SPI1_D0, /TOP/BeagleBone_connectors/BBB_SPI1_D1, /TOP/BeagleBone_connectors/BBB_UART1_RxD, /TOP/BeagleBone_connectors/BBB_UART1_TxD, /TOP/Ethernet_PHY/PHY_RXD3, /TOP/Reset//BBB_RST, Net-(R55-Pad2), Net-(R62-Pad2), Net-(R64-Pad2), at 1 place, the longest 28.41 mm (fastest: Net-(R55-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/BeagleBone_connectors/BBB_UART1_TxD' on L3_DIGITAL, the GND plane on L4_DIGITAL has 28.41 mm under the track with copper of /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, at (164.74, -155.52), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 5 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 2.17 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -222.44..-86.44 and of the pour at x 165.92..181.85, y -162.98..-123.3 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 9 of the 12 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 12 reference layers: '/TOP/BeagleBone_connectors/BBB_I2C1_SCL' on L3_DIGITAL at (164.74, -158.48), 23.98 mm over copper of Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_I2C1_SDA' on L3_DIGITAL at (164.74, -158.95), 23.78 mm over copper of Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_I2C2_SCL' on L3_DIGITAL at (164.74, -156.31), 25.86 mm, running ALONG the bare copper for 2.17 mm, not across it over copper of Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_I2C2_SDA' on L3_DIGITAL at (164.74, -156.96), 26.02 mm, running ALONG the bare copper for 1.84 mm, not across it over copper of Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_UART1_RxD' on L3_DIGITAL at (164.74, -155.03), 27.99 mm over copper of /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_UART1_TxD' on L3_DIGITAL at (164.74, -155.52), 28.41 mm, running ALONG the bare copper for 2.12 mm, not across it over copper of /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Ethernet_PHY/PHY_RXD3' on L4_DIGITAL at (177.96, -167), 10.12 mm, running ALONG the bare copper for 0.94 mm, not across it over copper of /TOP/BeagleBone_connectors/BBB_UART1_TxD, /TOP/BeagleBone_connectors/BBB_UART1_RxD, /TOP/BeagleBone_connectors/BBB_SPI1_CS0, /TOP/BeagleBone_connectors/BBB_SPI1_D1, /TOP/BeagleBone_connectors/BBB_SPI1_D0, /TOP/BeagleBone_connectors/BBB_SPI1_CLK, not a plane, to the end of the track; other side: no plane on L5_PSU / '/TOP/Reset//BBB_RST' on L3_DIGITAL at (164.74, -159.96), 23.78 mm over copper of Net-(R55-Pad2), Net-(R64-Pad2), Net-(R62-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / 'Net-(R55-Pad2)' on L4_DIGITAL at (175.66, -165.27), 5.18 mm over copper of /TOP/Reset//BBB_RST, /TOP/BeagleBone_connectors/BBB_I2C1_SDA, /TOP/BeagleBone_connectors/BBB_I2C1_SCL, /TOP/BeagleBone_connectors/BBB_I2C2_SDA, /TOP/BeagleBone_connectors/BBB_I2C2_SCL, /TOP/BeagleBone_connectors/BBB_UART1_TxD, /TOP/BeagleBone_connectors/BBB_UART1_RxD, not a plane; other side: no plane on L5_PSU / 'Net-(R55-Pad2)' on L4_DIGITAL at (175.66, -165.12), 1.18 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(R62-Pad2)' on L4_DIGITAL at (171.34, -164.32), 6.58 mm over copper of /TOP/Reset//BBB_RST, /TOP/BeagleBone_connectors/BBB_I2C1_SDA, /TOP/BeagleBone_connectors/BBB_I2C1_SCL, /TOP/BeagleBone_connectors/BBB_I2C2_SDA, /TOP/BeagleBone_connectors/BBB_I2C2_SCL, /TOP/BeagleBone_connectors/BBB_UART1_TxD, /TOP/BeagleBone_connectors/BBB_UART1_RxD, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R64-Pad2)' on L4_DIGITAL at (172.36, -165.26), 6.2 mm, running ALONG the bare copper for 0.7 mm, not across it over copper of /TOP/Reset//BBB_RST, /TOP/BeagleBone_connectors/BBB_I2C1_SDA, /TOP/BeagleBone_connectors/BBB_I2C1_SCL, /TOP/BeagleBone_connectors/BBB_I2C2_SDA, /TOP/BeagleBone_connectors/BBB_I2C2_SCL, /TOP/BeagleBone_connectors/BBB_UART1_TxD, /TOP/BeagleBone_connectors/BBB_UART1_RxD, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A175.66%2C-165.12 serves each with its own layer_image region; all of them lie in x 157.21..180.46, y -170.45..-147.5 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:176,-107.01'/TOP/Ethernet_PHY/PHY_MDC' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.1 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_MDC at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_MDC' on L6_DIGITAL, the 1V2 plane on L5_PSU has 2.1 mm under the track with no copper, at (176, -107.01), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_MDC' on L6_DIGITAL at (176, -107.01), 2.1 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY/PHY_MDC' on L6_DIGITAL at (176, -107.01), 2.1 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A176%2C-107.01 serves each with its own layer_image region; all of them lie in x 173.95..178.05, y -108.01..-106.01 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:178.96,-159.77'/TOP/Ethernet_PHY/PHY_MDC' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.24 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_MDC at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_MDC' on L6_DIGITAL, the 1V2 plane on L5_PSU has 1.24 mm under the track with no copper, at (178.96, -159.77), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_MDC' on L6_DIGITAL at (178.96, -159.77), 1.24 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY/PHY_MDC' on L6_DIGITAL at (178.96, -159.77), 1.24 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A178.96%2C-159.77 serves each with its own layer_image region; all of them lie in x 177.96..179.96, y -161.39..-158.15 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:182.11,-134.19'/TOP/Ethernet_PHY//PHY_RST' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.13 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY//PHY_RST at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL, the 1V2 plane on L5_PSU has 1.13 mm under the track with no copper, at (182.11, -134.19), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL at (182.11, -134.19), 1.13 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL at (182.11, -134.19), 1.13 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A182.11%2C-134.19 serves each with its own layer_image region; all of them lie in x 181.11..183.11, y -135.76..-132.62 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:183,-98.78'/TOP/Ethernet_PHY/PHY_RXD1' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.14 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_RXD1 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD1' on L6_DIGITAL, the 3V3 plane on L7_PSU has 1.14 mm under the track with no copper, at (183, -98.78), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_RXD1' on L6_DIGITAL at (183, -98.78), 1.13 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY/PHY_RXD1' on L6_DIGITAL at (183, -98.78), 1.14 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A183%2C-98.78 serves each with its own layer_image region; all of them lie in x 182..184, y -100.35..-97.21 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:183.62,-143.39'/TOP/Ethernet_PHY/PHY_TXD7' crosses where the GND plane on L3_DIGITAL and the 1V2 plane on L5_PSU is drawn back round copper of /TOP/Ethernet_PHY/PHY_GTXCLK, at 1 place, the longest 62.53 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_TXD7 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD7' on L4_DIGITAL, the GND plane on L3_DIGITAL has 62.53 mm under the track with copper of /TOP/Ethernet_PHY/PHY_GTXCLK, not a plane, at (183.46, -156.16), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 60.33 mm). No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 and of the pour at x 173.36..184.83, y -119.84..-102.57 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 1 of the 2 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_TXD7' on L4_DIGITAL at (183.46, -156.16), 62.53 mm, running ALONG the bare copper for 60.33 mm, not across it over copper of /TOP/Ethernet_PHY/PHY_GTXCLK, not a plane, to the end of the track; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_TXD7' on L4_DIGITAL at (183.62, -143.39), 1.2 mm over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A183.62%2C-143.39 serves each with its own layer_image region; all of them lie in x 182.09..184.62, y -169.44..-104.93 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:183.77,-94.4'/TOP/Ethernet_PHY/PHY_RXD7' crosses where the outline of the GND plane on L3_DIGITAL and the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 1.53 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_RXD7 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL, the GND plane on L3_DIGITAL has 1.53 mm under the track with no copper, at (183.77, -94.4), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL at (183.77, -94.4), 1.53 mm over no copper; other side: no plane on L5_PSU / '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL at (183.77, -94.4), 1.53 mm over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A183.77%2C-94.4 serves each with its own layer_image region; all of them lie in x 182.77..185.29, y -95.8..-92.48 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:183.96,-143.58 nets cross where the GND plane on L3_DIGITAL, the GND plane on L4_DIGITAL and the 1V2 plane on L5_PSU is drawn back round copper of /TOP/Digital_interface/ADC_ENA, /TOP/Digital_interface/ADC_ENB, /TOP/Ethernet_PHY/PHY_COL, /TOP/Ethernet_PHY/PHY_CRS, /TOP/Ethernet_PHY/PHY_TXD6, /TOP/Ethernet_PHY/PHY_TXEN, /TOP/FPGA_configuration//PROG_B_FPGA, /TOP/FPGA_configuration/EEPROM_CS, Net-(R62-Pad2), Net-(R64-Pad2), at 1 place, the longest 75.75 mm (fastest: /TOP/FPGA_configuration//PROG_B_FPGA at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/Ethernet_PHY/PHY_CRS' on L4_DIGITAL, the GND plane on L3_DIGITAL has 75.75 mm under the track with copper of /TOP/Digital_interface/ADC_ENB, /TOP/Digital_interface/ADC_ENA, /TOP/Ethernet_PHY/PHY_TXEN, /TOP/Ethernet_PHY/PHY_TXD6, not a plane, at (184.96, -147.83), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 4 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 67.68 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -222.44..-86.44 and of the pour at x 183.25..184.83, y -174.66..-173.07 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 6 of the 16 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 16 reference layers: '/TOP/Digital_interface/ADC_ENA' on L3_DIGITAL at (184.96, -179.43), 8.05 mm over copper of Net-(R64-Pad2), Net-(R62-Pad2), /TOP/FPGA_configuration/EEPROM_CS, /TOP/FPGA_configuration//PROG_B_FPGA, /TOP/Ethernet_PHY/PHY_CRS, not a plane, to the end of the track; other side: no plane on L2_GND / '/TOP/Digital_interface/ADC_ENB' on L3_DIGITAL at (183.96, -180.59), 8.84 mm, running ALONG the bare copper for 1.62 mm, not across it over copper of /TOP/Ethernet_PHY/PHY_COL, /TOP/Ethernet_PHY/PHY_CRS, Net-(R64-Pad2), Net-(R62-Pad2), /TOP/FPGA_configuration/EEPROM_CS, /TOP/FPGA_configuration//PROG_B_FPGA, not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Ethernet_PHY/PHY_COL' on L4_DIGITAL at (183.96, -162.71), 74.91 mm, running ALONG the bare copper for 67.68 mm, not across it over copper of /TOP/Digital_interface/ADC_ENB, /TOP/Ethernet_PHY/PHY_TXD6, /TOP/Ethernet_PHY/PHY_TXEN, not a plane, to the end of the track; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_COL' on L4_DIGITAL at (183.96, -143.5), 1.22 mm over no copper; other side: no plane on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_COL' on L4_DIGITAL at (183.96, -149.62), 2.85 mm over no copper; other side: no plane on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_COL' on L4_DIGITAL at (183.96, -168.83), 6.06 mm over no copper; other side: no plane on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_COL' on L4_DIGITAL at (183.96, -175.49), 3.54 mm over copper of 1V2, not a plane, to the end of the track; other side: no plane on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_CRS' on L4_DIGITAL at (184.96, -147.83), 75.75 mm, running ALONG the bare copper for 64.67 mm, not across it over copper of /TOP/Digital_interface/ADC_ENB, /TOP/Digital_interface/ADC_ENA, /TOP/Ethernet_PHY/PHY_TXEN, /TOP/Ethernet_PHY/PHY_TXD6, not a plane, to the end of the track; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_CRS' on L4_DIGITAL at (184.96, -134.24), 1.9 mm over no copper; other side: no plane on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_CRS' on L4_DIGITAL at (184.96, -139.89), 1.58 mm over no copper; other side: no plane on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_CRS' on L4_DIGITAL at (184.96, -149.62), 2.85 mm over no copper; other side: no plane on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_CRS' on L4_DIGITAL at (184.96, -170.33), 13.39 mm, running ALONG the bare copper for 1.3 mm, not across it over copper of 1V2, not a plane, to the end of the track; other side: no plane on L3_DIGITAL / '/TOP/FPGA_configuration//PROG_B_FPGA' on L4_DIGITAL at (184.79, -184.77), 1.67 mm over copper of /TOP/Digital_interface/ADC_ENB, /TOP/Digital_interface/ADC_ENA, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / '/TOP/FPGA_configuration/EEPROM_CS' on L4_DIGITAL at (184.79, -184.33), 1.67 mm over copper of /TOP/Digital_interface/ADC_ENB, /TOP/Digital_interface/ADC_ENA, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R62-Pad2)' on L4_DIGITAL at (184.79, -184), 1.67 mm over copper of /TOP/Digital_interface/ADC_ENA, /TOP/Digital_interface/ADC_ENB, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R64-Pad2)' on L4_DIGITAL at (184.87, -182.33), 2.51 mm over copper of /TOP/Digital_interface/ADC_ENA, /TOP/Digital_interface/ADC_ENB, not a plane, to the end of the track; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A183.96%2C-143.5 serves each with its own layer_image region; all of them lie in x 182.38..187.23, y -186.35..-103.05 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:184.96,-105.54'/TOP/Ethernet_PHY/PHY_COL' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 1.11 mm (fastest: /TOP/Ethernet_PHY/PHY_COL at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_COL' on L4_DIGITAL, the 1V2 plane on L5_PSU has 1.11 mm under the track with no copper, at (184.96, -105.54), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_COL' on L4_DIGITAL at (184.96, -105.54), 1.11 mm over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A184.96%2C-105.54 serves each with its own layer_image region; all of them lie in x 183.96..186.11, y -106.99..-103.94 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:185.14,-105.45'/TOP/Ethernet_PHY/PHY_RXD6' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.94 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_RXD6 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD6' on L6_DIGITAL, the 1V2 plane on L5_PSU has 0.94 mm under the track with no copper, at (185.14, -105.45), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_RXD6' on L6_DIGITAL at (185.14, -105.45), 0.94 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY/PHY_RXD6' on L6_DIGITAL at (185.14, -105.45), 0.94 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A185.14%2C-105.45 serves each with its own layer_image region; all of them lie in x 184.14..186.14, y -106.92..-103.98 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:185.47,-106.1'/TOP/Ethernet_PHY/PHY_CRS' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 1.16 mm (fastest: /TOP/Ethernet_PHY/PHY_CRS at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_CRS' on L4_DIGITAL, the 1V2 plane on L5_PSU has 1.16 mm under the track with no copper, at (185.47, -106.1), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_CRS' on L4_DIGITAL at (185.47, -106.1), 1.16 mm over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A185.47%2C-106.1 serves each with its own layer_image region; all of them lie in x 184.47..186.47, y -107.68..-104.52 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:185.86,-89.9'/TOP/Ethernet_PHY/PHY_RXD4' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.18 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_RXD4 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD4' on L6_DIGITAL, the 1V2 plane on L5_PSU has 1.18 mm under the track with no copper, at (185.86, -89.9), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_RXD4' on L6_DIGITAL at (185.86, -89.9), 1.18 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY/PHY_RXD4' on L6_DIGITAL at (185.86, -89.9), 1.18 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A185.86%2C-89.9 serves each with its own layer_image region; all of them lie in x 184.27..187.45, y -90.9..-88.9 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:185.9,-91.08'/TOP/Ethernet_PHY/PHY_RXD5' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 0.96 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD5 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD5' on L6_DIGITAL, the 1V2 plane on L5_PSU has 0.96 mm under the track with no copper, at (185.9, -91.08), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD5' on L6_DIGITAL at (185.9, -91.08), 0.96 mm over no copper; other side: no plane on L7_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A185.9%2C-91.08 serves each with its own layer_image region; all of them lie in x 184.42..187.37, y -92.08..-90.08 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:186.13,-89.55'/TOP/Ethernet_PHY/PHY_RXD0' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.17 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_RXD0 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD0' on L6_DIGITAL, the 1V2 plane on L5_PSU has 1.17 mm under the track with no copper, at (186.13, -89.55), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_RXD0' on L6_DIGITAL at (186.13, -89.55), 1.17 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY/PHY_RXD0' on L6_DIGITAL at (186.13, -89.55), 1.17 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A186.13%2C-89.55 serves each with its own layer_image region; all of them lie in x 184.55..187.71, y -90.55..-88.55 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:186.96,-155.62 nets cross where the GND plane on L3_DIGITAL, the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back round copper of /TOP/Ethernet_PHY/PHY_MDIO, /TOP/FPGA_configuration/TDI, at 2 places, the longest 22.65 mm; 2 cleared on both sides of the track (fastest: Net-(Q3-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(Q3-Pad1)' on L4_DIGITAL, the GND plane on L3_DIGITAL has 22.65 mm under the track with copper of /TOP/FPGA_configuration/TDI, /TOP/Ethernet_PHY/PHY_MDIO, not a plane, at (186.96, -162.32), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 2 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 18.61 mm). 2 places on 2 net(s) cross it, listed below, the longest first. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 and of the pour at x 186.1..187.83, y -176.66..-173.2 is drawn back there. At 2 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 1 of the 6 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 4 reference layers: 'Net-(Q3-Pad1)' on L4_DIGITAL at (186.96, -162.32), 22.65 mm, running ALONG the bare copper for 18.61 mm, not across it over copper of /TOP/FPGA_configuration/TDI, /TOP/Ethernet_PHY/PHY_MDIO, not a plane, to the end of the track; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(Q3-Pad1)' on L4_DIGITAL at (186.96, -155.6), 1.22 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(Q3-Pad1)' on L4_DIGITAL at (186.96, -159.44), 1.3 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(Q3-Pad1)' on L4_DIGITAL at (186.96, -169.45), 9.24 mm, running ALONG the bare copper for 1.04 mm, not across it over no copper; other side: no plane on L3_DIGITAL
      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL at (186.96, -155.6), 1.22 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL at (186.96, -155.6), 1.22 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A186.96%2C-155.6 serves each with its own layer_image region; all of them lie in x 185.96..187.96, y -175.07..-150.13 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:186.96,-159.44'/TOP/Ethernet_PHY//PHY_RST' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.3 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY//PHY_RST at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL, the 1V2 plane on L5_PSU has 1.3 mm under the track with no copper, at (186.96, -159.44), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL at (186.96, -159.44), 1.3 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL at (186.96, -159.44), 1.3 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A186.96%2C-159.44 serves each with its own layer_image region; all of them lie in x 185.96..187.96, y -161.09..-157.79 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:187.12,-182.01'Net-(R62-Pad2)' crosses where the GND plane on L3_DIGITAL and the 1V2 plane on L5_PSU is drawn back round copper of /TOP/Digital_interface/SPARE4, /TOP/Digital_interface/SPARE5, /TOP/Digital_interface/SPARE6, at 1 place, the longest 5.86 mm; 1 cleared on both sides of the track (fastest: Net-(R62-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R62-Pad2)' on L4_DIGITAL, the GND plane on L3_DIGITAL has 5.86 mm under the track with copper of /TOP/Digital_interface/SPARE4, /TOP/Digital_interface/SPARE6, /TOP/Digital_interface/SPARE5, not a plane, at (186.46, -180.03), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.53 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 1 of the 3 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 3 reference layers: 'Net-(R62-Pad2)' on L4_DIGITAL at (186.46, -180.03), 5.86 mm, running ALONG the bare copper for 3.53 mm, not across it over copper of /TOP/Digital_interface/SPARE4, /TOP/Digital_interface/SPARE6, /TOP/Digital_interface/SPARE5, not a plane, to the end of the track; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R62-Pad2)' on L4_DIGITAL at (187.12, -182.01), 0.9 mm over no copper; other side: no plane on L3_DIGITAL / 'Net-(R62-Pad2)' on L4_DIGITAL at (187.17, -183.65), 1.57 mm over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A187.12%2C-182.01 serves each with its own layer_image region; all of them lie in x 185.46..188.45, y -184.93..-177.44 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:192.72,-174.88'/TOP/Spartan6_FPGA/EXTS0' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.01 mm; 1 cleared on both sides of the track (fastest: /TOP/Spartan6_FPGA/EXTS0 at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/Spartan6_FPGA/EXTS0' on L6_DIGITAL, the 1V2 plane on L5_PSU has 1.01 mm under the track with no copper, at (192.72, -174.88), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Spartan6_FPGA/EXTS0' on L6_DIGITAL at (192.72, -174.88), 1.01 mm over no copper; other side: no plane on L7_PSU / '/TOP/Spartan6_FPGA/EXTS0' on L6_DIGITAL at (192.72, -174.88), 1.01 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A192.72%2C-174.88 serves each with its own layer_image region; all of them lie in x 191.17..194.12, y -175.88..-173.73 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:192.82,-184.77'/TOP/FPGA_configuration//PROG_B_FPGA' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 0.49 mm (fastest: /TOP/FPGA_configuration//PROG_B_FPGA at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/FPGA_configuration//PROG_B_FPGA' on L4_DIGITAL, the 1V2 plane on L5_PSU has 0.49 mm under the track with no copper, at (192.82, -184.77), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/FPGA_configuration//PROG_B_FPGA' on L4_DIGITAL at (192.82, -184.77), 0.49 mm over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A192.82%2C-184.77 serves each with its own layer_image region; all of them lie in x 191.57..194.06, y -185.77..-183.77 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:192.93,-159.85'/TOP/Ethernet_PHY/PHY_TXD5' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 1.06 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD5 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD5' on L6_DIGITAL, the 1V2 plane on L5_PSU has 1.06 mm under the track with no copper, at (192.93, -159.85), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD5' on L6_DIGITAL at (192.93, -159.85), 1.06 mm over no copper; other side: no plane on L7_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A192.93%2C-159.85 serves each with its own layer_image region; all of them lie in x 191.93..193.93, y -161.38..-158.32 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:193.25,-149.56'/TOP/Ethernet_PHY/PHY_INT' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.69 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_INT at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL, the 1V2 plane on L5_PSU has 2.69 mm under the track with no copper, at (193.25, -149.56), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL at (193.25, -149.56), 2.69 mm over no copper; other side: no plane on L7_PSU / '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL at (193.25, -149.56), 2.69 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A193.25%2C-149.56 serves each with its own layer_image region; all of them lie in x 192.25..194.25, y -151.9..-147.21 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:193.25,-163.99'/TOP/Ethernet_PHY/PHY_INT' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 0.16 mm (fastest: /TOP/Ethernet_PHY/PHY_INT at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL, the 1V2 plane on L5_PSU has 0.16 mm under the track with no copper, at (193.25, -163.99), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL at (193.25, -163.99), 0.16 mm over no copper; other side: no plane on L7_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A193.25%2C-163.99 serves each with its own layer_image region; all of them lie in x 192.25..194.25, y -165.07..-162.91 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:194.43,-149.68'/TOP/Ethernet_PHY/PHY_TXD3' crosses where the outline of the GND plane on L3_DIGITAL and the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 2.61 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_TXD3 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD3' on L4_DIGITAL, the GND plane on L3_DIGITAL has 2.61 mm under the track with no copper, at (194.43, -149.68), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Ethernet_PHY/PHY_TXD3' on L4_DIGITAL at (194.43, -149.68), 2.61 mm over no copper; other side: no plane on L5_PSU / '/TOP/Ethernet_PHY/PHY_TXD3' on L4_DIGITAL at (194.43, -149.68), 2.61 mm over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A194.43%2C-149.68 serves each with its own layer_image region; all of them lie in x 193.43..195.43, y -151.98..-147.37 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:141.53,-98.06'Net-(J12-Pad5)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.98 mm (fastest: Net-(J12-Pad5) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J12-Pad5)' on L6_DIGITAL, the 3V3 plane on L7_PSU has 0.98 mm under the track with no copper, at (141.53, -98.06), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J12-Pad5)' on L6_DIGITAL at (141.53, -98.06), 0.98 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A141.53%2C-98.06 serves each with its own layer_image region; all of them lie in x 140.05..143.02, y -99.06..-97.06 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:172.27,-191.74'Net-(R66-Pad2)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.7 mm (fastest: Net-(R66-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R66-Pad2)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 0.7 mm under the track with no copper, at (172.27, -191.74), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R66-Pad2)' on L8_BOTTOM at (172.27, -191.74), 0.7 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A172.27%2C-191.74 serves each with its own layer_image region; all of them lie in x 170.92..173.62, y -192.74..-190.74 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:172.68,-121.57'/TOP/Ethernet_PHY/PHY_MDC' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 3.53 mm (fastest: /TOP/Ethernet_PHY/PHY_MDC at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_MDC' on L6_DIGITAL, the 3V3 plane on L7_PSU has 3.53 mm under the track with no copper, at (172.68, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_MDC' on L6_DIGITAL at (172.68, -121.57), 3.53 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A172.68%2C-121.57 serves each with its own layer_image region; all of them lie in x 171.68..173.68, y -124.33..-118.81 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:173.55,-191.74'Net-(R66-Pad2)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.03 mm (fastest: Net-(R66-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R66-Pad2)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.03 mm under the track with no copper, at (173.55, -191.74), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R66-Pad2)' on L8_BOTTOM at (173.55, -191.74), 2.03 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A173.55%2C-191.74 serves each with its own layer_image region; all of them lie in x 171.83..175.65, y -192.74..-189.75 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:175.18,-121.57'/TOP/Ethernet_PHY//PHY_RST' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 3.64 mm (fastest: /TOP/Ethernet_PHY//PHY_RST at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL, the 3V3 plane on L7_PSU has 3.64 mm under the track with no copper, at (175.18, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL at (175.18, -121.57), 3.64 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A175.18%2C-121.57 serves each with its own layer_image region; all of them lie in x 174.18..176.18, y -124.39..-118.75 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:176.01,-101.55'Net-(J12-Pad2)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.54 mm (fastest: Net-(J12-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J12-Pad2)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.54 mm under the track with no copper, at (176.01, -101.55), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J12-Pad2)' on L8_BOTTOM at (176.01, -101.55), 1.54 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A176.01%2C-101.55 serves each with its own layer_image region; all of them lie in x 174.56..177.35, y -103..-100.29 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:176.03,-107.03'/TOP/Ethernet_PHY/PHY_MDIO' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.3 mm (fastest: /TOP/Ethernet_PHY/PHY_MDIO at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_MDIO' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.3 mm under the track with no copper, at (176.03, -107.03), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_MDIO' on L8_BOTTOM at (176.03, -107.03), 2.3 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A176.03%2C-107.03 serves each with its own layer_image region; all of them lie in x 175.03..177.03, y -109.18..-104.88 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:176.05,-102.22'/TOP/Ethernet_PHY/PHY_HPD' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.35 mm (fastest: /TOP/Ethernet_PHY/PHY_HPD at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_HPD' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.35 mm under the track with no copper, at (176.05, -102.22), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_HPD' on L8_BOTTOM at (176.05, -102.22), 1.35 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A176.05%2C-102.22 serves each with its own layer_image region; all of them lie in x 173.78..177.35, y -103.71..-100.92 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:179.96,-105.08'/TOP/Ethernet_PHY/CONFIG1' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.32 mm (fastest: /TOP/Ethernet_PHY/CONFIG1 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/CONFIG1' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.32 mm under the track with no copper, at (179.96, -105.08), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/CONFIG1' on L8_BOTTOM at (179.96, -105.08), 1.32 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A179.96%2C-105.08 serves each with its own layer_image region; all of them lie in x 178.96..181.25, y -106.82..-103.62 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:180.13,-135.39'Net-(Q3-Pad1)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.12 mm (fastest: Net-(Q3-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(Q3-Pad1)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.12 mm under the track with no copper, at (180.13, -135.39), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(Q3-Pad1)' on L8_BOTTOM at (180.13, -135.39), 2.12 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A180.13%2C-135.39 serves each with its own layer_image region; all of them lie in x 178.8..181.45, y -137.44..-133.59 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:180.29,-121.57'/TOP/Ethernet_PHY/PHY_HPD' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 3.55 mm (fastest: /TOP/Ethernet_PHY/PHY_HPD at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_HPD' on L6_DIGITAL, the 3V3 plane on L7_PSU has 3.55 mm under the track with no copper, at (180.29, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_HPD' on L6_DIGITAL at (180.29, -121.57), 3.55 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A180.29%2C-121.57 serves each with its own layer_image region; all of them lie in x 179.29..181.29, y -124.35..-118.8 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:182.95,-168.4'/TOP/Ethernet_PHY/PHY_RXD1' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.91 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD1 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD1' on L6_DIGITAL, the 3V3 plane on L7_PSU has 1.91 mm under the track with copper of 3V3, not a plane, at (182.95, -168.4), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD1' on L6_DIGITAL at (182.95, -168.4), 1.91 mm over copper of 3V3, not a plane, to the end of the track; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A182.95%2C-168.4 serves each with its own layer_image region; all of them lie in x 181.95..184.46, y -170.44..-166.61 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:183,-121.57'/TOP/Ethernet_PHY/PHY_RXD1' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 3.5 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD1 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD1' on L6_DIGITAL, the 3V3 plane on L7_PSU has 3.5 mm under the track with no copper, at (183, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD1' on L6_DIGITAL at (183, -121.57), 3.5 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A183%2C-121.57 serves each with its own layer_image region; all of them lie in x 182..184, y -124.32..-118.82 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:183.21,-90.91'/TOP/Ethernet_PHY/PHY_RXD2' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.82 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD2 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD2' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.82 mm under the track with no copper, at (183.21, -90.91), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD2' on L8_BOTTOM at (183.21, -90.91), 1.82 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A183.21%2C-90.91 serves each with its own layer_image region; all of them lie in x 181.62..184.47, y -93.12..-89.65 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:183.9,-119.02'/TOP/Ethernet_PHY/PHY_MDIO' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.19 mm (fastest: /TOP/Ethernet_PHY/PHY_MDIO at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_MDIO' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.19 mm under the track with no copper, at (183.9, -119.02), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_MDIO' on L8_BOTTOM at (183.9, -119.02), 1.19 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A183.9%2C-119.02 serves each with its own layer_image region; all of them lie in x 182.3..185.5, y -120.02..-118.02 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:183.96,-169.49'/TOP/Ethernet_PHY/PHY_RXD2' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.56 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD2 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD2' on L6_DIGITAL, the 3V3 plane on L7_PSU has 2.56 mm under the track with copper of 3V3, not a plane, at (183.96, -169.49), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.1 mm). No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD2' on L6_DIGITAL at (183.96, -169.49), 2.56 mm, running ALONG the bare copper for 1.1 mm, not across it over copper of 3V3, not a plane, to the end of the track; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A183.96%2C-169.49 serves each with its own layer_image region; all of them lie in x 182.96..185.46, y -171.44..-166.81 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:184.19,-90.42'/TOP/Ethernet_PHY/PHY_RXD2' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.84 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD2 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD2' on L8_BOTTOM, the 3V3 plane on L7_PSU has 0.84 mm under the track with no copper, at (184.19, -90.42), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD2' on L8_BOTTOM at (184.19, -90.42), 0.84 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A184.19%2C-90.42 serves each with its own layer_image region; all of them lie in x 182.77..185.62, y -91.42..-89.42 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:184.96,-149.62'Net-(R51-Pad1)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.85 mm (fastest: Net-(R51-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R51-Pad1)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.85 mm under the track with no copper, at (184.96, -149.62), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R51-Pad1)' on L8_BOTTOM at (184.96, -149.62), 2.85 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A184.96%2C-149.62 serves each with its own layer_image region; all of them lie in x 183.96..185.96, y -152.04..-147.19 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:184.96,-176.49'Net-(R51-Pad1)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 10.56 mm (fastest: Net-(R51-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R51-Pad1)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 10.56 mm under the track with copper of 3V3, not a plane, at (184.96, -176.49), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.98 mm). No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R51-Pad1)' on L8_BOTTOM at (184.96, -176.49), 10.56 mm, running ALONG the bare copper for 0.98 mm, not across it over copper of 3V3, not a plane, to the end of the track; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A184.96%2C-176.49 serves each with its own layer_image region; all of them lie in x 183.96..186.46, y -179.44..-166.81 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:186.71,-188.69'Net-(R68-Pad2)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.18 mm (fastest: Net-(R68-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R68-Pad2)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 0.18 mm under the track with no copper, at (186.71, -188.69), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R68-Pad2)' on L8_BOTTOM at (186.71, -188.69), 0.18 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A186.71%2C-188.69 serves each with its own layer_image region; all of them lie in x 185.67..187.74, y -189.81..-187.66 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:188.32,-169.94'/TOP/Ethernet_PHY/PHY_TXD5' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.48 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD5 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD5' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.48 mm under the track with no copper, at (188.32, -169.94), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 188.1..191.25, y -172.66..-167.11 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD5' on L8_BOTTOM at (188.32, -169.94), 2.48 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A188.32%2C-169.94 serves each with its own layer_image region; all of them lie in x 186.73..190.19, y -171.17..-167.71 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:188.43,-111.46'/TOP/Ethernet_PHY/100_LED' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.92 mm (fastest: /TOP/Ethernet_PHY/100_LED at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/100_LED' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.92 mm under the track with no copper, at (188.43, -111.46), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/100_LED' on L8_BOTTOM at (188.43, -111.46), 1.92 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A188.43%2C-111.46 serves each with its own layer_image region; all of them lie in x 186.65..190.22, y -113.19..-110.01 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:188.53,-143.22'Net-(U12-PadE14)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.01 mm (fastest: Net-(U12-PadE14) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(U12-PadE14)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.01 mm under the track with no copper, at (188.53, -143.22), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(U12-PadE14)' on L8_BOTTOM at (188.53, -143.22), 2.01 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A188.53%2C-143.22 serves each with its own layer_image region; all of them lie in x 187.08..190.25, y -144.22..-141.22 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:188.7,-101.29'/TOP/Ethernet_PHY/PHY_TXD1' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.73 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD1 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD1' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.73 mm under the track with no copper, at (188.7, -101.29), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD1' on L8_BOTTOM at (188.7, -101.29), 1.73 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A188.7%2C-101.29 serves each with its own layer_image region; all of them lie in x 186.83..190.56, y -102.29..-100.29 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:189.95,-167.96'/TOP/Ethernet_PHY/PHY_INT' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.7 mm (fastest: /TOP/Ethernet_PHY/PHY_INT at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL, the 3V3 plane on L7_PSU has 0.7 mm under the track with no copper, at (189.95, -167.96), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 188.1..191.25, y -172.66..-167.11 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL at (189.95, -167.96), 0.7 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A189.95%2C-167.96 serves each with its own layer_image region; all of them lie in x 188.73..191.22, y -169.17..-166.67 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:189.96,-218.79'Net-(R67-Pad2)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.01 mm (fastest: Net-(R67-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R67-Pad2)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.01 mm under the track with no copper, at (189.96, -218.79), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R67-Pad2)' on L8_BOTTOM at (189.96, -218.79), 2.01 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A189.96%2C-218.79 serves each with its own layer_image region; all of them lie in x 188.96..191.89, y -220.58..-217.31 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:189.97,-167.93'/TOP/Ethernet_PHY/PHY_TXD5' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.69 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD5 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD5' on L8_BOTTOM, the 3V3 plane on L7_PSU has 0.69 mm under the track with no copper, at (189.97, -167.93), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 188.1..191.25, y -172.66..-167.11 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD5' on L8_BOTTOM at (189.97, -167.93), 0.69 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A189.97%2C-167.93 serves each with its own layer_image region; all of them lie in x 188.72..191.21, y -169.18..-166.69 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:190.48,-171.94'/TOP/Ethernet_PHY/PHY_RXD0' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 3.24 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD0 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD0' on L6_DIGITAL, the 3V3 plane on L7_PSU has 3.24 mm under the track with no copper, at (190.48, -171.94), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD0' on L6_DIGITAL at (190.48, -171.94), 3.24 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A190.48%2C-171.94 serves each with its own layer_image region; all of them lie in x 187.86..193.1, y -172.94..-170.94 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:190.84,-168.06'Net-(U12-PadE14)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.45 mm (fastest: Net-(U12-PadE14) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(U12-PadE14)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 0.45 mm under the track with no copper, at (190.84, -168.06), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 188.1..191.25, y -172.66..-167.11 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(U12-PadE14)' on L8_BOTTOM at (190.84, -168.06), 0.45 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A190.84%2C-168.06 serves each with its own layer_image region; all of them lie in x 189.72..191.96, y -169.18..-166.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:190.96,-165.54'Net-(U12-PadE14)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 3.17 mm (fastest: Net-(U12-PadE14) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(U12-PadE14)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 3.17 mm under the track with no copper, at (190.96, -165.54), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(U12-PadE14)' on L8_BOTTOM at (190.96, -165.54), 3.17 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A190.96%2C-165.54 serves each with its own layer_image region; all of them lie in x 189.96..191.96, y -168.13..-162.96 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:190.98,-170.94'/TOP/Ethernet_PHY/PHY_RXD4' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.24 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD4 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD4' on L6_DIGITAL, the 3V3 plane on L7_PSU has 2.24 mm under the track with no copper, at (190.98, -170.94), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD4' on L6_DIGITAL at (190.98, -170.94), 2.24 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A190.98%2C-170.94 serves each with its own layer_image region; all of them lie in x 188.86..193.1, y -171.94..-169.94 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:191.22,-166.67'/TOP/Ethernet_PHY/PHY_INT' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.45 mm (fastest: /TOP/Ethernet_PHY/PHY_INT at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL, the 3V3 plane on L7_PSU has 1.45 mm under the track with no copper, at (191.22, -166.67), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL at (191.22, -166.67), 1.45 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A191.22%2C-166.67 serves each with its own layer_image region; all of them lie in x 189.71..192.73, y -168.18..-165.16 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:191.47,-219.41'Net-(R67-Pad2)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.55 mm (fastest: Net-(R67-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R67-Pad2)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 0.55 mm under the track with no copper, at (191.47, -219.41), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R67-Pad2)' on L8_BOTTOM at (191.47, -219.41), 0.55 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A191.47%2C-219.41 serves each with its own layer_image region; all of them lie in x 190.26..192.64, y -220.58..-218.21 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:191.64,-218.56'Net-(R67-Pad2)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.1 mm (fastest: Net-(R67-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R67-Pad2)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.1 mm under the track with no copper, at (191.64, -218.56), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R67-Pad2)' on L8_BOTTOM at (191.64, -218.56), 1.1 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A191.64%2C-218.56 serves each with its own layer_image region; all of them lie in x 190.46..192.64, y -219.83..-216.8 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:196.59,-219.17'Net-(R67-Pad2)' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 3.11 mm (fastest: Net-(R67-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R67-Pad2)' on L8_BOTTOM, the 3V3 plane on L7_PSU has 3.11 mm under the track with no copper, at (196.59, -219.17), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R67-Pad2)' on L8_BOTTOM at (196.59, -219.17), 3.11 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A196.59%2C-219.17 serves each with its own layer_image region; all of them lie in x 194.59..197.96, y -220.54..-216.9 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:relief2 nets cross the thermal reliefs of the 3V3 plane on L7_PSU at 2 places, the longest 7.97 mm (fastest: Net-(R56-Pad1) at 100 ps 10-90 %, ASSUMED)

      The 3V3 plane on L7_PSU is drawn back round copper of its own net - pads spoked into it, in thermal reliefs - and tracks cross those reliefs: over the bare ring either side of the pad or spoke the return has no plane under it, and finds its way round through the spokes. 2 place(s) on 2 net(s), each the relief's bare stretches either side of that copper counted together, the longest 7.97 mm. One decision covers the pour's reliefs: whether tracks may cross them, or the reliefs or the routing should keep them apart. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R56-Pad1)' on L8_BOTTOM at (185.96, -168.45), 7.97 mm, running ALONG the bare copper for 0.58 mm, not across it over no copper; other side: none: the signal layer is outermost
      • '/TOP/Ethernet_PHY//PHY_RST' on L6_DIGITAL at (186.96, -168.53), 5.04 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3Arelief serves each with its own layer_image region; all of them lie in x 184.96..187.96, y -175.07..-163.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:140.94,-98.62'Net-(J12-Pad4)' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.13 mm (fastest: Net-(J12-Pad4) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J12-Pad4)' on L1_TOP, the GND plane on L2_GND has 1.13 mm under the track with no copper, at (140.94, -98.62), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J12-Pad4)' on L1_TOP at (140.94, -98.62), 1.13 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A140.94%2C-98.62 serves each with its own layer_image region; all of them lie in x 139.94..141.94, y -100.18..-97.05 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:162.42,-121.574 nets cross where the GND plane on L2_GND, the GND plane on L3_DIGITAL and the 2V5 plane on L4_DIGITAL is drawn back round copper of /TOP/BeagleBone_connectors/BBB_SPI1_CLK, /TOP/BeagleBone_connectors/BBB_SPI1_CS0, /TOP/BeagleBone_connectors/BBB_SPI1_D0, /TOP/BeagleBone_connectors/BBB_SPI1_D1, /TOP/Ethernet_PHY/PHY_RXD3, /TOP/Ethernet_PHY/PHY_RXD7, Net-(R55-Pad2), at 1 place, the longest 54.41 mm (fastest: Net-(R55-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/BeagleBone_connectors/BBB_SPI1_D1' on L3_DIGITAL, the 2V5 plane on L4_DIGITAL has 54.41 mm under the track with copper of /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), not a plane, at (162.42, -132.54), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 3 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 27.12 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 155.74..177.58, y -162.86..-123.3 and of the pour at x 160.21..239.71, y -182.44..-81.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 4 of the 7 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 7 reference layers: '/TOP/BeagleBone_connectors/BBB_SPI1_CLK' on L3_DIGITAL at (165.33, -121.57), 3.88 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_SPI1_CLK' on L3_DIGITAL at (165.33, -133.55), 53.63 mm, running ALONG the bare copper for 27.12 mm, not across it over copper of /TOP/Ethernet_PHY/PHY_RXD7, /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_SPI1_D0' on L3_DIGITAL at (162.76, -121.57), 3.76 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_SPI1_D0' on L3_DIGITAL at (162.76, -132.51), 53.22 mm, running ALONG the bare copper for 23.76 mm, not across it over copper of /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_SPI1_D1' on L3_DIGITAL at (162.42, -121.57), 3.88 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_SPI1_D1' on L3_DIGITAL at (162.42, -132.54), 54.41 mm, running ALONG the bare copper for 24.3 mm, not across it over copper of /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / 'Net-(R55-Pad2)' on L4_DIGITAL at (175.66, -157.33), 3.14 mm over copper of /TOP/BeagleBone_connectors/BBB_SPI1_CS0, /TOP/BeagleBone_connectors/BBB_SPI1_D1, /TOP/BeagleBone_connectors/BBB_SPI1_D0, /TOP/BeagleBone_connectors/BBB_SPI1_CLK, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A162.42%2C-121.57 serves each with its own layer_image region; all of them lie in x 161.42..182.96, y -167.44..-118.63 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:172.74,-121.574 nets cross where the GND plane on L2_GND, the GND plane on L3_DIGITAL and the 2V5 plane on L4_DIGITAL is drawn back round copper of /TOP/BeagleBone_connectors/BBB_CLKOUT2, /TOP/BeagleBone_connectors/BBB_SPI1_CLK, /TOP/Ethernet_PHY/PHY_RXD3, /TOP/Ethernet_PHY/PHY_RXD7, Net-(R55-Pad2), at 1 place, the longest 49.36 mm (fastest: Net-(R55-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/BeagleBone_connectors/BBB_CLKOUT2' on L3_DIGITAL, the 2V5 plane on L4_DIGITAL has 49.36 mm under the track with copper of /TOP/Ethernet_PHY/PHY_RXD7, /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), not a plane, at (172.74, -136.01), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 2 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 32.01 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -182.44..-81.44 and of the pour at x 165.92..181.85, y -162.98..-123.3 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 4 of the 5 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 5 reference layers: '/TOP/BeagleBone_connectors/BBB_CLKOUT2' on L3_DIGITAL at (172.74, -121.57), 3.47 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_CLKOUT2' on L3_DIGITAL at (172.74, -136.01), 49.36 mm, running ALONG the bare copper for 32.01 mm, not across it over copper of /TOP/Ethernet_PHY/PHY_RXD7, /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Ethernet_PHY/PHY_RXD3' on L4_DIGITAL at (177.96, -156.89), 1.74 mm over copper of /TOP/BeagleBone_connectors/BBB_CLKOUT2, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL at (181.96, -162.77), 7.49 mm, running ALONG the bare copper for 4.84 mm, not across it over copper of /TOP/BeagleBone_connectors/BBB_SPI1_CLK, /TOP/BeagleBone_connectors/BBB_CLKOUT2, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R55-Pad2)' on L4_DIGITAL at (175.66, -154.59), 1.73 mm over copper of /TOP/BeagleBone_connectors/BBB_CLKOUT2, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A172.74%2C-121.57 serves each with its own layer_image region; all of them lie in x 171.74..183.46, y -168.99..-118.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:174.41,-176.34'/TOP/Spartan6_FPGA/LED_G' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.41 mm (fastest: /TOP/Spartan6_FPGA/LED_G at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/Spartan6_FPGA/LED_G' on L3_DIGITAL, the GND plane on L2_GND has 1.41 mm under the track with no copper, at (174.41, -176.34), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Spartan6_FPGA/LED_G' on L3_DIGITAL at (174.41, -176.34), 1.41 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A174.41%2C-176.34 serves each with its own layer_image region; all of them lie in x 173.14..176.32, y -177.61..-175.06 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:181.67,-182.95 nets cross where the GND plane on L2_GND, the GND plane on L3_DIGITAL and the GND plane on L4_DIGITAL is drawn back round copper of /TOP/Digital_interface/FD_ENA, /TOP/FPGA_configuration//PROG_B_FPGA, /TOP/FPGA_configuration/EEPROM_CS, Net-(R62-Pad2), Net-(R64-Pad2), at 1 place, the longest 7.17 mm (fastest: /TOP/FPGA_configuration//PROG_B_FPGA at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/Digital_interface/FD_ENA' on L3_DIGITAL, the GND plane on L4_DIGITAL has 7.17 mm under the track with copper of Net-(R64-Pad2), Net-(R62-Pad2), /TOP/FPGA_configuration/EEPROM_CS, /TOP/FPGA_configuration//PROG_B_FPGA, not a plane, at (181.96, -180.78), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 5 of the 6 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 6 reference layers: '/TOP/Digital_interface/FD_ENA' on L3_DIGITAL at (181.67, -182.9), 1.07 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/Digital_interface/FD_ENA' on L3_DIGITAL at (181.96, -180.78), 7.17 mm over copper of Net-(R64-Pad2), Net-(R62-Pad2), /TOP/FPGA_configuration/EEPROM_CS, /TOP/FPGA_configuration//PROG_B_FPGA, not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/FPGA_configuration//PROG_B_FPGA' on L4_DIGITAL at (181.49, -184.77), 1.17 mm over copper of /TOP/Digital_interface/FD_ENA, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / '/TOP/FPGA_configuration/EEPROM_CS' on L4_DIGITAL at (181.49, -184.33), 1.17 mm over copper of /TOP/Digital_interface/FD_ENA, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R62-Pad2)' on L4_DIGITAL at (181.49, -184), 1.17 mm over copper of /TOP/Digital_interface/FD_ENA, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / 'Net-(R64-Pad2)' on L4_DIGITAL at (181.99, -183.69), 2.16 mm over copper of /TOP/Digital_interface/FD_ENA, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A181.67%2C-182.9 serves each with its own layer_image region; all of them lie in x 179.58..183.74, y -186.35..-177.44 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:183,-121.57'/TOP/Ethernet_PHY/PHY_GTXCLK' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 3.5 mm (fastest: /TOP/Ethernet_PHY/PHY_GTXCLK at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_GTXCLK' on L3_DIGITAL, the GND plane on L2_GND has 3.5 mm under the track with no copper, at (183, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_GTXCLK' on L3_DIGITAL at (183, -121.57), 3.5 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A183%2C-121.57 serves each with its own layer_image region; all of them lie in x 182..184, y -124.32..-118.82 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:183.62,-143.39'/TOP/Ethernet_PHY/PHY_GTXCLK' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.2 mm (fastest: /TOP/Ethernet_PHY/PHY_GTXCLK at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_GTXCLK' on L3_DIGITAL, the GND plane on L2_GND has 1.2 mm under the track with no copper, at (183.62, -143.39), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_GTXCLK' on L3_DIGITAL at (183.62, -143.39), 1.2 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A183.62%2C-143.39 serves each with its own layer_image region; all of them lie in x 182.62..184.62, y -144.99..-141.79 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:183.93,-143.5'/TOP/Ethernet_PHY/PHY_TXD6' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.15 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD6 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL, the GND plane on L2_GND has 1.15 mm under the track with no copper, at (183.93, -143.5), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL at (183.93, -143.5), 1.15 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A183.93%2C-143.5 serves each with its own layer_image region; all of them lie in x 182.93..184.93, y -145.08..-141.93 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:183.93,-149.26'/TOP/Ethernet_PHY/PHY_TXD6' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 2.83 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD6 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL, the GND plane on L2_GND has 2.83 mm under the track with no copper, at (183.93, -149.26), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL at (183.93, -149.26), 2.83 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A183.93%2C-149.26 serves each with its own layer_image region; all of them lie in x 182.93..184.96, y -152.04..-147.22 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:183.96,-168.95'/TOP/Ethernet_PHY/PHY_TXD6' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 6.24 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD6 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL, the GND plane on L2_GND has 6.24 mm under the track with no copper, at (183.96, -168.95), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.74 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL at (183.96, -168.95), 6.24 mm, running ALONG the bare copper for 0.74 mm, not across it over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A183.96%2C-168.95 serves each with its own layer_image region; all of them lie in x 182.96..184.96, y -173.07..-164.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:183.96,-173.52'/TOP/Ethernet_PHY/PHY_TXD6' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 2.56 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD6 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL, the GND plane on L2_GND has 2.56 mm under the track with copper of GND, not a plane, at (183.96, -173.52), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.92 mm). No hole cleared it: the outline of the pour at x 183.25..184.68, y -172.81..-172.07 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL at (183.96, -173.52), 2.56 mm, running ALONG the bare copper for 0.92 mm, not across it over copper of GND, not a plane, to the end of the track; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A183.96%2C-173.52 serves each with its own layer_image region; all of them lie in x 182.46..184.96, y -176.44..-171.81 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:184.96,-134.24'/TOP/Ethernet_PHY/PHY_TXEN' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.9 mm (fastest: /TOP/Ethernet_PHY/PHY_TXEN at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXEN' on L3_DIGITAL, the GND plane on L2_GND has 1.9 mm under the track with no copper, at (184.96, -134.24), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXEN' on L3_DIGITAL at (184.96, -134.24), 1.9 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A184.96%2C-134.24 serves each with its own layer_image region; all of them lie in x 183.96..185.96, y -136.19..-132.29 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:184.96,-139.89'/TOP/Ethernet_PHY/PHY_TXEN' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.58 mm (fastest: /TOP/Ethernet_PHY/PHY_TXEN at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXEN' on L3_DIGITAL, the GND plane on L2_GND has 1.58 mm under the track with no copper, at (184.96, -139.89), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXEN' on L3_DIGITAL at (184.96, -139.89), 1.58 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A184.96%2C-139.89 serves each with its own layer_image region; all of them lie in x 183.96..185.96, y -141.68..-138.1 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:184.96,-149.62'/TOP/Ethernet_PHY/PHY_TXEN' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 2.85 mm (fastest: /TOP/Ethernet_PHY/PHY_TXEN at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXEN' on L3_DIGITAL, the GND plane on L2_GND has 2.85 mm under the track with no copper, at (184.96, -149.62), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXEN' on L3_DIGITAL at (184.96, -149.62), 2.85 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A184.96%2C-149.62 serves each with its own layer_image region; all of them lie in x 183.96..185.96, y -152.04..-147.19 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:185.41,-106.09'/TOP/Ethernet_PHY/PHY_TXD6' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.05 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD6 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL, the GND plane on L2_GND has 1.05 mm under the track with no copper, at (185.41, -106.09), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD6' on L3_DIGITAL at (185.41, -106.09), 1.05 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A185.41%2C-106.09 serves each with its own layer_image region; all of them lie in x 184.41..186.41, y -107.61..-104.56 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:185.96,-169.85'/TOP/Ethernet_PHY/PHY_TXER' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 6.54 mm (fastest: /TOP/Ethernet_PHY/PHY_TXER at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXER' on L3_DIGITAL, the GND plane on L2_GND has 6.54 mm under the track with copper of GND, not a plane, at (185.96, -169.85), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.17 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXER' on L3_DIGITAL at (185.96, -169.85), 6.54 mm, running ALONG the bare copper for 1.17 mm, not across it over copper of GND, not a plane, to the end of the track; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A185.96%2C-169.85 serves each with its own layer_image region; all of them lie in x 184.46..186.96, y -174.44..-165.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:186.96,-155.24'/TOP/Ethernet_PHY/PHY_MDIO' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.92 mm (fastest: /TOP/Ethernet_PHY/PHY_MDIO at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_MDIO' on L3_DIGITAL, the GND plane on L2_GND has 0.92 mm under the track with no copper, at (186.96, -155.24), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_MDIO' on L3_DIGITAL at (186.96, -155.24), 0.92 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A186.96%2C-155.24 serves each with its own layer_image region; all of them lie in x 185.96..188.26, y -156.79..-153.99 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:187.96,-167.44'/TOP/Ethernet_PHY/PHY_MDIO' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 3.22 mm (fastest: /TOP/Ethernet_PHY/PHY_MDIO at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_MDIO' on L3_DIGITAL, the GND plane on L2_GND has 3.22 mm under the track with no copper, at (187.96, -167.44), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.02 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_MDIO' on L3_DIGITAL at (187.96, -167.44), 3.22 mm, running ALONG the bare copper for 1.02 mm, not across it over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A187.96%2C-167.44 serves each with its own layer_image region; all of them lie in x 186.96..188.96, y -170.05..-164.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:187.96,-171.33'/TOP/Ethernet_PHY/PHY_MDIO' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 3.54 mm (fastest: /TOP/Ethernet_PHY/PHY_MDIO at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_MDIO' on L3_DIGITAL, the GND plane on L2_GND has 3.54 mm under the track with copper of GND, not a plane, at (187.96, -171.33), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 187.1..191.25, y -170.66..-167.11 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_MDIO' on L3_DIGITAL at (187.96, -171.33), 3.54 mm over copper of GND, not a plane, to the end of the track; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A187.96%2C-171.33 serves each with its own layer_image region; all of them lie in x 186.46..188.96, y -174.44..-168.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:188.96,-166.95'/TOP/Ethernet_PHY/PHY_TXD2' crosses where the GND plane on L2_GND and the 2V5 plane on L4_DIGITAL is drawn back round copper of /TOP/FPGA_configuration/EEPROM_IO3, at 1 place, the longest 65.62 mm; 1 cleared on both sides of the track (fastest: /TOP/Ethernet_PHY/PHY_TXD2 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD2' on L3_DIGITAL, the 2V5 plane on L4_DIGITAL has 65.62 mm under the track with copper of /TOP/FPGA_configuration/EEPROM_IO3, not a plane, at (188.96, -162.13), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 3 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 60.88 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -182.44..-81.44 and of the pour at x 187.1..191.25, y -170.66..-167.11 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 3 reference layers: '/TOP/Ethernet_PHY/PHY_TXD2' on L3_DIGITAL at (188.96, -166.95), 2.24 mm, running ALONG the bare copper for 0.59 mm, not across it over no copper; other side: no plane on L4_DIGITAL / '/TOP/Ethernet_PHY/PHY_TXD2' on L3_DIGITAL at (188.96, -170.33), 4.54 mm, running ALONG the bare copper for 0.88 mm, not across it over copper of GND, not a plane, to the end of the track; other side: no plane on L4_DIGITAL / '/TOP/Ethernet_PHY/PHY_TXD2' on L3_DIGITAL at (188.96, -162.13), 65.62 mm, running ALONG the bare copper for 60.88 mm, not across it over copper of /TOP/FPGA_configuration/EEPROM_IO3, not a plane, to the end of the track; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A188.96%2C-166.95 serves each with its own layer_image region; all of them lie in x 186.22..190.34, y -174.44..-107.9 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:220.55,-194.05'/TOP/Spartan6_FPGA/SW2' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 1.25 mm; 1 cleared on both sides of the track (fastest: /TOP/Spartan6_FPGA/SW2 at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/Spartan6_FPGA/SW2' on L3_DIGITAL, the GND plane on L2_GND has 1.25 mm under the track with no copper, at (220.55, -194.05), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Spartan6_FPGA/SW2' on L3_DIGITAL at (220.55, -194.05), 1.25 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW2' on L3_DIGITAL at (220.55, -194.05), 1.25 mm over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A220.55%2C-194.05 serves each with its own layer_image region; all of them lie in x 218.93..222.18, y -195.05..-193.05 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:221.96,-176.42'Net-(R126-Pad2)' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.06 mm (fastest: Net-(R126-Pad2) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(R126-Pad2)' on L1_TOP, the GND plane on L2_GND has 1.06 mm under the track with no copper, at (221.96, -176.42), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(R126-Pad2)' on L1_TOP at (221.96, -176.42), 1.06 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A221.96%2C-176.42 serves each with its own layer_image region; all of them lie in x 220.4..223.42, y -177.42..-175.32 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:231.9,-194.05'/TOP/Spartan6_FPGA/SW2' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 1.19 mm; 1 cleared on both sides of the track (fastest: /TOP/Spartan6_FPGA/SW2 at 100 ps 10-90 %, ASSUMED)

      Along '/TOP/Spartan6_FPGA/SW2' on L3_DIGITAL, the GND plane on L2_GND has 1.19 mm under the track with no copper, at (231.9, -194.05), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Spartan6_FPGA/SW2' on L3_DIGITAL at (231.9, -194.05), 1.19 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW2' on L3_DIGITAL at (231.9, -194.05), 1.19 mm over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A231.9%2C-194.05 serves each with its own layer_image region; all of them lie in x 230.3..233.5, y -195.05..-193.05 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L3_DIGITAL:177.96,-121.57'/TOP/Ethernet_PHY/PHY_RXD3' crosses where the outline of the GND plane on L3_DIGITAL is drawn back, at 1 place, the longest 3.6 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD3 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD3' on L4_DIGITAL, the GND plane on L3_DIGITAL has 3.6 mm under the track with no copper, at (177.96, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.19 mm). No hole cleared it: the outline of the pour at x 173.36..183.04, y -161.27..-123.3 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD3' on L4_DIGITAL at (177.96, -121.57), 3.6 mm, running ALONG the bare copper for 1.19 mm, not across it over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L3_DIGITAL%3A177.96%2C-121.57 serves each with its own layer_image region; all of them lie in x 176.96..178.96, y -124.37..-118.77 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L3_DIGITAL:182.73,-104.37'/TOP/Ethernet_PHY/PHY_RXD7' crosses where the outline of the GND plane on L3_DIGITAL is drawn back, at 1 place, the longest 0.36 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD7 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL, the GND plane on L3_DIGITAL has 0.36 mm under the track with no copper, at (182.73, -104.37), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 173.36..184.83, y -119.84..-102.57 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL at (182.73, -104.37), 0.36 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L3_DIGITAL%3A182.73%2C-104.37 serves each with its own layer_image region; all of them lie in x 181.73..183.73, y -105.55..-103.19 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L3_DIGITAL:190.01,-133.12'/TOP/Ethernet_PHY/PHY_TXD4' crosses where the outline of the GND plane on L3_DIGITAL is drawn back, at 1 place, the longest 1.14 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD4 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD4' on L4_DIGITAL, the GND plane on L3_DIGITAL has 1.14 mm under the track with no copper, at (190.01, -133.12), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD4' on L4_DIGITAL at (190.01, -133.12), 1.14 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L3_DIGITAL%3A190.01%2C-133.12 serves each with its own layer_image region; all of them lie in x 189.01..191.01, y -134.69..-131.55 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L3_DIGITAL:191.23,-103.42'/TOP/Ethernet_PHY/PHY_TXD4' crosses where the outline of the GND plane on L3_DIGITAL is drawn back, at 1 place, the longest 0.69 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD4 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD4' on L4_DIGITAL, the GND plane on L3_DIGITAL has 0.69 mm under the track with no copper, at (191.23, -103.42), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Ethernet_PHY/PHY_TXD4' on L4_DIGITAL at (191.23, -103.42), 0.69 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L3_DIGITAL%3A191.23%2C-103.42 serves each with its own layer_image region; all of them lie in x 190.23..192.23, y -104.77..-102.07 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:routed@L3_DIGITAL|L4_DIGITALTracks on L3_DIGITAL and L4_DIGITAL cross each other at 9 places, each layer the other's reference with its pour cleared round its own tracks, the longest 56.11 mm; 1 runs ALONG the cut round another net's track (fastest: /TOP/FPGA_configuration//PROG_B_FPGA at 100 ps 10-90 %, ASSUMED)

      L3_DIGITAL and L4_DIGITAL each carry a pour and routed tracks, and each is the other's nearest reference. Wherever a track on one crosses a track on the other, the pour under it is cleared round that other track, so for the width of the cut the return has no plane under it and detours round the cut. 9 place(s) on 14 net(s), 5 of them seen from both tracks (each counted once). 1 of the crossings run ALONG the cut round another net's track rather than across it, parallel to its edges (the longest 53.59 mm): over or right beside that track, broadside to it as well as off the plane. One decision covers the layer pair: whether these layers may take a pour their own tracks cut as the reference, or the routing or the stackup should give the tracks a plane that is not cut where they cross. 22 of the 23 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one crossing of two tracks, seen from each: '/TOP/FPGA_configuration/EEPROM_CS' on L4_DIGITAL at (196.56, -180.04), 1.16 mm over copper of Net-(R61-Pad1), not a plane; other side: no plane on L5_PSU / 'Net-(R61-Pad1)' on L3_DIGITAL at (196.23, -179.71), 0.87 mm over copper of /TOP/FPGA_configuration/EEPROM_CS, not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/Ethernet_PHY/PHY_TXD0' on L4_DIGITAL at (188.02, -133.36), 56.11 mm, running ALONG the bare copper for 53.59 mm, not across it over copper of /TOP/Ethernet_PHY/PHY_TXER, /TOP/Ethernet_PHY/PHY_MDIO, not a plane, to the end of the track; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL
      • one crossing of two tracks, seen from each: '/TOP/FPGA_configuration//PROG_B_FPGA' on L4_DIGITAL at (202.12, -176.83), 4.59 mm over copper of /TOP/Spartan6_FPGA/SW0, /TOP/Spartan6_FPGA/SW1, /TOP/Spartan6_FPGA/SW2, /TOP/Spartan6_FPGA/SW3, /TOP/Spartan6_FPGA/SW4, /TOP/Spartan6_FPGA/SW5, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / '/TOP/Spartan6_FPGA/SW1' on L3_DIGITAL at (202.45, -179.94), 1.65 mm over copper of /TOP/FPGA_configuration//PROG_B_FPGA, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW2' on L3_DIGITAL at (202.45, -179.42), 1.65 mm over copper of /TOP/FPGA_configuration//PROG_B_FPGA, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW3' on L3_DIGITAL at (202.45, -178.81), 1.65 mm over copper of /TOP/FPGA_configuration//PROG_B_FPGA, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW4' on L3_DIGITAL at (202.45, -178.23), 1.65 mm over copper of /TOP/FPGA_configuration//PROG_B_FPGA, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW5' on L3_DIGITAL at (202.45, -177.63), 1.65 mm over copper of /TOP/FPGA_configuration//PROG_B_FPGA, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • one crossing of two tracks, seen from each: '/TOP/FPGA_configuration/EEPROM_CS' on L4_DIGITAL at (196.56, -171.27), 4.59 mm over copper of /TOP/Spartan6_FPGA/SW0, /TOP/Spartan6_FPGA/SW1, /TOP/Spartan6_FPGA/SW2, /TOP/Spartan6_FPGA/SW3, /TOP/Spartan6_FPGA/SW4, /TOP/Spartan6_FPGA/SW5, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / '/TOP/Spartan6_FPGA/SW1' on L3_DIGITAL at (196.89, -174.38), 1.65 mm over copper of /TOP/FPGA_configuration/EEPROM_CS, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW2' on L3_DIGITAL at (196.89, -173.86), 1.65 mm over copper of /TOP/FPGA_configuration/EEPROM_CS, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW3' on L3_DIGITAL at (196.89, -173.25), 1.65 mm over copper of /TOP/FPGA_configuration/EEPROM_CS, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW4' on L3_DIGITAL at (196.89, -172.67), 1.65 mm over copper of /TOP/FPGA_configuration/EEPROM_CS, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Spartan6_FPGA/SW5' on L3_DIGITAL at (197.34, -172.52), 2.91 mm over copper of /TOP/FPGA_configuration/EEPROM_CS, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • one crossing of two tracks, seen from each: '/TOP/Ethernet_PHY/ACT_LED' on L3_DIGITAL at (182.47, -103.09), 2.01 mm over copper of /TOP/Ethernet_PHY/PHY_TXD7, /TOP/Ethernet_PHY/PHY_RXD7, not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL at (182.73, -103.3), 1.65 mm over copper of /TOP/Ethernet_PHY/ACT_LED, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL / '/TOP/Ethernet_PHY/PHY_TXD7' on L4_DIGITAL at (183.09, -102.94), 1.65 mm over copper of /TOP/Ethernet_PHY/ACT_LED, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL
      • '/TOP/Spartan6_FPGA/SW0' on L3_DIGITAL at (196.89, -175.01), 1.65 mm over copper of /TOP/FPGA_configuration/EEPROM_CS, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • '/TOP/Spartan6_FPGA/SW0' on L3_DIGITAL at (202.45, -180.57), 1.65 mm over copper of /TOP/FPGA_configuration//PROG_B_FPGA, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL
      • one crossing of two tracks, seen from each: '/TOP/Ethernet_PHY/ACT_LED' on L3_DIGITAL at (177.68, -104.02), 1.56 mm over copper of /TOP/Ethernet_PHY/PHY_RXD3, not a plane; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL / '/TOP/Ethernet_PHY/PHY_RXD3' on L4_DIGITAL at (177.96, -104.21), 1.65 mm over copper of /TOP/Ethernet_PHY/ACT_LED, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL
      • '/TOP/FPGA_configuration//PROG_B_FPGA' on L4_DIGITAL at (193.69, -184.77), 1.17 mm over copper of /TOP/Digital_interface/SPARE3, not a plane; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3Arouted%40L3_DIGITAL%7CL4_DIGITAL serves each with its own layer_image region; all of them lie in x 176.38..203.71, y -185.77..-100.65 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

  11. SinglePointNetmajorOpen

    SinglePointNet: 5 nets×5

    5 checked by the review by Claude walker (cern session) — 5 different reasons

    At Net-(R10-Pad1), Net-(R48-Pad1), Net-(R7-Pad1), Net-(R8-Pad1), Net-(R9-Pad1)

    Each finding, with its own headline
    • Net-(R10-Pad1)'Net-(R10-Pad1)' reaches only U6.2

      Net 'Net-(R10-Pad1)' is EFFECTIVELY single-point: it is wired to 2 pins but only one is POPULATED - the other connection(s) are DNP (R10.1). The populated end U6.2 is an IC INPUT, so as built it FLOATS. Confirm the depopulation is intended and the input has a defined level another way. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • Net-(R48-Pad1)'Net-(R48-Pad1)' reaches only U14.6

      Net 'Net-(R48-Pad1)' is EFFECTIVELY single-point: it is wired to 2 pins but only one is POPULATED - the other connection(s) are DNP (R48.1). The populated end U14.6 is an IC INPUT, so as built it FLOATS. Confirm the depopulation is intended and the input has a defined level another way. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • Net-(R7-Pad1)'Net-(R7-Pad1)' reaches only U3.2

      Net 'Net-(R7-Pad1)' is EFFECTIVELY single-point: it is wired to 2 pins but only one is POPULATED - the other connection(s) are DNP (R7.1). The populated end U3.2 is an IC INPUT, so as built it FLOATS. Confirm the depopulation is intended and the input has a defined level another way. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • Net-(R8-Pad1)'Net-(R8-Pad1)' reaches only U4.2

      Net 'Net-(R8-Pad1)' is EFFECTIVELY single-point: it is wired to 2 pins but only one is POPULATED - the other connection(s) are DNP (R8.1). The populated end U4.2 is an IC INPUT, so as built it FLOATS. Confirm the depopulation is intended and the input has a defined level another way. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • Net-(R9-Pad1)'Net-(R9-Pad1)' reaches only U5.2

      Net 'Net-(R9-Pad1)' is EFFECTIVELY single-point: it is wired to 2 pins but only one is POPULATED - the other connection(s) are DNP (R9.1). The populated end U5.2 is an IC INPUT, so as built it FLOATS. Confirm the depopulation is intended and the input has a defined level another way. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

  12. PartLifecyclemajorOpen

    W25Q64FVSSIG on U14: the distributor catalogue reports "Obsolete" for Winbond Electronics's W25Q64FVSSIG

    W25Q64FVSSIG on U14: the distributor catalogue reports "Obsolete" for Winbond Electronics's W25Q64FVSSIG — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. That is the maker this board's BOM names (Winbond). A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/W25Q64FVSSIG/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). No approved alternate is recorded for this position.

    At U14

  13. observationOBS-153minorOpen

    LDO heat-sink tabs U23/U24/U25 (TO-263) are on no net, so their only copper is the 7 x 10.8 mm pad; the datasheet thermal ratings assume 0.5 in^2 or a plane

    The TO-263 heat-sink tabs (pad 6) of LDOs U23, U24 and U25 are on no net, so each regulator's only heat spreader is about 75 mm^2 of isolated top copper, where the datasheet ratings assume 0.5 in^2 or a plane.

    Where it is

    • U23 LP3966-3.3, U24 LP3966-2.5 and U25 LP3883-1.2: the TO-263-5 tab pad (pad 6) carries net $NONE$. Pads 1-5 are SD, VIN, GND, VOUT and SENSE/BIAS.
    • In pcb/CPU/TimIQ_CPU.kicad_pcb each is (pad 6 smd rect ... (size 6.99008 10.80008) (layers L1_TOP F.Paste F.Mask)) with no net.
    • Board zones exist for GND, 5V, 3V3, 2V5, 1V2 and IN5V, none of which can join a net-less pad, and no vias tie it to inner planes.

    The numbers

    QuantityValueSource
    Tab copper per regulator6.99 x 10.80 mm = about 75 mm^2 (0.12 in^2)PCB file; derived
    LP3966 TO-263 derating60 C/W with 0.5 in^2 of 1 oz copperLP3966 datasheet, p.4
    LP3883about 40 C/W soldered to a copper planeLP3883 datasheet, p.2
    Drops U23 / U24 / U251.7 V / 2.5 V / 2.1 V (from 5 V or 3.3 V)derived
    U23 dissipation at 0.6 A1 Wderived

    U23 also carries U25's input current. At 1 W, U23 already exceeds what 60 C/W allows for a 20 C margin at 50 C ambient, and with a quarter of the rated copper the real theta-JA is higher.

    Why it matters

    The tab is the thermal path of a TO-263. Tie pad 6 to GND (the tab is the device ground) with a GND pour and thermal vias, or confirm the rail currents keep every Tj well inside 125 C. Load currents are not on file, so the magnitude is not established here.

  14. observationOBS-156minorOpen

    LP3966 capacitors outside the datasheet's ESR rules: input tantalums at about 14x the ESR/C limit, and about 10 uF of ceramic on 2V5 against a stated ~3 uF

    The LP3966 regulators U23/U24 break the datasheet's capacitor rules: their input tantalums are at about 14x the ESR/C limit, and U24 sees about 10 uF of ceramic on 2V5 against a stated ~3 uF.

    Input side (U23 LP3966-3.3, U24 LP3966-2.5, both from 5V)

    QuantityValueSource
    Local input capacitorsC114, C115: TAJB686K010 68 uF 10 V tantalum at U23 pin 2 and U24 pin 2netlist, net 5V
    Tantalum ESR1.4 ohm max at 100 kHzTAJB686K010RNJ datasheet, p.6
    LP3966 input ruleESR(mohm) / C(uF) <= 1.5LP3966 datasheet, p.10
    One capacitor1400 / 68 = 20.6derived
    Both in parallel5.1derived

    The remaining 5V capacitance is C123 10 uF aluminium and 100 nF ceramics (C124, C116).

    Output side (U24, 2V5)

    ``mermaid flowchart LR U24["U24 VOUT"] --> C121["C121 68 uF tantalum<br/>Net-(C121-Pad1)"] --> L5["L5 ferrite"] --> R2["2V5<br/>C89 10 uF X5R + C83-C88 100 nF<br/>10.6 uF ceramic"] ``

    QuantityValueSource
    Ceramic on 2V5 after L510.6 uF (C89 10 uF X5R plus six 100 nF)netlist
    Ceramic allowed before stability becomes marginalabout 3 uF, with a 100 uF tantalumLP3966 datasheet, p.10

    At 100 kHz the bead between C121 and the 2V5 ceramics is a low impedance, so those ceramics sit inside the loop. The 3V3 side is within the guidance (3.5 uF ceramic against 186 uF of tantalum).

    Why it matters

    The LP3966 relies on both the input impedance and the output-capacitor ESR zero for stability, and the datasheet states both as conditions for stable full-load operation. Remedy: a low-ESR 68-100 uF input capacitor per LP3966 (or add ceramic input capacitance to meet the ratio), and less ceramic on 2V5 or more tantalum at C121. Oscillation risk is load- and temperature-dependent, hence minor.

  15. observationOBS-158minorOpen

    SPI flash U14 (W25Q64) is fitted but unreachable: its only clock link R48 is not fitted, so CLK floats, and the FPGA constraints prohibit its pins

    SPI flash U14 (W25Q64) is fitted but unreachable: its only clock link R48 is not fitted, so CLK floats, and the FPGA constraints prohibit its pins.

    Where it is

    ``mermaid flowchart LR CCLK["CCLK<br/>FPGA_configuration"] --- R48["R48 0R<br/>Qty 0, not fitted"] --- CLK["U14 pin 6 CLK<br/>one-pad net"] CSO["U12 T3 CSO_B<br/>EEPROM_CS"] --> CS["U14 pin 1 /CS"] R47["R47 1k to 3V3"] --> CS ``

    • U14 W25Q64FVSSIG is fitted (design BOM Qty 1). Its CLK (pin 6) connects only to R48 0R, which leads to CCLK. R48 is marked Qty 0, so pin 6 is on a one-pad net.
    • The design configures from the XCF04S U15 in Master Serial mode (M[1:0] = 01, fpga/TimIQ/TimIQ_EEPROM/TimIQ_XCF.mcs).
    • fpga/sources/top.ucf prohibits the balls that reach U14 (T10 IO0, N12 IO2, P12 IO3) and CCLK R11.
    • /CS is held high by R47 1k, so U14 sits in standby with a floating CLK input. In this build nothing can clock it.

    Why it matters

    Either the flash is an alternative configuration source that was deliberately left unclocked, in which case U14 is a fitted part with no function, or R48 should be fitted for SPI configuration or user storage. Both the BOM line and the floating CMOS input should be settled: mark U14 DNP with R48, or fit R48. Impact is cost and an undriven input on a part held in standby, hence minor.

  16. observationOBS-159minorOpen

    No fiducials on either side, although the board carries a 1 mm-pitch BGA and 0.5 mm-pitch QFN, TSSOP and QSH parts on both sides

    No fiducials on either side, although the board carries a 1 mm-pitch BGA and 0.5 mm-pitch QFN, TSSOP and QSH parts on both sides.

    pcb/CPU/TimIQ_CPU.kicad_pcb has 341 footprints and none is a fiducial. The only non-electrical footprints are FIX1-FIX6 (3 mm holes), TP1-TP8 test pads and three logos, and no bare copper fiducial is drawn on L1_TOP or L8_BOTTOM.

    Fine-pitch parts

    PartPackagePitchSide
    U12 XC6SLX16FTG256 BGA1.0 mmtop
    U20TSSOP380.5 mmtop
    U21 LAN881072-QFN0.5 mmbottom
    U16-U18 SN75LVDS389/LVDT388ATSSOP380.5 mmbottom
    J11 Samtec QSH-0400.5 mmbottom

    Why it matters

    Pick-and-place vision aligns each side to global fiducials, and 0.5 mm-pitch and BGA parts are usually given local fiducials as well. Without them the assembler must align on pads or add panel-rail fiducials, which is less accurate for this board's densest parts. Add three global fiducials per side, and local ones at U12 and U21.

  17. observationOBS-160minorOpen

    Silkscreen: J11 and SW1 designators sit under their own bodies, and the BeagleBone outline drawn by J8/J9 crosses the J12 shield pads and the FIX3 pad

    J11 and SW1 have their designators under their own bodies, and the BeagleBone outline drawn by J8/J9 crosses the J12 shield pads and the FIX3 pad.

    Measured from pcb/CPU/TimIQ_CPU.kicad_pcb. All 338 visible designators are 1.0 mm tall with a 0.15 mm stroke, and none overlaps another.

    The problems

    • Designators under the part. The reference texts of J11 (QSH-040 board-to-board, bottom) and SW1 (A6S-6104 DIP switch, top) are centred inside their own pad field, so the fitted part covers them.
    • Silk over copper. The J8 and J9 footprints (SOLEIL-BeagleBoneBlack-P8/P9, both at the same origin 128.314, 72.04) each draw the full BeagleBone Black outline on F.SilkS. That outline runs across:
    • plated shield pads 15 and 16 of J12 (HFJ11 RJ45, GND);
    • the FIX3 mounting-hole pad (GND).

    Why it matters

    Designators under a body cannot be read after assembly, which slows inspection and rework of the board-to-board connector and the configuration switch. Silk over exposed copper is clipped by the fabricator or prints on the pad and can mar the joint; drawing the outline twice also doubles it. Move the J11 and SW1 designators outside their bodies, keep the BeagleBone outline in one footprint, and clip it clear of J12 and FIX3. Cosmetic and assembly-only, hence minor.

  18. observationOBS-161minorOpen

    Supervisor trip points for 3V3 and 1V2 are set by resistor dividers on the LTC2908 ADJ inputs but not annotated; computed they are about 3.06 V and 1.12 V

    The U22 LTC2908 trip points for 3V3 and 1V2 are set by resistor dividers on its ADJ inputs but not annotated on the sheet; computed they are about 3.06 V and 1.12 V.

    The numbers

    Sheet 4 'Reset & power monitor' gives no threshold for either input.

    QuantityValueSource
    ADJ threshold0.5 V nominalLTC2908 datasheet, p.1
    VADJ2 (pin 5) divider from 3V3R124 511k / R125 100k to GNDschematic sheet 4
    3V3 trip point0.5 x 611/100 = 3.06 V (-7.4 % of 3.3 V)derived
    VADJ1 (pin 7) divider from 1V2R126 124k / R127 100k to GNDschematic sheet 4
    1V2 trip point0.5 x 224/100 = 1.12 V (-6.7 % of 1.2 V)derived

    The other inputs:

    • V1 = 5V, V2 = 3V3 and V3 = 2V5 use the A1 option's fixed thresholds.
    • V4 (the fixed 1.8 V input) is tied to 2V5.

    Why it matters

    The reset thresholds decide when the FPGA is held in reset, so a reviewer needs them, and the 3V3 rail is watched twice at different levels (V2 fixed and VADJ2). Annotate both trip points and their tolerance on the sheet, and note that V4 is deliberately shorted to 2V5 (LTC2908 p.1 allows inputs to be shorted when fewer than six supplies are monitored). Documentation only.

  19. observationOBS-516minorOpen

    TTL input buffers U3-U6 are fitted with floating inputs: their only input links R7-R10 are not fitted

    U3-U6 (SN74LVC1G17 Schmitt buffers, inTTL1-4 to the FPGA) are fitted, but the 0 R links R7-R10 that connect their inputs to the TTL_IO1-4 connectors are not, so each buffer input (pin 2) floats; TI requires unused inputs to be held at VCC or GND.

    What is fitted

    ItemValueSource
    U3-U6SN74LVC1G17, fitteddesign BOM timiq-cpu-bom.csv
    R6-R10, C10-C130R, order Qty 0 (not fitted)design BOM row "C10-C13,R6-R10"
    Net-(R7-Pad1)only R7.1 and U3.2 (likewise R8/U4, R9/U5, R10/U6)netlist
    Unused-input rule"All unused inputs of the device must be held at VCC or GND"SN74LVC1G17 datasheet c76fa723 p.5, note (1)

    Why it matters

    With the TTL ports built as outputs (R7-R10 open), the four input buffers stay powered from 3V3 with an open CMOS input. The Schmitt input limits oscillation, but the input level, and so inTTL1-4 seen by the FPGA, is undefined and the buffer can draw shoot-through current. A pull-down on each buffer input (or leaving U3-U6 unfitted in the output build) would define it. Only a concern if the gateware reads inTTL1-4 in this build.

    ``mermaid flowchart LR J[TTL_IO1 connector] -- R7 0R not fitted --x B[U3 pin 2 input, floating] B --> F[U12 FPGA inTTL1] ``

  20. ReferencePlaneDiscontinuityminorOpen

    16 nets change reference between 1V2 and 3V3 at 18 vias, none with a reference that continues across (fastest: /TOP/FPGA_configuration//PROG_B_FPGA at 100 ps 10-90 %, ASSUMED)

    At 18 via(s), on 16 net(s), the signal leaves a layer referenced by one of 1V2 and 3V3 for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 18 served. Every site is served, so the finding is the lower tier (info). 18 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether 1V2 and 3V3 are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

    • 'Net-(R64-Pad2)' at (172.36, -159.76), L4_DIGITAL -> L8_BOTTOM: GND on L3_DIGITAL, 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 10.4 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • '/TOP/Ethernet_PHY/PHY_TXD4' at (189.46, -166.44), L4_DIGITAL -> L8_BOTTOM: GND on L3_DIGITAL, 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 8.1 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • '/TOP/Ethernet_PHY/PHY_TXD4' at (190.59, -98.79), L4_DIGITAL -> L8_BOTTOM: GND on L3_DIGITAL, 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 8.1 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • 'Net-(R55-Pad2)' at (176.59, -143.39), L4_DIGITAL -> L8_BOTTOM: GND on L3_DIGITAL, 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 7.9 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • '/TOP/Ethernet_PHY/PHY_TXD0' at (188.43, -101.79), L4_DIGITAL -> L8_BOTTOM: GND on L3_DIGITAL, 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 7.4 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • '/TOP/Ethernet_PHY/PHY_TXD0' at (188.46, -162.53), L4_DIGITAL -> L8_BOTTOM: 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 7.4 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • '/TOP/FPGA_configuration/EEPROM_IO3' at (189.47, -133.12), L4_DIGITAL -> L8_BOTTOM: 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 7.3 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (2 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • '/TOP/Ethernet_PHY/PHY_TXD3' at (194.43, -99.5), L4_DIGITAL -> L8_BOTTOM: GND on L3_DIGITAL, 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 7.2 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • '/TOP/Ethernet_PHY/PHY_RXER' at (194.45, -93.79), L4_DIGITAL -> L8_BOTTOM: GND on L3_DIGITAL, 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 7.1 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • '/TOP/FPGA_configuration/EEPROM_IO0' at (186.21, -134.51), L4_DIGITAL -> L8_BOTTOM: 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 6.6 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (2 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • 'Net-(R62-Pad2)' at (171.34, -159.29), L4_DIGITAL -> L8_BOTTOM: GND on L3_DIGITAL, 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 5.4 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • '/TOP/FPGA_configuration/EEPROM_CS' at (196.56, -142.18), L4_DIGITAL -> L8_BOTTOM: GND on L3_DIGITAL, 1V2 on L5_PSU to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 4.0 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (2 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 1V2 on L5_PSU is 0.130 mm from GND on L4_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
    • and 6 more

    Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=refchange%3A1V2%7C3V3 serves each with its own layer_image region; all of them lie in x 169.34..204.12, y -173.75..-89.81 mm (board frame, Y up).

    The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    At refchange:1V2|3V3

  21. DecapViaFanoutminorOpen

    DecapViaFanout: 4 components×4

    Checked by the review, stands · Claude walker W1 (Cern session) — Checked: fan-out lengths read from the copper stand (23 capacitors); the 0.5 nH limit is Probe's starting value, not a Spartan-6 or LP39xx requirement, and no PDN target is stated. Left for the owner.

    At C116, C32, C58, C85

    Each finding, with its own headline
    • C116C116 on '5V': its rail pad reaches its via over 2.10 mm of track, adding about 0.56 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value)

      C116 on '5V': its rail pad reaches its via over 2.10 mm of track, adding about 0.56 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value). C116.1 (rail) runs 2.10 mm along its copper to its nearest via, 1.10 mm past the 1 mm beside the pad: 0.56 nH; C116.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.59 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.56 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.00 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.65 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C32C32 on '3V3': its rail pad reaches its via over 1.86 mm of track, adding about 0.52 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value)

      C32 on '3V3': its rail pad reaches its via over 1.86 mm of track, adding about 0.52 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value). C32.1 (rail) runs 1.86 mm along its copper to its nearest via, 0.86 mm past the 1 mm beside the pad: 0.52 nH; C32.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.52 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.47 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.78 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C58C58 on '3V3': its rail pad reaches its via over 1.85 mm of track, adding about 0.51 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value)

      C58 on '3V3': its rail pad reaches its via over 1.85 mm of track, adding about 0.51 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value). C58.1 (rail) runs 1.85 mm along its copper to its nearest via, 0.85 mm past the 1 mm beside the pad: 0.51 nH; C58.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 2.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.51 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.47 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.78 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C85C85 on '2V5': its rail pad reaches its via over 2.07 mm of track, adding about 0.54 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value)

      C85 on '2V5': its rail pad reaches its via over 2.07 mm of track, adding about 0.54 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value). C85.1 (rail) runs 2.07 mm along its copper to its nearest via, 1.07 mm past the 1 mm beside the pad: 0.54 nH; C85.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.58 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.54 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.84 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.39 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

  22. ReferencePlaneDiscontinuityminorOpen

    ReferencePlaneDiscontinuity: 55 boards×55

    Checked by the review, stands · Claude walker W1 (Cern session) — Checked: splits, voids and reference changes read from the copper stand as reported (166 sites over the FPGA, PHY and BeagleBone nets). They are layout-practice findings with Probe's default limits; no datasheet or app note on file sets one for these nets. Not refutable with a citation; left for the owner.

    At refchange:2V5|3V3, refchange:2V5|5V, void:1V2@L5_PSU:180.51,-182.55, void:1V2@L5_PSU:181.96,-134.2, void:1V2@L5_PSU:182.73,-98.06, void:1V2@L5_PSU:183.09,-98.86 and 49 more

    Each finding, with its own headline
    • refchange:2V5|3V32 nets change reference between 2V5 and 3V3 at 2 vias, none with a reference that continues across (fastest: /TOP/Ethernet_PHY/ACT_LED at 1 ns 10-90 %, suggested by its name)

      At 2 via(s), on 2 net(s), the signal leaves a layer referenced by one of 2V5 and 3V3 for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 2 served. Every site is served, so the finding is the lower tier (info). 2 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether 2V5 and 3V3 are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

      • '/TOP/Ethernet_PHY/ACT_LED' at (173.57, -85.17), L3_DIGITAL -> L6_DIGITAL: GND on L2_GND, 2V5 on L4_DIGITAL to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching served, 63.0 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 2V5 on L4_DIGITAL is 0.130 mm from GND on L3_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.
      • '/TOP/Ethernet_PHY/PHY_TXD2' at (188.95, -100.79), L3_DIGITAL -> L8_BOTTOM: GND on L2_GND, 2V5 on L4_DIGITAL to 3V3 on L7_PSU; pure, no reference continues across; stitching served, 1.6 mm of track past the via on L8_BOTTOM: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 2V5 on L4_DIGITAL is 0.130 mm from GND on L3_DIGITAL and 3V3 on L7_PSU 0.130 mm from GND on L6_DIGITAL: their own capacitance carries the return. Served.

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=refchange%3A2V5%7C3V3 serves each with its own layer_image region; all of them lie in x 171.57..190.95, y -102.79..-83.17 mm (board frame, Y up).

      The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • refchange:2V5|5V'/TOP/Ethernet_PHY/ACT_LED' changes reference between 2V5 and 5V at a via, none with a reference that continues across (fastest: /TOP/Ethernet_PHY/ACT_LED at 1 ns 10-90 %, suggested by its name)

      At 1 via(s), on 1 net(s), the signal leaves a layer referenced by one of 2V5 and 5V for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 1 served. Every site is served, so the finding is the lower tier (info). 1 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether 2V5 and 5V are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

      • '/TOP/Ethernet_PHY/ACT_LED' at (173.57, -85.17), L3_DIGITAL -> L6_DIGITAL: GND on L2_GND, 2V5 on L4_DIGITAL to 5V on L5_PSU, 3V3 on L7_PSU; pure, no reference continues across; stitching served, 63.0 mm of track past the via on L6_DIGITAL: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 2V5 on L4_DIGITAL and 5V on L5_PSU are adjacent, 0.130 mm apart: their own capacitance carries the return. Served.

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=refchange%3A2V5%7C5V serves each with its own layer_image region; all of them lie in x 171.57..175.57, y -87.17..-83.17 mm (board frame, Y up).

      The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:180.51,-182.55'/TOP/Digital_interface/PLL_END' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.36 mm; 1 cleared on both sides of the track (fastest: /TOP/Digital_interface/PLL_END at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/PLL_END' on L6_DIGITAL, the 1V2 plane on L5_PSU has 1.36 mm under the track with no copper, at (180.51, -182.55), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Digital_interface/PLL_END' on L6_DIGITAL at (180.51, -182.55), 1.36 mm over no copper; other side: no plane on L7_PSU / '/TOP/Digital_interface/PLL_END' on L6_DIGITAL at (180.51, -182.55), 1.36 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A180.51%2C-182.55 serves each with its own layer_image region; all of them lie in x 179.51..181.51, y -184.23..-180.87 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:181.96,-134.2'/TOP/Ethernet_PHY/PHY_RXD7' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 0.78 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD7 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL, the 1V2 plane on L5_PSU has 0.78 mm under the track with no copper, at (181.96, -134.2), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 50% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL at (181.96, -134.2), 0.78 mm over no copper; other side: GND on L3_DIGITAL, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A181.96%2C-134.2 serves each with its own layer_image region; all of them lie in x 180.96..182.96, y -135.59..-132.81 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:182.73,-98.06'/TOP/Ethernet_PHY/PHY_RXD7' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 1.21 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD7 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL, the 1V2 plane on L5_PSU has 1.21 mm under the track with no copper, at (182.73, -98.06), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 50% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL at (182.73, -98.06), 1.21 mm over no copper; other side: GND on L3_DIGITAL, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A182.73%2C-98.06 serves each with its own layer_image region; all of them lie in x 181.73..183.73, y -99.66..-96.45 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:183.09,-98.86'/TOP/Ethernet_PHY/PHY_TXD7' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 1.18 mm (fastest: /TOP/Ethernet_PHY/PHY_TXD7 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_TXD7' on L4_DIGITAL, the 1V2 plane on L5_PSU has 1.18 mm under the track with no copper, at (183.09, -98.86), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 50% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • '/TOP/Ethernet_PHY/PHY_TXD7' on L4_DIGITAL at (183.09, -98.86), 1.18 mm over no copper; other side: GND on L3_DIGITAL, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A183.09%2C-98.86 serves each with its own layer_image region; all of them lie in x 182.09..184.09, y -100.46..-97.27 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:185.96,-169.94'/TOP/FPGA_configuration/EEPROM_IO0' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 10.22 mm (fastest: /TOP/FPGA_configuration/EEPROM_IO0 at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/FPGA_configuration/EEPROM_IO0' on L4_DIGITAL, the 1V2 plane on L5_PSU has 10.22 mm under the track with no copper, at (185.96, -169.94), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.9 mm). No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/FPGA_configuration/EEPROM_IO0' on L4_DIGITAL at (185.96, -169.94), 10.22 mm, running ALONG the bare copper for 0.9 mm, not across it over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A185.96%2C-169.94 serves each with its own layer_image region; all of them lie in x 184.96..186.96, y -176.05..-163.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:187.96,-191.2'/TOP/Digital_interface/SPARE7' crosses where the outline of the 1V2 plane on L5_PSU and the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.02 mm; 1 cleared on both sides of the track (fastest: /TOP/Digital_interface/SPARE7 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE7' on L6_DIGITAL, the 3V3 plane on L7_PSU has 1.02 mm under the track with no copper, at (187.96, -191.2), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Digital_interface/SPARE7' on L6_DIGITAL at (187.96, -191.2), 1.02 mm over no copper; other side: no plane on L7_PSU / '/TOP/Digital_interface/SPARE7' on L6_DIGITAL at (187.96, -191.2), 1.02 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A187.96%2C-191.2 serves each with its own layer_image region; all of them lie in x 186.96..188.96, y -192.72..-189.69 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:192.85,-184.33'/TOP/FPGA_configuration/EEPROM_CS' crosses where the GND plane on L3_DIGITAL and the 1V2 plane on L5_PSU is drawn back round copper of /TOP/Digital_interface/SPARE3, at 1 place, the longest 1.68 mm; 1 cleared on both sides of the track (fastest: /TOP/FPGA_configuration/EEPROM_CS at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/FPGA_configuration/EEPROM_CS' on L4_DIGITAL, the GND plane on L3_DIGITAL has 1.68 mm under the track with copper of /TOP/Digital_interface/SPARE3, not a plane, at (192.78, -184.33), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/FPGA_configuration/EEPROM_CS' on L4_DIGITAL at (192.78, -184.33), 1.68 mm over copper of /TOP/Digital_interface/SPARE3, not a plane; other side: no plane on L5_PSU / '/TOP/FPGA_configuration/EEPROM_CS' on L4_DIGITAL at (192.85, -184.33), 1.17 mm over no copper; other side: no plane on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A192.85%2C-184.33 serves each with its own layer_image region; all of them lie in x 191.27..194.95, y -185.33..-183.33 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:193.25,-159.87'/TOP/Ethernet_PHY/PHY_INT' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 0.97 mm (fastest: /TOP/Ethernet_PHY/PHY_INT at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL, the 1V2 plane on L5_PSU has 0.97 mm under the track with no copper, at (193.25, -159.87), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 50% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL at (193.25, -159.87), 0.97 mm over no copper; other side: 3V3 on L7_PSU, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A193.25%2C-159.87 serves each with its own layer_image region; all of them lie in x 192.25..194.25, y -161.36..-158.38 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:1V2@L5_PSU:193.25,-162.66'/TOP/Ethernet_PHY/PHY_INT' crosses where the outline of the 1V2 plane on L5_PSU is drawn back, at 1 place, the longest 1.09 mm (fastest: /TOP/Ethernet_PHY/PHY_INT at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL, the 1V2 plane on L5_PSU has 1.09 mm under the track with no copper, at (193.25, -162.66), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 160.21..239.71, y -222.44..-86.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 50% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • '/TOP/Ethernet_PHY/PHY_INT' on L6_DIGITAL at (193.25, -162.66), 1.09 mm over no copper; other side: 3V3 on L7_PSU, 0.13 mm from the track against 0.13 mm to L5_PSU: 50% of the return on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A1V2%40L5_PSU%3A193.25%2C-162.66 serves each with its own layer_image region; all of them lie in x 192.25..194.25, y -164.2..-161.12 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:174.11,-187.32'/TOP/Digital_interface/SPARE1' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.46 mm (fastest: /TOP/Digital_interface/SPARE1 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE1' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.46 mm under the track with no copper, at (174.11, -187.32), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/SPARE1' on L8_BOTTOM at (174.11, -187.32), 1.46 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A174.11%2C-187.32 serves each with its own layer_image region; all of them lie in x 172.76..175.11, y -189.2..-185.88 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:174.42,-187.59'/TOP/Digital_interface/SPARE2' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.27 mm (fastest: /TOP/Digital_interface/SPARE2 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE2' on L8_BOTTOM, the 3V3 plane on L7_PSU has 0.27 mm under the track with no copper, at (174.42, -187.59), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/SPARE2' on L8_BOTTOM at (174.42, -187.59), 0.27 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A174.42%2C-187.59 serves each with its own layer_image region; all of them lie in x 173.42..175.42, y -188.72..-186.45 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:176.96,-178.46'/TOP/Digital_interface/PLL_ENA' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.28 mm (fastest: /TOP/Digital_interface/PLL_ENA at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/PLL_ENA' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.28 mm under the track with no copper, at (176.96, -178.46), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/PLL_ENA' on L8_BOTTOM at (176.96, -178.46), 1.28 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A176.96%2C-178.46 serves each with its own layer_image region; all of them lie in x 175.96..177.96, y -180.1..-176.82 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:176.96,-180.95'/TOP/Digital_interface/PLL_ENA' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.24 mm (fastest: /TOP/Digital_interface/PLL_ENA at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/PLL_ENA' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.24 mm under the track with no copper, at (176.96, -180.95), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/PLL_ENA' on L8_BOTTOM at (176.96, -180.95), 2.24 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A176.96%2C-180.95 serves each with its own layer_image region; all of them lie in x 175.96..177.96, y -183.07..-178.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:177.96,-180.84'/TOP/Digital_interface/PLL_ENB' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.53 mm (fastest: /TOP/Digital_interface/PLL_ENB at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/PLL_ENB' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.53 mm under the track with no copper, at (177.96, -180.84), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/PLL_ENB' on L8_BOTTOM at (177.96, -180.84), 2.53 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A177.96%2C-180.84 serves each with its own layer_image region; all of them lie in x 176.64..178.96, y -183.2..-178.81 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:178.56,-177.94'/TOP/Digital_interface/PLL_ENB' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 2.44 mm (fastest: /TOP/Digital_interface/PLL_ENB at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/PLL_ENB' on L8_BOTTOM, the 3V3 plane on L7_PSU has 2.44 mm under the track with copper of 3V3, not a plane, at (178.56, -177.94), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.02 mm). No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/PLL_ENB' on L8_BOTTOM at (178.56, -177.94), 2.44 mm, running ALONG the bare copper for 1.02 mm, not across it over copper of 3V3, not a plane, to the end of the track; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A178.56%2C-177.94 serves each with its own layer_image region; all of them lie in x 176.96..180.46, y -180.07..-176.94 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:186.96,-180.44'/TOP/Digital_interface/SPARE6' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.22 mm (fastest: /TOP/Digital_interface/SPARE6 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE6' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.22 mm under the track with no copper, at (186.96, -180.44), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/SPARE6' on L8_BOTTOM at (186.96, -180.44), 1.22 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A186.96%2C-180.44 serves each with its own layer_image region; all of them lie in x 185.96..187.96, y -182.05..-178.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:187.46,-183.36'/TOP/Digital_interface//DAC_CS' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.84 mm (fastest: /TOP/Digital_interface//DAC_CS at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface//DAC_CS' on L8_BOTTOM, the 3V3 plane on L7_PSU has 0.84 mm under the track with no copper, at (187.46, -183.36), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface//DAC_CS' on L8_BOTTOM at (187.46, -183.36), 0.84 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A187.46%2C-183.36 serves each with its own layer_image region; all of them lie in x 186.46..188.62, y -184.67..-181.89 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:191.12,-103.43'/TOP/Ethernet_PHY/PHY_RXCLK' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.47 mm (fastest: /TOP/Ethernet_PHY/PHY_RXCLK at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXCLK' on L6_DIGITAL, the 3V3 plane on L7_PSU has 0.47 mm under the track with no copper, at (191.12, -103.43), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 50% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • '/TOP/Ethernet_PHY/PHY_RXCLK' on L6_DIGITAL at (191.12, -103.43), 0.47 mm over no copper; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L7_PSU: 50% of the return on L7_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A191.12%2C-103.43 serves each with its own layer_image region; all of them lie in x 190.12..192.12, y -104.67..-102.19 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:191.28,-181.5'/TOP/Digital_interface//ADC_CS' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 0.66 mm (fastest: /TOP/Digital_interface//ADC_CS at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface//ADC_CS' on L8_BOTTOM, the 3V3 plane on L7_PSU has 0.66 mm under the track with no copper, at (191.28, -181.5), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface//ADC_CS' on L8_BOTTOM at (191.28, -181.5), 0.66 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A191.28%2C-181.5 serves each with its own layer_image region; all of them lie in x 189.95..192.61, y -182.5..-180.5 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:3V3@L7_PSU:192.77,-182.5'/TOP/Digital_interface//ADC_CS' crosses where the outline of the 3V3 plane on L7_PSU is drawn back, at 1 place, the longest 1.93 mm (fastest: /TOP/Digital_interface//ADC_CS at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface//ADC_CS' on L8_BOTTOM, the 3V3 plane on L7_PSU has 1.93 mm under the track with no copper, at (192.77, -182.5), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 110.21..268.21, y -222.44..-64.44 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface//ADC_CS' on L8_BOTTOM at (192.77, -182.5), 1.93 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3A3V3%40L7_PSU%3A192.77%2C-182.5 serves each with its own layer_image region; all of them lie in x 191.17..194.36, y -184.34..-180.9 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:142.29,-121.57'/TOP/Reset//BBB_RST' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 3.46 mm; 1 cleared on both sides of the track (fastest: /TOP/Reset//BBB_RST at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Reset//BBB_RST' on L3_DIGITAL, the GND plane on L2_GND has 3.46 mm under the track with no copper, at (142.29, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/Reset//BBB_RST' on L3_DIGITAL at (142.29, -121.57), 3.46 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/Reset//BBB_RST' on L3_DIGITAL at (142.29, -121.57), 3.46 mm over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A142.29%2C-121.57 serves each with its own layer_image region; all of them lie in x 141.29..143.29, y -124.3..-118.84 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:147.23,-121.57'/TOP/BeagleBone_connectors/BBB_I2C1_SDA' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 3.68 mm; 1 cleared on both sides of the track (fastest: /TOP/BeagleBone_connectors/BBB_I2C1_SDA at 10 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_I2C1_SDA' on L3_DIGITAL, the GND plane on L2_GND has 3.68 mm under the track with no copper, at (147.23, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.03 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/BeagleBone_connectors/BBB_I2C1_SDA' on L3_DIGITAL at (147.23, -121.57), 3.68 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_I2C1_SDA' on L3_DIGITAL at (147.23, -121.57), 3.68 mm, running ALONG the bare copper for 1.03 mm, not across it over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A147.23%2C-121.57 serves each with its own layer_image region; all of them lie in x 146.23..148.23, y -124.41..-118.73 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:147.53,-121.57'/TOP/BeagleBone_connectors/BBB_I2C1_SCL' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 3.8 mm; 1 cleared on both sides of the track (fastest: /TOP/BeagleBone_connectors/BBB_I2C1_SCL at 10 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_I2C1_SCL' on L3_DIGITAL, the GND plane on L2_GND has 3.8 mm under the track with no copper, at (147.53, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.16 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/BeagleBone_connectors/BBB_I2C1_SCL' on L3_DIGITAL at (147.53, -121.57), 3.8 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_I2C1_SCL' on L3_DIGITAL at (147.53, -121.57), 3.8 mm, running ALONG the bare copper for 1.16 mm, not across it over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A147.53%2C-121.57 serves each with its own layer_image region; all of them lie in x 146.53..148.53, y -124.47..-118.67 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:149.73,-121.57'/TOP/BeagleBone_connectors/BBB_I2C2_SDA' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 3.84 mm; 1 cleared on both sides of the track (fastest: /TOP/BeagleBone_connectors/BBB_I2C2_SDA at 10 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_I2C2_SDA' on L3_DIGITAL, the GND plane on L2_GND has 3.84 mm under the track with no copper, at (149.73, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.18 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/BeagleBone_connectors/BBB_I2C2_SDA' on L3_DIGITAL at (149.73, -121.57), 3.84 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_I2C2_SDA' on L3_DIGITAL at (149.73, -121.57), 3.84 mm, running ALONG the bare copper for 1.18 mm, not across it over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A149.73%2C-121.57 serves each with its own layer_image region; all of them lie in x 148.73..150.73, y -124.49..-118.65 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:150.07,-121.57'/TOP/BeagleBone_connectors/BBB_I2C2_SCL' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 3.8 mm; 1 cleared on both sides of the track (fastest: /TOP/BeagleBone_connectors/BBB_I2C2_SCL at 10 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_I2C2_SCL' on L3_DIGITAL, the GND plane on L2_GND has 3.8 mm under the track with no copper, at (150.07, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.16 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/BeagleBone_connectors/BBB_I2C2_SCL' on L3_DIGITAL at (150.07, -121.57), 3.8 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_I2C2_SCL' on L3_DIGITAL at (150.07, -121.57), 3.8 mm, running ALONG the bare copper for 1.16 mm, not across it over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A150.07%2C-121.57 serves each with its own layer_image region; all of them lie in x 149.07..151.07, y -124.47..-118.67 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:151.59,-79.24'/TOP/BeagleBone_connectors/BBB_I2C2_SCL' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 1.02 mm; 1 cleared on both sides of the track (fastest: /TOP/BeagleBone_connectors/BBB_I2C2_SCL at 10 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_I2C2_SCL' on L3_DIGITAL, the GND plane on L2_GND has 1.02 mm under the track with no copper, at (151.59, -79.24), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/BeagleBone_connectors/BBB_I2C2_SCL' on L3_DIGITAL at (151.59, -79.24), 1.02 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_I2C2_SCL' on L3_DIGITAL at (151.59, -79.24), 1.02 mm over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A151.59%2C-79.24 serves each with its own layer_image region; all of them lie in x 150.23..152.95, y -80.6..-77.88 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:154.81,-121.57'/TOP/BeagleBone_connectors/BBB_UART1_TxD' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 3.84 mm; 1 cleared on both sides of the track (fastest: /TOP/BeagleBone_connectors/BBB_UART1_TxD at 3 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_UART1_TxD' on L3_DIGITAL, the GND plane on L2_GND has 3.84 mm under the track with no copper, at (154.81, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.18 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/BeagleBone_connectors/BBB_UART1_TxD' on L3_DIGITAL at (154.81, -121.57), 3.84 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_UART1_TxD' on L3_DIGITAL at (154.81, -121.57), 3.84 mm, running ALONG the bare copper for 1.18 mm, not across it over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A154.81%2C-121.57 serves each with its own layer_image region; all of them lie in x 153.81..155.81, y -124.49..-118.65 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:155.15,-121.57'/TOP/BeagleBone_connectors/BBB_UART1_RxD' crosses where the outline of the GND plane on L2_GND and the GND plane on L4_DIGITAL is drawn back, at 1 place, the longest 3.8 mm; 1 cleared on both sides of the track (fastest: /TOP/BeagleBone_connectors/BBB_UART1_RxD at 3 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_UART1_RxD' on L3_DIGITAL, the GND plane on L2_GND has 3.8 mm under the track with no copper, at (155.15, -121.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.16 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 2 reference layers: '/TOP/BeagleBone_connectors/BBB_UART1_RxD' on L3_DIGITAL at (155.15, -121.57), 3.8 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_UART1_RxD' on L3_DIGITAL at (155.15, -121.57), 3.8 mm, running ALONG the bare copper for 1.16 mm, not across it over no copper; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A155.15%2C-121.57 serves each with its own layer_image region; all of them lie in x 154.15..156.15, y -124.47..-118.67 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:160.26,-121.57'/TOP/BeagleBone_connectors/BBB_SPI1_CS0' crosses where the GND plane on L2_GND and the 2V5 plane on L4_DIGITAL is drawn back round copper of /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), at 1 place, the longest 56.13 mm; 1 cleared on both sides of the track (fastest: /TOP/BeagleBone_connectors/BBB_SPI1_CS0 at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_SPI1_CS0' on L3_DIGITAL, the 2V5 plane on L4_DIGITAL has 56.13 mm under the track with copper of /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), not a plane, at (160.26, -131.64), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 23.21 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -182.44..-81.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 1 of the 3 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 3 reference layers: '/TOP/BeagleBone_connectors/BBB_SPI1_CS0' on L3_DIGITAL at (160.26, -121.57), 3.91 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_SPI1_CS0' on L3_DIGITAL at (169.13, -152.75), 0.92 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/BeagleBone_connectors/BBB_SPI1_CS0' on L3_DIGITAL at (160.26, -131.64), 56.13 mm, running ALONG the bare copper for 23.21 mm, not across it over copper of /TOP/Ethernet_PHY/PHY_RXD3, Net-(R55-Pad2), not a plane, to the end of the track; other side: GND on L2_GND, 0.13 mm from the track against 0.13 mm to L4_DIGITAL: 50% of the return on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A160.26%2C-121.57 serves each with its own layer_image region; all of them lie in x 159.26..181.46, y -168.44..-118.41 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:164.31,-80.01'/TOP/BeagleBone_connectors/BBB_SPI1_D0' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.99 mm (fastest: /TOP/BeagleBone_connectors/BBB_SPI1_D0 at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_SPI1_D0' on L3_DIGITAL, the GND plane on L2_GND has 0.99 mm under the track with no copper, at (164.31, -80.01), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/BeagleBone_connectors/BBB_SPI1_D0' on L3_DIGITAL at (164.31, -80.01), 0.99 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A164.31%2C-80.01 serves each with its own layer_image region; all of them lie in x 162.96..165.66, y -81.36..-78.66 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:174.91,-180.22'/TOP/Digital_interface/PLL_ENout' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.96 mm (fastest: /TOP/Digital_interface/PLL_ENout at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/PLL_ENout' on L1_TOP, the GND plane on L2_GND has 0.96 mm under the track with no copper, at (174.91, -180.22), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/PLL_ENout' on L1_TOP at (174.91, -180.22), 0.96 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A174.91%2C-180.22 serves each with its own layer_image region; all of them lie in x 173.62..176.21, y -181.64..-178.94 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:177.47,-182.2'/TOP/Digital_interface/FD0_N1' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.35 mm (fastest: /TOP/Digital_interface/FD0_N1 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/FD0_N1' on L1_TOP, the GND plane on L2_GND has 0.35 mm under the track with no copper, at (177.47, -182.2), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/FD0_N1' on L1_TOP at (177.47, -182.2), 0.35 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A177.47%2C-182.2 serves each with its own layer_image region; all of them lie in x 176.29..178.64, y -183.2..-181.2 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:177.96,-181.93'/TOP/Digital_interface/FD0_N1' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.73 mm (fastest: /TOP/Digital_interface/FD0_N1 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/FD0_N1' on L1_TOP, the GND plane on L2_GND has 0.73 mm under the track with no copper, at (177.96, -181.93), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/FD0_N1' on L1_TOP at (177.96, -181.93), 0.73 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A177.96%2C-181.93 serves each with its own layer_image region; all of them lie in x 176.71..179.22, y -183.18..-180.67 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:178.11,-165.09'/TOP/BeagleBone_connectors/BBB_UART1_TxD' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.43 mm (fastest: /TOP/BeagleBone_connectors/BBB_UART1_TxD at 3 ns 10-90 %, suggested by its name)

      Along '/TOP/BeagleBone_connectors/BBB_UART1_TxD' on L3_DIGITAL, the GND plane on L2_GND has 0.43 mm under the track with no copper, at (178.11, -165.09), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/BeagleBone_connectors/BBB_UART1_TxD' on L3_DIGITAL at (178.11, -165.09), 0.43 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A178.11%2C-165.09 serves each with its own layer_image region; all of them lie in x 177..179.22, y -166.2..-163.86 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:178.84,-176.82'/TOP/Digital_interface/SPARE2' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.67 mm (fastest: /TOP/Digital_interface/SPARE2 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE2' on L1_TOP, the GND plane on L2_GND has 0.67 mm under the track with no copper, at (178.84, -176.82), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/SPARE2' on L1_TOP at (178.84, -176.82), 0.67 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A178.84%2C-176.82 serves each with its own layer_image region; all of them lie in x 177.72..179.96, y -177.94..-175.7 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:180.21,-182.84'/TOP/Digital_interface/FD1_BYP' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.88 mm (fastest: /TOP/Digital_interface/FD1_BYP at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/FD1_BYP' on L1_TOP, the GND plane on L2_GND has 1.88 mm under the track with no copper, at (180.21, -182.84), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/FD1_BYP' on L1_TOP at (180.21, -182.84), 1.88 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A180.21%2C-182.84 serves each with its own layer_image region; all of them lie in x 179.21..181.21, y -184.78..-180.9 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:180.51,-182.55'/TOP/Digital_interface/FD1_N1' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.36 mm (fastest: /TOP/Digital_interface/FD1_N1 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/FD1_N1' on L1_TOP, the GND plane on L2_GND has 1.36 mm under the track with no copper, at (180.51, -182.55), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/FD1_N1' on L1_TOP at (180.51, -182.55), 1.36 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A180.51%2C-182.55 serves each with its own layer_image region; all of them lie in x 179.51..181.51, y -184.23..-180.87 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:182.23,-182.42'/TOP/Digital_interface/FD1_N0' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.63 mm (fastest: /TOP/Digital_interface/FD1_N0 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/FD1_N0' on L1_TOP, the GND plane on L2_GND has 1.63 mm under the track with no copper, at (182.23, -182.42), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/FD1_N0' on L1_TOP at (182.23, -182.42), 1.63 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A182.23%2C-182.42 serves each with its own layer_image region; all of them lie in x 180.46..183.67, y -183.42..-180.8 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:184.11,-198.02'/TOP/Digital_interface/FD1_N0' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.92 mm (fastest: /TOP/Digital_interface/FD1_N0 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/FD1_N0' on L1_TOP, the GND plane on L2_GND has 0.92 mm under the track with no copper, at (184.11, -198.02), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/FD1_N0' on L1_TOP at (184.11, -198.02), 0.92 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A184.11%2C-198.02 serves each with its own layer_image region; all of them lie in x 183.11..185.33, y -199.54..-196.72 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:185.35,-183.01'/TOP/Digital_interface/ADC_MISO' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.51 mm (fastest: /TOP/Digital_interface/ADC_MISO at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/ADC_MISO' on L1_TOP, the GND plane on L2_GND has 0.51 mm under the track with no copper, at (185.35, -183.01), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/ADC_MISO' on L1_TOP at (185.35, -183.01), 0.51 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A185.35%2C-183.01 serves each with its own layer_image region; all of them lie in x 184.23..186.48, y -184.29..-181.89 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:186.96,-165.83'/TOP/FPGA_configuration/TDI' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 2.54 mm (fastest: /TOP/FPGA_configuration/TDI at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/FPGA_configuration/TDI' on L3_DIGITAL, the GND plane on L2_GND has 2.54 mm under the track with copper of GND, not a plane, at (186.96, -165.83), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/FPGA_configuration/TDI' on L3_DIGITAL at (186.96, -165.83), 2.54 mm over copper of GND, not a plane, to the end of the track; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A186.96%2C-165.83 serves each with its own layer_image region; all of them lie in x 185.46..187.96, y -168.44..-163.83 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:186.99,-181.94'/TOP/Digital_interface/SPARE5' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.86 mm (fastest: /TOP/Digital_interface/SPARE5 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE5' on L3_DIGITAL, the GND plane on L2_GND has 0.86 mm under the track with no copper, at (186.99, -181.94), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/SPARE5' on L3_DIGITAL at (186.99, -181.94), 0.86 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A186.99%2C-181.94 serves each with its own layer_image region; all of them lie in x 185.49..188.25, y -182.94..-180.7 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:187.2,-182.11'/TOP/Digital_interface/PLL_LOCKED' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.82 mm (fastest: /TOP/Digital_interface/PLL_LOCKED at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/PLL_LOCKED' on L1_TOP, the GND plane on L2_GND has 0.82 mm under the track with no copper, at (187.2, -182.11), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/PLL_LOCKED' on L1_TOP at (187.2, -182.11), 0.82 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A187.2%2C-182.11 serves each with its own layer_image region; all of them lie in x 185.96..188.45, y -183.36..-180.74 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:188.47,-181.94'/TOP/Digital_interface/SPARE5' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.21 mm (fastest: /TOP/Digital_interface/SPARE5 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE5' on L3_DIGITAL, the GND plane on L2_GND has 1.21 mm under the track with no copper, at (188.47, -181.94), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/SPARE5' on L3_DIGITAL at (188.47, -181.94), 1.21 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A188.47%2C-181.94 serves each with its own layer_image region; all of them lie in x 186.86..190.07, y -182.94..-180.94 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:188.96,-179.86'/TOP/Digital_interface/SPARE3' crosses where the GND plane on L2_GND and the 2V5 plane on L4_DIGITAL is drawn back round copper of /TOP/FPGA_configuration/EEPROM_IO3, at 1 place, the longest 7.29 mm; 1 cleared on both sides of the track (fastest: /TOP/Digital_interface/SPARE3 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE3' on L3_DIGITAL, the 2V5 plane on L4_DIGITAL has 7.29 mm under the track with copper of /TOP/FPGA_configuration/EEPROM_IO3, not a plane, at (188.96, -179.38), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 2.17 mm). No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 and of the pour at x 160.21..239.71, y -182.44..-81.44 is drawn back there. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one stretch, cleared on 3 reference layers: '/TOP/Digital_interface/SPARE3' on L3_DIGITAL at (188.96, -179.86), 2.58 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/Digital_interface/SPARE3' on L3_DIGITAL at (191.28, -181.5), 0.65 mm over no copper; other side: no plane on L4_DIGITAL / '/TOP/Digital_interface/SPARE3' on L3_DIGITAL at (188.96, -179.38), 7.29 mm, running ALONG the bare copper for 2.17 mm, not across it over copper of /TOP/FPGA_configuration/EEPROM_IO3, not a plane, to the end of the track; other side: no plane on L2_GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A188.96%2C-179.86 serves each with its own layer_image region; all of them lie in x 187.46..192.61, y -182.5..-175.44 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:190.48,-219.42'/TOP/Digital_interface/ADC_ALARM' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.23 mm (fastest: /TOP/Digital_interface/ADC_ALARM at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/ADC_ALARM' on L1_TOP, the GND plane on L2_GND has 1.23 mm under the track with no copper, at (190.48, -219.42), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/ADC_ALARM' on L1_TOP at (190.48, -219.42), 1.23 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A190.48%2C-219.42 serves each with its own layer_image region; all of them lie in x 188.86..192.09, y -220.42..-218.42 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:190.97,-217.9'/TOP/Digital_interface/SPARE4' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.17 mm (fastest: /TOP/Digital_interface/SPARE4 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE4' on L1_TOP, the GND plane on L2_GND has 1.17 mm under the track with no copper, at (190.97, -217.9), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/SPARE4' on L1_TOP at (190.97, -217.9), 1.17 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A190.97%2C-217.9 serves each with its own layer_image region; all of them lie in x 189.39..192.56, y -218.9..-216.9 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:191.92,-167.59'/TOP/Reset//RST_FPGA' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 1.11 mm (fastest: /TOP/Reset//RST_FPGA at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Reset//RST_FPGA' on L1_TOP, the GND plane on L2_GND has 1.11 mm under the track with no copper, at (191.92, -167.59), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Reset//RST_FPGA' on L1_TOP at (191.92, -167.59), 1.11 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A191.92%2C-167.59 serves each with its own layer_image region; all of them lie in x 190.15..193.2, y -168.59..-166.43 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:193.36,-183.55'/TOP/Digital_interface/SPARE3' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 2.06 mm (fastest: /TOP/Digital_interface/SPARE3 at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/SPARE3' on L3_DIGITAL, the GND plane on L2_GND has 2.06 mm under the track with no copper, at (193.36, -183.55), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/SPARE3' on L3_DIGITAL at (193.36, -183.55), 2.06 mm over no copper; other side: no plane on L4_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A193.36%2C-183.55 serves each with its own layer_image region; all of them lie in x 192.13..194.36, y -185.41..-181.45 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2_GND:194.8,-182.58'/TOP/Digital_interface/DAC_ENA' crosses where the outline of the GND plane on L2_GND is drawn back, at 1 place, the longest 0.9 mm (fastest: /TOP/Digital_interface/DAC_ENA at 20 ns 10-90 %, suggested by its name)

      Along '/TOP/Digital_interface/DAC_ENA' on L1_TOP, the GND plane on L2_GND has 0.9 mm under the track with no copper, at (194.8, -182.58), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/Digital_interface/DAC_ENA' on L1_TOP at (194.8, -182.58), 0.9 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L2_GND%3A194.8%2C-182.58 serves each with its own layer_image region; all of them lie in x 193.6..195.8, y -183.89..-181.07 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L3_DIGITAL:178.88,-97.45'/TOP/Ethernet_PHY/PHY_RXD3' crosses where the outline of the GND plane on L3_DIGITAL is drawn back, at 1 place, the longest 1.33 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD3 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD3' on L4_DIGITAL, the GND plane on L3_DIGITAL has 1.33 mm under the track with no copper, at (178.88, -97.45), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 50% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • '/TOP/Ethernet_PHY/PHY_RXD3' on L4_DIGITAL at (178.88, -97.45), 1.33 mm over no copper; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L3_DIGITAL%3A178.88%2C-97.45 serves each with its own layer_image region; all of them lie in x 177.41..180.35, y -98.92..-95.98 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L3_DIGITAL:182.73,-114.88'/TOP/Ethernet_PHY/PHY_RXD7' crosses where the outline of the GND plane on L3_DIGITAL is drawn back, at 1 place, the longest 17.9 mm (fastest: /TOP/Ethernet_PHY/PHY_RXD7 at 1 ns 10-90 %, suggested by its name)

      Along '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL, the GND plane on L3_DIGITAL has 17.9 mm under the track with no copper, at (182.73, -114.88), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 16.85 mm). No hole cleared it: the outline of the pour at x 173.36..183.04, y -161.27..-123.3 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 50% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • '/TOP/Ethernet_PHY/PHY_RXD7' on L4_DIGITAL at (182.73, -114.88), 17.9 mm, running ALONG the bare copper for 16.85 mm, not across it over no copper; other side: 1V2 on L5_PSU, 0.13 mm from the track against 0.13 mm to L3_DIGITAL: 50% of the return on L3_DIGITAL

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L3_DIGITAL%3A182.73%2C-114.88 serves each with its own layer_image region; all of them lie in x 181.22..183.73, y -124.98..-105.29 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L3_DIGITAL:195.47,-182.95'/TOP/FPGA_configuration/EEPROM_CS' crosses where the outline of the GND plane on L3_DIGITAL is drawn back, at 1 place, the longest 1.87 mm (fastest: /TOP/FPGA_configuration/EEPROM_CS at 2 ns 10-90 %, suggested by its name)

      Along '/TOP/FPGA_configuration/EEPROM_CS' on L4_DIGITAL, the GND plane on L3_DIGITAL has 1.87 mm under the track with no copper, at (195.47, -182.95), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 109.71..268.71, y -222.94..-63.94 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/TOP/FPGA_configuration/EEPROM_CS' on L4_DIGITAL at (195.47, -182.95), 1.87 mm over no copper; other side: no plane on L5_PSU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/61/reference-planes?group=void%3AGND%40L3_DIGITAL%3A195.47%2C-182.95 serves each with its own layer_image region; all of them lie in x 193.81..197.13, y -184.61..-181.29 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

Main parts

Part numberMakerDescriptionWhere
1725669Phoenix ContactJ10
20021121-00010C4LFFCIJ6
39-30-1061MolexJ13
510ABA100M000AAGSilicon LabsU11
7B-25.000MEEQ-TTXCX1
87832-1420MolexJ7
A6S-6104-HOmronSW1
BSH103NXPQ3
HFJ11-1G01E-L12RLHalo ElectronicsJ12
KP-3216SGCKingbrightD1
KPC-3216SRC-PRVKingbrightD2
LAN8810I-AKZEMicrochip TechnologyU21
LG M67K-G1J2-24OsramD4
LP3883ES-1.2National SemiconductorU25
LP3966ES-2.5/NOPBTexas InstrumentsU24
LP3966ES-3.3National SemiconductorU23
LS M67K-H2L1-1OsramD3
LTC2908CTS8-A1Linear TechnologyU22
NFM41PC155B1H3LMurataL6
QSH-040-01-F-D-DP-ASamtecJ11
SN65HVD78DTIU19
SN75LVDT388ADBTTIU17
W25Q64FVSSIGWinbondU14
XC6SLX16-2FTG256CXilinxU12
XCF04SVOG20CXilinxU15
TSW-123-14-G-DSamtecJ8, J9
SN75LVDS389DBTTIU16, U18, U20
449.42.2522.201IMSJ1, J2, J3, J4, J5
SN74ABT541BDWTIU10, U2, U7, U8, U9
SN74LVC1G17DBVRG4TIU1, U3, U4, U5, U6
742792116Wuerth ElektronikL1, L2, L3, L4, L5, L7
D_3mm1FIX1, FIX2, FIX3, FIX4, FIX5, FIX6
BSN20NXPQ1, Q2, Q4, Q5, Q6, Q7, Q8
TEST-22MulticompTP1, TP2, TP3, TP4, TP5, TP6, TP7, TP8
C0603C102J5GACTUKEMETC111
CRCW06031M24FKEAVishayR97
CRCW0805180RFKEAVishayR32
CRCW08051K50FKEAVishayR142
CRCW0805220RFKEAVishayR38
CRCW0805511KFKEAVishayR124

About this design

Design
TIMIQ CPU — OHWR0060 R1
Designed in
KiCad EDA
Board
8 copper layers, 160 × 160 mm, 338 components, 456 nets
Licence
CERN-OHL-1.2
Source
https://gitlab.com/ohwr/project/timiq/timiq-hw at commit 2cd7bfd55267
Attribution
CERN Open Hardware Repository, project ohwr/project/timiq/timiq-hw (commit 2cd7bfd55267cfea6673e703eb4b873480e2dee8, 2025-04-10). Licence: CERN-OHL-1.2. Source: https://gitlab.com/ohwr/project/timiq/timiq-hw. This is a snapshot of the copy published on the OHWR GitLab pages (R1), not CERN's released record. CERN's source of truth is EDMS (https://edms.cern.ch), and the current release may be newer.
Reviewed with
Probe by E# (E-Sharp AB)