
Kicad ci test
INTI-CMNB/kicad_ci_test
Test for Continuous Integration using KiCad

Test for Continuous Integration using KiCad
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.
Test for Continuous Integration using KiCad.
This repo contains two examples, one is the simplest situation and the other complicates things a little bit.
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:
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'- uses: actions/checkout@v4The actions are executed by KiBot and stored in the Fabrication directory
The resulting files are stored as artifacts using:
- name: Retrieve results
uses: actions/upload-artifact@v4
with:
name: ERC_Output
path: FabricationFor more information about the GitHub configuration read the Workflow syntax for GitHub Actions page.
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:
- name: Run ERC
run: |
make -C test_subdir/ ercThis changes the workind directory to test_subdir/ and then makes the erc target, defined in the Makefile like this:
erc:
kibot -d Fabrication -s drc -iUsing 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:
- uses: actions/checkout@v4
with:
submodules: 'true'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
| Qty | Value | Footprint | References |
|---|---|---|---|
| 4 | Conn_01x08_Male | Connector_PinHeader_2.54mm:PinHeader_1x08_P2.54mm_Vertical | J1, J2, J3, J5 |
| 2 | 27 pF | Capacitor_THT:C_Disc_D3.0mm_W1.6mm_P2.50mm | C1, C2 |
| 1 | 12 MHz | Crystal:Crystal_HC49-U_Vertical | Y1 |
| 1 | 12k | Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P5.08mm_Vertical | R2 |
| 1 | 2k2 | Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P5.08mm_Vertical | R1 |
| 1 | Conn_01x06_Male | Connector_PinSocket_2.54mm:PinSocket_1x06_P2.54mm_Vertical | J6 |
| 1 | FT2232H | Package_QFP:LQFP-64_10x10mm_P0.5mm | U1 |
| 1 | USB_B | Connector_USB:USB_B_OST_USB-B1HSxx_Horizontal | J4 |

INTI-CMNB/kicad_ci_test
Test for Continuous Integration using KiCad

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

rosco-m68k/rosco_m68k
Design, documentation and software for the Really Old School Computer (M68K)

anthony-bernaert/ftdi-jtag-programmer
FTDI-based JTAG Programmer Circuit for FPGAs

vanbwodonk/ft2232hl-jtag-clone
Digilent JTAG clone hardware + eeprom firmware (.bin)




It measures 49.8 × 48.2 mm and has 4 copper layers, 1.6 mm thick.
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.
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.
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).