• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Hardware/Software Co-Development, Verification…
  3. C-to-Silicon

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 50
  • Views 13522
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

C-to-Silicon

roel
roel over 15 years ago
Dear reader, For my PhD research I am currently comparing several C to VHDL/Silicon approaches and tools. We have set up a library of kernels and on this library we automatically run the DWARV c-to-vhdl compiler and the C-to-Verilog compiler from Israel. We were also considering doing the generation of hardware from CTOS, but it seems not straightforward to automatically run CTOS over a large set of C functions. Is there a manual describing how to use CTOS from the command line? Or is there some scripting manual that I may use? If not, is there any Cadence CtoS expert out there that can give me some pointers as to how I can automate generating hardware from many different functions. thank you very much in advance for any help you may provide. regards, Roel Meeuws, PhD Candidate Computer Engineering Dept. Delft University of Technology
  • Cancel
Parents
  • Mark Warren
    Mark Warren over 15 years ago
    Hi Roel,

    Great topic for a PhD!

    The Cadence C-to-Silicon Compiler (CtoS) is fully documented in the 900 page Users Guide that ships in the install.  You can contact your local sales/AE for details.   We also have a University program that makes it available to some schools when appropriate.

    CtoS can take high-abstraction SystemC to generate functionally equivalent RTL-Verilog which will then easily synthesize to gates to meet timing (and be leq-able).   The main input language is SystemC, but CtoS also offers the capability to read in C/C++ functions in which you can then choose a built-in TLM lib interface/transactor and CtoS automates the generation of the SystemC wrapper.

    CtoS can be run via standard tcl scripts (very similiar to RC)  to automate many options/flows, but otherwise CtoS has a very different use-model than other HLS tools since we put a very large effort into having a powerful GUI that visualizes the design and offers many choices to try differing micro-archititectures, plus lots of analysis to compare and further refine to achieve optimal Quality of Results.

    hope this helps.

    -mark
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Mark Warren
    Mark Warren over 15 years ago
    Hi Roel,

    Great topic for a PhD!

    The Cadence C-to-Silicon Compiler (CtoS) is fully documented in the 900 page Users Guide that ships in the install.  You can contact your local sales/AE for details.   We also have a University program that makes it available to some schools when appropriate.

    CtoS can take high-abstraction SystemC to generate functionally equivalent RTL-Verilog which will then easily synthesize to gates to meet timing (and be leq-able).   The main input language is SystemC, but CtoS also offers the capability to read in C/C++ functions in which you can then choose a built-in TLM lib interface/transactor and CtoS automates the generation of the SystemC wrapper.

    CtoS can be run via standard tcl scripts (very similiar to RC)  to automate many options/flows, but otherwise CtoS has a very different use-model than other HLS tools since we put a very large effort into having a powerful GUI that visualizes the design and offers many choices to try differing micro-archititectures, plus lots of analysis to compare and further refine to achieve optimal Quality of Results.

    hope this helps.

    -mark
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information