• 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. Custom IC Design
  3. Import Verilog

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 127
  • Views 19435
  • 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

Import Verilog

eppramod
eppramod over 14 years ago
Hi, Don't know if this query was raised before here. I am new to doing "Import ==> Verilog" in Cadence Virtuoso. I am having a gate level Verilog netlist and was trying to do Import==> Verilog function through Cadence Virtuoso(icfb). I am getting the import to work but unfortunately the reference dfII library which i am using for "component" symbols have VDD and VSS pins in their symbols. After import I am seeing that these ports are unconnected in the schematic view(as there are no VDD/VSS definition in the verilog netlist). Is there a way to have these pins connected after import? Thanks in advance.
  • Cancel
Parents
  • Quek
    Quek over 14 years ago

    Hi eppramod

    There is currently no easy way to resolve this. We can solve the problem using either of the following methods:
    a. Use a perlscript to add in VDD and VSS connections to the verilog netlist
    b. Use a skillscript to route the VDD and VSS connections after importing the netlist

    You can use the following perlscript. It adds VDD and VSS to the verilog netlist. It is also available in COS solution 11598626.

    Best regards
    Quek


    #!/usr/bin/perl

    # This script adds power pins to a verilog netlist
    # Usage: addpower.pl input.v output.v

    if(@ARGV<2) {
       die("Please enter 2 inputs: E.g. addpower.pl input.v output.v\n")
    } #if

    if(!open(inPort, @ARGV[0])) {
       die("Cannot open file @ARGV[0]\n")
    } #if

    if(!open(outPort, ">@ARGV[1]")) {
       die("Cannot create file @ARGV[1]\n")
    } #if

    $pin1="VDD";
    $pin2="VSS";

    while( chomp($inLine=<inPort>) ) {
       $inLine2 = $inLine;
       $inLine2 =~ s/^ *//;
       @myList=split / /, $inLine2;
       if( @myList[0] =~ /module/ ) {
          $inLine=~s/\(/\($pin1, $pin2, /;
       } #if
       if( @myList[0] =~ /input/ ) {
          $inLine=~s/input/inout $pin1, $pin2;\n  input/;
       } #if
       if( $inLine =~ /.*\(..*\(.*\).*/ ) {
          $inLine=~s/\(/\(.$pin1\($pin1\), .$pin2\($pin2\), /;
       } #if
       print outPort $inLine, "\n";
    } #while

    • addpower.txt
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • madhesh
    madhesh over 6 years ago in reply to Quek

    Hi Quek,

    you can help on this,  after routing we can change the component for same net, but component size is too big, that case routing as unconnected the component how to auto connect the these validate component.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • madhesh
    madhesh over 6 years ago in reply to Quek

    Hi Quek,

    you can help on this,  after routing we can change the component for same net, but component size is too big, that case routing as unconnected the component how to auto connect the these validate component.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Quek
    Quek over 6 years ago in reply to madhesh

    Hi madhesh

    Would you please kindly start a new thread for your issue? Appending to an old thread is a violation of forum rules. You might also want to consider breaking down your question in point form so that we can understand the issue more issues. Thanks


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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