Skip to the content
4 layers49.8 × 48.2 mmTest subdir, the printed circuit board in 3D

Test for Continuous Integration using KiCad

Size
49.8 × 48.2 mm
Copper layers
4
Thickness
1.6 mm
Parts
12
Nets
47
Pads
118
Tracks, vias
199, 20
Pours
2
Routed
Yes
KiCad
KiCad 8.0 (file 20240108)
Created
18 Apr 2020
Updated
24 Feb 2025

Overview

Test subdir is an open-source printed circuit board by INTI-CMNB, from the INTI-CMNB/kicad_ci_test repository on GitHub, published under the BSD-3-Clause licence. It is a 4-layer board of 49.8 × 48.2 mm with 12 parts on 47 nets, routed with 199 tracks and 20 vias.

It is built around the FT2232HL. Its parts include 6 connectors, 2 capacitors, 2 resistors, 1 IC and 1 crystal.

Main components

1

README

README.md

kicad_ci_test

main test subdir

Test for Continuous Integration using KiCad.

This repo contains two examples, one is the simplest situation and the other complicates things a little bit.

Simple example

This is an example of how to test and generate documentation for a KiCad project automatically every time you commit a change to the schematic and/or PCB.

In this example we use a docker image containing KiCad, KiBot and all the supporting tools.

The kicad_ci_test.kibot.yaml configures KiBot and says what's available.

The .github/workflows/test1.yml configures what GitHub workflow.

In this file we:

  • Instruct GitHub to run the tasks every time a change in the pertinent files is detected:
text
on:
  push:
    paths:
      - 'kicad_ci_test.kicad_sch'
      - 'kicad_ci_test.kicad_pcb'
      - 'kicad_ci_test.kibot.yaml'
      - '.github/workflows/test1.yml'
  pull_request:
    paths:
      - 'kicad_ci_test.kicad_sch'
      - 'kicad_ci_test.kicad_pcb'
      - 'kicad_ci_test.kibot.yaml'
      - '.github/workflows/test1.yml'
  • Define actions for ERC, DRC, schematic documentation generation and PCB documentation generation.
  • Each action takes the repo content as input using:
text
- uses: actions/checkout@v4
  • The actions are executed by KiBot and stored in the Fabrication directory

  • The resulting files are stored as artifacts using:

text
    - name: Retrieve results
      uses: actions/upload-artifact@v4
      with:
        name: ERC_Output
        path: Fabrication

For more information about the GitHub configuration read the Workflow syntax for GitHub Actions page.

Second example

This example is a little bit more complicated. First we have our project located in a sub directory called test_subdir and second we use an external library found in the kicad_ci_test_lib project.

The test_subdir/test_subdir.kibot.yaml configures KiBot and says what's available.

Note that this project has a four layers PCB so we generate gerbers for all of them. In the example file we refer to the ground plane as GND.Cu this is the name used in our PCB. Another option is to use the legacy KiBot format: Inner.1, and this is what we do for the power plane (Inner.2 in this case).

The .github/workflows/test_subdir.yml configures what GitHub makes.

In this example we are putting all the real commands inside a Makefile and then invoking it like this:

text
    - name: Run ERC
      run: |
        make -C test_subdir/ erc

This changes the workind directory to test_subdir/ and then makes the erc target, defined in the Makefile like this:

text
erc:
	kibot -d Fabrication -s drc -i

Using a Makefile is just another way of doing things, you could put the commands in the GitHub worflow, but don't forget to change the working directory to test_subdir.

Another detail is how to checkout the submodules. One option is to use the submodules option of the checkout action, like this:

text
    - uses: actions/checkout@v4
      with:
        submodules: 'true'

Example using development images

Sometimes a bug in KiBot might prevent using it. In this case report it here.

Once the bug is fixed you can use the dev (development) docker images. You just need to chage latest by dev The following example shows it: .github/workflows/test_using_dev.yml

Parts

12
QtyValueFootprintReferences
4Conn_01x08_MaleConnector_PinHeader_2.54mm:PinHeader_1x08_P2.54mm_VerticalJ1, J2, J3, J5
227 pFCapacitor_THT:C_Disc_D3.0mm_W1.6mm_P2.50mmC1, C2
112 MHzCrystal:Crystal_HC49-U_VerticalY1
112kResistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P5.08mm_VerticalR2
12k2Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P5.08mm_VerticalR1
1Conn_01x06_MaleConnector_PinSocket_2.54mm:PinSocket_1x06_P2.54mm_VerticalJ6
1FT2232HPackage_QFP:LQFP-64_10x10mm_P0.5mmU1
1USB_BConnector_USB:USB_B_OST_USB-B1HSxx_HorizontalJ4

More from INTI-CMNB/kicad_ci_test

1
  • 2 layers27.9 × 12.7 mmKicad ci test, the printed circuit board in 3D

    Kicad ci test

    INTI-CMNB/kicad_ci_test

    Test for Continuous Integration using KiCad

    4 parts24BSD-3-Clause

Similar boards

  • 4 layers68.6 × 53.3 mmIcezum, the printed circuit board in 3D

    Icezum

    FPGAwars/icezum

    :star2: IceZUM Alhambra: an Arduino-like Open FPGA electronic board

    218 parts357GPL-3.0
  • 4 layers160 × 100 mmRosco m68k, the printed circuit board in 3D

    Rosco m68k

    rosco-m68k/rosco_m68k

    Design, documentation and software for the Really Old School Computer (M68K)

    140 parts200
  • 4 layers44 × 64 mmJTAGProgrammer, the printed circuit board in 3D

    JTAGProgrammer

    anthony-bernaert/ftdi-jtag-programmer

    FTDI-based JTAG Programmer Circuit for FPGAs

    122 parts77CERN-OHL-P-2.0
  • 2 layers38 × 20.7 mmJTAG HW, the printed circuit board in 3D

    JTAG HW

    vanbwodonk/ft2232hl-jtag-clone

    Digilent JTAG clone hardware + eeprom firmware (.bin)

    38 parts73
  • 4 layers100 × 180 mmX65-sbc revB1, the printed circuit board in 3D

    X65-sbc revB1

    jsyk/x65

    The 65c02 and 65c816s-based modern retro computer

    344 parts59MIT
  • 4 layers165 × 107 mmSpla board, the printed circuit board in 3D

    Spla board

    khaydarian/spla

    SNES PPU Logic Analyzer

    290 parts32
  • 4 layers50 × 22.9 mmICE40-fpga, the printed circuit board in 3D

    ICE40-fpga

    joshajohnson/iCE40-feather

    iCE40UP5K in an Adafruit Feather form factor

    69 parts26
  • 2 layers100 × 100 mmM68k, the printed circuit board in 3D

    M68k

    annoyatron255/m68k

    A Motorola 68000 Computer

    110 parts24

Questions

How big is the Test subdir PCB?

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

What parts does the Test subdir use?

12 parts, built around the FT2232HL. 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 Test subdir KiCad files?

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

Can I use the Test subdir 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).