Home > Community > Blogs > System Design and Verification > ctos support of multiple clocks
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more convenient.

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: *

CtoS support of Multiple Clocks

Comments(0)Filed under: C-to-Silicon Compiler, High-Level Synthesis, SystemC, CTOS, clocking, clock, System Design & VerificationIn a previous blog entry we discussed C-to-Silicon’s (CtoS’s) ability to support multiple threads in a similar way that traditional Hardware Description Languages (HDLs) support multiple processes.

There are many applications, such as multi-rate DSP applications, in which it is not only necessary to describe the circuit as multiple concurrent threads but also that  these threads operate on different clock domains.

Multiple clocks are fully supported by traditional RTL based synthesis tools and therefore must also be supported by any viable ESL High Level Synthesis alternative.

SystemC and CtoS support multiple clock domains. Each thread declared inside an SC_MODULE can be clocked by a separate clock signal.

By supporting multiple threads and multiple clocks SystemC and CtoS provide a viable alternative to the traditional RTL Synthesis approach. This support is usually not provided by a pure C / C++ High Level Synthesis approach.

 

This Team ESL posting is provided by Dr. Sergio Ramirez, Sr Staff Product Engineer for the C-to-Silicon Compiler high level synthesis product. 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.