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

Atmel library: SMD symbols lack pin for center pad #13

Closed
madworm opened this issue Jul 13, 2014 · 3 comments
Closed

Atmel library: SMD symbols lack pin for center pad #13

madworm opened this issue Jul 13, 2014 · 3 comments

Comments

@madworm
Copy link
Contributor

madworm commented Jul 13, 2014

At least one symbol (ATMEGA168A-M) [QFN32 + center pad (GND)] only has 32 electrical pins. The datasheet states that the center pad should be connected to GND, which requires another pin, e.g. #33.

The symbol should fully represent the device.

@ghost
Copy link

ghost commented Jul 14, 2014

This is a contentious issue.

  1. As Atmel wrote in his DS: "NOTE: Bottom pad should be soldered to ground.". Neither "must be", nor "have to be" only "should be". IMO this is a suggestion only.
  2. Bottom pad hasn't pad number nor name, so how to represent something that "electrically doesn't exist"?
  3. The QFN bottom pad can be connected to the GND net through static assignment in footprint.

@madworm
Copy link
Contributor Author

madworm commented Jul 14, 2014

1: maybe
2: Give it a number that is guaranteed to be unused ( last normal pad # + 1 - e.g. "33" for QFN32 ), as is done in [SMD_Packages:QFN32]. Some of these 'official' footprints are named e.g. "QFN48" (no pad) or "QFN48+1" (with pad). What is the harm of representing the extra pad in the symbol?
3: Yes, I can assign a net name. But every time I re-read the netlist that assignment goes away.

@ghost
Copy link

ghost commented Apr 16, 2015

  1. OK. Let the designer decide. When atmel.lib will be adjusted to KLC rules I will try to suggest to include bottom pad.
  2. QFN-xx-1EP footprints has this pad numbered as n+1.
  3. Like in 1. Let the designer decide, when we give him a choice.

@ghost ghost closed this as completed Apr 16, 2015
jkriege2 pushed a commit that referenced this issue Nov 23, 2017
sync with kicad master
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant