Stats

  • Locked Locked
  • Replies 3
  • Subscribers 166
  • Views 14707
  • 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

Problem while creating netlist.

NEPDEEP

Hi, I had the following error while trying to create the netlist. Could anyone please tell me where am i going wrong and what is the soulution.

www.tiikoni.com/.../

  • oldmouldy
    The required information is in the Session Log window, can't help at all with the screen shot provided - where the message says "Correct the errors..."
  • NEPDEEP
    Hi,
     It says something like this....are not the foot prints already included in schematic...if not do i have to add it from somewhere?? please recommend me...i just began using orcad
    Spawning... "C:\Cadence\SPB_16.5\tools\capture\pstswp.exe" -pst -d "D:\ORCAD\SCH\LEARN.DSN" -n "D:\ORCAD\SCH\allegro" -c "C:\Cadence\SPB_16.5\tools\capture\allegro.cfg" -v 3   -l 255 -s "ALG0051" -j "PCB Footprint" -hpath "HPathForCollision"
    #1 ERROR(ORCAP-36002): Property "PCB Footprint" missing from instance C2: VersionR0XX, power supply (2.20, 2.80).
    #2 ERROR(ORCAP-36002): Property "PCB Footprint" missing from instance R1: VersionR0XX, power supply (4.60, 3.70).
    #3 ERROR(ORCAP-36002): Property "PCB Footprint" missing from instance J2: VersionR0XX, power supply (0.40, 2.40).
    #4 ERROR(ORCAP-36002): Property "PCB Footprint" missing from instance J3: VersionR0XX, power supply (4.60, 5.10).
    #5 ERROR(ORCAP-36002): Property "PCB Footprint" missing from instance SW1: VersionR0XX, power supply (3.10, 2.60).
    #6 ERROR(ORCAP-36002): Property "PCB Footprint" missing from instance SW2: VersionR0XX, power supply (3.20, 4.00).
    #7 ERROR(ORCAP-36002): Property "PCB Footprint" missing from instance U1: VersionR0XX, xilinx (1.70, 1.60).
    #8 ERROR(ORCAP-36002): Property "PCB Footprint" missing from instance D1: VersionR0XX, power supply (4.60, 3.20).
    #9 ERROR(ORCAP-36002): Property "PCB Footprint" missing from instance C1: VersionR0XX, power supply (1.50, 2
    .80).
    #10 ERROR(ORCAP-36041): Duplicate Pin Name "C" found on Package CD10-DIP-BCD , SW1 Pin Number 5: VersionR0XX, power supply (3.10, 2.60). Please renumber one of these.
    #11 ERROR(ORCAP-36041): Duplicate Pin Name "C" found on Package CD10-DIP-BCD , SW2 Pin Number 5: VersionR0XX, power supply (3.20, 4.00). Please renumber one of these.
    #12 ERROR(ORCAP-36041): Duplicate Pin Name "IO" found on Package lm324 , U1 Pin Number 3: VersionR0XX, xilinx (1.70, 1.60). Please renumber one of these.
    #13 ERROR(ORCAP-36041): Duplicate Pin Name "IO" found on Package lm324 , U1 Pin Number 4: VersionR0XX, xilinx (1.70, 1.60). Please renumber one of these.
    #14 ERROR(ORCAP-36041): Duplicate Pin Name "IO" found on Package lm324 , U1 Pin Number 5: VersionR0XX, xilinx (1.70, 1.60). Please renumber one of these.
    #15 ERROR(ORCAP-36041): Duplicate Pin Name "IO" found on Package lm324 , U1 Pin Number 6: VersionR0XX, xilinx (1.70, 1.60). Please renumber one of these.
    #16 ERROR(ORCAP-36018): Aborting Netlisting... Please correct
     the above errors and retry.

    Exiting... "C:\Cadence\SPB_16.5\tools\capture\pstswp.exe" -pst -d "D:\ORCAD\SCH\LEARN.DSN" -n "D:\ORCAD\SCH\allegro" -c "C:\Cadence\SPB_16.5\tools\capture\allegro.cfg" -v 3   -l 255 -s "ALG0051" -j "PCB Footprint" -hpath "HPathForCollision"
    INFO(ORCAP-32005): *** Done ***
  • oldmouldy
    OK, so yes, you do have to specify the PCB Footprint for the parts, for example, a resistor could have a power rating "anywhere" between 1/16W and many watts, there is no chance that they would share the same PCB footprint but, they would likely share the same schematic symbol with different properties. Next issue, connect pins, apart from pins of type Power, need to be uniquely named, you have some duplicate pin names, the schematic symbols are going to need to be corrected to fix this.
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.