• 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. Packager error SPCODD-7

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 163
  • Views 15446
  • 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

Packager error SPCODD-7

Autarchex
Autarchex over 14 years ago

I heavily modified an existing board design in Allegro Design Entry HDL, including moving components between heirarchy blocks (despite warnings that Allegro does not handle that well...)   When I go to do an Export Physical, with only "package design" checked, and set to 'repackage', I get ERROR(SPCODD-7) which I have pasted below.  Like most Cadence error messages this doesn't really seem to tell me much, and I cannot find a lookup table of error messages on the website.  The component it is complaining about is a TI TPS54160 buck converter and is not a multi-section part, yet it seems to want multiple sections for packaging.  Anyone else run into this?

 

#1   ERROR(SPCODD-7): Following Primitive instance of size requires 2 section~s for packaging.  Only 1 sections available in package of type '18222500_A-182~2-2500'.  Check the size of all pins on this primitive.

Primitive Instance: @MAGPIE_LIB.ROOT(SCH_1):PAGE1_I22@MAGPIE_LIB.PEN_I~NTERFACE(SCH_1):PAGE1_I2@MAGPIE_LIB.PEN_SUPPLY_VPP(SCH_1):PAGE1_I1@IC_POWER.TP~S54160(CHIPS) (MODULE: PEN_SUPPLY_VPP; PART: TPS54160)

Physical Path: @magpie_lib.root(sch_1):page3_i22@magpie_lib.pen_interf~ace(sch_1):page1_i2@magpie_lib.pen_supply_vpp(sch_1):page1_i1@ic_power.tps5416~0(chips)

 

  • Cancel
  • Jerry GenPart
    Jerry GenPart over 14 years ago
    Hi,

    Has this design been upreved from the 16.3 to the 16.5 release? If so, please read this excellent Cadence Online Support Solution that will provide you the resolution –

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11751374

    Jerry

     
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Autarchex
    Autarchex over 14 years ago
    Yes, it was upreved from 16.3 to 16.5, and then heavily edited.  I followed the instructions for the second option, using the environment variable.  It did not appear to make any difference;  I still receive several hundred SPCODD-7 errors when I package the design.  At this point I am considering writing a Perl script to strip out the unwanted and uneditable $SEC attributes from all of the components, but I am wary of directly editing the underlying files.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Autarchex
    Autarchex over 14 years ago
    My apologies, I apparently had not fully patched my installation.  Once I patched it to the most current revision, I tried this again and it worked!  Thanks!
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Jerry GenPart
    Jerry GenPart over 14 years ago
    Thanks for the feedback – glad it’s working!

    Jerry
    • 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.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information