editor's blog
Subscribe Now

Getting a Jump on Power Integrity

Apache announced their RTL Power Model (RPM) recently. The idea is that it lets designers understand their power and power integrity issues earlier in the design cycle. “Early,” however, is a relative term. Unlike some technologies that move such estimates to the architectural phase, this moves the capability from post-layout to RTL. That’s not to take anything away from it – they claim it gives designers a six-month jump on the problem.

The way this works involves a number of Apache tools, starting with PowerArtist. Actually, in order for PowerArtist to do its thing, one other piece has to be in place: a so-called PACE model.

A PACE model provides an estimate of a cell’s parasitics for a given technology. It’s done once, along with the development of the cell, and the PACE model becomes part of the designer’s kit.

That PACE model, along with other technology information, then feeds PowerArtist, which looks through the RTL and infers cells for the circuit. Even though no layout has been done, by knowing the cells, you can call up the PACE model and estimate the parasitics and power implications.

You then simulate your design, and PowerArtist creates the RPM. It does this by calculating an estimate of the energy consumed by each cell as it runs and dividing that by the clock period to derive a power-per-cycle metric for each cell. Those are summed together, and, from that, the tool can identify both power peaks and events with rapid current changes (high di/dt).

For each of these types of event, they define a “frame” around it – roughly 10 or so clock cycles, which includes both the lead-up to and follow-up from the event. The RPM consists of these frames, accompanied by various libraries and pieces of proprietary information that can then be delivered to the RedHawk tool.

With this information, RedHawk will build a current waveform for each clock cycle in each frame. With that waveform, you can use RedHawk to play with early power grid ideas or to start working on chip/package co-design issues, focusing only on those events known to be a challenge.

So this lets you get started dealing with potential power integrity issues long before the layout is available to give you exact results. Obviously, the analysis will need to be repeated for confirmation when the layout is ready, but, hopefully, by then, the major issues will already have been addressed.

More info in their release

Leave a Reply

featured blogs
Jan 24, 2020
Someone has created a song by taking Pi, assigning each number to a note, and adding harmonies. The result is strangely captivating....
Jan 24, 2020
[From the last episode: We looked at the different ways memory can be organized in different kinds of systems.] Let'€™s look at a scenario: you run a restaurant, but you'€™re short on funds to hire people. So you'€™re your own chief cook and bottle-washer. You do everyt...
Jan 23, 2020
Embedded design trends typically revolve around three main ideas: faster data rates, smaller form factors and cost-effective solutions. Those design trends drive the theme for the 2020 Embedded Tech Trends forum: The Business and Technology Forum for Critical and Intelligent ...
Jan 22, 2020
Master the design and verification of next gen transport: Part One – Overview Master the design and verification of next gen transport: Part Two – High-Level Synthesis Master the design and verification of next gen transport: Part Three – Functional Safety M...

Featured Video

Automotive Trends Driving New SoC Architectures -- Synopsys

Sponsored by Synopsys

Today’s automotive trends are driving new design requirements for automotive SoCs targeting ADAS, gateways, connected cars and infotainment. Find out why it is essential to use pre-designed, pre-verified, reusable automotive-optimized IP to meet such new requirements and accelerate design time.

Drive Your Next Design to Completion Today with DesignWare IP® for Automotive SoCs