• 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. RTL compiler Verilog_out netlist

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 13437
  • 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

RTL compiler Verilog_out netlist

superman321
superman321 over 16 years ago

Im trying to get a verilog (structural) netlist of a synthesized, mapped design and I would like to have it in "positional" format rather than the deafult named format.

I have tried using the attribute "set_attribute write_vlog_port_association_style positional" which give me an error: 

[TUI-19] The object for this attribute is missing or invalid. [TUI-19] [set_attribute]
        : You must specify a 'instance' object type as the final (fourth) argument when setting the 'write_vlog_port_association_style'  attribute.

Any suggestion on how to use this attribute or any other attribute that may give me a structural "positional" format rather than the default "named" format?

  • Cancel
Parents
  • grasshopper
    grasshopper over 16 years ago

     Hi Superman321,

     from RC command-line

    rc:/> get_attr -h write_vlog_port_association_style *

    Usage: get_attribute <string> [<object>+]

        <string>:
            attribute name
        [<object>+]:
            object of interest (must be unique)

        attribute category: write

        attribute name: write_vlog_port_association_style
              category: write (controls write output)
           object type: instance
           access type: read-write
             data type: string
         default value: default
                  help: Determines the style for writing out port connections of an instance. The style can be default(i.e. same as in the
                        user design input), positional or named.

    Note that the attribute you mention is applicable to instances hence you should be applying it to an instance. You should have something like

    set_attr  write_vlog_port_association_style positional  [find /  -instance <instance name>]

     gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • grasshopper
    grasshopper over 16 years ago

     Hi Superman321,

     from RC command-line

    rc:/> get_attr -h write_vlog_port_association_style *

    Usage: get_attribute <string> [<object>+]

        <string>:
            attribute name
        [<object>+]:
            object of interest (must be unique)

        attribute category: write

        attribute name: write_vlog_port_association_style
              category: write (controls write output)
           object type: instance
           access type: read-write
             data type: string
         default value: default
                  help: Determines the style for writing out port connections of an instance. The style can be default(i.e. same as in the
                        user design input), positional or named.

    Note that the attribute you mention is applicable to instances hence you should be applying it to an instance. You should have something like

    set_attr  write_vlog_port_association_style positional  [find /  -instance <instance name>]

     gh-

    • 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