• 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. PCB Design
  3. Error in Netlist: Multiple pin ...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 166
  • Views 18777
  • Members are here 0
More Content
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

Error in Netlist: Multiple pin ...

Hossein1357
Hossein1357 over 10 years ago

Hi,

I am trying to use Bus pin capability for creating schematic symbols in OrCAD 16.6 like below picture:

and connected bus from FPGA to it in schematic like below:

However, it fails during netlist creation and I receive mass of errors like below:

#1 ERROR(ORCAP-36036): Multiple pin [25..27]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#2 ERROR(ORCAP-36036): Multiple pin [25..27]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#3 ERROR(ORCAP-36036): Multiple pin [25..27]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#4 ERROR(ORCAP-36036): Multiple pin [31..39]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#5 ERROR(ORCAP-36036): Multiple pin [31..39]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#6 ERROR(ORCAP-36036): Multiple pin [31..39]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54)
.
Check for incorrect packaging of all devices in U1.
#7 ERROR(ORCAP-36036): Multiple pin [31..39]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#8 ERROR(ORCAP-36036): Multiple pin [31..39]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#9 ERROR(ORCAP-36036): Multiple pin [31..39]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#10 ERROR(ORCAP-36036): Multiple pin [31..39]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#11 ERROR(ORCAP-36036): Multiple pin [31..39]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#12 ERROR(ORCAP-36036): Multiple pin [31..39]'s which have differe
nt nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#13 ERROR(ORCAP-36036): Multiple pin [42..44]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#14 ERROR(ORCAP-36036): Multiple pin [42..44]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#15 ERROR(ORCAP-36036): Multiple pin [42..44]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#16 ERROR(ORCAP-36036): Multiple pin [52..54]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#17 ERROR(ORCAP-36036): Multiple pin [52..54]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#18
ERROR(ORCAP-36036): Multiple pin [52..54]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#19 ERROR(ORCAP-36036): Multiple pin [49..50]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#20 ERROR(ORCAP-36036): Multiple pin [49..50]'s which have different nets connected for U1: SCHEMATIC1, 01-DDS (203.20, 2.54).
Check for incorrect packaging of all devices in U1.
#21 ERROR(ORCAP-36018): Aborting Netlisting... Please correct the above errors and retry.

I really appreciate any help in this regard,

Hossein

  • Cancel
  • oldmouldy
    oldmouldy over 10 years ago
    You cannot use bus pins on primitive parts, see page 291 of the Capture Users Guide, cap_ug.pdf, in the doc\cap_ug directory of the installation.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Hossein1357
    Hossein1357 over 10 years ago

    Sorry, there is something else in mentioned page. I couldn't realize its relation to my issue. I am using OrCAD 16.6, did you reference the same revision?

    Anyway, Why can't I place bus pins in my symbol when its available in symbol editor? 

    What else can I do to get rid of placing bunch of pins instead of a bus? Is there a workaround?

    Thanks,

    Hossein

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 10 years ago
    16.6 version Page 291 has a discussion on Bus Connectivity: "You can use bus pins...." then: "Bus pins will only work with the VHDL netlist format. No other netlist format understands them.
    Do not use bus pins in the following situations:
    Pins on primitive parts.
    Any design that you intend to use with PCB Editor." There is no workaround, part pins need to be scalar, individual pins.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Hossein1357
    Hossein1357 over 10 years ago

    Thank you for the answer. Yes, It seems so.

    However, in my document it is on P245 not P291!.

    I found it by searching the exact phrase you had written. Is there any new update for document? I would appreciate if you can give me a link.

    Thanks again,

    Hossein

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Cadence Guidelines

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