Tock Hardware CI

• About
• Guide
• The Team

Installation

Click here to see the installation guide on how to set up your very own hardware harness and connect it to the main Tock repository.

About the Repo

Our design consists of one main repo which uses two existing Tock repos.

• Tock Test Harness (Our main repo) (Owned by us for now until we officially launch the CI)
  which consists of:
  • lib: a folder containing all python code that runs on the Pi during testing.
  • runner_init.py: a script used in the initial setup of the Pi
  • config.toml: a configuration file created by runner_init that saves information about the target board for that Pi as well as a harness identifier.
• Tock: (The main Tock OS repo) (Forked for now until we officially launch the CI)
  from which we use:
  • /.github/workflows/ci-test.yaml: a configuration file that specifies to Github what to run and where (all of the tests for each Raspberry Pi)
  • boards: a directory we use to compile Tock for the target board as well as save board-specific test information in a configuration file called test.config.toml.
• libtock-c: (The main repo for Tock OS apps) (Forked for now until we officially launch the CI)
  from which we use:
  • /examples/ci-test, where there is a directory for each test.
    These are general and can be tested by any board with the necessary features tested in the test. The name of a test directory can be uniquely specified in the "test.config.toml" file. Inside the directory is a test.py file and main.c file for the Raspberry Pi test and Tock test app respectively, as well as a Makefile to compile the test app.