KiCad / kicad-footprints

Official KiCad Footprint Libraries for Kicad version 5
https://kicad.github.io/footprints
Other
613 stars 715 forks source link

TI-specific footprint names #606

Open evanshultz opened 6 years ago

evanshultz commented 6 years ago

@poeschlr @jkriege2 @Ratfink https://github.com/KiCad/kicad-footprints/pull/604 brought this up again so I think it's worth talking about. We have many TI-specific footprints using different nomenclature. TI often gives various names for the same footprint which can make it hard to know what to call any given footprint.

We should be consistent in how we name the footprints so contributors and users don't have such a burden. With searching in KiCad, we can settle on a nice footprint naming scheme and then include other information in the description and keywords for discovery (plus default footprints, of course).

I confirmed with TI that the 3-letter name (RLW in the link above) is more descriptive and unique than S-PWQFN-N20. So perhaps we should go with that?

Some examples of the confusion:

Ratfink commented 6 years ago

It looks like they refer to RUM0016A also as SQB16A, S-PQFP-N16, and simply RUM. You say the 3-letter name is more descriptive, but is it the most descriptive? Or is it descriptive enough that we could add our usual fields to make it fully descriptive?

If we decide to stop using the names like Texas_S-PQFP-N16, we'll have to update KLC rule F2.3 to use the new nomenclature.

evanshultz commented 6 years ago

Yes, that is what I am saying, according to TI. They tell me the 3 letter nomenclature is the most unique term for a package/footprint.

poeschlr commented 5 years ago

If we choose to rename footprints now then we need to keep the original one such that we do not break old designs. (Otherwise the lib can not be included in bugfix releases) Such orphaned footprints could be marked in the description field for later deletion (or we could create a list somewhere)

s-light commented 5 years ago

any news on this? i have found some Texas QFN footprints that seems to be not generated by the scripts: searched in kicad-footprint-generator/..../Package_DFN_QFN/size_definitions/qfn_texas.yaml and kicad-footprints/..../Package_DFN_QFN.pretty

i originally wanted to add a N40 variant with other EP dimensions.. i searched some more and on this journey found the TI -Package Lookup tool: http://www.ti.com/support-packaging/packaging-tools/find-packages.html

there the 'RTA' Package - also called S-PQFP-N40 (WQFN) i wanted to add linked to http://www.ti.com/lit/ml/mpqf134a/mpqf134a.pdf and in this document it is clearly stated that the dimensions of the EP are not specific to this Package but are defined in the Datasheet of the part itself. conclusion: we need the EP size in the footprint name

Question remains: should i add this as a Texas Specific part name or better use the 'normal' name form? @pointhi can the QFN-script can generate the D-Shaped Pads as in the Datasheets of these Parts? image (screenshot comes from TLC5951 Page 45)

evanshultz commented 5 years ago

There are many still hand-built. The scripts are relatively new and we've been using them to add new footprints and not replaced existing ones (yet).

Great find on the packaging link from TI! I had not seen this before but surely we'll make good use of it. And it does seem to indicate that the 3-letter code does define uniqueness at TI. Thanks again!

I checked out the datasheets for the RTA package parts (http://www.ti.com/packaging/docs/searchproductbypackage.tsp?orderablePartNumber=&packageDesignator=RTA&pinCount=40&results=results#resultspage) and found a variety of documentation methods:

The last bullet above shows RTA0040A but the 4.15mm one doesn't have a corresponding number. In the bottom right corner of the drawings the 4.15mm one has 4206335-2/F and the last bullet is 4214989/B. It appears this is just the drawing number and isn't helpful to us either.

So yes, it does seem like the EP size should be added since that's the most clear solution to this mess.

While TI surely uses generic packages (like from Amkor), at least in some cases, I think going specific is good. AFAIK, using Texas_RTA_EPXxYmm or the standard QFN package name but prefixed by Texas_. I prefer the former since it includes the 3-letter designation.

No, the script cannot currently generate D-shape pads.