• 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, LVS, new layer

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 14725
  • 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, LVS, new layer

samer1
samer1 over 8 years ago

I am using cadence ic616 and calibre for lvs/DRC/xRC. I added a new layer in the kit (IBM 65nm 10LPe). I want that layer to be shorted during LVS. I learnt that CDS_thru can help with that and I have been trying to add several views of the CDS_thru to my device representing that new layer but still the LVS is not working. It is showing the following error:

No matching ".SUBCKT" statement for "memr_hfox" at line 62 in file "/home/samer1/cmos65nm/TS_Form_prog.src.net"
Source could not be read

can someone help with that?

thanks

  • Cancel
Parents
  • samer1
    samer1 over 8 years ago
    I just had an extra question. LVS cannot find the SUBCKT for the device "memr_hfox" in the auCDL netlist. I assume when Calibre exports the auCDL of the schematic, it ignores the "memr_hfox" device or cannot find its definition. What I did from a cadence standpoint is, I added the auCdl view of the device in the viewlist (otherwise it was not running at all) and copied the spectre parameters in the CDF to auCdl (in the by simulator tab). I'm just wandering why Calibre cannot find the SUBCKT of the device. Do you think there is any cadence related issue that might be causing that?

    Thanks
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • samer1
    samer1 over 8 years ago
    I just had an extra question. LVS cannot find the SUBCKT for the device "memr_hfox" in the auCDL netlist. I assume when Calibre exports the auCDL of the schematic, it ignores the "memr_hfox" device or cannot find its definition. What I did from a cadence standpoint is, I added the auCdl view of the device in the viewlist (otherwise it was not running at all) and copied the spectre parameters in the CDF to auCdl (in the by simulator tab). I'm just wandering why Calibre cannot find the SUBCKT of the device. Do you think there is any cadence related issue that might be causing that?

    Thanks
    • 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