integrated-circuitpackages
I'm working on a free universal parts library tool. In an effort to optimize memory use and performance, I'm trying to work out the practical maximum number of pins you'd ever see on a part.
Right now, our limit is set at 4096. I'd like to bring that down substantially, but I don't want to compromise our ability to support high density interconnect components.
What is the largest package you've ever used/seen?
Thanks for viewing/responding.
Whereas most packages are used by several manufacturers, \$\mu\$MAX seems to be a package solely used by Maxim. It's an 8 pin SMT package, about as wide as an SO-8, but just 3mm long instead of the 5mm of an SO-8. This is achieved by using a 0.65mm pitch instead of 1.27mm.
Other manufacturers also go to ever smaller packages, but most often choose for leadless packages like DFN (Dual Flat No Leads).
Intersil has this list of packages.
NXP has this list.
Unfortunately my experience is that recommended footprints for a certain package aren't always consistent between manufacturers.
I'm pretty sure that auto-insertion machines expect to set pins to the desired orientation by pushing in on them from the outside. If the part is gripped from the outside and squeezed just far enough for the pins to enter the holes while the part is being squeezed, the elasticity of the pins will usually cause it to "grip" the holes as soon as they're released. Such gripping behavior may help keep the parts from being dislodged before wave soldering is complete.
Best Answer
The largest I'm aware of at the moment is LGA2011 so I wouldn't recommend dropping your 4096 pin limit to cover the near future as it's already close to the next nearest lower power of two of 2048. I would however recommend looking at your data structures and limits to make them dynamic, if performance and memory use are a problem I assume you're using some static data structures that will waste a lot of space for two pin devices?
Instead maybe allow for a 32-bit number in the metadata (only a few extra bytes) so that if packages of greater density arrive in the future they will be covered. If you're trying to store data in a relational database or similar and currently have 4096 columns it should be normalised and store each pin description in a seperate table.