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.

Place and Route - Slew rate outbound

Status
Not open for further replies.

dshoter13

Member level 4
Joined
Oct 20, 2014
Messages
72
Helped
4
Reputation
8
Reaction score
4
Trophy points
8
Activity points
619
Hi guys,

I am trying to place and route a digital design. During the pre place time analysis, the software (Innovus) issues a warning alerting that the slew rate of the several cells is out of bounds with regard to the value specified in timing lib. The weird thing is that I am specifying a maximum slew rate (max transition time) of 0.6ns, while the min bound of the lib is 0.5 ns. Unfortunately, during time analysis the Innovus software is considering that the slew rate is 0.25ns. My user design rule violations are less stricter than the ones specified by the tech (max capacitance etc).

Any suggestions regarding this?

Thank you for your time.

With best regards

P.S. - Although this software is different from SoC Encounter, almost all the commands and warnings are the same
 

Hi, I have seen the same behavior in Innovus for both GF14 and TSMC16. For me this warning is mostly related to the IO cells. A typical time for an IO to transition is ~0.7ns, and the first standard cell connected to the IO will always be 'out of bounds'. It is not a big deal as long as you understand what is happening and that the software will estimate/extrapolate the behavior of the standard cell.
 

Well, this is quite similar to my situation. However, I get such warnings only regarding IO cells and not the sub-sequent std cells.
Thank you very much for your time.

With kind regards.

Hi, I have seen the same behavior in Innovus for both GF14 and TSMC16. For me this warning is mostly related to the IO cells. A typical time for an IO to transition is ~0.7ns, and the first standard cell connected to the IO will always be 'out of bounds'. It is not a big deal as long as you understand what is happening and that the software will estimate/extrapolate the behavior of the standard cell.
 

have you tried to set a driver cell? (SDC command)
 

Actually I have not. This is because I do not know yet which block/cell/IO will be interfacing my chip from the outside world.
But any recommendations regarding that?

have you tried to set a driver cell? (SDC command)
 

you can just create a mock up scenario for now. use a big (X8,X16) buffer to drive the IO cells. should smooth things out.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top