Stats

  • Locked Locked
  • Replies 8
  • Subscribers 90
  • Views 21338
  • 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

No matching .SUBCKT statement error in LVS check

archive

Hello All I am using Calibre-LVS for LVS check between final layout and verilog code both are generated by Cadence-Encounter v4.1. The output log file is enclosed. The LVS does not compare two files because of some errors like: Error: No matching ".SUBCKT" statement for "BFSVTX10" at line 43459 in file "/tmp/lvsRunDir/_decoder36.v.sp" Error: No matching ".SUBCKT" statement for "BFSVTX10" at line 43460 in file "/tmp/lvsRunDir/_decoder36.v.sp" BFSVTX10 is a standard lib given in STM cmos90nm lib. I appreciate your comment to solve this issue. Thanks, Ali


Originally posted in cdnusers.org by Naderi
Parents

  • Ali,

    Sounds like you may be running LVS from a GUI, which I have no experience with. I've always done command-line. I think we normally see those warnings about the module declaration and they are ok, but the SUBCKT errors you got later is what makes me think you're missing the std cell spice. I'm not sure what GUI line this will match to, but my typical v2lvs command looks like this:

    v2lvs -v design.v -s library.spi -o design.source.spice > v2lvs.log

    The file "library.spi" looks like this:

    .INCLUDE stdcell.cir
    .INCLUDE io.cir
    .INCLUDE ram.cir

    Maybe that will help you match it to the GUI option. Hope it helps!

    - Kari


    Originally posted in cdnusers.org by Kari
Reply

  • Ali,

    Sounds like you may be running LVS from a GUI, which I have no experience with. I've always done command-line. I think we normally see those warnings about the module declaration and they are ok, but the SUBCKT errors you got later is what makes me think you're missing the std cell spice. I'm not sure what GUI line this will match to, but my typical v2lvs command looks like this:

    v2lvs -v design.v -s library.spi -o design.source.spice > v2lvs.log

    The file "library.spi" looks like this:

    .INCLUDE stdcell.cir
    .INCLUDE io.cir
    .INCLUDE ram.cir

    Maybe that will help you match it to the GUI option. Hope it helps!

    - Kari


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