Skip to content
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.

add QFN-56-1EP_8x8mm_P0.5mm_EP6.1x6.1mm #271

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

penoud
Copy link
Contributor

@penoud penoud commented Jan 18, 2019

@codeclimate
Copy link

codeclimate bot commented Jan 18, 2019

Code Climate has analyzed commit 35778bb and detected 0 issues on this pull request.

View more on Code Climate.

@poeschlr
Copy link
Collaborator

The datasheet only gives nominal values for all dimensions (I really dislike that to be honest.)
I am checking if there is a JEDEC standard that we can use as a replacement for this parts drawing. (Currently i am waiting for the automated mail that will give me access.)

@penoud
Copy link
Contributor Author

penoud commented Jan 18, 2019

Fine, I will also prefer to follow JEDEC standard. Let me know if you find it.

@poeschlr
Copy link
Collaborator

poeschlr commented Feb 7, 2019

Sadly it seems i will not get an account at jedec (it might be that one would need a company mail address and state the same company in the application. I am not really prepared to do this.)


And another thing: I have noticed that body_height is not the correct name for what that parameter. I changed it to overall_height in my other parts already.

@evanshultz
Copy link
Collaborator

All the dimensions are there, I think, so it's only the tolerances that are missing. Right?

JEDEC MO-220 variation VLLD-2 may describe this package. I just use their package drawings as needed, so I'm not an expert, but it looks correct to me. If I Google for this string in a PDF file I am able to come up with the spec. Take a look and see if it seems suitable.

If so, though, it still leaves the question open of what link we use for the package drawing. This is also an open question for the non-EP SO packages in your PR, Rene.

@poeschlr
Copy link
Collaborator

poeschlr commented Jan 5, 2020

To be honest i kind of forgot about this pull request. If there is a fitting JEDEC standard then we can use that of course. If not then we might as well merge as is (possibly add the manufacturer name to the footprint name to show users that it is not really generic) We can then still link to the original datasheet but mention that the JEDEC standard was used for getting the tolerances. (plus adding the jedec name)

@evanshultz
Copy link
Collaborator

I checked again, and MO-220 (all variations) shows pin width as 0.18/0.25/0.3mm (min/nom/max). The datasheet only shows 0.23mm, which I assume is nominal. It seems this package matches.

@penoud
As it sounds like you don't have the JEDEC doc, I've updated the script and pushed changes. Can you please check that the package in the datasheet will fit with the changes I made, and then re-generate the footprint if it looks OK to you?

@chschlue
Copy link
Collaborator

#422

@evanshultz
Copy link
Collaborator

@chschlue
#422 has been merged.

@chschlue
Copy link
Collaborator

@evanshultz
I know. I mentioned #422 on all open, affected PRs back then for reference.

@evanshultz
Copy link
Collaborator

@chschlue
Since it was relatively easy to catch PRs here with multiple comments, I flagged you so if they only need a simple re-generation by the contributor with this repo updated it should be quick to wrap up the footprint and script PRs. :)

@myfreescalewebpage
Copy link
Contributor

@penoud the footprint need to be generated again following merge of #422, can you do that ?

@myfreescalewebpage
Copy link
Contributor

No news of the author.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants