7 open source boards using the TPS56A37RPAR
Real designs built with the TPS56A37RPAR, 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.
HackerDAQ Digital IO Card
multiplemonomials
90 × 90 mm251 parts2LNo license2TPS56A37RPAR-11V-22V-to-6V-6A
OptimusCoderr
42.2 × 23.8 mm20 parts2LNo license1STM32
Side board
AndreiVladescu
87.5 × 50.6 mm227 parts4LCERN-OHL-S-2.00ESP32
EnvDaqBox
Yongci
96.3 × 71 mm96 parts4LApache-2.00STM32
UYDUTEPE
emirhanuluakan
85 × 56 mm93 parts6LCERN-OHL-W-2.00Roamr power
uw-roamr
115 × 55 mm50 parts2LNo license6HackerDAQ Main Unit
multiplemonomials
244.5 × 91 mm177 parts4LNo license2
How designs wire the TPS56A37RPAR
Read from the KiCad layouts of 6 open source designs, one per repository: what each pin of the TPS56A37RPAR connects to, and the resistors, capacitors and other passives placed on it.
- The VIN_8 pin has a decoupling capacitor on 6 of 6 designs, most often 100 nF (then 10 µF).
- The FB_2 pin has a resistor to GND on 5 of 6 designs, most often 10 kΩ (then 20 kΩ).
- The SW_6 pin has a inductor on 5 of 6 designs, most often 3.3 µH (then 4.7 µH).
- The SW_6 pin has a series capacitor on 5 of 6 designs, most often 100 nF.
| Pin | Connected to | Parts on the pin |
|---|---|---|
| EN_1pin 1 | Connected to: Not connected 50% · GND 17% · a signal 33% |
|
| FB_2pin 2 | Connected to: Signal 100% |
|
| AGND_3pin 3 | Connected to: GND 83% · a signal 17% | — |
| PG_4pin 4 | Connected to: Signal 50% · not connected 33% · GND 17% |
|
| SS_5pin 5 | Connected to: Signal 67% · not connected 33% |
|
| SW_6pin 6 | Connected to: Signal 83% · not connected 17% |
|
| BOOT_7pin 7 | Connected to: Signal 100% |
|
| VIN_8pin 8 | Connected to: 12V 67% · a signal 33% |
|
| PGND_9pin 9 | Connected to: GND 100% | — |
| MODE_10pin 10 | Connected to: Signal 100% |
|
| VIN_2pin 11 | Connected to: VBAT_F 50% · a signal 50% |
|
| VIN_3pin 12 | Connected to: VBAT_F 50% · a signal 50% |
|
| VIN_4pin 13 | Connected to: VBAT_F 50% · a signal 50% |
|
Connections count pins, parts count designs; values in brackets are how many parts had that value. Designs read include Roamr power by uw-roamr, HackerDAQ Digital IO Card by multiplemonomials, TPS56A37RPAR-11V-22V-to-6V-6A by OptimusCoderr and Side board by AndreiVladescu.
The TPS56A37RPAR in open source designs
The gallery holds 7 open source boards using the TPS56A37RPAR from 6 GitHub repositories; a typical one measures about 90 × 56 mm and carries around 96 components.
57% use four copper layers or more, and 43% carry an open source license.
The most starred is Roamr power by uw-roamr.
What boards using the TPS56A37RPAR are built for
TPS56A37RPAR: common questions
Where can I find a TPS56A37RPAR reference design?
Each of the 7 boards on this page is a real design using the TPS56A37RPAR. 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 decoupling capacitors do designs use on the TPS56A37RPAR VIN_8 pin?
The VIN_8 pin has a decoupling capacitor on 6 of 6 designs, most often 100 nF (then 10 µF). Counted from the KiCad layouts of 6 open source designs using the TPS56A37RPAR.
What resistor goes on the TPS56A37RPAR FB_2 pin?
The FB_2 pin has a resistor to GND on 5 of 6 designs, most often 10 kΩ (then 20 kΩ). Counted from the KiCad layouts of 6 open source designs using the TPS56A37RPAR.
How is the TPS56A37RPAR SW_6 pin connected?
The SW_6 pin has a inductor on 5 of 6 designs, most often 3.3 µH (then 4.7 µH). Counted from the KiCad layouts of 6 open source designs using the TPS56A37RPAR.
Which microcontrollers do boards using the TPS56A37RPAR use?
Most are built on STM32 (2) and ESP32 (1).
How big is a typical board using the TPS56A37RPAR?
The median is 90 × 56 mm, and 43% are two-layer designs.
What is the most popular open source board using the TPS56A37RPAR?
By GitHub stars, Roamr power by uw-roamr, with 6 stars.
Can I simulate one of these boards using the TPS56A37RPAR 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.