• 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. Digital Implementation
  3. loadViolationReport for calibre NG

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 13763
  • 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

loadViolationReport for calibre NG

archive
archive over 19 years ago

HI ,
can any once suggest me how to overcome or load calibre DRC violations on to Soce  "4.2.2"
 older version is OK (4.1)  no problem .

cmd used :

loadViolationReport -type  Calibre -filename calibre.err

it reports as can't read "designName": no such variable

thanks in advice .


Originally posted in cdnusers.org by mohanch007
  • Cancel
  • archive
    archive over 19 years ago

    Hello,

    The proper syntax for loadViolationReport is "loadViolationReport -type -filename .

    The first line in calibre.err file should be,

    The deisgn name could be the name of the design/block for which the calibre was run. Units are GDSII units usually set to 1000.

    In your case, you are missing this line. Hence the error. Hope this helps this issue. You may also want to try running “PVS” which is Cadence solution for DRC. PVS reads Calibre rule deck verbatim and generates output in Calibre format.

    Regards,

    Elvis


    Originally posted in cdnusers.org by elvis
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    Dear Elvis,
    Thanks for your comment,
    As you have specified the syntax is similar to which i have specified , (syntax is correct but only -type is calibre as i`m using calibre error report )
     FYI. *(loadViolationReport -type -filename )

    And the first line in calibre.err file contains design name and units :
    (TOP_CHIP 1000 ) , I confirm you that the line is existing in the file.

    One more thing the same syntax and same file is used on Soce  (4.1) and reported correctly and displayed violation markers.
    But my concern is the new Soce version i.e (4.2.2)
     [First Encounter v04.20-s383_1 ] its not working ,

    any comments ??


    Originally posted in cdnusers.org by mohanch007
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    Dear Elvis,
    I could able to find the work around for Soce 4.2 "loadViolationReport " .
    the limitations of Soce is the top cell  (design name ) should not start with character "C" or "N" ,
    As my design name is starting with "C" ( C***) . causing Error .

    Regards,
    Mohan Ch


    Posted By mohanch007 on 4/10/2006 6:19 PM
    Dear Elvis,
    Thanks for your comment,
    As you have specified the syntax is similar to which i have specified , (syntax is correct but only -type is calibre as i`m using calibre error report )
     FYI. *(loadViolationReport -type -filename )

    And the first line in calibre.err file contains design name and units :
    (TOP_CHIP 1000 ) , I confirm you that the line is existing in the file.

    One more thing the same syntax and same file is used on Soce  (4.1) and reported correctly and displayed violation markers.
    But my concern is the new Soce version i.e (4.2.2)
     [First Encounter v04.20-s383_1 ] its not working ,

    any comments ??



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