4.7. Power¶
Hammer supports RTL, post-synthesis, and post-P&R power analysis. It provides a simple API to add flags to the power tool call and automatically passes in collateral to the power tool from the other tool steps.
This action requires a tool plugin to implement HammerPowerTool.
4.7.1. Power Setup Keys¶
Namespace:
vlsi.corepower_tool_path- Set to the directory containing the tool plugin directory for the power tool, typically
/path/to/tool_plugin/power. This will be the parent directory of the directory containing__init__.pyanddefaults.yml.
- Set to the directory containing the tool plugin directory for the power tool, typically
power_tool- Actual name of the power tool that is setup in the directory
power_tool_path, e.g.voltus
- Actual name of the power tool that is setup in the directory
4.7.2. Simulation Input Keys¶
Namespace:
power.inputsdatabase(str)- Path to the place and route database of the design to be analyzed. This path may be relative to the directory in which
hammer-vlsiis called.
- Path to the place and route database of the design to be analyzed. This path may be relative to the directory in which
tb_name(str)- The name of the testbench/test driver in the simulation.
tb_dut(str)- Hierarchical path to the to top level instance of the “dut” from the testbench.
spefs([str])- List of paths to all spef (parasitic extraction) files for the design. This list may include a spef file per MMMC corner. Paths may be relative to the directory in which
hammer-vlsiis called.
- List of paths to all spef (parasitic extraction) files for the design. This list may include a spef file per MMMC corner. Paths may be relative to the directory in which
waveforms([str])- List of paths to waveforms to be used for dynamic power analysis. Paths may be relative to the directory in which
hammer-vlsiis called.
- List of paths to waveforms to be used for dynamic power analysis. Paths may be relative to the directory in which
start_times([TimeValue])- List of analysis start times corresponding to each of the
waveformsused for dynamic power analysis.
- List of analysis start times corresponding to each of the
end_times([TimeValue])- List of analysis end times corresponding to each of the
waveformsused for dynamic power analysis.
- List of analysis end times corresponding to each of the
saifs([str])- List of paths to SAIF (activity files) for dynamic power analysis. Generally generated by a gate-level simulation. Paths may be relative to the directory in which
hammer-vlsiis called.
- List of paths to SAIF (activity files) for dynamic power analysis. Generally generated by a gate-level simulation. Paths may be relative to the directory in which
extra_corners_only(bool)- If overridden to
true, the power tool will report for only the extra MMMC corners, saving runtime. The typical use case is to only report power and rail analysis for a typical/nominal corner.
- If overridden to
input_files([str])- A list of the paths to the design inputs files (HDL or netlist) for power analysis.
sdc(str)- Path to SDC input file.
report_configs([dict])- List of report configs that specify
PowerReportstructs.
- List of report configs that specify
level(FlowLevel)- Power analysis mode for different levels of the VLSI flow. The available options are
rtl,syn, andpar.
- Power analysis mode for different levels of the VLSI flow. The available options are
top_module(str)- Top RTL module for power analysis.
4.7.3. Power Inputs¶
Hammer’s power analysis can be run with an RTL input, or post-synthesis or post-place-and-route (and with corresponding simulations).
Auto-translation of of Hammer IR to the power tool from those outputs are accomplished using the sim-rtl-to-power, syn-to-power, sim-syn-to-power, par-to-power, and sim-par-to-power actions, as demonstrated below.
The required files for power analysis (database, SAIF, SPEF, etc.) are generated and piped to the power tool from the pre-requisite action’s outputs.
4.7.4. Power Outputs¶
The power tool outputs static and active power estimations into the OBJ_DIR/power-rundir/ directory. Exact report format may vary by tool used.
4.7.5. Power Commands¶
RTL Power Analysis:
RTL Sim
hammer-vlsi -e env.yml -p config.yml --obj_dir OBJ_DIR sim-rtl
Simulation to Power
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/sim-rundir/sim-rtl-output.json -o OBJ_DIR/sim-rtl-to-power_input.json --obj_dir OBJ_DIR sim-rtl-to-power
Power
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/sim-rtl-to-power_input.json --obj_dir OBJ_DIR power-rtl
Post-synthesis Power Analysis:
Syn to Power
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/syn-rundir/syn-output.json -o OBJ_DIR/syn-to-power_input.json --obj_dir OBJ_DIR syn-to-power
Syn to Simulation
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/syn-rundir/syn-output.json -o OBJ_DIR/syn-to-sim_input.json --obj_dir OBJ_DIR syn-to-sim
Post-Syn Gate Level Sim
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/syn-to-sim_input.json --obj_dir OBJ_DIR sim-syn
Simulation to Power
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/sim-rundir/sim-syn-output.json -o OBJ_DIR/sim-syn-to-power_input.json --obj_dir OBJ_DIR sim-syn-to-power
Power
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/syn-to-power_input.json -p OBJ_DIR/sim-syn-to-power_input.json --obj_dir OBJ_DIR power-syn
Post-P&R Power Analysis:
P&R to Power
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/par-rundir/par-output.json -o OBJ_DIR/par-to-power_input.json --obj_dir OBJ_DIR par-to-power
P&R to Simulation
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/par-rundir/par-output.json -o OBJ_DIR/par-to-sim_input.json --obj_dir OBJ_DIR par-to-sim
Post-P&R Gate Level Sim
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/par-to-sim_input.json --obj_dir OBJ_DIR sim-par
Simulation to Power
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/sim-rundir/sim-par-output.json -o OBJ_DIR/sim-par-to-power_input.json --obj_dir OBJ_DIR sim-par-to-power
Power
hammer-vlsi -e env.yml -p config.yml -p OBJ_DIR/par-to-power_input.json -p OBJ_DIR/sim-par-to-power_input.json --obj_dir OBJ_DIR power-par