Skip to the content
4 layers53.5 × 53.5 mmMiniTULPAR, the printed circuit board in 3D

This project is under active development. The table below shows what is finished and what is still in progress:

Size
53.5 × 53.5 mm
Copper layers
4
Thickness
1.6 mm
Parts
92
Nets
86
Pads
375
Tracks, vias
814, 289
Pours
19
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
24 Aug 2026
Updated
24 Aug 2026

Overview

MiniTULPAR is an open-source printed circuit board by ErdemHtyl, from the ErdemHtyl/Tulpar_Mini_FCB repository on GitHub, published under the BSD-3-Clause licence. It is a 4-layer board of 53.5 × 53.5 mm with 92 parts on 86 nets, routed with 814 tracks and 289 vias.

It is built around the STM32F405RGT6, BMP581 and IIS2MDC, with the W25Q128JVSIQ, ICM-42670-P and LD39200PU33R among its other parts. Its parts include 31 capacitors, 16 resistors, 13 connectors, 7 ICs and 6 diodes. It belongs with the STM32 boards of this library.

Main components

12

README

README.md

MiniTULPAR — Custom Flight Controller Board (FCB)

A quadcopter flight controller designed from scratch around the STM32F405. Schematic, 4-layer PCB, power architecture, sensor integration and firmware all live in this repository — no existing open-source flight controller is used.

Hardware Firmware MCU PCB EDA


⚠️ Project Status

This project is under active development. The table below shows what is finished and what is still in progress:

ComponentStatusNotes
Schematic design✅ Rev A completeMiniTulpar_Schematic.pdf
PCB layout (4 layer)✅ Complete53.6 × 53.6 mm, 1.6 mm
Manufacturing files (Gerber/BOM/CPL)✅ Generatedmfr/
System architecture documentation✅ Completedocs/architecture.md
Pin configuration (CubeMX)✅ VerifiedNo timer channel conflicts
Clock tree configuration✅ Verified168 MHz SYSCLK, 48 MHz USB
Board fabrication and assembly🔄 Planned—
Firmware🚧 In development — not startedSee the roadmap below
Flight testing⏳ BlockedDepends on firmware
Lower-cost board variants🔄 PlannedSee Planned Variants

Firmware note: the firmware is in development. Nothing described in the roadmap below has been implemented yet — drivers, sensor fusion, PID control and the safety layer are all still to be written. The architectural decisions behind them (bus allocation, timer/DMA assignments, interrupt priorities) are documented in advance in docs/architecture.md, and development will follow that document. The board does not fly in its current state.


Table of Contents


Project Goal

The goal is to design, understand and implement every hardware and software component rather than buying an off-the-shelf flight controller (Betaflight / ArduPilot hardware). That includes:

  • Multi-layer PCB design and power architecture
  • Writing IMU / barometer / magnetometer drivers from scratch
  • Sensor fusion (Mahony / Madgwick / EKF)
  • PID-based stabilisation and mixing
  • Generating the DShot ESC protocol directly from timers and DMA
  • GPS, telemetry, blackbox logging and the failsafe/safety layer

Every design decision is recorded in docs/architecture.md together with the alternative that was rejected and the reason it was rejected.


Hardware Overview

FeatureValue
MCUSTM32F405RGT6 — Cortex-M4F, 168 MHz, 1 MB Flash, 192 KB RAM (128 KB SRAM + 64 KB CCM)
Oscillator8 MHz HSE (ECS-80-10-30B-CKM-TR)
PCB4 layer, 53.6 × 53.6 mm, 1.6 mm thickness
PowerUSB-C 5 V ↔ VIN, Schottky OR (D2/D3) + JP1 jumper → LD39200PU33R 3.3 V / 2 A LDO
IMUICM-42670-P (accel + gyro) — SPI1 @ 21 MHz, INT1 → PC4
BarometerBMP581 — I2C2, 0x46, INT → PB1
MagnetometerIIS2MDC — I2C2, 0x1E, DRDY → PB2
Blackbox flashW25Q128JVS 16 MB — SPI2 @ 21 MHz
Motor outputs4× DShot600 — TIM8_CH1..CH4 (PC6–PC9), single DMA burst
Auxiliary PWMTIM1_CH1/CH3 (PA8/PA10) + TIM3_CH1/CH2 (PB4/PB5 — camera gimbal)
RC inputCRSF / ELRS — UART4 (J10)
GPSUSART2 (J12)
TelemetryUART5 (J11)
Spare UARTUSART3 (J5)
External I²CI2C1 (J6) — separate from the internal sensor bus
ADCBattery voltage → PC3 (ADC1_IN13), external → PC2 (ADC1_IN12)
USBUSB-C 2.0, USBLC6-2SC6 ESD protection + polyfuse + 5.1 kΩ CC
Debug10-pin 1.27 mm SWD (J13)
LEDs3× status LEDs + power LED

System Architecture

mermaid
flowchart TB
    subgraph PWR["Power Tree"]
        XT[["VIN / Rail"]]
        USB5[["USB-C 5 V"]]
        OR{{"D2 / D3 Schottky OR<br/>+ JP1"}}
        LDO["U1 LD39200PU33R<br/>3.3 V / 2 A"]
        XT --> OR
        USB5 --> OR
        OR --> LDO
        LDO --> V33[("+3.3 V")]
        LDO -. "FB1 600Ω@100MHz" .-> VDDA[("VDDA")]
    end

    subgraph MCU["STM32F405RGT6 @ 168 MHz"]
        CORE["Cortex-M4F<br/>FPU + DSP"]
    end

    subgraph FAST["High rate — SPI1 @ 21 MHz"]
        IMU["U2 ICM-42670-P<br/>CS = PA4 · INT1 → PC4"]
    end

    subgraph SLOW["Slow sensor bus — I2C2 @ 400 kHz"]
        BARO["U4 BMP581 · 0x46"]
        MAG["U6 IIS2MDC · 0x1E"]

The critical data path: the IMU's INT1 line raises an EXTI interrupt → a SPI1 DMA burst read starts → the DMA completion interrupt runs the filter, PID and mixer chain → the result is encoded into a DShot frame and handed to the TIM8 DMA. The whole chain completes inside one interrupt context, never waiting on any other peripheral.


Bus Allocation and Rationale

The founding principle of the architecture:

The critical path lives on SPI. Everything non-critical lives on I²C.

DeviceBusSpeedWhy
ICM-42670-PSPI1 (alone)21 MHzThe only high-rate path; the same read takes ~68× longer on I²C
BMP581 + IIS2MDCI2C2 (shared)400 kHz~4 % combined bus load; neither is on the critical path
W25Q128JVSSPI2 (alone)21 MHzA sector erase can take 400 ms and must never delay a gyro read
External devicesI2C1400 kHzA cable means ESD, capacitance and lockup risk — isolated from the internal sensors

Why the IMU is on SPI. A 15-byte sample read takes ~5.7 µs on SPI1 versus ~388 µs on I²C Fast-mode:

Loop rateSPI loadI²C load
1 kHz0.6 %39 %
1.6 kHz0.9 %62 %
4 kHz2.3 %impossible

Beyond bandwidth: SPI is deterministic (no clock stretching), has no bus-lockup failure mode, survives the noisy environment of ESCs switching at 20–40 kHz thanks to its push-pull drivers, and costs the CPU nothing when paired with DMA.


Timer and DMA Allocation

Timer assignment

The current CubeMX pin configuration is conflict-free — all four motor outputs, both auxiliary PWM channels and both gimbal channels are usable at the same time:

FunctionTimerChannelPinTimer clock
Motor 1–4TIM8CH1–CH4PC6 / PC7 / PC8 / PC9168 MHz (APB2)
Aux PWM 1–2TIM1CH1 / CH3PA8 / PA10168 MHz (APB2)
Camera gimbal 1–2TIM3CH2 / CH1PB5 / PB484 MHz (APB1)

The motors are on TIM8 rather than TIM3 for four reasons:

  1. TIM3_CH1 can be routed to either PC6 or PB4, but only one at a time — putting the motors on TIM8 leaves TIM3 entirely free for the gimbal outputs.
  2. TIM8 sits on APB2, so its timer clock is 168 MHz (twice TIM3's) — twice the DShot bit-timing resolution.
  3. TIM8 is an advanced-control timer: its break input can drive a hardware motor cutoff for failsafe later.
  4. All four motors on one timer are bit-synchronous and need only a single DMA burst (TIM8_UP + DMAR).

Because the two gimbal channels sit on TIM3 (84 MHz) and the aux PWM channels on TIM1 (168 MHz), driving both at a common servo rate means programming the two timers separately with different prescaler values.

DShot600 timing (TIM8 @ 168 MHz)

ProtocolARRCCR for "0"CCR for "1"Frame
DShot30055921042053.3 µs
DShot60027910521026.7 µs

DShot is digital: ESC calibration stops being a step that exists, and every frame carries a 4-bit CRC — a command corrupted by noise is discarded by the ESC instead of silently applying the wrong throttle.

DMA assignments (under the RM0090 Table 42/43 constraints)

DMA2

StreamChAssignment
S03SPI1_RX — IMU read (the critical path)
S17TIM8_UP — DShot burst output
S53SPI1_TX — IMU command
S2/S3/S4/S77Reserved: bidirectional DShot (unused in v1)

DMA1

StreamChAssignment
S04UART5_RX — telemetry
S14USART3_RX — spare
S24UART4_RX — CRSF/RC (420 kbaud, critical)
S30SPI2_RX — flash
S40SPI2_TX — blackbox
S54USART2_RX — GPS (circular + IDLE)
S64USART2_TX — GPS configuration
S74UART5_TX — telemetry

I2C1/I2C2, UART4_TX, USART3_TX and ADC1 are interrupt-driven — their streams went to higher-value work and their load is negligible.

Interrupt priorities (NVIC)

PriorityInterrupt
0EXTI4 — IMU INT1 (timestamps the sampling instant)
1DMA2_S0 — SPI1_RX complete (triggers the control chain)
2DMA2_S1 — TIM8_UP (motor frame)
3DMA1_S2 — UART4_RX (RC / failsafe)
4DMA1_S5 — USART2_RX (GPS)
5I2C2_EV / I2C2_ER
6SysTick
7Flash, UART5, USB

The rule: blackbox writes, USB and telemetry must never preempt the control loop.

Target timing budget (1 kHz loop)

StepDurationOccupies the CPU?
IMU SPI burst read5.7 µsNo (DMA)
Filtering (3× biquad + PT1)~10 µsYes
Attitude update (Mahony)~20 µsYes
PID (3 axes)~12 µsYes
Mixer + motor limiting~4 µsYes
DShot frame encoding~6 µsYes
Total CPU~52 µs≈ 5 % load

Pin Map

This table is the single source of truth for the pin map — it is never maintained in two places.

PortSignalFunction
PA4 / PA5 / PA6 / PA7SPI1 CS/SCK/MISO/MOSIIMU
PC4INT_IMU1EXTI4 — data ready
PB12 / PB13 / PB14 / PB15SPI2 CS/SCK/MISO/MOSIBlackbox flash
PB10 / PB11I2C2 SCL/SDAInternal sensor bus
PB1 / PB2INT_BAR / INT_MAGEXTI1 / EXTI2
PB8 / PB9I2C1 SCL/SDAExternal connector (J6)
PC6 / PC7 / PC8 / PC9DSHOT_1..4TIM8_CH1..CH4
PA8 / PA10Aux PWM 1–2TIM1_CH1 / TIM1_CH3
PB4 / PB5CAM_GIMBAL2 / CAM_GIMBAL1TIM3_CH1 / TIM3_CH2
PA0 / PA1UART4 TX/RXCRSF / RC (J10)
PA2 / PA3USART2 TX/RXGPS (J12)
PC12 / PD2UART5 TX/RXTelemetry (J11)
PC10 / PC11USART3 TX/RXSpare (J5)
PC2 / PC3ADC1_IN12 / ADC1_IN13External ADC / battery
PA11 / PA12 / PA9USB DM/DP/VBUSUSB-C
PA13 / PA14SWDIO / SWCLKSWD (J13)
PC13 / PC14 / PC15LD1 / LD2 / LD3Status LEDs
PH0 / PH1HSE IN/OUT8 MHz crystal

Unused and available: PA15, PB0, PB3, PB6, PB7, PC0, PC1, PC5. PB6/PB7 = USART1, PB0/PB1 = TIM3_CH3/CH4, and PB0 + PC5 together are exactly the chip select + interrupt pair a second IMU would need.

Full pin table including physical pin numbers: docs/architecture.md


Clock Configuration

8 MHz HSE crystal → PLL (M = 4, N = 168, P = 2) → 168 MHz SYSCLK, with the PLL Q divider set to 7 for the 48 MHz USB clock. CSS (clock security system) is enabled, so a crystal failure falls back to the HSI instead of stopping the core.

DomainPrescalerFrequency
SYSCLK / HCLK (AHB, core, memory, DMA)/1168 MHz
APB1 peripheral clock (PCLK1)/442 MHz
APB1 timer clock (TIM3 …)—84 MHz
APB2 peripheral clock (PCLK2)/284 MHz
APB2 timer clock (TIM1, TIM8)—168 MHz
USB OTG FSPLL /Q = 748 MHz
IWDGLSI32 kHz

The RTC runs from the internal LSI — no LSE crystal is fitted, because PC14/PC15 are used as status LED outputs. This is irrelevant for a flight controller.

SPI1 and SPI2 both run at 21 MHz: SPI1 from PCLK2 (84 MHz ÷ 4) and SPI2 from PCLK1 (42 MHz ÷ 2), both comfortably under the ICM-42670-P's 24 MHz and the W25Q128's 133 MHz limits.


Firmware Roadmap

🚧 Nothing in this section has been implemented yet. The order is chosen to minimise bring-up risk; each step depends on the previous one being verified.

Stage 0 — Bring-up

  • Project skeleton and build system
  • SWD connection and LED blink — is the board alive?
  • Bring up the clock tree on hardware and measure it (8 MHz HSE → 168 MHz)
  • Generate the pin configuration from the pin map above
  • Debug console over USB CDC

Stage 1 — Sensors

  • SPI1 + DMA driver, ICM-42670-P WHO_AM_I
  • Raw IMU reads (INT1 → EXTI → DMA burst chain)
  • IMU internal UI filter / ODR configuration (anti-aliasing is critical)
  • I2C2 as a non-blocking state machine + timeouts + bus recovery (9× SCL)
  • BMP581 driver (pressure → altitude)
  • IIS2MDC driver + hard/soft-iron calibration
  • Gyro/accel calibration and temperature compensation

Stage 2 — Actuators

  • DShot600 frame generation via TIM8 + DMAR burst
  • Motor test mode — props off, verify frames on a scope
  • Mixer (quad X), motor limiting / airmode

Stage 3 — Control

  • Gyro filter chain (biquad LPF + notch + PT1)
  • Attitude estimation — Mahony (EKF later)
  • Rate PID loop (acro mode)
  • Angle/horizon loop (self-level)
  • PID gain tuning interface

Stage 4 — RC and safety

  • CRSF parser (UART4 DMA + IDLE line)
  • Arming/disarming state machine + sensor health check
  • IWDG (~50 ms, fed only by the main control loop)
  • Gyro timeout → immediate disarm
  • RC timeout (~500 ms) → progressive throttle-cut failsafe
  • Battery voltage monitoring + low-voltage warning

Stage 5 — Navigation and logging

  • GPS UBX/NMEA parser (USART2 DMA)
  • Blackbox logging (SPI2 → W25Q128, pre-erase while idle)
  • Telemetry (UART5) and the CRSF back-channel
  • Altitude hold → position hold → return-to-home

Stage 6 — Advanced

  • Bidirectional DShot (RPM telemetry) + RPM-based notch filtering
  • EKF-based sensor fusion
  • Host-side unit tests (HIL/SIL)

The safety layer is non-negotiable: motors are always disarmed at power-up; arming requires low throttle plus an explicit arm command plus a sensor health check.


Planned Variants

MiniTULPAR Rev A is the reference design — it is deliberately built with good parts rather than cheap ones, so that when something misbehaves the cause is the design and not the bill of materials.

More affordable versions of this board will be added later. The plan is to publish lower-cost variants alongside the reference design, so the project stays buildable on a smaller budget:

  • Cheaper sensor options (a lower-cost IMU and barometer in place of the ICM-42670-P / BMP581)
  • A reduced-feature build — dropping the blackbox flash, the magnetometer or the gimbal outputs where they are not needed
  • Widely stocked, low-cost alternatives for the passives, connectors and the regulator
  • Where a substitution changes the firmware, the difference will be documented rather than hidden behind a build flag

Each variant will ship with its own BOM and a short note on what was traded away. The reference design stays the one that is documented and tested first.


Repository Layout

Hardware and firmware live in a single repository (monorepo) — when a pin changes, KiCad, the documentation and the firmware are all updated in the same commit.

text
custom-fcb/
├── README.md
├── docs/                    architecture, power tree, pinout, BOM, test plan
│   ├── architecture.md      design decisions and their rationale (EN)
│   └── images/
├── hardware/
│   ├── MiniTULPAR.kicad_pro / .kicad_sch / .kicad_pcb
│   ├── libs/                custom symbol + footprint libraries
│   ├── datasheets/
│   └── production/          Gerber / drill / BOM / CPL — gitignored
└── firmware/                🚧 in development — nothing implemented yet
    ├── drivers/             imu, baro, mag, gps, crsf, esc/dshot
    ├── fusion/              mahony / madgwick / ekf
    ├── control/             pid, rate and angle loops, mixer
    ├── telemetry/
    ├── safety/              failsafe, arming, watchdog
    └── tests/               host-side unit tests

Version control rules

  • hardware/production/ is gitignored. Gerbers are added by hand only when a board is ordered, together with git tag hw-vX.Y — so it is always certain which board was built from which files.
  • Flight logs (logs/, *.bbl) never enter the repository.
  • .gitattributes normalises line endings to LF in the repository.

Development Environment

Hardware side

ToolVersion / note
KiCad8.x
SchematicMiniTULPAR.kicad_sch (+ scheme_diagram.kicad_sch)
Custom footprintsftp.pretty/
Custom symbolsMiniTULPAR_sym.kicad_sym

Firmware side (planned)

ToolNote
Toolchainarm-none-eabi-gcc
BuildCMake + Ninja
Peripheral layerSTM32CubeF4 (mostly LL; register level on the critical path)
Pin & clock configurationSTM32CubeMX
DebugST-Link / J-Link + OpenOCD, SWO trace
MeasurementLoop-time profiling with the DWT cycle counter

Ordering a board

powershell
git tag -a hw-v0.1 -m "First board order"
git push --tags
gh release create hw-v0.1 hardware\production\*.zip

Known Issues and Rev B Notes

Findings from the schematic review. None of them makes the board non-functional, but they should be decided before fabrication.

#IssueStatus / recommendation
1ICM-42670-P ODR ceiling of 1.6 kHz — this is the low-power member of the family, not the ICM-42688-P. An 8 kHz loop is not possible on this board (sensor-limited, not bus-limited).Target a 1 kHz PID loop. Because of the aliasing risk, the internal UI filter must be configured deliberately and the IMU soft-mounted.
2The battery divider is off-board, with no overvoltage protection.Rev B: 1 kΩ series into PC3 plus a Schottky clamp to 3.3 V.
3LDO thermal budget — 0.85 W at 500 mA with 5 V in. J5/J6/J7/J10/J11/J12 all supply 3.3 V, and a GPS module alone can draw 100–150 mA.Thermal via array under the LDO; the load budget belongs in docs/power-tree.md.
4DShot pins after reset are high-impedance.Confirm the ESCs do not apply throttle in that state; add pull-downs on the motor lines if they do (Rev B).

License

BSD 3-Clause License — Copyright © 2026 Erdem Hatayoğlu.

One licence covers the whole repository: firmware, hardware design files and documentation. It is permissive — you may use, modify and redistribute this work in source and binary form, including commercially and in closed-source products, provided that:

  • the copyright notice, the list of conditions and the disclaimer are retained
  • neither the project name nor the author's name is used to endorse or promote derived products without prior written permission

The work comes with no warranty of any kind. Full text: LICENSE

New files should carry an SPDX header so each file's licence is unambiguous:

text
SPDX-License-Identifier: BSD-3-Clause
SPDX-FileCopyrightText: 2026 Erdem Hatayoğlu

Third-party files (vendor headers, generated peripheral libraries, imported footprints) keep the licence of their original author; where such a file carries its own licence header, that header takes precedence.


Disclaimer

This board and its firmware are in development and untested. Spinning propellers can cause serious injury. Always run motor tests with the propellers removed, perform the first closed-loop attempts on a safe test bench, and verify the arming and failsafe logic before flying. Use this project entirely at your own risk.

Parts

92
QtyValueFootprintReferences
190.1uFCapacitor_SMD:C_0603_1608MetricC2, C3, C4, C5, C6, C10, C15, C18, C22, C23, C24, C26, C27, C29, C30, C31 +3
410uFCapacitor_SMD:C_0603_1608MetricC1, C11, C12, C25
41KResistor_SMD:R_0603_1608MetricR2, R11, R12, R13
44.7KResistor_SMD:R_0603_1608MetricR3, R4, R5, R6
310KResistor_SMD:R_0603_1608MetricR14, R15, R16
310pFCapacitor_SMD:C_0603_1608MetricC13, C14, C19
32.2uFCapacitor_SMD:C_0603_1608MetricC17, C20, C21
3FiducialFiducial:Fiducial_1mm_Mask2mmFID2, FID4, FID5
222Resistor_SMD:R_0603_1608MetricR9, R10
25.1KResistor_SMD:R_0603_1608MetricR7, R8
2600 Ohms @ 100 MHzftp:MPZ2012S601AT000FB1, FB2
2D_SchottkyDiode_SMD:D_SOD-323D2, D3
2PolyfuseFuse:Fuse_0603_1608Metric_Pad1.05x0.95mm_HandSolderF1, F2
10Resistor_SMD:R_0603_1608MetricR1
11uFCapacitor_SMD:C_0603_1608MetricC16
1220nFCapacitor_SMD:C_0603_1608MetricC28
13.3V_TestTestPoint:TestPoint_Pad_D2.0mmTP1
18MHzftp:ECS-80-10-30B-CKM-TRX1
1ADCftp:CONN03_530480310_MOLJ7
1ADC_Bftp:CONN02_530480210_MOLJ8
1BMP581Package_LGA:ST_HLGA-10_2x2mm_P0.5mm_LayoutBorder3x2yU4
1CRSFftp:CONN04_530480410_MOLJ10
1Device_Jumper_NO_SmallConnector_PinHeader_1.27mm:PinHeader_1x02_P1.27mm_VerticalJP1
1GND_TestTestPoint:TestPoint_Pad_D2.0mmTP2
1GPSftp:CONN04_530480410_MOLJ12
1I2C1ftp:CONN04_530480410_MOLJ6
1ICM-42670-PPackage_LGA:LGA-14_3x2.5mm_P0.5mm_LayoutBorder3x4yU2
1IIS2MDCPackage_LGA:LGA-12_2x2mm_P0.5mmU6
1LD39200PU33Rftp:LD39200PU33RU1
1LED_GRLED_SMD:LED_0603_1608MetricD4
1LED_RDLED_SMD:LED_0603_1608MetricD5
1LED_YELED_SMD:LED_0603_1608MetricD6
1LOGOLOGOG***
1M1MountingHole:MountingHole_3.2mm_M3_Pad_ViaH1
1M2MountingHole:MountingHole_3.2mm_M3_Pad_ViaH3
1M3MountingHole:MountingHole_3.2mm_M3_Pad_ViaH5
1M4MountingHole:MountingHole_3.2mm_M3_Pad_ViaH8
1PTS815SJM250SMTRLFSftp:PTS815SJM250SMTRLFSS1
1PWR1_GRLED_SMD:LED_0603_1608MetricD1
1Rail_PWRConnector_PinHeader_2.54mm:PinHeader_2x08_P2.54mm_VerticalJ2
1Rail_TerminalTerminalBlock_Phoenix:TerminalBlock_Phoenix_PT-1,5-2-3.5-H_1x02_P3.50mm_HorizontalJ1
1STM32F405RGTxPackage_QFP:LQFP-64_10x10mm_P0.5mmU3
1SWDConnector_PinHeader_1.27mm:PinHeader_2x05_P1.27mm_Vertical_SMDJ13
1SignalConnector_PinHeader_2.54mm:PinHeader_1x08_P2.54mm_VerticalJ3
1TDD01H0SB1Rftp:TDD01H0SB1RS2
1TELEMftp:CONN04_530480410_MOLJ11
1UART3ftp:CONN04_530480410_MOLJ5
1USBLC6-2SC6Package_TO_SOT_SMD:SOT-23-6U5
1USB_C_Receptacle_USB2.0_16Pftp:USB_CJ4
1VCC_TestTestPoint:TestPoint_Pad_D2.0mmTP3
1VINftp:CONN02_530480210_MOLJ9
1W25Q128JVSPackage_SO:SOIC-8_5.3x5.3mm_P1.27mmU7

Similar boards

  • 12 layers68 × 40 mmTeresina Rack, the printed circuit board in 3D

    Teresina Rack

    marcoallegretti/Teresina-Rack

    The goal is an open, self-fabricatable Daisy Patch SM-compatible Eurorack submodule: the same carrier interface and libDaisy application compatibility through a small Teresina firmware variant.

    214 parts
  • 2 layers73.4 × 117.4 mmLTC6812-15W, the printed circuit board in 3D

    LTC6812-15W

    UCDFS/Circuits

    KiCad projects and PCB designs for UCDFS electronic circuits.

    252 parts1
  • 4 layers61.4 × 38.8 mmFeather, the printed circuit board in 3D

    Feather

    wolf-yuan-6115/lightwolf

    Pumper is an experimental RP2354-based USB Audio Class 2 DAC. The board uses a PCM5102A DAC with OPA1652 and OPA1622 analog stages in a compact design intended for learning about USB audio and DAC hardware.

    153 parts1GPL-3.0
  • 4 layers38 × 55 mmDoubleSports.kicad pro, the printed circuit board in 3D

    DoubleSports.kicad pro

    Ameister621/Double-Sports

    COMP3200 Individual Project - Aidan Reidy

    54 parts
  • 4 layers60 × 60 mmHdlcSpy, the printed circuit board in 3D

    HdlcSpy

    FastRabbit/hdlcSpy

    37 parts
  • 2 layers100 × 51.3 mmDesk controller, the printed circuit board in 3D

    Desk controller

    FLRHW/Desk_controller

    Standing desk controller - Touch display as HMI and servo motor interface

    105 parts
  • 4 layers85 × 76 mmValvedrivers, the printed circuit board in 3D

    Valvedrivers

    npgo22/APRL-Electrical-New

    To use the board templates, set KICADUSERTEMPLATEDIR by:

    145 parts

Questions

How big is the MiniTULPAR PCB?

It measures 53.5 × 53.5 mm and has 4 copper layers, 1.6 mm thick.

What parts does the MiniTULPAR use?

92 parts, built around the STM32F405RGT6, BMP581, IIS2MDC and W25Q128JVSIQ. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the MiniTULPAR KiCad files?

From the ErdemHtyl/Tulpar_Mini_FCB repository on GitHub, at the commit this page was made from: the board is hardware/MiniTULPAR_KiCAD/MiniTULPAR.kicad_pcb and its schematic hardware/MiniTULPAR_KiCAD/MiniTULPAR.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the MiniTULPAR design in my own project?

Its repository publishes it under the BSD-3-Clause licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).