Visible to Intel only — GUID: mwh1410384109189
Ixiasoft
1.1. Comparison of the EPE and the Intel® Quartus® Prime Power Analyzer
1.2. Power Estimations and Design Requirements
1.3. Power Analyzer Walkthrough
1.4. Inputs for the Power Analyzer
1.5. Power Analysis in Modular Design Flows
1.6. Power Analyzer Compilation Report
1.7. Scripting Support
1.8. Power Analysis Revision History
1.4.2.1. Waveforms from Supported Simulators
1.4.2.2. .vcd Files from Third-Party Simulation Tools
1.4.2.3. Signal Activities from RTL (Functional) Simulation, Supplemented by Vectorless Estimation
1.4.2.4. Signal Activities from Vectorless Estimation and User-Supplied Input Pin Activities
1.4.2.5. Signal Activities from User Defaults Only
1.5.1. Complete Design Simulation
1.5.2. Modular Design Simulation
1.5.3. Multiple Simulations on the Same Entity
1.5.4. Overlapping Simulations
1.5.5. Partial Simulations
1.5.6. Node Name Matching Considerations
1.5.7. Glitch Filtering
1.5.8. Node and Entity Assignments
1.5.9. Default Toggle Rate Assignment
1.5.10. Vectorless Estimation
2.5.1. Clock Power Management
2.5.2. Pipelining and Retiming
2.5.3. Architectural Optimization
2.5.4. I/O Power Guidelines
2.5.5. Memory Optimization (M20K/MLAB)
2.5.6. DDR Memory Controller Settings
2.5.7. DSP Implementation
2.5.8. Reducing High-Speed Tile (HST) Usage
2.5.9. Unused Transceiver Channels
2.5.10. Periphery Power reduction XCVR Settings
Visible to Intel only — GUID: mwh1410384109189
Ixiasoft
1.7.1. Running the Power Analyzer from the Command–Line
The executable to run the Power Analyzer is quartus_pow. For a complete listing of all command–line options supported by quartus_pow, type the following command at a system command prompt:
quartus_pow --helpor
quartus_sh --qhelp
The following lists the examples of using the quartus_pow executable. Type the command listed in the following section at a system command prompt:
Note: These examples assume that operations are performed on Intel® Quartus® Prime project called sample.
- To instruct the Power Analyzer to generate a EPE File:
quartus_pow sample --output_epe=sample.csv ←
- To instruct the Power Analyzer to generate a EPE File without performing the power estimate:
quartus_pow sample --output_epe=sample.csv --estimate_power=off ←
- To instruct the Power Analyzer to use a .vcd as input (sample.vcd):
quartus_pow sample --input_vcd=sample.vcd ←
- To instruct the Power Analyzer to use two .vcd files as input files (sample1.vcd and sample2.vcd), perform glitch filtering on the .vcd and use a default input I/O toggle rate of 10,000 transitions per second:
quartus_pow sample --input_vcd=sample1.vcd --input_vcd=sample2.vcd \ --vcd_filter_glitches=on --\ default_input_io_toggle_rate=10000transitions/s
- To instruct the Power Analyzer to not use an input file, a default input I/O toggle rate of 60%, no vectorless estimation, and a default toggle rate of 20% on all remaining signals:
quartus_pow sample --no_input_file --default_input_io_toggle_rate=60% \ --use_vectorless_estimation=off --default_toggle_rate=20%
Note: No command–line options are available to specify the information found on the Power Analyzer Settings Operating Conditions page. Use the Intel® Quartus® Prime GUI to specify these options.
The quartus_pow executable creates a report file, <revision name> .pow.rpt. You can locate the report file in the main project directory. The report file contains the same information that the Power Analyzer Compilation Report.
Related Information