Home > Community > Blogs > Digital Implementation > five minute tutorial default naming conventions in edi
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more conveniennt.

Register | Membership benefits
Get email delivery of the Digital Implementation blog (individual posts).
 

Email
* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

Cadence Contacts

Global Office Locator
Find Offices worldwide »

Sales Inquiry
Request for Product information »
Cadence Channel Partners »

Corporate Headquarters
Cadence Design Systems, Inc.
2655 Seely Avenue
San Jose, CA 95134
Phone: 408.943.1234
* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Five-Minute Tutorial: Default Naming Conventions in Encounter Digital Implementation (EDI)

By Kari Summers on February 27, 2012Comments(3)Filed under: Digital Implementation, encounter, Encounter Digital Implementation, EDI, tutorial, five-minute, naming, default naming conventions, timing debug

This is a topic that frequently comes up on both internal and external forums. And the answer is right in the Encounter Digital Implementation System (EDI) User Guide, but unless you already know that, you may not think to look for it there.

At some point, all of us have looked at a timing report, and reviewed the list of cells that EDI added during timing optimization. Then we wondered, "Hmmm. What does that prefix mean?" I'm sure you've seen the prefixes of the form FE_PHC, FE_RC, FE_OFC, etc. They do have specific meanings, and when debugging a timing path, it can be very helpful to know where these cells came from.

The following list is located in the EDI User Guide. It's at the end of the Optimizing Timing chapter, in a section called Default Naming Conventions.

Prefix

Description

Command

FE_MDBC

Instance added by multi-driver net buffering

optDesign

FE_MDBN

Net added by multi-driver net buffering

optDesign

FE_OCP_DRV_C

Instance added by DRV fixing

optDesign

FE_OCP_DRV_N

Net added by DRV fixing

optDesign

FE_OCP_RBC

Instance added by rebuffering

optDesign

FE_OCP_RBN

Net added by rebuffering

optDesign

FE_OCPC

Instance added by critical path optimization

optDesign

FE_OCPN

Net added by critical path optimization

optDesign

FE_OFC

Buffer instance added by rule-based buffer insertion

insertRepeater/optDesign

FE_OFN

Buffer net added by rule-based buffer insertion

insertRepeater/optDesign

FE_PHC

Instance added by hold time repair

optDesign

FE_PHN

Net added by hold time repair

optDesign

FE_PSBC

Instance added by buffer insertion in optDesign -postRoute

optDesign

FE_PSBN

Net added by buffer insertion in optDesign -postRoute

optDesign

FE_PSC

Instance added by postroute setuprepair

optDesign

FE_PSN

Net added by postroute setup repair

optDesign

FE_RC

Instance created by netlist restructuring

optDesign

FE_RN

Net created by netlist restructuring

optDesign

FE_USC

Instance added during useful skew optimization

optDesign

Hopefully this information will help you debug a timing path gone wrong, and prompt you to check out the EDI User Guide!

Here are two previous blogs related to debugging timing in EDI:

Demo: Calling Global Timing Debug for a Single Path

An Interview with Global Timing Debug Architect Thad McCracken

- Kari Summers
 

 

Comments(3)

By Thomas Schuster on February 29, 2012
Thanks for that. I find this very useful for beginners and even advanced users.

By ajay on January 30, 2013
in my design huge no of buffers added with prefix FE_OFC.here what the thing is i have n't given any rule for buffer insertion.could anybody please tell me the reason for it?

By Kari on January 31, 2013
Hi Ajay, If you look in the chart, you'll see that the OFC tag can also come from optDesign. I believe these will come from fixing DRVs, like high fanout (if you have that turned on) and most likely max transition violations.

Leave a Comment


Name
E-mail (will not be published)
Comment
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.