• 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. cds_thru unbound

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 20953
  • 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

cds_thru unbound

csst
csst over 11 years ago

Dear All,

In LVS i get this error

*ERROR* Device 'cds_thru(RES)' on Schematic is unbound to any Layout device.

IC sub-version 5.10.41.500.6.143
Assura sub-version 4.1_USR4

How to fix this error?

Regards

 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    See solution 11598344

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • csst
    csst over 11 years ago

    Thank you for the reply, but i have no access in Cadence Online Support.

    It would be greatly appreciated if you could paste the answer in this post. 

    Regards

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago
    Problem

    The cds_thru device from the "basic" library is used when it is required to join up 2 different pins in a schematic (.e.g to join up a VSSA net to a VSS net). How can an LVS mismatch due to this extra device be resolved?

    Solution

    The LVS mismatch can be resolved as follows:

    === Assura ===
    avCompareRules(
       schematic(
          filterDevice("cds_thru" short("src" "dst"))
       ) ;schematic
    ) ;avCompareRules

    Using the above command, Assura will filter the cds_thru device from the schematic and short the 2 terminals. The net connecting to the 1st terminal specified in the command will be retained. For the above example, it will be the net connecting to the "src" terminal.

    For a CDL netlist input, the command would be:

    avCompareRules(
       schematic(
          filterDevice( "SH" short("src" "dst"))
       ) ;schematic
    ) ;avCompareRules

    cds_thru is exported to a CDL netlist as a resistor with the model "SH" and resistance 0.1 ohms. Alternatively, the following CDL control command can be used in the CDL netlist:
    *.RESI 2000

    The above means that resistors with R values of 2000 and below will be automatically shorted.

    === PVS ===
    lvs_filter_device R(SH) -short -source

    === Calibre ===
    LVS FILTER R(SH) SHORT SOURCE

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • csst
    csst over 11 years ago

     Thank you so much

    adding

       schematic(
          filterDevice( "SH" short("src" "dst"))
       ) ;schematic

     in avCompareRules() in  compare.rul file   fixed the error.

    Kind Regards

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • KarthikJaiho
    KarthikJaiho over 11 years ago

     Hi csst,

         I also deals with the same problem. I am using IC615 and for verifying LVS i am using calibre.  I added the line LVS FILTER R(SH) SHORT SOURCE in lvs.rul file. But it shows compilation error. How to resolve this problem in Calibre.

    Thanks & Regards,

    Karthik.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    You might want to ask Mentor this or read the Mentor Calibre documentation. Another approach is to ensure that *.RESI is set in the CDL netlist (this can be set on the File->Export->CDL form) so that resistors with values smaller than the threshold get shorted. I'm not sure if you have to do anything in Calibre to get it to honour *.RESI

    Regards,

    Andrew 

    • 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