• 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. Logic Design
  3. synthesis System Verilog design

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 61
  • Views 18848
  • 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

synthesis System Verilog design

archive
archive over 18 years ago

Hi there,

I am a new user in System Verilog and wish to gain some help here.
Do anyone know how to synthesis System Verilog design? Which CAD tool should I use?and how?


Originally posted in cdnusers.org by SHL
  • Cancel
Parents
  • archive
    archive over 18 years ago

    SHL,

    a file can take any extension you want. Different design teams use different design practices and naming conventions. Some use .v, .v2k., .sv, .vg, .VG, .VRL, .VHD, .vhd, .verilog, .VLOG, .rtl, etc. You catch the drift... The tool does not care about the extension you choose but you do need to tell the tool what HDL language you are using hence the '-sv' switch needed in your read_hdl command.

    hope this helps,
    gh-


    Originally posted in cdnusers.org by grasshopper
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    SHL,

    a file can take any extension you want. Different design teams use different design practices and naming conventions. Some use .v, .v2k., .sv, .vg, .VG, .VRL, .VHD, .vhd, .verilog, .VLOG, .rtl, etc. You catch the drift... The tool does not care about the extension you choose but you do need to tell the tool what HDL language you are using hence the '-sv' switch needed in your read_hdl command.

    hope this helps,
    gh-


    Originally posted in cdnusers.org by grasshopper
    • 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