• 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. Logic Design
  3. CCD check fails as Encounter cannot parse a design file...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 61
  • Views 5778
  • 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

CCD check fails as Encounter cannot parse a design file which has a "generate" block in it

dp2402
dp2402 over 13 years ago

Hello all,

I am currently running a CONFORMAL (R) Constraint Designer v10.10 check for an IP which consists several *.v files.

In one of the .v files the "generate" statement has been used -- This is causing an error while I run my CCD script.

-----------------
Error msg given by compiler:

// Parsing file ~hdl/abc.v ...
// Error: hdl_default_checks/rtl_checks/RTL13.6: Standalone generated blocks are not supported in the IEEE standard
// In line 235, file '~hdl/abc.v'
// Error: Fail to read design.
// Read design summary: Error: 1, Warning: 0, Note: 0
-----------------

CCD script which reads the design file:

read design -verilog2k -define <company_tech_name>\
-root <....> \
-parameter <...> \
hdl/some_file.v \
hdl/abc.v \
hdl/some_file.v \
-lastmod -noelab

-------------------------

Please throw some light on the RTL13.6 error message and tell me which switch I shall use witn the "read design" command so that the error message regarding use of "generate" statement in design dosen't show up?

Hope I am clear in the explanation!

Thanks

  • Cancel
  • Shalom B
    Shalom B over 13 years ago

    A standalone generate block is one in which the generate construct contains content outside a generate-if/case/for.

     Example:

    generate

    wire x;

    endgenerate

    The 'wire x;' declaration does not appear inside a generate if/for/case.

    This is legal in Verilog-2001, but not in Verilog-2005 and SystemVerilog.

    Maybe Conformal has a switch to tell it to use the 2001 version instead of the 2005 versio.

    Or you can tell Conformal to treat this as a warning instead of an error.

    Shalom

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dp2402
    dp2402 over 13 years ago

    Yes, that's what I believe too, that the "read design" must be having a switch!

    You see in my 1st post, I am already using the switch " -verilog2k  " but that dosen't solve the problem.

    I have checked the Conformal_Ref.pdf documentation for all switches belonging to the cmd "read design", but couldn't find it there.

    Also it is no use changing an Error to a Warning! Coz if my script cannot parse the design file, it is no use running the constraint.

    I am using CCD for the 1st time & have no experience!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • croy
    croy over 13 years ago

    R&D made RTL13.6 an error in 10.1. It went back to a warning within 2 months. You could download 11.1 or do 'set rule handling RTL13.6 -warning' if continuing with 10.1.

     

    Chrystian

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dp2402
    dp2402 over 13 years ago

    Hi Chrystian,

    Just when I thought my problem is solved, CCD now says that RTL13.6 is an unknown rule!

    But if I run the script without the 'set rule handling ....', compiler gives error:

    // Error: hdl_default_checks/rtl_checks/RTL13.6: Standalone generated blocks are not supported in the IEEE standard

    :(  Can't understand what's happening!

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • croy
    croy over 13 years ago

    Please use 10.10-s280 or later.

    set rule handling hdl_default_checks/rtl_checks/RTL13.6 -severity warning

    Chrystian

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dp2402
    dp2402 over 13 years ago

    Thanks a lot  Chrystian.

    Works perfectly!

    • 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