rules module#
UG863’s spacing between the VP1002 to Micron LPDDR4 link’s signal groups.
Source: AMD, Versal Adaptive SoC PCB Design User Guide, UG863 v1.12 (2026-06-16), “Physical Design Rules for LPDDR4/4x Signals”, Table 24, https://docs.amd.com/r/en-US/ug863-versal-pcb-design.
Spacing#
Table 24 gives spacing in multiples of H, the height to the nearest ground
plane, and relaxes it “under adaptive SoC or LPDDR4/4x device”. Each rule
here is trace to trace only, so pads and vias keep the structure’s own
clearance. The ball-field tag (ball_field.BallFieldTag) stands
for “under the device”. Only a pair’s segment inside a ball field carries
it (ball_field.BallFieldPairTag, on the strobe escapes); a
single-ended line carries no tag, so it takes the open values under the
device too, the larger ones:
Table 24 relation |
Open |
Under device |
|---|---|---|
Data/strobe between different bytes |
7 H |
2 H |
CAC/clock to data/strobe, same channel |
7 H |
2 H |
Signals in one channel to signals in the other |
7 H |
2 H |
Data to strobe, same byte |
5 H |
1 H |
CAC to clock, same channel |
5 H |
2 H |
Data to data, same byte; CAC to CAC, same channel |
2 H |
1 H |
spacing_rules() writes the first five rows as rules between the
spacing groups (each byte lane, and each channel’s CAC and clock) and
between a group’s pairs and its other nets. The last row and the 1 H cases
are left to the structures, whose clearances are larger: SE-46’s 6.2 mil
against 2 H = 5.0 mil, and the ball-field pair’s clearance of 3.5 mil
against 1 H = 2.5 mil under the device, which is also under the
fabrication floor of 2.8 mil. Rules that keep one net from another are
protections, so they sit above the ball-field structure
(ball_field.ball_field_rules(), at 4) at 5 to 7, the larger
clearance higher.
- class ByteLane0Tag[source]#
Bases:
LPDDR4GroupTagByte lane 0: channel A, byte 0.
- class ByteLane1Tag[source]#
Bases:
LPDDR4GroupTagByte lane 1: channel A, byte 1.
- class ByteLane2Tag[source]#
Bases:
LPDDR4GroupTagByte lane 2: channel B, byte 0.
- class ByteLane3Tag[source]#
Bases:
LPDDR4GroupTagByte lane 3: channel B, byte 1.
- class CacClockATag[source]#
Bases:
LPDDR4GroupTagChannel A’s command, address, control and clock.
- class CacClockBTag[source]#
Bases:
LPDDR4GroupTagChannel B’s command, address, control and clock.
- BYTE_LANE_TAGS: tuple[type[LPDDR4GroupTag], ...] = (<class 'jitxexamples.jumpstart_kits.js4_fpga_lpddr4.rules.ByteLane0Tag'>, <class 'jitxexamples.jumpstart_kits.js4_fpga_lpddr4.rules.ByteLane1Tag'>, <class 'jitxexamples.jumpstart_kits.js4_fpga_lpddr4.rules.ByteLane2Tag'>, <class 'jitxexamples.jumpstart_kits.js4_fpga_lpddr4.rules.ByteLane3Tag'>)#
Spacing group tags of the four byte lanes, in byte-lane order.
- CAC_CLOCK_TAGS: tuple[type[LPDDR4GroupTag], ...] = (<class 'jitxexamples.jumpstart_kits.js4_fpga_lpddr4.rules.CacClockATag'>, <class 'jitxexamples.jumpstart_kits.js4_fpga_lpddr4.rules.CacClockBTag'>)#
Spacing group tags of the two channels’ CAC and clock, A then B.
- spacing_rules(byte_lanes, cac_clock, pairs, height)[source]#
Tag the spacing groups and return UG863’s spacing rules between them.
- Parameters:
- Return type: