Home > Community > Blogs > Logic Design > encounter 174 rtl compiler hierarchical ilm interface logic model flow
 
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 Logic Design blog (individual posts).
 

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Encounter® RTL Compiler Hierarchical ILM (Interface Logic Model) Flow

Comments(0)Filed under: RTL compiler, rc, rapid adoption kits, EDI, synthesis flow, ILM, RAK, Interface Logic Model, synthesis eda tools, routing resources at SoC level, top-level synthesis, placement, synthesis tips for RTL compilers, hierarchical VLSI implementation flows, hierarchical synthesis

We are often asked, by engineers doing synthesis, "Does Encounter® RTL Compiler support ILM(s) - Interface Logic Model(s) during synthesis? How to use ILM? What are its benefits?"

In this blog, I will not only provide some basic information about ILMs, but  also point readers to a learn-by-doing content on RC Hierarchical ILM flow packaged in a RAK (Rapid Adoption Kit).

Interface Logic Model (ILM) is a technique to model blocks in hierarchal VLSI implementation flows. The advantage of the abstracted ILM approach is that entire path (clock to clock path) is visible at top level for interface nets unlike traditional block based hierarchal implementation flow. That gives better accuracy in analysis for interface nets at negligible additional memory and runtime overhead.

There is no specific requirement for ILM models. You would generate an ILM model for your implemented block, in Encounter® Digital Implementation or Encounter® RTL Compiler. The requirement will change at top level in terms of constraints. You will need to read your top-level constraints which include references to block as well. So you will need full top-level constraints so that exceptions like false-paths between top and block etc. are correctly applied.

Here is the simple version of using ILM at top level:

***

read_hdl <RTL>

read_ilm -basename <path of ILM of other blocks> -module <>

elaborate <TOP>

read_def TOP.def

assemble_design # This will load data for ILMs

<TOP level constraints and setup>

<synthesize>

Write_design -hierarchical -encounter

*** 

Also, in today's high utilization designs, following steps are essential:

  • Possibility of extra logic optimization at top level 
  • Consequent possibility of creating placement/routing resources at SoC level
    • Hence, TOP level synthesis required
  • However, massive design sizes can push software to its limit
    • Hence, hierarchical synthesis required

 

Benefits of ILM:

  • ILMs are highly accurate representations of the original design. ILMs do not abstract. They simply discard what is not required for modeling boundary timing.
  • ILMs can have very small memory footprint leading to very fast runtimes.
  • Differences in the timing characteristics of an ILM, when compared to the original netlist, are easy to debug because the interface logic is maintained.
  • Model generation runtime using ILMs is fast because identifying the interface logic for a design is a structural operation that is performed by analyzing circuit topology.
  • ILMs, for a mapped design, can be created at any stage during design flow - postSynth, prePlace, preCts, postCts or postRoute.
  • ILMs provide an accurate and robust model generation solution for chip-level analysis in a hierarchical design flow.

 

 

 

In general, Interface logic contains all the circuitry leading from I/O ports to edge-triggered registers called interface registers. The clock tree leading to interface registers is maintained as it is in ILM. Logic/circuitry that only consists of register-to-register paths on a block is not a part of an ILM.

 

The SI ILM logic model, also known as XILM, contains logic and capacitance information to model SI effects on interface timing.

 

 

Keeping this in mind, Shreyash Shukla, Principal PE, Synthesis R&D, Cadence Design Systems has developed a new RAK on RTL Compiler: Hierarchical ILM (Interface Logic Model) Flow, that will help user walk through the complete Hierarchical ILM flow available in RC, including generating ILM from RC and assemble design flow for ILM blocks.

Rapid Adoption Kits

Overview

RAK Database

Last Updated

RTL Compiler: Hierarchical ILM (Interface Logic Model) Flow

View

Download (48 MB)

10 Dec, 2013

We are covering the following technologies through our RAKs at this moment:

Synthesis, Test and Verification flow
Encounter Digital Implementation (EDI) System and Sign-off Flow
Virtuoso Custom IC and Sign-off Flow
Silicon-Package-Board Design
Verification IP
SOC and IP level Functional Verification
System level verification and validation with Palladium XP

Please visit http://support.cadence.com/raks to download any RAKs of interest.

We will continue to provide self-help content on Cadence Online Support, your 24/7 partner for learning more about Cadence tools, technologies, and methodologies as well as getting help in resolving issues related to Cadence software. If you are signed up for e-mail notifications, you will be notified of new solutions, application notes (technical papers), videos, manuals, etc.

Note: To access above docs, click a link and use your Cadence credentials to logon to the Cadence Online Support http://support.cadence.com website.

Happy Learning!

Sumeet Aggarwal

 

Comments(0)

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.