Stats

  • Locked Locked
  • Replies 3
  • Subscribers 165
  • Views 13981
  • 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

Allegro Netlist error

FFSDEV

 Hi,

 

Please could anyone tell me what how do I get rid of this error in Orcad 10.3? I am trying to generate an allegro netlist and have tried a few simple tricks sucha s re-creatign teh design file and part etc but the error still persists.

“packaging the design view...#228 DDB_ERROR: Cannot package the primitive instance '@\main board\.schematic1(sch_1):ins13143800@ffs_parts.\gtl2003bq.normal\(chips)' in any sections of the physical part 'GTL2003BQ_SM_QFN20_19P685_166X0'.  Check the pin definitions for each section in the chips_prt file.
#53 DDB_ERROR: Null object id specified in call to ddbPackInstInSections.
Error: Line 0 in file :
        Could not pack inst <instId->OPName> in sections 
      Detected in function: ddbiPkgDesign
#53 DDB_ERROR: Null object id specified in call to ddbStopGen.”
 
Thanks
Parents
  • oldmouldy

    10.3 is quite an old version now and some of the specifics with Allegro netlisting messages may well be lost in time. I suggest that you start with a Design Rules Check, Tools>Design Rules Check, enable all the checks except "SDT Compatibility" and see what you get, look into all the errors and see if there are any specific to the part in question. The netlister will have attempted to build a primitive to hold the pins of the part, when it comes to actually place the pins into the primitive, the netlister cannot find a consistent match between the pins and the primitive created.

    Without the DSN file, investigating this remotely will be virtually impossible.

Reply
  • oldmouldy

    10.3 is quite an old version now and some of the specifics with Allegro netlisting messages may well be lost in time. I suggest that you start with a Design Rules Check, Tools>Design Rules Check, enable all the checks except "SDT Compatibility" and see what you get, look into all the errors and see if there are any specific to the part in question. The netlister will have attempted to build a primitive to hold the pins of the part, when it comes to actually place the pins into the primitive, the netlister cannot find a consistent match between the pins and the primitive created.

    Without the DSN file, investigating this remotely will be virtually impossible.

Children
No Data
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.