Stats

  • Locked Locked
  • Replies 4
  • Subscribers 165
  • Views 13847
  • 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

Net list error

girish
Hi, Now days I am frequently encounter with attached netlist error , if i copy the hole design to a new design file this error will solve ,but in one schematic if i copy to new design file (.dsn) all refdes will change & heterogenous parts will get different refedes , Any one faced this problem? pls suggest if you have any solution Have a nice day Regards, Girish Kumar Bangaloru

  • Open the pstxnet.dat file with a text editor that displays line numbers. At, or around, the line number 9068 will be the problem. My guess would be that the ref des / pin number listed at that location is duplicated in the symbol and the definition of the pin differs between the sections, possibly the pin is visible in one section on the schematic and not visible on another.

  • Hi , Thanks oldmouldy for spending your time . I got the problem this due to multi refdes to the same part (please find the attached screen shot ), i dont know the reason how it comes . If I copy this page as it is U19C will get change to U8C after copyig . I made both fields same (U19C U19C) & then copied now it will retains it original refdes . But it is huge effort since i have 1000 parts each i have to manually edit & make the both field same . I hope above explanation will not confuse you , but my concern is why single part getting multi refdes? Looking forward for your comment . Regards, Girish Kumar Bangaloru

  • The problem is you have instance and occurrence properties.When you copy you are copying the instance properties which means you could have a big problem on your hands.  The fix?  Be sure to use the utility "Transfter occurrence properties to instance" upon completion of  a design that you want to archive and/or copy.  Problem will be fixed. :)

  • Whatever the problem is , the differences between the "white", Instances, values and the "yellow", Occurrences, won't be it. The netlister will be using the appropriate set of properties for the mode that the design is in, in this case it looks like the design is in Occurrences mode. The netlister is, most likely, complaining that a pin is defined in two sections of the U19 schematic part and the properties assigned to the pin in section C differ from the original definition in the netlist and the netlist integrity checking fails - which is what the error is reporting.

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.