5 open source boards using the AVR-64DA32
Real designs built with the AVR-64DA32, from public GitHub projects: a quick way to see how others power, decouple and connect it. Each board comes with its KiCad files, full parts list and a render — and you can simulate its firmware on HardLabs.
RTB D16
git4dcc
17 × 10.9 mm43 parts6LApache-2.02AVR/Arduino
RTB D98
git4dcc
12.7 × 8.8 mm60 parts4LApache-2.01RTB D15
git4dcc
76 × 11 mm65 parts4LApache-2.00AVR/Arduino
RTB D24
git4dcc
17 × 10.9 mm52 parts6LApache-2.00RTB E15
git4dcc
48.4 × 21.6 mm21 parts2LApache-2.00
How designs wire the AVR-64DA32
Read from the KiCad layouts of 5 open source designs, one per repository: what each pin of the AVR-64DA32 connects to, and the resistors, capacitors and other passives placed on it.
- The PD1 pin has a series resistor on 5 of 5 designs, most often 33 kΩ (then 220 kΩ).
- The PD2 pin has a series resistor on 5 of 5 designs, most often 1 kΩ (then 220 kΩ).
- The PD3 pin has a series resistor on 5 of 5 designs, most often 3.3 kΩ (then 2.2 kΩ).
- The PD4 pin has a series resistor on 5 of 5 designs, most often 2.2 kΩ (then 22 kΩ).
| Pin | Connected to | Parts on the pin |
|---|---|---|
| PC1pin 7 | Connected to: Signal 80% · not connected 20% |
|
| PC2pin 8 | Connected to: Signal 100% |
|
| PC3pin 9 | Connected to: Signal 80% · not connected 20% |
|
| PD0pin 10 | Connected to: Signal 100% |
|
| PD1pin 11 | Connected to: Signal 100% |
|
| PD2pin 12 | Connected to: Signal 100% |
|
| PD3pin 13 | Connected to: Signal 100% |
|
| PD4pin 14 | Connected to: Signal 100% |
|
| PD5pin 15 | Connected to: Signal 100% |
|
| PD6pin 16 | Connected to: VREF 60% · a signal 40% | — |
| PD7pin 17 | Connected to: A connector 40% |
|
| AVDDpin 18 | Connected to: 3.3V 100% |
|
| GNDpin 19, 29, 33 | Connected to: GND 100% | — |
| PF0/TOSC1pin 20 | Connected to: A connector 40% |
|
| PF1/TOSC2pin 21 | Connected to: A connector 40% |
|
| PF3pin 23 | Connected to: A connector 40% |
|
| PF4pin 24 | Connected to: Signal 100% |
|
| PF5pin 25 | Connected to: Not connected 60% · a signal 40% | — |
| PF6/RESETpin 26 | Connected to: Not connected 60% · a signal 40% | — |
| VDDpin 28 | Connected to: 3.3V 100% |
|
11 more pins vary from design to design. Connections count pins, parts count designs; values in brackets are how many parts had that value. Designs read include RTB D16 by git4dcc, RTB D98 by git4dcc, RTB D15 by git4dcc and RTB D24 by git4dcc.
The AVR-64DA32 in open source designs
The gallery holds 5 open source boards using the AVR-64DA32 from 5 GitHub repositories; a typical one measures about 17 × 10.9 mm and carries around 52 components.
80% use four copper layers or more, and 100% carry an open source license.
The most starred is RTB D16 by git4dcc.
Parts used alongside the AVR-64DA32
Microcontrollers on boards using the AVR-64DA32
AVR-64DA32: common questions
Where can I find a AVR-64DA32 reference design?
Each of the 5 boards on this page is a real design using the AVR-64DA32. Open one to see how it is wired up, with the full BOM, a render of the layout and links to its KiCad files.
What resistor goes on the AVR-64DA32 PD1 pin?
The PD1 pin has a series resistor on 5 of 5 designs, most often 33 kΩ (then 220 kΩ). Counted from the KiCad layouts of 5 open source designs using the AVR-64DA32.
What resistor goes on the AVR-64DA32 PD2 pin?
The PD2 pin has a series resistor on 5 of 5 designs, most often 1 kΩ (then 220 kΩ). Counted from the KiCad layouts of 5 open source designs using the AVR-64DA32.
What resistor goes on the AVR-64DA32 PD3 pin?
The PD3 pin has a series resistor on 5 of 5 designs, most often 3.3 kΩ (then 2.2 kΩ). Counted from the KiCad layouts of 5 open source designs using the AVR-64DA32.
Which microcontrollers do boards using the AVR-64DA32 use?
Most are built on AVR/Arduino (2).
How big is a typical board using the AVR-64DA32?
The median is 17 × 10.9 mm, and 20% are two-layer designs.
What is the most popular open source board using the AVR-64DA32?
By GitHub stars, RTB D16 by git4dcc, with 2 stars.
Can I simulate one of these boards using the AVR-64DA32 before building it?
Yes. HardLabs turns a board's netlist and BOM into a working simulation, so you can boot and test firmware against it with no hardware on your desk.