10 open source boards using the ICP-20100
Real designs built with the ICP-20100, 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.
STM32
STM32-FC
NARAE-INHA-UNIV
50 × 70 mm106 parts4LNo license1ChariotFC
Rispats
272.4 × 570.4 mm106 parts2LNo license1STM32
CC M7
OzanE1
40 × 65 mm126 parts4LLGPL-2.10STM32
Jfox fmu
Jettanakorn
100 × 80 mm125 parts6LNo license0STM32
CC M7
OzanE1
40 × 65 mm123 parts4LLGPL-2.10STM32
Custom flight controller
Ekta-Gupta27
51 × 53.5 mm122 parts6LNo license0STM32
Aerix core
FBIopeningUPP
29 × 29 mm91 parts8LNo license0ESP32
Ambient air
mawoka-myblock
50 × 35 mm51 parts2LNo license0ESP32
Stencil
mawoka-myblock
50 × 35 mm47 parts2LNo license0Sensor
mawoka-myblock
10 × 22 mm11 parts2LNo license0
How designs wire the ICP-20100
Read from the KiCad layouts of 8 open source designs, one per repository: what each pin of the ICP-20100 connects to, and the resistors, capacitors and other passives placed on it.
- The VDD pin has a decoupling capacitor on 6 of 8 designs, most often 100 nF (then 10 µF).
- The VDDIO pin has a decoupling capacitor on 6 of 8 designs, most often 100 nF (then 10 µF).
- The RESV pins is tied to GND on 81% of them (not connected on 3).
- The CSB pin is tied to 3.3V on 5 of 8 designs (a signal on 3).
| Pin | Connected to | Parts on the pin |
|---|---|---|
| CSBpin 1 | Connected to: 3.3V 63% · a signal 38% | — |
| SCLpin 2 | Connected to: The microcontroller 63%, a connector 25%, BMM150 25% |
|
| VSSpin 3 | Connected to: GND 100% | — |
| SDA/SDIO/SDIpin 4 | Connected to: The microcontroller 63%, a connector 25%, BMM150 25% |
|
| VDDpin 5 | Connected to: 3.3V 100% |
|
| SDO/AD0pin 6 | Connected to: GND 63% · a signal 38% | — |
| RESVpin 8, 9 | Connected to: GND 81% · not connected 19% | — |
| VDDIOpin 10 | Connected to: 3.3V 100% |
|
1 more pin varies from design to design. Connections count pins, parts count designs; values in brackets are how many parts had that value. Designs read include STM32-FC by NARAE-INHA-UNIV, ChariotFC by Rispats, Custom flight controller pcb by Ekta-Gupta27 and Aerix core by FBIopeningUPP.
The ICP-20100 in open source designs
The gallery holds 10 open source boards using the ICP-20100 from 8 GitHub repositories; a typical one measures about 50 × 59.3 mm and carries around 106 components.
60% use four copper layers or more, and 20% carry an open source license.
The most starred is STM32-FC by NARAE-INHA-UNIV.
Parts used alongside the ICP-20100
What boards using the ICP-20100 are built for
ICP-20100: common questions
Where can I find a ICP-20100 reference design?
Each of the 10 boards on this page is a real design using the ICP-20100. 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 ICP-20100 VDD pin?
The VDD pin has a decoupling capacitor on 6 of 8 designs, most often 100 nF (then 10 µF). Counted from the KiCad layouts of 8 open source designs using the ICP-20100.
What decoupling capacitors do designs use on the ICP-20100 VDDIO pin?
The VDDIO pin has a decoupling capacitor on 6 of 8 designs, most often 100 nF (then 10 µF). Counted from the KiCad layouts of 8 open source designs using the ICP-20100.
How is the ICP-20100 RESV pin connected?
The RESV pins is tied to GND on 81% of them (not connected on 3). Counted from the KiCad layouts of 8 open source designs using the ICP-20100.
What parts are used alongside the ICP-20100?
The BMI088, BMM150, ICM-45686, ICM-42688-P and 24AA64T-I/OT appear in the most repositories here.
Which microcontrollers do boards using the ICP-20100 use?
Most are built on STM32 (6) and ESP32 (2).
How big is a typical board using the ICP-20100?
The median is 50 × 59.3 mm, and 40% are two-layer designs.
What is the most popular open source board using the ICP-20100?
By GitHub stars, STM32-FC by NARAE-INHA-UNIV, with 1 stars.
Can I simulate one of these boards using the ICP-20100 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.