Template repository for creating a custom Toit envelope

This repository can be used to create custom envelopes for Toit.

There are already many pre-built envelopes available, but if you need to create a custom envelope, this repository can be used as a starting point.

External services

See the README-external-service.md file for information on how to use external services.

Setup

Prerequisites

• Make sure you have a complete build environment. See
  • https://github.com/toitlang/toit, and
  • https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/index.html
  • A good starting point is to run install.sh from the toit/third_party/esp-idf folder.

The ci.yml file uses Toit's setup action to install all prerequisites on a GitHub runner. You can use this as a reference for setting up your own environment.

Initial setup

• Duplicate this repository:

  Start by creating a fresh repository on GitHub. Then run the following commands, replacing your-owner/your-repo with the name of your repository:

  git clone --bare https://github.com/toitlang/template-custom-envelope.git
  cd template-custom-envelope.git
  git push --mirror [email protected]:your-owner/your-repo.git
  cd ..
  rm -rf template-custom-envelope.git

  Also see GitHub's instructions. If you forked it, you can also detach the fork: https://support.github.com/request/fork

• Check out your new repository (again replacing your-repo with the name of your repository):

  git clone [email protected]:your-owner/your-repo.git
  cd your-repo

• Update the Toit submodule to match your needs. If you are using an installed Jaguar, you should use the same SDK version as Jaguar. Use jag version to find the version. Otherwise, consider using the latest version.

  pushd toit
  git checkout YOUR_VERSION
  git submodule update --init --recursive
  popd

• Change the license to your license.

• Change the TARGET variable in the Makefile to the name of your chip. By default it is set to esp32.

• Run make init. This will copy some of the Toit files, depending on the target, to your repository.

After initialization you should have the files sdkconfig.defaults and partitions.csv in the build-root folder. Together with the sdkconfig file, which is created when building, these files should be checked into your repository.

Configuration

• Adjust or remove the C components in the components folder.
• Run make menuconfig to configure the build.
• Adjust the ci.yml file to match your setup. Typically, you don't need to compile on Windows or macOS.

Build

• Run make to build the envelope. It should end up with a build/esp32/firmware.envelope.

Makefile targets

• make or make all - Build the envelope.
• make init - Initialize after cloning. See the Setup section above.
• make menuconfig - Runs the ESP-IDF menuconfig tool in the build-root. Also creates the sdkconfig.defaults file.
• make diff - Show the differences between your configuration (sdkconfig and partitions.csv) and the default Toit configuration.
• make clean - Remove all build artifacts.