Skip to the content
2 layers40 × 22.5 mmTemplate, the printed circuit board in 3D

Template for my KiCad projects

Size
40 × 22.5 mm
Copper layers
2
Thickness
1.6 mm
Parts
4
Nets
3
Pads
9
Tracks, vias
24, 5
Routed
Yes
KiCad
KiCad 9.0 (file 20241229)
Created
5 Oct 2025
Updated
12 Mar 2026

Overview

Template is an open-source printed circuit board by marinecircuits, from the marinecircuits/kicad-template repository on GitHub. It is a 2-layer board of 40 × 22.5 mm with 4 parts on 3 nets, routed with 24 tracks and 5 vias.

It is built around the BSS138 and MBR0530-TP. Its parts include 1 resistor, 1 diode, 1 transistor and 1 connector.

Main components

2

README

README.md

Usage

  • Create new project directory
    • mkdir new-prorject && cd new-project
  • Copy content of repository
    • curl -L https://github.com/marinecircuits/kicad-template/archive/refs/heads/main.tar.gz | tar -xz --strip-components=1
  • setup python environment python3 -m venv .venv && source .venv/bin/activate && pip install -r requirements.txt
  • execute setup script
    • python3 scripts/setup_template.py
  • init git repository (if not already done) and add all files git init . && git add .
  • install pre-commit hook pre-commit install --hook-type commit-msg

Variables

These variables are relevant for this template / workflow:

  • ${ISSUE_DATE}: the release PR workflow will update this with the current date, in the YYYY-MM-DD format (the only date format you should ever use by the way). It is committed and added in the PR as a change
  • ${REVISION}: the release PR will update this with the git tag (not 100% true, the git tag will be only created one the PR is merged into main, but the result is the same). It is committed and added in the PR as a change. This field will have +! appended if it's not a released version.
  • ${COMMENT9}: before kibot is invoked on github, this variable is updated with the short git hash from git rev-parse --short HEAD. It is committed and added in the PR as a change
  • ${COMMENT8}: This contains the project name. It is not updated automatically, you should set it once at the beginning of the project.

Versioning

It follows the semantic versionin approach. Schematics and PCB always have the same version. Anything breaking functional interfaces will be a breaking change which increments the major version. This includes board shape, connector position. TBD: will adding functionality without breaking interfaces just increment the minor version? Difficult to say if adding a connector will interfere with an existing case or other mechanical constraints. Changes in schematics which do not affect anything electrical (documentation, re-organize wires) will increment a patch. Changes in schematics which affect the value of a component, new connections, removal of components will increment a minor version.

Assembly variant

This is a property of the BOM. At the moment variants are not fully supported (or better: only one variant is fully supported). VARIANT.md lists all the different variants with a textual description with the differences with respect to variant 1.

Github

In github you must allow actions to create pullrequest for this workflow to be working. Under Settings, Actions, General this settings must be enabled. If greyed out, it must be enabled at the organization level. Github PR setting

Description of usage

Daily use

During daily work, the user branches off from main, makes changes, commits them, pushes to github, opens a PR, and merges the changes back to main. It is important to commit using the commitizen commit format, otherwise the whole versioning will not make sense. Checkout the documentation. When a PR to main is opened, the jobs inside .github/worflows/pullrequest.yml get triggered. The worflow will call .github/workflows/module-kibot.yml, which generates all the files needed for production. In kibot.yaml the output files can be tweaked. The most important thing is to have dont_stop set to false under preflight in erc and drc, such that the workflow will fail and nothing broken is merged into main.

Release process

Pull request

A release is started by invoking the Create Release PR Action. This will trigger the jobs inside .github/workflows/create-release-pr.yml. First, commitizen will bump the version, create (update) the CHANGELOG.md. Then the date, rev, comment 9 fields are updated and committed to a release branch release/v$VERSION. Then, a pull request to main is opened. The user can now inspect the changes and merge it.

Release

Once the PR has been merged, the jobs inside .github/workflows/tag-release-merge.yml are triggered. The job extracts the version from the pull request title and creates a corresponding tag on main. The kibot workflow is invoked, and artifacts are generated. An official Github release Release X.Y.Z is created and the production files are uploaded to it.

Parts

4
QtyValueFootprintReferences
147k_0805Resistor_SMD:R_0805_2012MetricR1
1BSS138Package_TO_SOT_SMD:SOT-23-3Q1
1MBR0530Diode_SMD:D_SOD-123D1
1Screw Terminal Block 5.00 mm 2 pol2s_connectors:TerminalBlock_MaiXu_MX126-5.0-02P_1x02_P5.00mmJ1

Similar boards

  • 2 layers52 × 36 mmCyphalPicoBase CAN, the printed circuit board in 3D

    CyphalPicoBase CAN

    generationmake/CyphalPicoBase-CAN

    Board for the Raspberry Pi Pico to connect via CAN using OpenCyphal and UCANPHY Micro

    62 parts5CERN-OHL-W-2.0
  • 2 layersVca mix, the printed circuit board in 3D

    Vca mix

    sgreene30/Synthesis-Projects

    190 parts
  • 4 layers36 × 50.2 mmRacer, the printed circuit board in 3D

    Racer

    StuckAtPrototype/Racer

    These are structured into their own files. I could have used submodules, but decided against it.

    83 parts3.8kApache-2.0
  • 4 layers95 × 95 mmCube motherboard, the printed circuit board in 3D

    Cube motherboard

    willem-pennings/balancing-cube

    A cube that balances itself in a corner or edge using reaction wheels

    52 parts1.1kGPL-3.0
  • 2 layers54.6 × 70.9 mmBeagleLogic Cape, the printed circuit board in 3D

    BeagleLogic Cape

    abhishek-kakkar/BeagleLogic

    A Software Suite that implements a logic analyzer with the PRU on the BeagleBone / BeagleBone Black.

    22 parts479GPL-3.0
  • 2 layers44.2 × 29.3 mmI2c tiny usb, the printed circuit board in 3D

    I2c tiny usb

    harbaum/I2C-Tiny-USB

    Cheap and simple I²C to USB interface

    27 parts454

Questions

How big is the Template PCB?

It measures 40 × 22.5 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Template use?

4 parts, built around the BSS138 and MBR0530-TP. 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 Template KiCad files?

From the marinecircuits/kicad-template repository on GitHub, at the commit this page was made from: the board is template.kicad_pcb and its schematic template.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Template design in my own project?

Its repository states no licence, so its author keeps all rights: ask marinecircuits before reusing the design.