Many-Channel Centralized DMA Controller with AMBA AXI Interface
Considerations for writing UPF for a hierarchical flow
Jeffrey Lee and Mary Ann White (Synopsys)
4/6/2012 11:01 AM EDT
Introduction
Writing power intent for a design using the IEEE 1801 Unified Power Format (UPF) is generally an easy and straight-forward task. If the design will be optimized in a flat fashion (e.g. the entire design is optimized top-down in a single session), then writing the power intent is fairly simple.
Situations such as being too rigid in where your power management cells need to be implemented and writing power intent for hierarchical designs can make writing UPF a much more difficult task. This article details the considerations that you need to take into account when writing UPF for a hierarchical design methodology.
![]() |
E-mail This Article | ![]() |
![]() |
Printer-Friendly Page |
|
Synopsys, Inc. Hot IP
Related Articles
- SoC Design: Hierarchical Flow Only Way to Go
- Four ways to build a CAD flow: In-house design to custom-EDA tool
- Capitalizing on the Architectural Flexibility of FPGAs with RISC-V and a Simplified Programming Flow
- Understanding Logic Equivalence Check (LEC) Flow and Its Challenges and Proposed Solution
- UPF Constraint coding for SoC - A Case Study
New Articles
- When Traceability Catches What Verification Does Not
- Implementing C model integration using DPI in SystemVerilog
- Stop-For-Top IP model to replace One-Stop-Shop by 2025... and support the creation of successful Chiplet business
- Lossless Compression Efficiency of JPEG-LS, PNG, QOI and JPEG2000: A Comparative Study
- Four ways to build a CAD flow: In-house design to custom-EDA tool