WREN IE
OHWR0092 · revision R4
WREN IE (OHWR0092 R4) is an open-hardware circuit board from its public repository, designed in KiCad EDA: a 10-layer board of 174 × 111.2 mm with 785 components and 952 nets, published under CERN-OHL-W-2.0.
review 93% walked · 13 findings: 1 blocker · 7 major · 5 minor (101 items)
Open in the interactive viewerRead the full review

Design review
Probe recorded 13 findings: 1 blocker · 7 major · 5 minor (101 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.
- PowerGroundShortblockerOpen
'GND' carries a power pin (IC36.32) and a ground pin (IC14.11)
Net 'GND' connects a power pin (IC36.32) and a ground pin (IC14.11).
At GND
- DecapOrdermajorOpen
DecapOrder: 2 findings (1 component, 1 pin)×2
2 checked by the review by Claude walker I1 (Cern session) — 2 different reasons
At IC19.A1, IC24
Each finding, with its own headline
IC19.A1IC19 supply pin A1 on 'P1V2': the smallest capacitor C266 sits 2.7 mm away, behind C278 at 1.1 mm
IC19 supply pin A1 on 'P1V2': the smallest capacitor C266 sits 2.7 mm away, behind C278 at 1.1 mm. IC19.A1: the smallest value, C266 (470 nF), is 2.7 mm from the pin and C278 (4.7 uF) 1.1 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. Swap them, or bring the smallest value to the pin: it serves the fastest current and is the one the loop inductance defeats. Distances are pad centre to pin centre in the board plane. The 5 mm radius, the 10x value step and the 1 mm / 1.5x tie tolerance are Probe's starting values.
IC24IC24 supply pins D1, F2 on 'P1V2': the smallest capacitor C84 sits 2.2 mm away, behind C294 at 1.2 mm
IC24 supply pins D1, F2 on 'P1V2': the smallest capacitor C84 sits 2.2 mm away, behind C294 at 1.2 mm. IC24.D1: the smallest value, C84 (470 nF), is 2.2 mm from the pin and C294 (4.7 uF) 1.2 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC24.F2: the smallest value, C84 (470 nF), is 3.7 mm from the pin and C294 (4.7 uF) 2.3 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. Swap them, or bring the smallest value to the pin: it serves the fastest current and is the one the loop inductance defeats. Distances are pad centre to pin centre in the board plane. The 5 mm radius, the 10x value step and the 1 mm / 1.5x tie tolerance are Probe's starting values.
- EsdProtectorPlacementmajorOpen
EsdProtectorPlacement: 31 components×31
Checked by the review, stands · Claude walker I1 (Cern session) — All 31 findings are on the PRTR5V0U4D clamps of J10 (board-to-board pp connector) lines D4/D8/D10-D16/D18: the clamps join each line 13-85 mm from J10 near the driver/pull-down end, after 2-3 vias, on stubs longer than the 1 mm default (no datasheet figure). The geometry stands as measured; whether board-to-board lines need port-style placement depends on the mating board (not in Probe). Practice, not a datasheet requirement.
At D10, D11, D12, D13, D14, D15 and 4 more
Each finding, with its own headline
D10D10.1 on '/io_drivers_pp/PP_OUT0': 3 via(s) between J10.32 and D10.1
D10 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT0' at J10.32. Along the copper: 27.43 mm of track from the contact, 3 via(s) before it, on a 6.14 mm branch off the line; the line runs 21.8 mm on to R195.2; D10 sits 12.95 mm farther from the contact than the nearest place outside J10.
3 via(s) between J10.32 and D10.1: the strike reaches an inner layer before it is clamped. D10.1 hangs 6.14 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D10 joins the line 21.29 mm from J10.32 on a 21.8 mm run to R195.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D10D10.6 on '/io_drivers_pp/PP_OUT3': 2 via(s) between J10.26 and D10.6
D10 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT3' at J10.26. Along the copper: 33.24 mm of track from the contact, 2 via(s) before it, on a 6.15 mm branch off the line; the line runs 27.59 mm on to R205.2; D10 sits 12.94 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.26 and D10.6: the strike reaches an inner layer before it is clamped. D10.6 hangs 6.15 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D10 joins the line 27.09 mm from J10.26 on a 27.59 mm run to R205.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D11D11.3 on '/io_drivers_pp/PP_OUT6': 2 via(s) between J10.27 and D11.3
D11 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT6' at J10.27. Along the copper: 32.23 mm of track from the contact, 2 via(s) before it, on a 3.93 mm branch off the line; the line runs 29.5 mm on to R219.2; D11 sits 22.74 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.27 and D11.3: the strike reaches an inner layer before it is clamped. D11.3 hangs 3.93 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D11 joins the line 28.3 mm from J10.27 on a 29.5 mm run to R219.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D11D11.4 on '/io_drivers_pp/PP_OUT7': 2 via(s) between J10.25 and D11.4
D11 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT7' at J10.25. Along the copper: 37.47 mm of track from the contact, 2 via(s) before it, on a 3.57 mm branch off the line; the line runs 34.4 mm on to R231.2; D11 sits 22.74 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.25 and D11.4: the strike reaches an inner layer before it is clamped. D11.4 hangs 3.57 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D11 joins the line 33.9 mm from J10.25 on a 34.4 mm run to R231.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D11D11.6 on '/io_drivers_pp/PP_OUT5': 2 via(s) between J10.29 and D11.6
D11 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT5' at J10.29. Along the copper: 36.35 mm of track from the contact, 2 via(s) before it, on a 10.35 mm branch off the line; the line runs 26.59 mm on to R211.2; D11 sits 22.74 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.29 and D11.6: the strike reaches an inner layer before it is clamped. D11.6 hangs 10.35 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D11 joins the line 26 mm from J10.29 on a 26.59 mm run to R211.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D12D12.1 on '/io_drivers_pp/PP_OUT8': 2 via(s) between J10.23 and D12.1
D12 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT8' at J10.23. Along the copper: 43.78 mm of track from the contact, 2 via(s) before it, on a 4.53 mm branch off the line; the line runs 39.84 mm on to R53.2; D12 sits 29.48 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.23 and D12.1: the strike reaches an inner layer before it is clamped. D12.1 hangs 4.53 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D12 joins the line 39.25 mm from J10.23 on a 39.84 mm run to R53.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D12D12.3 on '/io_drivers_pp/PP_OUT9': 2 via(s) between J10.24 and D12.3
D12 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT9' at J10.24. Along the copper: 55.38 mm of track from the contact, 2 via(s) before it, on a 3.62 mm branch off the line; the line runs 52.35 mm on to R52.2; D12 sits 31.71 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.24 and D12.3: the strike reaches an inner layer before it is clamped. D12.3 hangs 3.62 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D12 joins the line 51.76 mm from J10.24 on a 52.35 mm run to R52.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D12D12.4 on '/io_drivers_pp/PP_OUT10': 2 via(s) between J10.22 and D12.4
D12 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT10' at J10.22. Along the copper: 52.84 mm of track from the contact, 2 via(s) before it, on a 3.78 mm branch off the line; the line runs 49.72 mm on to R59.2; D12 sits 32.1 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.22 and D12.4: the strike reaches an inner layer before it is clamped. D12.4 hangs 3.78 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D12 joins the line 49.06 mm from J10.22 on a 49.72 mm run to R59.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D13D13.1 on '/io_drivers_pp/PP_OUT12': 2 via(s) between J10.18 and D13.1
D13 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT12' at J10.18. Along the copper: 59.96 mm of track from the contact, 2 via(s) before it, on a 4.49 mm branch off the line; the line runs 56.11 mm on to R79.2; D13 sits 41.47 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.18 and D13.1: the strike reaches an inner layer before it is clamped. D13.1 hangs 4.49 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D13 joins the line 55.47 mm from J10.18 on a 56.11 mm run to R79.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D13D13.3 on '/io_drivers_pp/PP_OUT14': 2 via(s) between J10.14 and D13.3
D13 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT14' at J10.14. Along the copper: 65.01 mm of track from the contact, 2 via(s) before it, on a 3.83 mm branch off the line; the line runs 61.73 mm on to R89.2; D13 sits 42.1 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.14 and D13.3: the strike reaches an inner layer before it is clamped. D13.3 hangs 3.83 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D13 joins the line 61.18 mm from J10.14 on a 61.73 mm run to R89.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D13D13.4 on '/io_drivers_pp/PP_OUT15': 2 via(s) between J10.12 and D13.4
D13 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT15' at J10.12. Along the copper: 72.03 mm of track from the contact, 2 via(s) before it, on a 5.26 mm branch off the line; the line runs 67.35 mm on to R100.2; D13 sits 42.43 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.12 and D13.4: the strike reaches an inner layer before it is clamped. D13.4 hangs 5.26 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D13 joins the line 66.77 mm from J10.12 on a 67.35 mm run to R100.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D13D13.6 on '/io_drivers_pp/PP_OUT13': 2 via(s) between J10.16 and D13.6
D13 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT13' at J10.16. Along the copper: 63.89 mm of track from the contact, 2 via(s) before it, on a 3.43 mm branch off the line; the line runs 61.06 mm on to R94.2; D13 sits 41.79 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.16 and D13.6: the strike reaches an inner layer before it is clamped. D13.6 hangs 3.43 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D13 joins the line 60.46 mm from J10.16 on a 61.06 mm run to R94.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D14D14.1 on '/io_drivers_pp/PP_OUT24': 2 via(s) between J10.15 and D14.1
D14 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT24' at J10.15. Along the copper: 45.36 mm of track from the contact, 2 via(s) before it, on a 8.35 mm branch off the line; the line runs 37.52 mm on to R228.2; D14 sits 36.04 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.15 and D14.1: the strike reaches an inner layer before it is clamped. D14.1 hangs 8.35 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D14 joins the line 37.01 mm from J10.15 on a 37.52 mm run to R228.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D14D14.3 on '/io_drivers_pp/PP_OUT25': 2 via(s) between J10.13 and D14.3
D14 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT25' at J10.13. Along the copper: 40.96 mm of track from the contact, 2 via(s) before it, on a 2.55 mm branch off the line; the line runs 38.91 mm on to R241.2; D14 sits 36.04 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.13 and D14.3: the strike reaches an inner layer before it is clamped. D14.3 hangs 2.55 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D14 joins the line 38.41 mm from J10.13 on a 38.91 mm run to R241.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D14D14.4 on '/io_drivers_pp/PP_OUT26': 2 via(s) between J10.11 and D14.4
D14 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT26' at J10.11. Along the copper: 43.87 mm of track from the contact, 2 via(s) before it, on a 4.06 mm branch off the line; the line runs 40.32 mm on to R238.2; D14 sits 36.05 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.11 and D14.4: the strike reaches an inner layer before it is clamped. D14.4 hangs 4.06 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D14 joins the line 39.81 mm from J10.11 on a 40.32 mm run to R238.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D14D14.6 on '/io_drivers_pp/PP_OUT27': 2 via(s) between J10.9 and D14.6
D14 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT27' at J10.9. Along the copper: 50.4 mm of track from the contact, 2 via(s) before it, on a 5.57 mm branch off the line; the line runs 45.33 mm on to R251.2; D14 sits 36.07 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.9 and D14.6: the strike reaches an inner layer before it is clamped. D14.6 hangs 5.57 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D14 joins the line 44.83 mm from J10.9 on a 45.33 mm run to R251.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D15D15.3 on '/io_drivers_pp/PP_OUT17': 2 via(s) between J10.8 and D15.3
D15 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT17' at J10.8. Along the copper: 80.76 mm of track from the contact, 2 via(s) before it, on a 7.08 mm branch off the line; the line runs 74.23 mm on to R111.2; D15 sits 50.53 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.8 and D15.3: the strike reaches an inner layer before it is clamped. D15.3 hangs 7.08 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D15 joins the line 73.68 mm from J10.8 on a 74.23 mm run to R111.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D15D15.4 on '/io_drivers_pp/PP_OUT18': 2 via(s) between J10.6 and D15.4
D15 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT18' at J10.6. Along the copper: 72.23 mm of track from the contact, 2 via(s) before it, on a 1.49 mm branch off the line; the line runs 83.34 mm on to R124.2; D15 sits 50.82 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.6 and D15.4: the strike reaches an inner layer before it is clamped. D15.4 hangs 1.49 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D15 joins the line 70.74 mm from J10.6 on a 83.34 mm run to R124.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D16D16.3 on '/io_drivers_pp/PP_OUT30': 2 via(s) between J10.3 and D16.3
D16 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT30' at J10.3. Along the copper: 56.7 mm of track from the contact, 2 via(s) before it, on a 4.08 mm branch off the line; the line runs 53.12 mm on to R261.2; D16 sits 45.44 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.3 and D16.3: the strike reaches an inner layer before it is clamped. D16.3 hangs 4.08 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D16 joins the line 52.62 mm from J10.3 on a 53.12 mm run to R261.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D16D16.4 on '/io_drivers_pp/PP_OUT31': 2 via(s) between J10.1 and D16.4
D16 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT31' at J10.1. Along the copper: 66.52 mm of track from the contact, 2 via(s) before it, on a 8.87 mm branch off the line; the line runs 58.15 mm on to R263.2; D16 sits 45.47 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.1 and D16.4: the strike reaches an inner layer before it is clamped. D16.4 hangs 8.87 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D16 joins the line 57.65 mm from J10.1 on a 58.15 mm run to R263.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D16D16.6 on '/io_drivers_pp/PP_OUT29': 2 via(s) between J10.5 and D16.6
D16 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT29' at J10.5. Along the copper: 50.29 mm of track from the contact, 2 via(s) before it, on a 0.92 mm branch off the line; the line runs 51.07 mm on to R253.2; D16 sits 45.41 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.5 and D16.6: the strike reaches an inner layer before it is clamped. D16 joins the line 49.37 mm from J10.5 on a 51.07 mm run to R253.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D18D18.1 on '/io_drivers_pp/PP_OUT20': 2 via(s) between J10.2 and D18.1
D18 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT20' at J10.2. Along the copper: 81.68 mm of track from the contact, 2 via(s) before it, on a 7.72 mm branch off the line; the line runs 74.55 mm on to R121.2; D18 sits 61.2 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.2 and D18.1: the strike reaches an inner layer before it is clamped. D18.1 hangs 7.72 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D18 joins the line 73.96 mm from J10.2 on a 74.55 mm run to R121.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D18D18.4 on '/io_drivers_pp/PP_OUT23': 2 via(s) between J10.17 and D18.4
D18 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT23' at J10.17. Along the copper: 91.36 mm of track from the contact, 2 via(s) before it, on a 5.98 mm branch off the line; the line runs 86 mm on to R143.2; D18 sits 56.03 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.17 and D18.4: the strike reaches an inner layer before it is clamped. D18.4 hangs 5.98 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D18 joins the line 85.38 mm from J10.17 on a 86 mm run to R143.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D18D18.6 on '/io_drivers_pp/PP_OUT21': 2 via(s) between J10.21 and D18.6
D18 (PRTR5V0U4D) protects '/io_drivers_pp/PP_OUT21' at J10.21. Along the copper: 80.18 mm of track from the contact, 2 via(s) before it, on a 6.15 mm branch off the line; the line runs 74.59 mm on to R117.2; D18 sits 55.57 mm farther from the contact than the nearest place outside J10.
2 via(s) between J10.21 and D18.6: the strike reaches an inner layer before it is clamped. D18.6 hangs 6.15 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D18 joins the line 74.03 mm from J10.21 on a 74.59 mm run to R117.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D4D4.3 on '/pp_connector/PP_ID0': 3 via(s) between J10.35 and D4.3
D4 (PRTR5V0U4D) protects '/pp_connector/PP_ID0' at J10.35. Along the copper: 27.99 mm of track from the contact, 3 via(s) before it, on a 14.59 mm branch off the line; the line runs 13.4 mm on to R193.1; D4 sits 6.75 mm farther from the contact than the nearest place outside J10.
3 via(s) between J10.35 and D4.3: the strike reaches an inner layer before it is clamped. D4.3 hangs 14.59 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D4 joins the line 13.4 mm from J10.35 on a 13.4 mm run to R193.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D4D4.4 on '/pp_connector/PP_ID1': D4.4 hangs 7.59 mm off the line (limit 1 mm, default
D4 (PRTR5V0U4D) protects '/pp_connector/PP_ID1' at J10.36. Along the copper: 9.81 mm of track from the contact, 0 via(s) before it, on a 7.59 mm branch off the line; the line runs 26.58 mm on to R198.1; D4 sits 4.07 mm farther from the contact than the nearest place outside J10.
D4.4 hangs 7.59 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D4D4.5 on '/pp_connector/PP_VDD': D4.5 hangs 7.31 mm off the line (limit 1 mm, default
D4 (PRTR5V0U4D) protects '/pp_connector/PP_VDD' at J10.38. Along the copper: 12.64 mm of track from the contact, 0 via(s) before it, on a 7.31 mm branch off the line; the line runs 5.32 mm on to C15.2; D4 sits 4.5 mm farther from the contact than the nearest place outside J10.
D4.5 hangs 7.31 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D4 joins the line 5.33 mm from J10.38 on a 5.32 mm run to C15.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D4D4.5 on '/pp_connector/PP_VDD': D4.5 hangs 7.31 mm off the line (limit 1 mm, default
D4 (PRTR5V0U4D) protects '/pp_connector/PP_VDD' at J10.39. Along the copper: 16.54 mm of track from the contact, 0 via(s) before it, on a 7.31 mm branch off the line; the line runs 9.23 mm on to C15.2; D4 sits 7.34 mm farther from the contact than the nearest place outside J10.
D4.5 hangs 7.31 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. D4 joins the line 9.23 mm from J10.39 on a 9.23 mm run to C15.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D4D4.6 on '/pp_connector/PP_LED0_DATA': D4.6 hangs 8.53 mm off the line (limit 1 mm, default
D4 (PRTR5V0U4D) protects '/pp_connector/PP_LED0_DATA' at J10.33. Along the copper: 18 mm of track from the contact, 0 via(s) before it, on a 8.53 mm branch off the line; the line runs 61.2 mm on to R114.2; D4 sits 6.48 mm farther from the contact than the nearest place outside J10.
D4.6 hangs 8.53 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D8D8.5 on '/pp_connector/PP_VDD': 1 via(s) between J10.38 and D8.5
D8 (PRTR5V0U4D) protects '/pp_connector/PP_VDD' at J10.38. Along the copper: 4.1 mm of track from the contact, 1 via(s) before it, on a 4.1 mm branch off the line; the line runs 5.32 mm on to C15.2; D8 sits at J10, within 0 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of J10's own pins, which no placement shortens.
1 via(s) between J10.38 and D8.5: the strike reaches an inner layer before it is clamped. D8.5 hangs 4.1 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
D8D8.5 on '/pp_connector/PP_VDD': 1 via(s) between J10.39 and D8.5
D8 (PRTR5V0U4D) protects '/pp_connector/PP_VDD' at J10.39. Along the copper: 4.59 mm of track from the contact, 1 via(s) before it, on a 2.39 mm branch off the line; the line runs 9.23 mm on to C15.2; D8 sits at J10, within 0 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of J10's own pins, which no placement shortens.
1 via(s) between J10.39 and D8.5: the strike reaches an inner layer before it is clamped. D8.5 hangs 2.39 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.
Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.
- FloatingInputmajorOpen
FloatingInput: 15 nets×15
e.g. “IC40.1 on 'unconnected-(IC40-IN1-Pad1)' has no driver and no pull” · 15 different statements
At unconnected-(IC35-CTS_ECI-Pad10), unconnected-(IC35-CTS_SCI-Pad18), unconnected-(IC35-GPIO.0_SCI{slash}DCD_SCI-Pad24), unconnected-(IC35-GPIO.1_ECI{slash}DSR_ECI-Pad14), unconnected-(IC35-GPIO.2_SCI{slash}DSR_SCI-Pad22), unconnected-(IC35-NC{slash}VPP{slash}DCD_ECI-Pad16) and 9 more
Each finding, with its own headline
unconnected-(IC35-CTS_ECI-Pad10)IC35.10 on 'unconnected-(IC35-CTS_ECI-Pad10)' has no driver and no pull
Net 'unconnected-(IC35-CTS_ECI-Pad10)': input(s) IC35.10 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC35-CTS_SCI-Pad18)IC35.18 on 'unconnected-(IC35-CTS_SCI-Pad18)' has no driver and no pull
Net 'unconnected-(IC35-CTS_SCI-Pad18)': input(s) IC35.18 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC35-GPIO.0_SCI{slash}DCD_SCI-Pad24)IC35.24 on 'unconnected-(IC35-GPIO.0_SCI{slash}DCD_SCI-Pad24)' has no driver and no pull
Net 'unconnected-(IC35-GPIO.0_SCI{slash}DCD_SCI-Pad24)': input(s) IC35.24 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC35-GPIO.1_ECI{slash}DSR_ECI-Pad14)IC35.14 on 'unconnected-(IC35-GPIO.1_ECI{slash}DSR_ECI-Pad14)' has no driver and no pull
Net 'unconnected-(IC35-GPIO.1_ECI{slash}DSR_ECI-Pad14)': input(s) IC35.14 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC35-GPIO.2_SCI{slash}DSR_SCI-Pad22)IC35.22 on 'unconnected-(IC35-GPIO.2_SCI{slash}DSR_SCI-Pad22)' has no driver and no pull
Net 'unconnected-(IC35-GPIO.2_SCI{slash}DSR_SCI-Pad22)': input(s) IC35.22 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC35-NC{slash}VPP{slash}DCD_ECI-Pad16)IC35.16 on 'unconnected-(IC35-NC{slash}VPP{slash}DCD_ECI-Pad16)' has no driver and no pull
Net 'unconnected-(IC35-NC{slash}VPP{slash}DCD_ECI-Pad16)': input(s) IC35.16 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC35-~{SUSPEND}{slash}RI_ECI-Pad17)IC35.17 on 'unconnected-(IC35-~{SUSPEND}{slash}RI_ECI-Pad17)' has no driver and no pull
Net 'unconnected-(IC35-~{SUSPEND}{slash}RI_ECI-Pad17)': input(s) IC35.17 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC35-~{SUSPEND}{slash}RI_SCI-Pad1)IC35.1 on 'unconnected-(IC35-~{SUSPEND}{slash}RI_SCI-Pad1)' has no driver and no pull
Net 'unconnected-(IC35-~{SUSPEND}{slash}RI_SCI-Pad1)': input(s) IC35.1 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC40-FB_IN-Pad41)IC40.41 on 'unconnected-(IC40-FB_IN-Pad41)' has no driver and no pull
Net 'unconnected-(IC40-FB_IN-Pad41)': input(s) IC40.41 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC40-IN1-Pad1)IC40.1 on 'unconnected-(IC40-IN1-Pad1)' has no driver and no pull
Net 'unconnected-(IC40-IN1-Pad1)': input(s) IC40.1 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC40-IN2-Pad10)IC40.10 on 'unconnected-(IC40-IN2-Pad10)' has no driver and no pull
Net 'unconnected-(IC40-IN2-Pad10)': input(s) IC40.10 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC40-~{FB_IN}-Pad42)IC40.42 on 'unconnected-(IC40-~{FB_IN}-Pad42)' has no driver and no pull
Net 'unconnected-(IC40-~{FB_IN}-Pad42)': input(s) IC40.42 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC40-~{IN1}-Pad2)IC40.2 on 'unconnected-(IC40-~{IN1}-Pad2)' has no driver and no pull
Net 'unconnected-(IC40-~{IN1}-Pad2)': input(s) IC40.2 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC40-~{IN2}-Pad11)IC40.11 on 'unconnected-(IC40-~{IN2}-Pad11)' has no driver and no pull
Net 'unconnected-(IC40-~{IN2}-Pad11)': input(s) IC40.11 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
unconnected-(IC40-~{OE}-Pad12)IC40.12 on 'unconnected-(IC40-~{OE}-Pad12)' has no driver and no pull
Net 'unconnected-(IC40-~{OE}-Pad12)': input(s) IC40.12 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.
- DecapOrdermajorOpen
IC16 supply pins AB22, AD23, Y26 on 'P1V2': the smallest capacitor C228 sits 3.5 mm away, behind C246 at 0.8 mm
IC16 supply pins AB22, AD23, Y26 on 'P1V2': the smallest capacitor C228 sits 3.5 mm away, behind C246 at 0.8 mm. IC16.AB22: the smallest value, C228 (470 nF), is 3.5 mm from the pin and C246 (4.7 uF) 0.8 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC16.AD23: the smallest value, C261 (470 nF), is 2.7 mm from the pin and C246 (4.7 uF) 1.1 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC16.Y26: the smallest value, C228 (470 nF), is 1.7 mm from the pin and C245 (4.7 uF) 0.4 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. Swap them, or bring the smallest value to the pin: it serves the fastest current and is the one the loop inductance defeats. Distances are pad centre to pin centre in the board plane. The 5 mm radius, the 10x value step and the 1 mm / 1.5x tie tolerance are Probe's starting values.
At IC16
- PartLifecyclemajorOpen
MT40A512M16TD-062EA IT:R on 2 placements (IC19, IC24): the distributor catalogue reports "Obsolete" for Micron Technology Inc.'s MT40A512M16TD-062E AIT:R
MT40A512M16TD-062EA IT:R on 2 placements (IC19, IC24): the distributor catalogue reports "Obsolete" for Micron Technology Inc.'s MT40A512M16TD-062E AIT:R — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. That is the maker this board's BOM names (MICRON TECHNOLOGY). 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/MT40A512M16TD-062EA IT:R/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 (2026-07-30, 108 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.
At IC19
- ReferencePlaneDiscontinuitymajorOpen
ReferencePlaneDiscontinuity: 14 boards×14
Checked by the review, stands · Claude walker I2 (Cern session) — Re-affirmed on 2026-10-28 over the current facts (one finding had gone stale after today's rail/edge filings): the 31 reference-plane findings (via reference changes GND<->rails, splits on inner layers between P1V8/MGT_0V85/5VREG/P0V85/P1V2) are SI layout practice; no datasheet or app note on file settles them for these nets. They stand as layout observations for CERN.
At void:GND@IN2.CU_GND:125.48,-151.3, void:GND@IN2.CU_GND:125.51,-139.1, void:GND@IN2.CU_GND:126.36,-151.3, void:GND@IN2.CU_GND:126.76,-138.53, void:GND@IN2.CU_GND:126.8,-151.78, void:GND@IN2.CU_GND:127,-152 and 8 more
Each finding, with its own headline
void:GND@IN2.CU_GND:125.48,-151.3'/pp_connector/PP_ID2' crosses where the outline of the GND plane on IN2.CU_GND is drawn back, at 1 place, the longest 0.39 mm (fastest: /pp_connector/PP_ID2 at 100 ps 10-90 %, ASSUMED)
Along '/pp_connector/PP_ID2' on F.CU, the GND plane on IN2.CU_GND has 0.39 mm under the track with no copper, at (125.48, -151.3), 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 63.33..236.62, y -185.38..-79.48 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.
- '/pp_connector/PP_ID2' on F.CU at (125.48, -151.3), 0.39 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/97/reference-planes?group=void%3AGND%40IN2.CU_GND%3A125.48%2C-151.3 serves each with its own layer_image region; all of them lie in x 124.28..126.67, y -152.3..-150.3 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@IN2.CU_GND:125.51,-139.1'/pp_connector/PP_LED1_DATA' crosses where the outline of the GND plane on IN2.CU_GND is drawn back, at 1 place, the longest 0.33 mm (fastest: /pp_connector/PP_LED1_DATA at 100 ps 10-90 %, ASSUMED)
Along '/pp_connector/PP_LED1_DATA' on F.CU, the GND plane on IN2.CU_GND has 0.33 mm under the track with no copper, at (125.51, -139.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 63.33..236.62, y -185.38..-79.48 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.
- '/pp_connector/PP_LED1_DATA' on F.CU at (125.51, -139.1), 0.33 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/97/reference-planes?group=void%3AGND%40IN2.CU_GND%3A125.51%2C-139.1 serves each with its own layer_image region; all of them lie in x 124.34..126.67, y -140.1..-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@IN2.CU_GND:126.36,-151.3'/pp_connector/PP_ID2' crosses where the outline of the GND plane on IN2.CU_GND is drawn back, at 1 place, the longest 0.38 mm (fastest: /pp_connector/PP_ID2 at 100 ps 10-90 %, ASSUMED)
Along '/pp_connector/PP_ID2' on F.CU, the GND plane on IN2.CU_GND has 0.38 mm under the track with no copper, at (126.36, -151.3), 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 63.33..236.62, y -185.38..-79.48 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.
- '/pp_connector/PP_ID2' on F.CU at (126.36, -151.3), 0.38 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/97/reference-planes?group=void%3AGND%40IN2.CU_GND%3A126.36%2C-151.3 serves each with its own layer_image region; all of them lie in x 125.17..127.55, y -152.3..-150.3 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@IN2.CU_GND:126.76,-138.53'/pp_connector/PP_LED1_DATA' crosses where the outline of the GND plane on IN2.CU_GND is drawn back, at 1 place, the longest 1.63 mm (fastest: /pp_connector/PP_LED1_DATA at 100 ps 10-90 %, ASSUMED)
Along '/pp_connector/PP_LED1_DATA' on F.CU, the GND plane on IN2.CU_GND has 1.63 mm under the track with no copper, at (126.76, -138.53), 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 63.33..236.62, y -185.38..-79.48 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.
- '/pp_connector/PP_LED1_DATA' on F.CU at (126.76, -138.53), 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/97/reference-planes?group=void%3AGND%40IN2.CU_GND%3A126.76%2C-138.53 serves each with its own layer_image region; all of them lie in x 125.17..128.33, y -140.1..-136.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:GND@IN2.CU_GND:126.8,-151.78'/io_drivers_pp/PP_OUT2' crosses where the outline of the GND plane on IN2.CU_GND and the GND plane on IN4.CU_GND is drawn back, at 1 place, the longest 1.68 mm; 1 cleared on both sides of the track (fastest: /io_drivers_pp/PP_OUT2 at 100 ps 10-90 %, ASSUMED)
Along '/io_drivers_pp/PP_OUT2' on IN3.CU, the GND plane on IN2.CU_GND has 1.68 mm under the track with no copper, at (126.8, -151.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 63.33..236.62, y -185.38..-79.48 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: '/io_drivers_pp/PP_OUT2' on IN3.CU at (126.8, -151.78), 1.68 mm over no copper; other side: no plane on IN4.CU_GND / '/io_drivers_pp/PP_OUT2' on IN3.CU at (126.8, -151.78), 1.68 mm over no copper; other side: no plane on IN2.CU_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AGND%40IN2.CU_GND%3A126.8%2C-151.78 serves each with its own layer_image region; all of them lie in x 125.21..128.39, y -153.37..-150.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@IN2.CU_GND:127,-152'/pp_connector/PP_ID2' crosses where the outline of the GND plane on IN2.CU_GND is drawn back, at 1 place, the longest 1.4 mm (fastest: /pp_connector/PP_ID2 at 100 ps 10-90 %, ASSUMED)
Along '/pp_connector/PP_ID2' on F.CU, the GND plane on IN2.CU_GND has 1.4 mm under the track with no copper, at (127, -152), 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 63.33..236.62, y -185.38..-79.48 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.
- '/pp_connector/PP_ID2' on F.CU at (127, -152), 1.4 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/97/reference-planes?group=void%3AGND%40IN2.CU_GND%3A127%2C-152 serves each with its own layer_image region; all of them lie in x 125.6..128.4, y -153.4..-150.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:GND@IN2.CU_GND:165.62,-94.37'/DDR4-PS.BA1' crosses where the outline of the GND plane on IN2.CU_GND and the GND plane on IN4.CU_GND is drawn back, at 1 place, the longest 0.08 mm; 1 cleared on both sides of the track (fastest: /DDR4-PS.BA1 at 100 ps 10-90 %, ASSUMED)
Along '/DDR4-PS.BA1' on IN3.CU, the GND plane on IN2.CU_GND has 0.08 mm under the track with no copper, at (165.62, -94.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 63.33..236.62, y -185.38..-79.48 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: '/DDR4-PS.BA1' on IN3.CU at (165.62, -94.37), 0.08 mm over no copper; other side: no plane on IN4.CU_GND / '/DDR4-PS.BA1' on IN3.CU at (165.61, -94.37), 0.08 mm over no copper; other side: no plane on IN2.CU_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AGND%40IN2.CU_GND%3A165.62%2C-94.37 serves each with its own layer_image region; all of them lie in x 164.58..166.66, y -95.37..-93.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:GND@IN2.CU_GND:177.52,-99.17'/DDR4-PS.A1' crosses where the outline of the GND plane on IN2.CU_GND and the GND plane on IN4.CU_GND is drawn back, at 1 place, the longest 0.08 mm; 1 cleared on both sides of the track (fastest: /DDR4-PS.A1 at 100 ps 10-90 %, ASSUMED)
Along '/DDR4-PS.A1' on IN3.CU, the GND plane on IN2.CU_GND has 0.08 mm under the track with no copper, at (177.52, -99.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 63.33..236.62, y -185.38..-79.48 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: '/DDR4-PS.A1' on IN3.CU at (177.52, -99.17), 0.08 mm over no copper; other side: no plane on IN4.CU_GND / '/DDR4-PS.A1' on IN3.CU at (177.51, -99.17), 0.08 mm over no copper; other side: no plane on IN2.CU_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AGND%40IN2.CU_GND%3A177.52%2C-99.17 serves each with its own layer_image region; all of them lie in x 176.48..178.56, y -100.17..-98.17 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@IN2.CU_GND:232.15,-107.63'/user_interface/USB_D_P' crosses where the outline of the GND plane on IN2.CU_GND is drawn back, at 1 place, the longest 0.52 mm (fastest: /user_interface/USB_D_P at 500 ps 10-90 %, suggested by its name)
Along '/user_interface/USB_D_P' on F.CU, the GND plane on IN2.CU_GND has 0.52 mm under the track with no copper, at (232.15, -107.63), 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 63.33..236.62, y -185.38..-79.48 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.
- '/user_interface/USB_D_P' on F.CU at (232.15, -107.63), 0.52 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/97/reference-planes?group=void%3AGND%40IN2.CU_GND%3A232.15%2C-107.63 serves each with its own layer_image region; all of them lie in x 231.02..233.15, y -108.93..-106.46 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@IN4.CU_GND:165.61,-94.37'/DDR4-PS.A1' crosses where the outline of the GND plane on IN4.CU_GND and the P1V2 plane on IN6.CU is drawn back, at 1 place, the longest 0.08 mm; 1 cleared on both sides of the track (fastest: /DDR4-PS.A1 at 100 ps 10-90 %, ASSUMED)
Along '/DDR4-PS.A1' on IN5.CU, the P1V2 plane on IN6.CU has 0.08 mm under the track with no copper, at (165.62, -94.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 148.52..196.22, y -142.78..-89.58 and of the pour at x 63.33..236.62, y -185.38..-79.48 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: '/DDR4-PS.A1' on IN5.CU at (165.61, -94.37), 0.08 mm over no copper; other side: no plane on IN6.CU / '/DDR4-PS.A1' on IN5.CU at (165.62, -94.37), 0.08 mm over no copper; other side: no plane on IN4.CU_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AGND%40IN4.CU_GND%3A165.61%2C-94.37 serves each with its own layer_image region; all of them lie in x 164.58..166.66, y -95.37..-93.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:GND@IN7.CU_GND:177.51,-99.17'/DDR4-PS.CKE' crosses where the outline of the GND plane on IN7.CU_GND and the GND plane on IN9.CU_GND is drawn back, at 1 place, the longest 0.08 mm; 1 cleared on both sides of the track (fastest: /DDR4-PS.CKE at 100 ps 10-90 %, ASSUMED)
Along '/DDR4-PS.CKE' on IN8.CU, the GND plane on IN7.CU_GND has 0.08 mm under the track with no copper, at (177.51, -99.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 63.33..236.62, y -185.38..-79.48 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: '/DDR4-PS.CKE' on IN8.CU at (177.51, -99.17), 0.08 mm over no copper; other side: no plane on IN9.CU_GND / '/DDR4-PS.CKE' on IN8.CU at (177.51, -99.17), 0.08 mm over no copper; other side: no plane on IN7.CU_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AGND%40IN7.CU_GND%3A177.51%2C-99.17 serves each with its own layer_image region; all of them lie in x 176.48..178.55, y -100.17..-98.17 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@IN9.CU_GND:125.48,-151.3'/pp_connector/PP_ID0' crosses where the outline of the GND plane on IN9.CU_GND is drawn back, at 1 place, the longest 0.39 mm (fastest: /pp_connector/PP_ID0 at 100 ps 10-90 %, ASSUMED)
Along '/pp_connector/PP_ID0' on B.CU, the GND plane on IN9.CU_GND has 0.39 mm under the track with no copper, at (125.48, -151.3), 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 63.33..236.62, y -185.38..-79.48 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.
- '/pp_connector/PP_ID0' on B.CU at (125.48, -151.3), 0.39 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/97/reference-planes?group=void%3AGND%40IN9.CU_GND%3A125.48%2C-151.3 serves each with its own layer_image region; all of them lie in x 124.28..126.67, y -152.3..-150.3 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@IN9.CU_GND:126.85,-151.85'/pp_connector/PP_ID0' crosses where the outline of the GND plane on IN9.CU_GND is drawn back, at 1 place, the longest 1.68 mm (fastest: /pp_connector/PP_ID0 at 100 ps 10-90 %, ASSUMED)
Along '/pp_connector/PP_ID0' on B.CU, the GND plane on IN9.CU_GND has 1.68 mm under the track with no copper, at (126.85, -151.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 63.33..236.62, y -185.38..-79.48 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.
- '/pp_connector/PP_ID0' on B.CU at (126.85, -151.85), 1.68 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/97/reference-planes?group=void%3AGND%40IN9.CU_GND%3A126.85%2C-151.85 serves each with its own layer_image region; all of them lie in x 125.17..128.4, y -153.4..-150.3 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@IN9.CU_GND:235.06,-102.19'Net-(J14-SH)' crosses where the outline of the GND plane on IN9.CU_GND is drawn back, at 1 place, the longest 0.23 mm (fastest: Net-(J14-SH) at 100 ps 10-90 %, ASSUMED)
Along 'Net-(J14-SH)' on B.CU, the GND plane on IN9.CU_GND has 0.23 mm under the track with no copper, at (235.06, -102.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 63.33..236.62, y -185.38..-79.48 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-(J14-SH)' on B.CU at (235.06, -102.19), 0.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/97/reference-planes?group=void%3AGND%40IN9.CU_GND%3A235.06%2C-102.19 serves each with its own layer_image region; all of them lie in x 233.32..236.1, y -104.73..-101.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.
- SinglePointNetmajorOpen
SinglePointNet: 15 pins×15
e.g. “IC40.1 (IN1) is an IC input left unconnected” · 15 different statements
At IC35.1, IC35.10, IC35.14, IC35.16, IC35.17, IC35.18 and 9 more
Each finding, with its own headline
IC35.1IC35.1 (RI_SCI) is an IC input left unconnected
Pin IC35.1 (RI_SCI) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC35-~{SUSPEND}{slash}RI_SCI-Pad1)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC35.10IC35.10 (CTS_ECI) is an IC input left unconnected
Pin IC35.10 (CTS_ECI) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC35-CTS_ECI-Pad10)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC35.14IC35.14 (DSR_ECI) is an IC input left unconnected
Pin IC35.14 (DSR_ECI) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC35-GPIO.1_ECI{slash}DSR_ECI-Pad14)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC35.16IC35.16 (DCD_ECI) is an IC input left unconnected
Pin IC35.16 (DCD_ECI) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC35-NC{slash}VPP{slash}DCD_ECI-Pad16)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC35.17IC35.17 (RI_ECI) is an IC input left unconnected
Pin IC35.17 (RI_ECI) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC35-~{SUSPEND}{slash}RI_ECI-Pad17)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC35.18IC35.18 (CTS_SCI) is an IC input left unconnected
Pin IC35.18 (CTS_SCI) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC35-CTS_SCI-Pad18)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC35.22IC35.22 (DSR_SCI) is an IC input left unconnected
Pin IC35.22 (DSR_SCI) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC35-GPIO.2_SCI{slash}DSR_SCI-Pad22)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC35.24IC35.24 (DCD_SCI) is an IC input left unconnected
Pin IC35.24 (DCD_SCI) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC35-GPIO.0_SCI{slash}DCD_SCI-Pad24)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC40.1IC40.1 (IN1) is an IC input left unconnected
Pin IC40.1 (IN1) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC40-IN1-Pad1)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC40.10IC40.10 (IN2) is an IC input left unconnected
Pin IC40.10 (IN2) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC40-IN2-Pad10)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC40.11IC40.11 (IN2b) is an IC input left unconnected
Pin IC40.11 (IN2b) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC40-~{IN2}-Pad11)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC40.12IC40.12 (OEb) is an IC input left unconnected
Pin IC40.12 (OEb) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC40-~{OE}-Pad12)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC40.2IC40.2 (IN1b) is an IC input left unconnected
Pin IC40.2 (IN1b) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC40-~{IN1}-Pad2)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC40.41IC40.41 (FB_IN) is an IC input left unconnected
Pin IC40.41 (FB_IN) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC40-FB_IN-Pad41)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
IC40.42IC40.42 (FB_INb) is an IC input left unconnected
Pin IC40.42 (FB_INb) is an IC INPUT the designer flagged no-connect (KiCad net 'unconnected-(IC40-~{FB_IN}-Pad42)'), but an input normally needs a defined level - confirm it is truly meant to float. 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.
J8 (ABSCAL) and J9 (PPS) U.FL are DNP in the schematic but mounted in CERN's assembly BOM
J8 and J9 (U.FL, the WR_CLK.ABSCAL and WR_CLK.PPS test outputs) are crossed out as not fitted on schematic sheet 12, but CERN's released assembly BOM lists them as mounted: the two documents describe different builds.
Document J8, J9 Source Schematic drawn crossed out (DNP); drivers IC8/IC9 SN74LV1T34DBV and series R25/R37 4R7 fitted EDA-04968-V4-0_sch.pdf (EDMS 3521789 v.1), sheet 12 "clocks" Assembly BOM mounted: "J2 > J5, J8, J9, J13", qty 7, HIROSE U.FL-R-SMT-1 EDA-04968-V4-0_pcb-mat.xls (EDMS 3521793 v.1), parts mounted Electrically harmless either way (the buffers and series resistors are fitted in both), but one of the two documents is wrong for V4-0, and the BOM drives the build. J2-J5 and J13 agree (fitted in both).
F1 (750 mA) on PP_VDD can never open: its source 5VREG is a 300 mA buck that current-limits first and takes the board's 5 V loads down with it
F1 (0466.750NR, 750 mA) protects PP_VDD on the pp connector J10, but it is fed from 5VREG, which IC32 (TPS62125) can supply only about 300 mA: an overload or short on PP_VDD current-limits IC32 long before F1 opens, and the sagging 5VREG drops P5V_REG_PG and the VCC/VDRV of both IRPS5401s, so the whole board browns out instead of the connector being isolated.
The fuse cannot reach its opening current
Quantity Value Source F1 rating 0.75 A BOM F1 0466.750NR; 466 Series datasheet p1 rating table (".750") F1 opening time at 100 % / 200 % of rating 4 h minimum / 5 s maximum 466 Series datasheet p1 IC32 output current capability (VIN 6-17 V) 300 mA TPS62125 datasheet p4, Recommended Operating Conditions IC32 output current in short circuit 0.5 x I_LIMF, typ. 300 mA TPS62125 datasheet p12, 7.4.5 Fault current as a share of F1's rating 300 / 750 = 40 % derived At 40 % of its rating the fuse is specified to carry the current indefinitely (it carries 100 % for at least 4 h), so F1 never clears a fault on this board.
What a fault on the connector does instead
``
mermaid graph LR P12V --> IC32[IC32 TPS62125, 300 mA] --> V5[5VREG] V5 --> F1[F1 750 mA] --> PPVDD[PP_VDD, J10.38/39] V5 --> L[IC31/IC36 VCC + VDRV, IC34 VCC, IC49 BIAS, LD1-LD9, IC21/IC25/IC52] IC32 -- PG --> PG[P5V_REG_PG] --> EN[IC36 enables, IC34 enable]``5VREG is the VCC (pins 20/29) and, through R150/R164, the VDRV of IRPS5401 IC31 and IC36, the VCC of power stage IC34, the BIAS of LDO IC49 and the supply of the nine RGB LEDs. IC32's PG drives P5V_REG_PG, which enables IC36 and IC34. A short or overload on the external pp connector therefore takes the board's supplies down rather than opening F1.
Question for the designer
Is F1 meant to protect against something other than an overload (it cannot clear one from this source), and is the PP_VDD load meant to share IC32's 300 mA with the board's own 5VREG loads? A current-limited switch on PP_VDD, or a fuse rated below IC32's limit, would keep a connector fault off the board's supplies. The same arrangement is on OHWR0091 R2 WREN XIE (OBS-653).
R156 (1k4 0402, LD13 indicator on P12V) dissipates about 70 mW, above the 0.063 W its own BOM line specifies
R156, the 1k4 0402 series resistor of the green P12V indicator LD13, dissipates about 70 mW at nominal 12 V (about 84 mW at the PCIe +8 % limit), more than the 0.063 W that CERN's own BOM line for it specifies and Vishay's standard rating for the CRCW0402 example part.
Dissipation in R156
Quantity Value Source Supply 12 V (P12V, PCIe +12 V / J11) netlist: R156.1 on P12V; rail clue LED forward voltage 2.1 V typ (at 20 mA; lower at 7 mA, which only raises R156's share) KPH-1608CGCK datasheet p2 Resistor 1k4, 0402 BOM R156 (CERN generic R0402_1K4_1%_0.063W_100PPM, example CRCW04021K40FK) Current (12 - 2.1) / 1400 = 7.1 mA derived Dissipation in R156 7.1 mA² x 1400 Ω = 70 mW (84 mW at 12.96 V) derived Rating CERN specifies 0.063 W BOM R156 description "0.063W" CRCW0402 rating 0.063 W standard operation, 0.10 W extended (larger resistance drift) Vishay D/CRCW e3 datasheet p2 Why it matters
The part is a CERN generic: any 0402 resistor meeting "1 %, 0.063 W" may be fitted, and at 70-84 mW such a part runs beyond its rating continuously while the board is powered. The named example (Vishay CRCW0402) only covers it in Vishay's "extended" operating mode, which allows a larger resistance change. A 0603 part, or a 2k2-2k7 value (about 3.5-4.5 mA, still a visible indicator), would bring the dissipation inside 0.063 W.
``
mermaid graph LR P12V --> R156[R156 1k4 0402] --> LD13[LD13 green KPH-1608CGCK] --> GND``- DecapViaFanoutminorOpen
C277 on 'P0V85': its rail pad reaches its via over 2.14 mm of track, adding about 0.71 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 100 uF bulk capacitor: its inductance matters only far above the band it serves)
C277 on 'P0V85': its rail pad reaches its via over 2.14 mm of track, adding about 0.71 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 100 uF bulk capacitor: its inductance matters only far above the band it serves). C277.2 (rail) runs 2.14 mm along its copper to its nearest via, 1.14 mm past the 1 mm beside the pad: 0.71 nH; C277.1 (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.80 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.71 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.25 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.42 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.
At C277
- ReferencePlaneDiscontinuityminorOpen
ReferencePlaneDiscontinuity: 17 boards×17
Checked by the review, stands · Claude walker I2 (Cern session) — Re-affirmed on 2026-10-28 over the current facts (one finding had gone stale after today's rail/edge filings): the 31 reference-plane findings (via reference changes GND<->rails, splits on inner layers between P1V8/MGT_0V85/5VREG/P0V85/P1V2) are SI layout practice; no datasheet or app note on file settles them for these nets. They stand as layout observations for CERN.
At along@IN6.CU:P0V85|P1V2, refchange:5VREG|GND, refchange:GND|MGT_0V85, refchange:GND|MGT_1V2, refchange:GND|MGT_1V8, refchange:GND|P1V2 and 11 more
Each finding, with its own headline
along@IN6.CU:P0V85|P1V2'/DDR4-PS.A11' runs ALONG the split between the P0V85 and P1V2 planes on IN6.CU at 1 place, the longest 0.74 mm; the impedance rises from 62 ohm to 62 ohm there at worst, 0 % of each edge reflected (fastest: /DDR4-PS.A11 at 100 ps 10-90 %, ASSUMED)
On IN6.CU the P0V85 and P1V2 planes part, and '/DDR4-PS.A11' 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 62 ohm; along the slot 62 ohm, reflecting up to 0 % 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 63 ohm). At every place the rise is within 10 %, the tolerance controlled impedance is commonly built to (the stackup states none), so the finding is the lower tier (info). One decision covers the split line's slot: whether these tracks may run down it, or should be moved over solid plane.
- '/DDR4-PS.A11' on IN5.CU at (160.22, -121.38), 0.96 mm, running ALONG the split for 0.74 mm, not across it, 62 ohm over solid plane, 62 ohm along it: 0 % of each edge reflected; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=along%40IN6.CU%3AP0V85%7CP1V2 serves each with its own layer_image region; all of them lie in x 158.92..161.52, y -122.79..-120.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.
refchange:5VREG|GND'/power-supply-1/P1V8AUX_PG' changes reference between 5VREG and GND at a via, each with another reference that continues across (fastest: /power-supply-1/P1V8AUX_PG at 20 ns 10-90 %, suggested by its name)
At 1 via(s), on 1 net(s), the signal leaves a layer referenced by one of 5VREG 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: 1 with none. 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 5VREG 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. Every one is partial: another reference continues across through a stitching via of its net, so only part of the return has nowhere to go, and the finding is the lower tier (info). They are listed with the farthest stitching via first.
- '/power-supply-1/P1V8AUX_PG' at (203.82, -143.18), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, 5VREG on IN6.CU; partial, GND continues through a via of GND 0.93 mm away; stitching none, 58.4 mm of track past the via on IN5.CU: At the 5 GHz knee of a 100 ps edge (20 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. 5VREG 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/97/reference-planes?group=refchange%3A5VREG%7CGND serves each with its own layer_image region; all of them lie in x 201.82..205.82, y -145.18..-141.18 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:GND|MGT_0V853 nets change reference between GND and MGT_0V85 at 3 vias, each with another reference that continues across (fastest: /SFP0_RSSI at 100 ps 10-90 %, ASSUMED)
At 3 via(s), on 3 net(s), the signal leaves a layer referenced by one of GND and MGT_0V85 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: 3 with none. 3 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 GND and MGT_0V85 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. Every one is partial: another reference continues across through a stitching via of its net, so only part of the return has nowhere to go, and the finding is the lower tier (info). They are listed with the farthest stitching via first.
- '/SFP0_RSSI' at (138.62, -132.32), IN6.CU -> B.CU: MGT_0V85 on IN5.CU, GND on IN7.CU_GND to GND on IN9.CU_GND; partial, GND continues through a via of GND 3.78 mm away; stitching none, 35.9 mm of track past the via on B.CU: 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. GND and MGT_0V85 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.
- '/io_drivers_fp/F_FP_I3' at (140.02, -132.32), IN6.CU -> B.CU: MGT_0V85 on IN5.CU, GND on IN7.CU_GND to GND on IN9.CU_GND; partial, GND continues through a via of GND 3.2 mm away; stitching none, 31.8 mm of track past the via on B.CU: 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. GND and MGT_0V85 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.
- '/fpga/F_FP_OE0' at (138.02, -132.32), IN6.CU -> B.CU: MGT_0V85 on IN5.CU, GND on IN7.CU_GND to GND on IN9.CU_GND; partial, GND continues through a via of GND 4.15 mm away; stitching none, 11.2 mm of track past the via on B.CU: 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. GND and MGT_0V85 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/97/reference-planes?group=refchange%3AGND%7CMGT_0V85 serves each with its own layer_image region; all of them lie in x 136.02..142.02, y -134.32..-130.32 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:GND|MGT_1V210 nets change reference between GND and MGT_1V2 at 27 vias, each with another reference that continues across (fastest: /fpga/F_PP_OE_N at 100 ps 10-90 %, ASSUMED)
At 27 via(s), on 10 net(s), the signal leaves a layer referenced by one of GND and MGT_1V2 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: 27 with none. 27 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 GND and MGT_1V2 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. Every one is partial: another reference continues across through a stitching via of its net, so only part of the return has nowhere to go, and the finding is the lower tier (info). They are listed with the farthest stitching via first.
- '/fpga/F_PP_OE_N' at (170.67, -153.87), IN5.CU -> B.CU: GND on IN4.CU_GND, MGT_1V2 on IN6.CU to GND on IN9.CU_GND; partial, GND continues through a via of GND 1.93 mm away; stitching none, 127.4 mm of track past the via on B.CU: 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. GND and MGT_1V2 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.
- '/fpga/F_PP_OE_N' at (176.67, -153.87), IN5.CU -> B.CU: GND on IN4.CU_GND, MGT_1V2 on IN6.CU to GND on IN9.CU_GND; partial, GND continues through a via of GND 1.93 mm away; stitching none, 127.4 mm of track past the via on B.CU: 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. GND and MGT_1V2 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.
- '/fpga/F_PP_OE_N' at (182.67, -153.87), IN5.CU -> B.CU: GND on IN4.CU_GND, MGT_1V2 on IN6.CU to GND on IN9.CU_GND; partial, GND continues through a via of GND 1.93 mm away; stitching none, 127.4 mm of track past the via on B.CU: 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. GND and MGT_1V2 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.
- '/fpga/F_PP_OE_N' at (167.9, -154.6), IN5.CU -> B.CU: GND on IN4.CU_GND, MGT_1V2 on IN6.CU to GND on IN9.CU_GND; partial, GND continues through a via of GND 1.23 mm away; stitching none, 127.4 mm of track past the via on B.CU: 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. GND and MGT_1V2 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.
- '/fpga/F_PP_OE_N' at (173.9, -154.6), IN5.CU -> B.CU: GND on IN4.CU_GND, MGT_1V2 on IN6.CU to GND on IN9.CU_GND; partial, GND continues through a via of GND 1.23 mm away; stitching none, 127.4 mm of track past the via on B.CU: 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. GND and MGT_1V2 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.
- '/fpga/F_PP_OE_N' at (179.9, -154.6), IN5.CU -> B.CU: GND on IN4.CU_GND, MGT_1V2 on IN6.CU to GND on IN9.CU_GND; partial, GND continues through a via of GND 1.23 mm away; stitching none, 127.4 mm of track past the via on B.CU: 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. GND and MGT_1V2 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.
- '/io_drivers_pp/PP_OUT31' at (182.77, -147.89), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V2 on IN6.CU; partial, GND continues through a via of GND 1.94 mm away; stitching none, 50.3 mm of track past the via on IN5.CU: 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. GND and MGT_1V2 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.
- '/pp_connector/PP_LED0_DATA' at (174.22, -141.57), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V2 on IN6.CU; partial, GND continues through a via of GND 3.67 mm away; stitching none, 47.3 mm of track past the via on IN5.CU: 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. GND and MGT_1V2 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.
- '/io_drivers_pp/PP_OUT30' at (177.86, -147.91), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V2 on IN6.CU; partial, GND continues through a via of GND 1.94 mm away; stitching none, 46.0 mm of track past the via on IN5.CU: 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. GND and MGT_1V2 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.
- '/io_drivers_pp/PP_OUT29' at (175.2, -146.7), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V2 on IN6.CU; partial, GND continues through a via of GND 1.3 mm away; stitching none, 43.4 mm of track past the via on IN5.CU: 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. GND and MGT_1V2 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.
- '/pp_connector/PP_LED1_DATA' at (175.12, -141.58), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V2 on IN6.CU; partial, GND continues through a via of GND 3.19 mm away; stitching none, 39.4 mm of track past the via on IN5.CU: 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. GND and MGT_1V2 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.
- '/io_drivers_pp/PP_OUT26' at (165.86, -147.91), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V2 on IN6.CU; partial, GND continues through a via of GND 1.94 mm away; stitching none, 38.3 mm of track past the via on IN5.CU: 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. GND and MGT_1V2 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 15 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=refchange%3AGND%7CMGT_1V2 serves each with its own layer_image region; all of them lie in x 162.77..184.77, y -156.6..-139.57 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:GND|MGT_1V814 nets change reference between GND and MGT_1V8 at 25 vias, each with another reference that continues across (fastest: /fpga/F_PP_OE_N at 100 ps 10-90 %, ASSUMED)
At 25 via(s), on 14 net(s), the signal leaves a layer referenced by one of GND and MGT_1V8 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: 25 with none. 25 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 GND and MGT_1V8 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. Every one is partial: another reference continues across through a stitching via of its net, so only part of the return has nowhere to go, and the finding is the lower tier (info). They are listed with the farthest stitching via first.
- '/fpga/F_PP_OE_N' at (164.67, -153.87), IN5.CU -> B.CU: GND on IN4.CU_GND, MGT_1V8 on IN6.CU to GND on IN9.CU_GND; partial, GND continues through a via of GND 1.93 mm away; stitching none, 127.4 mm of track past the via on B.CU: 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. GND and MGT_1V8 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.
- '/fpga/F_PP_OE_N' at (161.9, -154.6), IN5.CU -> B.CU: GND on IN4.CU_GND, MGT_1V8 on IN6.CU to GND on IN9.CU_GND; partial, GND continues through a via of GND 1.23 mm away; stitching none, 127.4 mm of track past the via on B.CU: 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. GND and MGT_1V8 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.
- '/io_drivers_pp/PP_OUT31' at (135.42, -142.42), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 3.56 mm away; stitching none, 50.3 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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.
- '/pp_connector/PP_LED0_DATA' at (127.3, -142.4), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 6.13 mm away; stitching none, 47.3 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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.
- '/io_drivers_pp/PP_OUT30' at (134.8, -142.6), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 3.3 mm away; stitching none, 46.0 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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.
- '/io_drivers_pp/PP_OUT29' at (134.32, -142.93), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 3.35 mm away; stitching none, 43.4 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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.
- '/io_drivers_pp/PP_OUT28' at (132.3, -143), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 3.16 mm away; stitching none, 42.9 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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.
- '/pp_connector/PP_LED1_DATA' at (136, -141.93), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 3.71 mm away; stitching none, 39.4 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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.
- '/io_drivers_pp/PP_OUT26' at (130.4, -142.9), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 3.91 mm away; stitching none, 38.3 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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.
- '/io_drivers_pp/PP_OUT27' at (136.1, -143.9), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 4.33 mm away; stitching none, 37.0 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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.
- '/io_drivers_pp/PP_OUT24' at (127.3, -143.4), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 6.6 mm away; stitching none, 35.2 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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.
- '/io_drivers_pp/PP_OUT24' at (159.76, -147.91), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, MGT_1V8 on IN6.CU; partial, GND continues through a via of GND 1.94 mm away; stitching none, 35.2 mm of track past the via on IN5.CU: 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. GND and MGT_1V8 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 13 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=refchange%3AGND%7CMGT_1V8 serves each with its own layer_image region; all of them lie in x 125.3..166.67, y -156.6..-139.93 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:GND|P1V215 nets change reference between GND and P1V2 at 33 vias, each with another reference that continues across (fastest: /DDR4-PS.A1 at 100 ps 10-90 %, ASSUMED)
At 33 via(s), on 15 net(s), the signal leaves a layer referenced by one of GND and P1V2 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: 33 with none. 33 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 GND and P1V2 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. Every one is partial: another reference continues across through a stitching via of its net, so only part of the return has nowhere to go, and the finding is the lower tier (info). They are listed with the farthest stitching via first.
- '/DDR4-PS.A12' at (161.62, -96.32), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 1.6 mm away; stitching none, 74.3 mm of track past the via on IN5.CU: 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. GND and P1V2 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.
- '/DDR4-PS.A12' at (177.52, -95.52), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 1.6 mm away; stitching none, 74.3 mm of track past the via on IN5.CU: 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. GND and P1V2 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.
- '/DDR4-PS.A12' at (160.32, -117.92), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 0.8 mm away; stitching none, 74.3 mm of track past the via on IN5.CU: 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. GND and P1V2 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. Measured for reference: C245 (4.7 uF 0402) 2.1 mm away: 0.91 nH in the 0.810 mm cavity + 0.30 nH ESL + 1.43 nH mounting (pad 0.07 nH (vias beside the pads) + 1 via pair(s) at 1.58 mm pitch, 0.20 mm drill, 1.23 mm to the farther plane): 82.7 ohm at the knee, 165 % of 50 ohm (assumed track impedance). None.
- '/DDR4-PS.A11' at (165.62, -92.32), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 1.19 mm away; stitching none, 69.7 mm of track past the via on IN5.CU: 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. GND and P1V2 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.
- '/DDR4-PS.A11' at (158.93, -117.84), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 0.9 mm away; stitching none, 69.7 mm of track past the via on IN5.CU: 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. GND and P1V2 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. Measured for reference: C245 (4.7 uF 0402) 0.8 mm away: 0.60 nH in the 0.810 mm cavity + 0.30 nH ESL + 1.43 nH mounting (pad 0.07 nH (vias beside the pads) + 1 via pair(s) at 1.58 mm pitch, 0.20 mm drill, 1.23 mm to the farther plane): 73.2 ohm at the knee, 146 % of 50 ohm (assumed track impedance). None.
- '/DDR4-PS.A11' at (182.32, -92.32), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 0.8 mm away; stitching none, 69.7 mm of track past the via on IN5.CU: 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. GND and P1V2 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. Measured for reference: C296 (470 nF 0402) 1.7 mm away: 0.84 nH in the 0.810 mm cavity + 0.30 nH ESL + 1.09 nH mounting (pad 0.07 nH (vias beside the pads) + 1 via pair(s) at 0.80 mm pitch, 0.20 mm drill, 1.23 mm to the farther plane): 70.0 ohm at the knee, 140 % of 50 ohm (assumed track impedance). None.
- '/DDR4-PS.A9' at (178.32, -93.92), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 2.53 mm away; stitching none, 69.6 mm of track past the via on IN5.CU: 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. GND and P1V2 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.
- '/DDR4-PS.A9' at (161.62, -93.92), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 2.26 mm away; stitching none, 69.6 mm of track past the via on IN5.CU: 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. GND and P1V2 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.
- '/DDR4-PS.A9' at (159.6, -120.3), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 1.81 mm away; stitching none, 69.6 mm of track past the via on IN5.CU: 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. GND and P1V2 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. Measured for reference: C246 (4.7 uF 0402) 1.4 mm away: 0.77 nH in the 0.810 mm cavity + 0.30 nH ESL + 1.43 nH mounting (pad 0.07 nH (vias beside the pads) + 1 via pair(s) at 1.60 mm pitch, 0.20 mm drill, 1.23 mm to the farther plane): 78.8 ohm at the knee, 158 % of 50 ohm (assumed track impedance). None.
- '/DDR4-PS.CASN' at (161.12, -118.72), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 0.8 mm away; stitching none, 49.5 mm of track past the via on IN5.CU: 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. GND and P1V2 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. Measured for reference: C246 (4.7 uF 0402) 2.4 mm away: 0.96 nH in the 0.810 mm cavity + 0.30 nH ESL + 1.43 nH mounting (pad 0.07 nH (vias beside the pads) + 1 via pair(s) at 1.60 mm pitch, 0.20 mm drill, 1.23 mm to the farther plane): 84.5 ohm at the knee, 169 % of 50 ohm (assumed track impedance). None.
- '/DDR4-PS.RASN' at (161.12, -119.52), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 1.6 mm away; stitching none, 49.5 mm of track past the via on IN5.CU: 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. GND and P1V2 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. Measured for reference: C246 (4.7 uF 0402) 1.6 mm away: 0.83 nH in the 0.810 mm cavity + 0.30 nH ESL + 1.43 nH mounting (pad 0.07 nH (vias beside the pads) + 1 via pair(s) at 1.60 mm pitch, 0.20 mm drill, 1.23 mm to the farther plane): 80.6 ohm at the knee, 161 % of 50 ohm (assumed track impedance). None.
- '/DDR4-PS.A7' at (158.72, -120.32), F.CU -> IN5.CU: GND on IN2.CU_GND to GND on IN4.CU_GND, P1V2 on IN6.CU; partial, GND continues through a via of GND 1.13 mm away; stitching none, 49.5 mm of track past the via on IN5.CU: 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. GND and P1V2 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. Measured for reference: C228 (470 nF 0402) 2.0 mm away: 0.89 nH in the 0.810 mm cavity + 0.30 nH ESL + 1.26 nH mounting (pad 0.07 nH (vias beside the pads) + 1 via pair(s) at 1.13 mm pitch, 0.20 mm drill, 1.23 mm to the farther plane): 77.2 ohm at the knee, 154 % of 50 ohm (assumed track impedance). None.
- and 21 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=refchange%3AGND%7CP1V2 serves each with its own layer_image region; all of them lie in x 155.92..184.32, y -122.32..-89.02 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:GND|P1V819 nets change reference between GND and P1V8 at 41 vias, each with another reference that continues across (fastest: /SFP0/FP_LED_STAT_DIN at 100 ps 10-90 %, ASSUMED)
At 41 via(s), on 19 net(s), the signal leaves a layer referenced by one of GND and P1V8 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: 41 with none. 41 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 GND and P1V8 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. Every one is partial: another reference continues across through a stitching via of its net, so only part of the return has nowhere to go, and the finding is the lower tier (info). They are listed with the farthest stitching via first.
- '/SFP0/FP_LED_STAT_DIN' at (126.4, -120), F.CU -> IN6.CU: GND on IN2.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 3.81 mm away; stitching none, 54.1 mm of track past the via on IN6.CU: 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. GND and P1V8 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.
- '/SFP0_SCL' at (93.61, -102.2), F.CU -> IN6.CU: GND on IN2.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 4.92 mm away; stitching none, 47.9 mm of track past the via on IN6.CU: At the 5 GHz knee of a 100 ps edge (10 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P1V8 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.
- '/SFP0_SCL' at (117.7, -129.9), IN3.CU -> IN6.CU: GND on IN2.CU_GND, GND on IN4.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 4.58 mm away; stitching none, 47.9 mm of track past the via on IN6.CU: At the 5 GHz knee of a 100 ps edge (10 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P1V8 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.
- '/SFP0_TXDIS' at (119.3, -128.3), IN3.CU -> IN6.CU: GND on IN2.CU_GND, GND on IN4.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 5.56 mm away; stitching none, 45.4 mm of track past the via on IN6.CU: At the 5 GHz knee of a 100 ps edge (3 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P1V8 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.
- '/SFP0_TXDIS' at (93.61, -99.2), F.CU -> IN6.CU: GND on IN2.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 5.55 mm away; stitching none, 45.4 mm of track past the via on IN6.CU: At the 5 GHz knee of a 100 ps edge (3 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P1V8 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.
- '/SFP0_MODABS' at (93.61, -100.3), F.CU -> IN6.CU: GND on IN2.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 5.12 mm away; stitching none, 44.2 mm of track past the via on IN6.CU: 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. GND and P1V8 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.
- '/SFP0_MODABS' at (118.7, -128.7), IN3.CU -> IN6.CU: GND on IN2.CU_GND, GND on IN4.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 5.04 mm away; stitching none, 44.2 mm of track past the via on IN6.CU: 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. GND and P1V8 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.
- '/fpga/F_FP_OE0' at (98.15, -134.59), F.CU -> IN6.CU: GND on IN2.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 1.7 mm away; stitching none, 43.8 mm of track past the via on IN6.CU: 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. GND and P1V8 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.
- '/SFP0_SDA' at (118.3, -129.4), IN3.CU -> IN6.CU: GND on IN2.CU_GND, GND on IN4.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 4.88 mm away; stitching none, 43.3 mm of track past the via on IN6.CU: At the 5 GHz knee of a 100 ps edge (10 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P1V8 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.
- '/SFP0_SDA' at (93.71, -101.4), F.CU -> IN6.CU: GND on IN2.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 4.82 mm away; stitching none, 43.3 mm of track past the via on IN6.CU: At the 5 GHz knee of a 100 ps edge (10 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P1V8 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.
- '/power-supply-1/PMBUS_SCL' at (222.63, -114.47), F.CU -> IN6.CU: GND on IN2.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 2.78 mm away; stitching none, 42.0 mm of track past the via on IN6.CU: At the 5 GHz knee of a 100 ps edge (10 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P1V8 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.
- '/power-supply-1/PMBUS_SCL' at (212.48, -137.66), F.CU -> IN6.CU: GND on IN2.CU_GND to P1V8 on IN5.CU, GND on IN7.CU_GND; partial, GND continues through a via of GND 1.93 mm away; stitching none, 42.0 mm of track past the via on IN6.CU: At the 5 GHz knee of a 100 ps edge (10 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P1V8 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 29 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=refchange%3AGND%7CP1V8 serves each with its own layer_image region; all of them lie in x 78.35..224.75, y -145.38..-83.6 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@IN5.CU:MGT_0V85|P1V83 nets cross the split between the MGT_0V85 and P1V8 planes on IN5.CU at 3 places, all with a plane on the track's other side (fastest: /SFP0_RSSI at 100 ps 10-90 %, ASSUMED)
On IN5.CU the MGT_0V85 and P1V8 planes part, and 3 nets cross from one to the other at 3 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 3 of the 3 crossing(s) the track's other neighbour carries a plane, which the return can use there. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 17% 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).
- '/SFP0_RSSI' on IN6.CU at (135.98, -130.95), 4.21 mm; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/fpga/F_FP_OE0' on IN6.CU at (136.15, -130.45), 3.73 mm; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/io_drivers_fp/F_FP_I3' on IN6.CU at (136.87, -129.17), 3.03 mm; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=split%40IN5.CU%3AMGT_0V85%7CP1V8 serves each with its own layer_image region; all of them lie in x 133.65..138.62, y -133.59..-127.28 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@IN6.CU:5VREG|P1V8'/power-supply-1/P1V8AUX_PG' crosses the split between the 5VREG and P1V8 planes on IN6.CU at 1 place, all with a plane on the track's other side (fastest: /power-supply-1/P1V8AUX_PG at 20 ns 10-90 %, suggested by its name)
On IN6.CU the 5VREG and P1V8 planes part, and '/power-supply-1/P1V8AUX_PG' crosses from one to the other at 1 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 1 of the 1 crossing(s) the track's other neighbour carries a plane, which the return can use there. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 17% 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).
- '/power-supply-1/P1V8AUX_PG' on IN5.CU at (215.97, -139.68), 9.29 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=split%40IN6.CU%3A5VREG%7CP1V8 serves each with its own layer_image region; all of them lie in x 208.91..219.12, y -143.29..-138.68 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@IN6.CU:MGT_1V2|MGT_1V810 nets cross the split between the MGT_1V2 and MGT_1V8 planes on IN6.CU at 11 places, all with a plane on the track's other side (fastest: /io_drivers_pp/PP_OUT24 at 100 ps 10-90 %, ASSUMED)
On IN6.CU the MGT_1V2 and MGT_1V8 planes part, and 10 nets cross from one to the other at 11 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 11 of the 11 crossing(s) the track's other neighbour carries a plane, which the return can use there. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 17% 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).
- '/io_drivers_pp/PP_OUT24' on IN5.CU at (158.66, -145.8), 0.74 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/io_drivers_pp/PP_OUT24' on IN5.CU at (159.76, -146.9), 0.74 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/io_drivers_pp/PP_OUT25' on IN5.CU at (158.26, -145.4), 0.74 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/io_drivers_pp/PP_OUT26' on IN5.CU at (157.86, -145), 0.74 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/io_drivers_pp/PP_OUT27' on IN5.CU at (156.86, -144), 0.75 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/io_drivers_pp/PP_OUT28' on IN5.CU at (157.36, -144.5), 0.74 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/io_drivers_pp/PP_OUT29' on IN5.CU at (156.26, -143.4), 0.75 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/io_drivers_pp/PP_OUT30' on IN5.CU at (155.86, -143), 0.75 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/io_drivers_pp/PP_OUT31' on IN5.CU at (155.46, -142.6), 0.75 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/pp_connector/PP_LED0_DATA' on IN5.CU at (154.34, -141.48), 0.75 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
- '/pp_connector/PP_LED1_DATA' on IN5.CU at (154.96, -142.1), 0.75 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=split%40IN6.CU%3AMGT_1V2%7CMGT_1V8 serves each with its own layer_image region; all of them lie in x 152.97..160.76, y -148.27..-140.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.
split@IN6.CU:P0V85|P1V2'/DDR4-PS.A11' crosses the split between the P0V85 and P1V2 planes on IN6.CU at 1 place, all with a plane on the track's other side (fastest: /DDR4-PS.A11 at 100 ps 10-90 %, ASSUMED)
On IN6.CU the P0V85 and P1V2 planes part, and '/DDR4-PS.A11' crosses from one to the other at 1 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 1 of the 1 crossing(s) the track's other neighbour carries a plane, which the return can use there. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 17% 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).
- '/DDR4-PS.A11' on IN5.CU at (161.1, -122.32), 0.1 mm; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=split%40IN6.CU%3AP0V85%7CP1V2 serves each with its own layer_image region; all of them lie in x 160.05..162.15, y -123.32..-121.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@IN7.CU_GND:222.84,-130.34'/power-supply-1/PMBUS_SDA' crosses where the outline of the GND plane on IN7.CU_GND is drawn back, at 1 place, the longest 0.35 mm (fastest: /power-supply-1/PMBUS_SDA at 10 ns 10-90 %, suggested by its name)
Along '/power-supply-1/PMBUS_SDA' on IN6.CU, the GND plane on IN7.CU_GND has 0.35 mm under the track with no copper, at (222.84, -130.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 63.33..236.62, y -185.38..-79.48 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- '/power-supply-1/PMBUS_SDA' on IN6.CU at (222.84, -130.34), 0.35 mm over no copper; other side: P1V8 on IN5.CU, 0.5 mm from the track against 0.1 mm to IN7.CU_GND: 83% of the return on IN7.CU_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AGND%40IN7.CU_GND%3A222.84%2C-130.34 serves each with its own layer_image region; all of them lie in x 221.67..224.02, y -131.34..-129.34 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@IN7.CU_GND:223.7,-130.34'/power-supply-1/PMBUS_SDA' crosses where the outline of the GND plane on IN7.CU_GND is drawn back, at 1 place, the longest 0.35 mm (fastest: /power-supply-1/PMBUS_SDA at 10 ns 10-90 %, suggested by its name)
Along '/power-supply-1/PMBUS_SDA' on IN6.CU, the GND plane on IN7.CU_GND has 0.35 mm under the track with no copper, at (223.7, -130.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 63.33..236.62, y -185.38..-79.48 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- '/power-supply-1/PMBUS_SDA' on IN6.CU at (223.7, -130.34), 0.35 mm over no copper; other side: P1V8 on IN5.CU, 0.5 mm from the track against 0.1 mm to IN7.CU_GND: 83% of the return on IN7.CU_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AGND%40IN7.CU_GND%3A223.7%2C-130.34 serves each with its own layer_image region; all of them lie in x 222.52..224.87, y -131.34..-129.34 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@IN7.CU_GND:98.8,-110.96'/SFP0_SDA' crosses where the outline of the GND plane on IN7.CU_GND is drawn back, at 1 place, the longest 0.13 mm (fastest: /SFP0_SDA at 10 ns 10-90 %, suggested by its name)
Along '/SFP0_SDA' on IN6.CU, the GND plane on IN7.CU_GND has 0.13 mm under the track with no copper, at (98.8, -110.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 63.33..236.62, y -185.38..-79.48 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- '/SFP0_SDA' on IN6.CU at (98.8, -110.96), 0.13 mm over no copper; other side: P1V8 on IN5.CU, 0.5 mm from the track against 0.1 mm to IN7.CU_GND: 83% of the return on IN7.CU_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AGND%40IN7.CU_GND%3A98.8%2C-110.96 serves each with its own layer_image region; all of them lie in x 97.8..99.8, y -112.02..-109.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@IN7.CU_GND:98.8,-111.58'/SFP0_SDA' crosses where the outline of the GND plane on IN7.CU_GND is drawn back, at 1 place, the longest 0.12 mm (fastest: /SFP0_SDA at 10 ns 10-90 %, suggested by its name)
Along '/SFP0_SDA' on IN6.CU, the GND plane on IN7.CU_GND has 0.12 mm under the track with no copper, at (98.8, -111.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 63.33..236.62, y -185.38..-79.48 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- '/SFP0_SDA' on IN6.CU at (98.8, -111.58), 0.12 mm over no copper; other side: P1V8 on IN5.CU, 0.5 mm from the track against 0.1 mm to IN7.CU_GND: 83% of the return on IN7.CU_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AGND%40IN7.CU_GND%3A98.8%2C-111.58 serves each with its own layer_image region; all of them lie in x 97.8..99.8, y -112.64..-110.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:MGT_1V2@IN6.CU:168.75,-145.85'/io_drivers_pp/PP_OUT28' crosses where the outline of the MGT_1V2 plane on IN6.CU is drawn back, at 1 place, the longest 5.65 mm (fastest: /io_drivers_pp/PP_OUT28 at 100 ps 10-90 %, ASSUMED)
Along '/io_drivers_pp/PP_OUT28' on IN5.CU, the MGT_1V2 plane on IN6.CU has 5.65 mm under the track with no copper, at (168.75, -145.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. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.82 mm). No hole cleared it: the outline of the pour at x 151.62..201.62, y -161.63..-135.38 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 17% 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).
- '/io_drivers_pp/PP_OUT28' on IN5.CU at (168.75, -145.85), 5.65 mm, running ALONG the bare copper for 3.82 mm, not across it over no copper; other side: GND on IN4.CU_GND, 0.1 mm from the track against 0.5 mm to IN6.CU: 17% of the return on IN6.CU
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3AMGT_1V2%40IN6.CU%3A168.75%2C-145.85 serves each with its own layer_image region; all of them lie in x 165.48..171.1, y -149.11..-143.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:routed@IN5.CU|IN6.CU6 nets on IN6.CU cross the tracks routed through the P1V8 pour on IN5.CU at 14 places, the longest 0.85 mm (fastest: /SFP0_RSSI at 100 ps 10-90 %, ASSUMED)
The P1V8 pour on IN5.CU is cleared round tracks routed through it, and tracks on IN6.CU, which take that pour as their reference, cross them: for the width of each cut the return has no plane under it and detours round the cut. 14 place(s) on 6 net(s). 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. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 17% 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).
- '/io_drivers_fp/F_FP_O3' on IN6.CU at (134.97, -133.43), 0.85 mm over copper of /pp_connector/PP_ID1, not a plane, to the end of the track; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/io_drivers_fp/F_FP_O2' on IN6.CU at (132.5, -130.55), 0.79 mm over copper of /fpga/USER_UFL0_P, /fpga/USER_UFL0_N, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/io_drivers_fp/F_FP_O3' on IN6.CU at (132.5, -131.16), 0.79 mm over copper of /fpga/USER_UFL0_N, /fpga/USER_UFL0_P, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/io_drivers_fp/F_FP_O5' on IN6.CU at (131.37, -131.04), 0.79 mm over copper of /fpga/USER_UFL1_N, /fpga/USER_UFL1_P, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/io_drivers_fp/F_FP_O5' on IN6.CU at (132.5, -132.16), 0.79 mm over copper of /fpga/USER_UFL0_N, /fpga/USER_UFL0_P, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/io_drivers_fp/F_FP_O3' on IN6.CU at (131.39, -130.05), 0.7 mm over copper of /fpga/USER_UFL1_N, /fpga/USER_UFL1_P, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/io_drivers_fp/F_FP_O2' on IN6.CU at (131.37, -129.58), 0.61 mm over copper of /fpga/USER_UFL1_P, /fpga/USER_UFL1_N, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/io_drivers_fp/F_FP_O2' on IN6.CU at (134.77, -132.82), 0.56 mm over copper of /pp_connector/PP_ID1, not a plane, to the end of the track; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/SFP0_RSSI' on IN6.CU at (131.37, -129.08), 0.56 mm over copper of /fpga/USER_UFL1_P, /fpga/USER_UFL1_N, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/SFP0_RSSI' on IN6.CU at (132.5, -129.08), 0.56 mm over copper of /fpga/USER_UFL0_P, /fpga/USER_UFL0_N, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/fpga/F_FP_OE0' on IN6.CU at (131.37, -128.68), 0.56 mm over copper of /fpga/USER_UFL1_N, /fpga/USER_UFL1_P, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- '/fpga/F_FP_OE0' on IN6.CU at (132.5, -128.68), 0.56 mm over copper of /fpga/USER_UFL0_N, /fpga/USER_UFL0_P, not a plane; other side: GND on IN7.CU_GND, 0.1 mm from the track against 0.5 mm to IN5.CU: 17% of the return on IN5.CU
- and 2 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/97/reference-planes?group=void%3Arouted%40IN5.CU%7CIN6.CU serves each with its own layer_image region; all of them lie in x 130.09..136.37, y -134.43..-127.28 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 number | Maker | Description | Where |
|---|---|---|---|
| 0466.750NR | LITTELFUSE | Very Fast-Acting Surface Mount Thin Film Fuse, Size 1206, Series 466 | F1 |
| 1888247-1 | TYCO ELECTRONICS | 20 Position, Pitch 0.8mm SFP+ Receptacle (Small Form-factor Pluggable) | J1 |
| 232270672004L | YAGEO PHYCOMP | ±1% 0.0625W ±100ppm/°C General Purpose Thick Film Chip Resistor | R168 |
| 24AA025E48T-I/OT | MICROCHIP TECHNOLOGY | 1.7V-5.5V, 2K I2C Serial EEPROM with EUI-48™ Node Identity; Cascadable | IC12 |
| 24AA64T-I/MS | MICROCHIP TECHNOLOGY | 1.7V-5.5V, 64K (8K x 8-bit) I2C Serial EEPROM | IC11 |
| 39-30-0060 | MOLEX | 4.20mm (.165") Pitch Mini-Fit Jr. Header, Dual Row, Right Angle with Snap-in Plastic Peg PCB Lock, 6 Circuits | J11 |
| 435451019820 | WURTH | SMT Washable Tactile Switch SPST-NO Top Actuated Surface Mount | PB1 |
| 500075-1517 | MOLEX | USB Mini-B Serie Type 2, Through Hole Straight Receptacle | J14 |
| 500R07S5R6BV4T | JOHANSON TECHNOLOGY | ±0.1pF 50V C0G/NP0 Ultra High-Q SMD Multilayer Capacitor | C346 |
| 515-1064-807F | DIALIGHT | Right Angle Tri-Level 2.5mm Round Light Pipe , with Black Shild for Middel Pipe | LP1 |
| 742792040 | WURTH ELEKTRONIK | ±25% 2A SMD EMI Suppression Chip Ferrite Bead (WE-CBF Series) | L14 |
| 74737-0009 | MOLEX | 1x1 Press Fit Cage for Use with SFP Connector (Small Form-factor Pluggable) | Cage1 |
| 87832-1420 | MOLEX | 2.00mm (.079") Pitch Milli-Grid™ Header, Surface Mount, Vertical, Shrouded, 14 Circuits, with Locking Windows and Centre Polarization Slot, PCB Locator | J7 |
| AMK325ABJ337MM-P | TAIYO YUDEN | ±20% 4V X5R SMD Multilayer Chip Ceramic Capacitor | C74 |
| C0402C101J5GACTU | KEMET | ±5% 50V C0G/NP0 SMD Multilayer Chip Ceramic Capacitor | C332 |
| C0402C270J5GACTU | KEMET | ±5% 50V C0G/NP0 SMD Multilayer Chip Ceramic Capacitor | C17 |
| C1005X7R1C224K050 | TDK | ±10% 16V X7R SMD Multilayer Chip Ceramic Capacitor | C142 |
| C1210C224F3GAC | KEMET | ±1% 25V C0G/NP0 SMD Multilayer Chip Ceramic Capacitor | C307 |
| C1808X102KHRAC | KEMET | ±10% 3kV X7R High Voltage SMD Multilayer Chip Ceramic Capacitor | C331 |
| CP2105-F01-GM | SILICON LABS | Single-Chip USB to Dual UART Bridge | IC35 |
| CPF0402B2K1E | TE CONNECTIVITY | ±0.1% 0.063W ±25ppm/°C Thin Film Precision Resistor | R267 |
| CRCW0402210KFK | VISHAY | ±1% 0.063W ±100ppm/°C General Purpose Thick Film Chip Resistor | R153 |
| CRCW0402402RFK | VISHAY | ±1% 0.063W ±100ppm/°C General Purpose Thick Film Chip Resistor | R161 |
| CRCW0402698RFK | VISHAY | ±1% 0.063W ±100ppm/°C General Purpose Thick Film Chip Resistor | R265 |
| CRCW040290K9FK | VISHAY | ±1% 0.063W ±100ppm/°C General Purpose Thick Film Chip Resistor | R129 |
| CX3225SB48000D0FPJC1 | KYOCERA | Tolerance: ±10ppm, Stability: ±15ppm, 8pF, -40°C to +85°C, Surface Mount Crystal | Q1 |
| EEFGX0D471R | PANASONIC | ±20% 2V ESR 0R003 Polymer Aluminum Electrolytic Capacitor | C108 |
| HSB18-232310 | SAME SKY | Heat Sink BGA Aluminum Alloy 3.7W @ 75°C Top Mount | HS1 |
| LMK1D2102RGT | TEXAS INSTRUMENTS | Low Additive Jitter LVDS Buffer | IC4 |
| LMZ31704RVQT | TEXAS INSTRUMENTS | 4A SIMPLE SWITCHER® Power Module with 2.95V-17V Input and Current Sharing in QFN Package | IC29 |
| LSHM-120-02.5-L-DV-A-S | SAMTEC | 40 Contacts, Pitch 0.5mm, Razor Beam™ Vertical High Speed Hermaphroditic Strip, with Shield, Lead Style-02.5 | J10 |
| MMSZ4683 | ON SEMICONDUCTOR | 3V 500mW Zener Voltage Regulator | D17 |
| MTLW-103-07-L-S-250 | SAMTEC | 3 Contacts, Pitch 2.54mm, Single Row Through Mount Straight Header (Post Lead = 6.35mm, Tail Lead 3.05mm, Insulator 1.52mm) | J12 |
| NRC06F16R0TRF | NIC COMPONENT | ±1% 0.1W ±100ppm/°C General Purpose Thick Film Chip Resistor | R130 |
| PA2607.181NL | PULSE ELECTRONICS | ±15% 62A SMT Power Inductor | L3 |
| PCA9306DCU | TEXAS INSTRUMENTS | Dual Bidirectional I2C Bus and SMBus Voltage-Level Translator | IC37 |
| PNM0402E5000BST1 | VISHAY | ±0.1% 0.05W ±25ppm/°C Surface Mount Precision Thin Film Non-Magnetic Resistor | R209 |
| PRTR5V0U2X | NXP SEMICONDUCTORS | 5.5V Ultra Low Capacitance (1pF) Double Rail-to-Rail ESD Protection Diode (8kV) | D21 |
| RN73C1J267RBTDF | TYCO HOLSWORTHY | ±0.1% 0.063W ±10ppm Thin Film Chip Resistor | R281 |
| RN73C1J845RBTDF | TYCO HOLSWORTHY | ±0.1% 0.063W ±10ppm Thin Film Chip Resistor | R282 |
About this design
- Design
- WREN IE — OHWR0092 R4
- Designed in
- KiCad EDA
- Board
- 10 copper layers, 174 × 111.2 mm, 785 components, 952 nets
- Licence
- CERN-OHL-W-2.0
- Source
- https://edms.cern.ch/item/EDA-04968-V4-0/0 at commit
EDMS EDA-049 - Attribution
- CERN EDMS item EDA-04968-V4-0 'WREN-Ie / QSPI24': document 3521789 v.1, retrieved 2026-10-23T04:40:43Z. Converted by E-Sharp with KiCad 10.0.6 (zones refilled); variant QSPI24 (V4-0); fit status and part identity from CERN's assembly BOM EDA-04968-V4-0_pcb-mat.xls.
- Reviewed with
- Probe by E# (E-Sharp AB)