Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to Create QSOP-EP 16 Footprint #2

Open
sabinoj opened this issue Dec 11, 2014 · 3 comments
Open

Need to Create QSOP-EP 16 Footprint #2

sabinoj opened this issue Dec 11, 2014 · 3 comments
Assignees

Comments

@sabinoj
Copy link
Contributor

sabinoj commented Dec 11, 2014

I need to create a custom footprint for the MAX15046BAEE. The footprint (QSOP-EP 16) is a QSOP16 with a large pad on the body of the chip. Maxim Integrated offers .bxl files that can be converted into their respective symbols and footprints, the only issue is that they do not have gEDA listed, though they do have EAGLE listed.

Provided are relevent documentation regarding the dimensions of the chip and the link search for the .bxl format.

http://pdfserv.maximintegrated.com/land_patterns/90-0239.PDF

http://www.maximintegrated.com/en/design/packaging/cad/

I will also look into contacting their technical support to see if they may be able to create the footprint for us if I am unable to complete this footprint.

@sabinoj sabinoj self-assigned this Dec 11, 2014
@sabinoj
Copy link
Contributor Author

sabinoj commented Dec 11, 2014

I have created the MAXIM folder and created the QSOPEP16 with regards to MAXIM's specifications. I have not tested it yet, if any issues occur I will remove it and re-evaluate it.

@jmaltby
Copy link

jmaltby commented Dec 12, 2014

Should we have someone review new footprints that are made? I see a new footprint being issued much like a new mechanical drawing, it should be approved. Just to be clear, I doubt that there is anything wrong with John's work, I just think this would be a good opportunity to get a newer member exposed to PCB design.

@sabinoj
Copy link
Contributor Author

sabinoj commented Dec 12, 2014

I agree it should go through the basic pull request process where it can be evaluated by the managing parties before confirming the merge.

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

No branches or pull requests

2 participants