-
Notifications
You must be signed in to change notification settings - Fork 715
Add 121-ball 0.8mm pitch BGA footprint. #693
Conversation
@evanshultz can you please take a look? |
Hey guys, is this a lattice only package or does anyone else use it? One remark, looking at: www.latticesemi.com/-/media/LatticeSemi/Documents/ApplicationNotes/PT/PCBLayoutRecommendationsforBGAPackages.ashx?document_id=671 one can see that the solder mask opening and pad dimensions are not the same. Do you have a pcb recommendation for this specific footprint? |
I based this footprint on Table 1 from that document. Specifically, the 121-ball caBGA on page 60 of the PackageDiagrams document has e = 0.8, b = 0.4, as does the 381-ball caBGA on page 99. The 256-ball caBGA has b = 0.45. So I used the PCB Solder Land Diameter from the NSMD column of the 2nd row of the 0.8mm Ball Pitch section of that table, which includes the 381-ball caBGA. EDIT: As far as whether anyone but Lattice uses this footprint - I don't know. |
Ok , than I do not get the dimensions for the solder pad and solder mask opening. I understand the physical dimensions of the balls (pitch 0,8mm and diameter 0,4mm as you said) Because the package only uses SMD for the device pads we need a NSMD pad on this footprint. The only thing that bugs me is that there is no definition for the solder mask opening. The Artix package I pulled (#616) has an example of what I mean. For the name, I could only find lattice products which mach the dimensions of this footprint. |
You're right - the document does not specify the size of the mask opening for NSMD, or the size of the pad for SMD. I agree that they should, but they don't. Given that, I left it as 0 as per the KLC, allowing the user to choose the value which matches their PCB process requirements. If you'd prefer I set it to a specific value, just let me know what that is.
I didn't run into any of these either, however, there's really nothing Lattice-specific about a fully-populated 11x11 BGA with 0.8mm pitch. If it were partially unpopulated (as many of the ECP5 packages, for example), then I'd agree with a vendor-specific name, but this package seems quite generic to me. The fact that nobody uses it now doesn't mean they won't in the future. If you tell me to add Lattice to the name again, I'll do it, but I wanted to express my disagreement once. |
Please have in mind that I am no maintainer and do not decide on anything. I'm just trying to help out a bit in order to speed up the merging of PRs. I don't have a problem with the name of your footprint, just making sure we thought about it :) So we'll have to wait for an official response |
Absolutely :) I appreciate your insight and feedback! |
The corresponding symbol PR is KiCad/kicad-symbols#777 and it now passes all Travis tests except the lack of this footprint. |
Just a reminder that this PR exists - is someone available to review? |
sure thing :) |
Hi @awygle A few notes:
|
Will fix.
Will fix.
Sure, just let me know what to do.
As I mentioned above, I went back and forth on this - so you want the explicit value to be set, rather than 0 as the KLC specifies? |
The above three issues have been corrected. |
thanks for the contribution :) |
Based on Lattice caBGA package, found at http://www.latticesemi.com/view_document?document_id=213.
Intended for the Lattice ice40HX FPGA in BG121 package - keep an eye out for the symbol PR.
Screenshot:
Thanks for creating a pull request to contribute to the KiCad libraries! To speed up integration of your PR, please check the following items: