• 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. Custom IC Design
  3. How to mark a floating bus net as noConn in Schematic Composer...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 20754
  • 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

How to mark a floating bus net as noConn in Schematic Composer in IC5141

RFStuff
RFStuff over 11 years ago

 Dear All,

I have circuit block (symbol) with a bus line which I want to keep it floating.

To avoid the blinking, itried to use noConn . But it is not taking as it is a bus.

How it can be fixed ?

Kind Regards,

 

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    If the bus pin is (say) outbus<5:0> then give the instance name of the noConn NOC<5:0> - i.e. make it an iterated instance with the same width as the bus. That will sort it.

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    If the bus pin is (say) outbus<5:0> then give the instance name of the noConn NOC<5:0> - i.e. make it an iterated instance with the same width as the bus. That will sort it.

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Children
  • Savankuamar
    Savankuamar over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    I used NOC<n:0> and it's working. Thank you so much

    But I have one another question, as I am designing sar adc and I have two bus pin name dacout<3:0> and bout<3:0> respectively. So noConn is not accepting the same instance name so can you please suggest to me what exactly I can do in this case? I am attaching here snapshot so it will be more clear.

                                                                                  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to Savankuamar

    Well, clearly you can't give two instances the same name, so give them different names. For example NOC1<3:0> and NOC2<3:0> or NOCdacout<3:0> and NOCbout<3:0>. There's nothing special about the instance name having "NOC" in it - you just need to make it a vectored name which has the same width as the bus to which it's connecting.

    Unless I've misunderstood your problem?

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Asad Fakhri
    Asad Fakhri over 4 years ago in reply to Andrew Beckett

    Sir Andrew! 

    I faced a problem to connect the output (q_bar) of flipflop with BUS and the ended point with ''noconn'' form basic library But it give 1 warning on the output of Flipflop by which the circuit doesn't simulate. please guide 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to Asad Fakhri

    I'd suggest you first read Guidelines for the Custom IC Design Forum as you'd then see that you should have posted in a new thread, specified the software version you were using, and provided enough information for somebody to have a hope of being able to answer (such as what the warning message was, how exactly it failed to simulate, and maybe a picture of what you've done).

    Andrew.

    • 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