Add SIL0008D MicroSiP Package

[awygle]

Adds the SIL0008D MicroSiP package used in TI's TPS82130 and similar parts.

Datasheet is http://www.ti.com/lit/ds/symlink/tps82130.pdf

Wasn't sure about the Pin 1 indicator, or even whether this goes in Packages_LGA at all... please feel free to advise.

---

Thanks for creating a pull request to contribute to the KiCad libraries! To speed up integration of your PR, please check the following items:

• Provide a URL to a datasheet for the footprint(s) you are contributing
• An example screenshot image is very helpful
• If there are matching symbol or 3D model pull requests, provide link(s) as appropriate
• Check the output of the Travis automated check scripts - fix any errors as required

[awygle]

Symbol PR is KiCad/kicad-symbols#921

[ghost]

I made/updated a generator script which also builds this package:
pointhi/kicad-footprint-generator#184

[Misca1234]

Is the provided foot print in this push from the script generation in push
pointhi/kicad-footprint-generator#184 ?

If so, all looks good

[ghost]

No, it is not the same.
The Script-PR might need some changes.

Differences compared to this PR

• Exposed pad is slightly smaller
• Pads are bigger in y direction
• Pin1 indicator has another style

Here is a screenshot of the script output:

[Misca1234]

@awygle
What do you say about making your foot print script based as well?

[awygle]

I have mixed feelings, frankly, but I'm open to giving it a shot. I'd like to see the script changed to more closely match both the KLC and the manufacturer recommendation (which I'm willing to do/help with). I'm a bit bogged down at the moment but I'll go to script based for this PR and the CM49 one sometime this week.

[Misca1234]

I have mixed feelings, frankly, but I'm open to giving it a shot.
I'd like to see the script changed to more closely match both the KLC and the manufacturer
recommendation (which I'm willing to do/help with). I'm a bit bogged down at the moment but I'll go

The nice thing with the scripts is that we only examine the parameters you have added to the .yaml file, it is understood and assumed that the scripts always do right
(if they do wrong, we just correct the script and remake all the depending foot prints)

It works like this

1. You checkout the repository https://github.com/pointhi/kicad-footprint-generator
2. You find the correct library and edit the right .yaml file
3. Generate the .kicad_mod file
4. Make a push to the https://github.com/KiCad/kicad-footprints with the .kicad_mod
5. Make a push to https://github.com/pointhi/kicad-footprint-generator with the generated .yaml file

We will never review the .kicad_mod file itself, only the .yaml file (add cross links between the both pushes so they are easy to find)

In your case you should update the file with the dimensions of your desired foot print
https://github.com/pointhi/kicad-footprint-generator/blob/master/scripts/Packages/Package_LGA/lga_definitions.yaml

You generate the foot print in directory kicad-footprint-generator/blob/master/scripts/Packages/Package_LGA/

python ipc_lga_layoutBorder_generator.py lga_definitions.yaml

Here is an example of such push
#966

[Misca1234]

@awygle
Have you giving it a shoot ?

[poeschlr]

I assigned myself as i will look into the script. Right now the LGA generator is kind of a weak spot. (It has not been updated to my latest discoveries regarding correct handling of tolerances.) So this one can be used as an excuse to fix that.

[poeschlr]

Scripted alternative available in #1263