vyges-pad — the IO pad ring and bumps

Physical construction — opt-in, and not part of vyges install loom. These engines build the design database that the sign-off and verification engines read, so they install as their own group:

vyges install physical   # all six
vyges install pad        # just this one

It is also a standalone vyges-pad binary on your PATH, which is what the dispatch calls and what a flow author targets directly. Source: vyges-tools/pad.

vyges-pad builds the chip’s outer edge: the pad ring and its cells, corner and filler pads, the bump array for a flip-chip part, and the RDL routes that connect bumps to pads.

Run it

vyges pad place    design.odb --config pads.json
vyges pad ring     design.odb --config pads.json
vyges pad connect  design.odb --config pads.json

Where it sits

Floorplanned database in, a ringed and bumped database out. It is the outermost structure on the die, and the one that decides where the package can reach.

Known bounds

• Row bounds for pad placement are computed per strategy; a derived class shadowing the row-start and row-end accessors is the class of bug this engine has been audited for specifically.

See the full CLI reference (generated from --help and --describe).