Stats

  • Locked Locked
  • Replies 7
  • Subscribers 124
  • Views 10214
  • 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

Pin names

StreamCX

 I have schematic and symbol with output/input liters like Q1, Q2, Q3....

CLK1, CLK2,

When I try plot outputs (add wires) in analyses I see net names in numeral.

How can I see pins of element in analysis output window (not in cipher, in form like Q1, Q2)?

Parents

  • OK, this is because you've not labelled the nets, and hence it is automatically naming them.

    In the schematic editor, if you go to Options->Editor and then the "Net Names" tab, change the "Net Name Method" to "derived". This will cause automatically named nets to be "instance_pin" form - based on the name of the output pin that is driving the net.

    This can be set in your ~/.cdsenv file by default as:

     schematic netNameMethod cyclic "derived"

    or in your .cdsinit as:

      envSetVal("schematic" "netNameMethod" 'cyclic "derived")

    So the nets were NOT numeric - they were "netNNN" - if you'd have said that in the first place, we'd have got there a lot more quickly!

    Regards,

    Andrew.

Reply

  • OK, this is because you've not labelled the nets, and hence it is automatically naming them.

    In the schematic editor, if you go to Options->Editor and then the "Net Names" tab, change the "Net Name Method" to "derived". This will cause automatically named nets to be "instance_pin" form - based on the name of the output pin that is driving the net.

    This can be set in your ~/.cdsenv file by default as:

     schematic netNameMethod cyclic "derived"

    or in your .cdsinit as:

      envSetVal("schematic" "netNameMethod" 'cyclic "derived")

    So the nets were NOT numeric - they were "netNNN" - if you'd have said that in the first place, we'd have got there a lot more quickly!

    Regards,

    Andrew.

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.