Home > Community > Blogs > System Design and Verification > c to silicon does not require a library characterization
 
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 System Design and Verification 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: *

C-to-Silicon Does Not Require a Library Characterization

Comments(0)Filed under: System Design and Verification, ESL handoff, high-level synthesis adoption, C-to-Silicon Compiler, High-Level Synthesis, ESL, architect, ESC, C-to-SiliconOne of the key strengths of C-to-Silicon Compiler (CtoS) over other ESL Synthesis tools is its ability to directly read industry standards .lib files. By providing this ability an expensive library characterization which is required by other ESL Synthesis tools is avoided.

This approach not only avoids an expensive library characterization, which only provides estimates of the component delays, but also has the advantage of using the synthesized components in the context of the actual design. This is done using CtoS's built-in RTL Compiler synthesis engine and the provided .lib file to synthesize and analyze the timing of the generated RTL from which CtoS gets accurate feedback to refine the scheduling of components.

The end result is higher quality RTL with more aggressive resource sharing that once synthesized, meets the timing requirements in the targeted technology.

This Team ESL posting is provided by Dr. Sergio Ramirez, Sr Staff Product Engineer for the C-to-Silicon Compiler high level synthesis product.

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.