Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

[SOLVED] CPF and UPF in low power

Status
Not open for further replies.

Thomas Robinson

Newbie level 3
Newbie level 3
Joined
Jan 21, 2013
Messages
3
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Visit site
Activity points
1,300
Hi,

Can any body help me to understand what is the difference between CPF and UPF format in low power synthesis.

Thanks in advance
-Thomas
 

With both format, you should be able to do the same.
UPF also used by Magma tool suit.
 

Adding the above said,
These (i.e. UPF and CPF) power-formats are recognised through-out the industry with which
you can specify power-gating considerations for a design.

UPF and CPF corresponding to any lowpower design being developed in RTL stage and referred till end (i.e. PG-netlist).

Lowpower Cells which are specified in the UPF or CPF are inserted separately in the netlist.
Thus Power Compilers (Cadence RC who works on CPF ) and (Synopsys DC which works on UPF) than reads the power
intent and insert the lowpower cells in the netlist. Thus at GLS it can be checked power-domains are following the
power-up and power-down sequence correctly.

UPF as said is IEEE standard and 1.0, 2.0 are currently available.
CPF is mantained by Si2 group and versions 1.0, 1.0e, 1.1 and 2.0 are currently available.
 
Mentor, Synopsys, and Cadence tools all support the power format from IEEE. Of those three vendors, only Cadence supports CPF.
 

Yes. Due to this
If in my SoC few IPs are UPF based and other are CPF based than it is difficult to merge than at SoC level unless
one of the power-format is converted (manually i feel) to another and than go on with verification but here new power-
intent needs to be re-checked for completeness.

Also if i am using Cadence tools for frontend and Synopsys tools for backend than again CPF to UPF conversion is needed
which again raise concern of complete functional testing.

Thus it is now needed that compatibility between CPF 2.0 and UPF 2.1 should be undentified.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top