vyges-upf — power intent
Installed with the physical engines. Install it with
vyges install physical, then runvyges physical upf. It is also a standalonevyges-upfbinary on your PATH (the integration contract for flow authors). Source: vyges-tools/upf.
A chip with several supplies needs its power intent written down: which logic sits in which
domain, and what guards each crossing. vyges-upf puts that intent (UPF) into the design database,
where floorplanning, power-grid generation and timing read it, and makes it physical.
| command | does |
|---|---|
run | the UPF read into the database: power domains, logic ports, power switches, isolation and level-shifter strategies, domain areas and voltages |
write | the database’s power intent written back as UPF |
eval | the intent made physical: a fence region and group per domain, the domain hierarchy, isolation cells and level shifters between domains |
Run it
vyges install physical # one-time
vyges physical upf run synth.odb intent.upf -o with-intent.odb
vyges physical upf eval with-intent.odb --liberty cells.lib -o domains.odb
vyges physical upf write domains.odb -o check.upf
eval chooses the isolation cells and level shifters from the Liberty libraries given, in the
order given. --trace prints one line per database write, in the order made.
What it accepts
A UPF file is Tcl. run reads the UPF commands for domains, ports, switches, isolation, level
shifters, domain areas and voltages, with keys abbreviated to any unique prefix. A variable or
command substitution, or any other Tcl command, is refused (exit 3) rather than guessed at, and an
error stops the read with exit 2 and writes nothing.