NOTE: When updating packages that need file permissions for executables to be preserved (like the Adafruit SAMD package and bossac executables) you MUST use either OSX or Linux to update the board package. There is a bug/issue with Windows Python losing file permissions when generating the tar.gz board package file.

To update Adafruit's Arduino board packages first you'll want to be familiar with the Arduino 3rd party board package index.  For Adafruit's boards they are defined and published in the package_adafruit_index.json file of the arduino-board-index repository's gh-pages branch.  Because this file is in the gh-pages branch it will use GitHub's pages publishing system and be available for anyone to access from the following URL:

This .json file contains the 'live' version of all the published Adafruit boards for Arduino's board manager.  The board package tool script automates much of the process of publishing a new or updated package to this file.

In addition to the package index .json file there are archive files of all the board packages in the boards directory of the board index repository.  This is not a hard requirement of the Arduino 3rd party board system but is a convention followed by Adafruit's board pacakges.  Each board package release version will have a .tar.bz2 archive inside this boards folder.

The list of boards which are published in the Adafruit Arduino board package index are defined in the bpt.ini file next to the script.  This INI style configuration file has a section for each board package, and inside the section are options to configure the source for the board package (i.e. what separate GitHub repository contains the board package) and how the package will be published to the index.  For just updating existing board packages you don't need to worry about the contents of this file.  Read the comments in the file if you're curious what different options are available and what they mean.

At a high level the workflow for updating an Adafruit board package follows these steps:

  1. Update the board package inside its GitHub repository.  You can make whatever changes necessary to the package and test them in isolation (like by dropping the package in the Arduino/hardware folder).  Don't go on until your package is working exactly as expected.
  2. Increase the version number in the package's platform.txt file. You'll see a line near the top of this file that looks like version=1.0.8.  This version inside platform.txt is the 'master' version for the package and will be used when pushing to the board index.  If the version number isn't higher than what's already in the package index it won't be able to be updated!
  3. Once the package is updated in its GitHub repository use the check-updates command with the board package tool to verify that the package version in the board index is not up to date and should be updated.
  4. Use the update-index command with board package tool to update the board index for the specified package.  This will pull down the latest package code from its GitHub repository, create an appropriate archive file with the package code inside, and update the package_adafruit_index.json file with the new package release metadata.
  5. Use the test-server command with board package tool to run a local webserver that allows you to test the Arduino IDE with the updated package index before making it 'live'.
  6. After verifying the package index and updated package works you can commit the updated files in the Adafruit Arduino board index repository.  Once these files are committed to the gh-pages branch they will be live for anyone to access!

TeeOnArdu Update Example

To demonstrate the update workflow we'll walk through updating the Adafruit TeeOnArdu board package.

First clone the TeeOnArdu repository and make any necessary changes to the package data.

Test out these changes before continuing--you want to make sure the package repository has working code as it will be much more difficult to later debug from the package index.

Once the TeeOnArdu code is updated make sure to increase the platform.txt version!  This version is the only source of truth for the current version of the package and must be increased for the board package tool to allow an update to the index (otherwise you'd be pushing new code with an old version and Arduino clients wouldn't see it!).

Now commit all the changes to the TeeOnArdu repository.  This will update the source of the TeeOnArdu package that the board package tool will later retrieve.

At this point you're ready to switch to the Adafruit arduino-board-index repository and use the board package tool scripts.  If you haven't cloned this repository already do so now.  If you already have the repository run a 'git pull' command to make sure it's up to date.

Now run the check-updates command to have the tool scan the source package repositories and compare their platform.txt versions to the versions published in the board index.  The tool will alert you of packages which are not up to date in the index.  Run the tool as follows (use python, not python3 on Windows in all the subsequent commands):

python3 check-updates

You should see the TeeOnArdu package is noted as out of date with the !!! warning text:

If you don't see the TeeOnArdu package as more recent in its origin vs. the index then something is wrong and the update to the TeeOnArdu package platform.txt did not work as you expected.  Go back to the TeeOnArdu repository and make sure it is updated in its master branch and that the platform.txt version is greater than the version in the index as noted by the check_update command output.

Now you're ready to update the board index file with the new TeeOnArdu package.  This update will only be done to your local git repository so don't worry about it breaking anything in the live index yet (just be careful not to commit the changed files until you're sure they work!).

To update the TeeOnArdu package run the following command:

python3 update-index "Adafruit TeeOnArdu"

This command takes as a parameter the name of the package to update.  This name is the value specified in the section title of the bpt.ini file, or you can see it printed in the check_update output.

You should see something like the following that confirms the board package archive was created and the index .json updated:

If you run the 'git status' command you should see both these files as changed/added:

Now you're ready to test out the updated package index using a local test web server.  Run the following command to start this test server:

python3 test-server

You should see the command start and print that a test server is running (note that you might need to confirm Windows firewall warning dialog first):

At this point the test webserver is running and will serve the updated board index on the URL it mentions: http://localhost:8000/package_test_index.json  If you configure the Arduino IDE to use this board platform URL you can test that the updated package and index are working as expected.

Open the Arduino IDE and in the board manager first remove any old versions of the TeeOnArdu package.  This will help ensure you're starting from a clean slate.

Now update the board package URL in the preference menu.  Add the localhost test server URL:

Make sure to remove the live adafruit package index too (i.e. the URL)!

Now open the board manager and allow it a few moments to update.  Then search for the TeeOnArdu package and confirm you see the new version that you added (1.0.2 in this example):

Click Install and make sure the package successfully installs (this will test the archive was created and packaged correctly).

Now use the Arduino IDE with your updated package.  Confirm that everything is working as expected and the new changes are available in the package.  If you tested the package in isolation earlier there shouldn't be any surprises here, but it can't hurt to test again.

Once you see the updated package is working you can exit the Arduino IDE (and optionally remove the test server URL from the preferences menu and remove the updated TeeOnArdu package).

Press Ctrl-C in the command window running the test server to stop it from running.

The final step to finish the package update is to commit the updated Adafruit arduino-board-index repository files.  As you saw earlier a new package .tar.bz2 file was added to the boards directory, and the package_adafruit_index.json file was updated.  Use the 'git add' command to add these files (or use whatever Git tool you're most comfortable using).  Then use the 'git commit' command to commit this change.  Finally push the new commit to GitHub with the 'git push origin gh-pages' command.

At this point the TeeOnArdu package update is complete!  Once the files are committed to the gh-pages branch the Adafruit Arduino board package index file is updated and available for any Arduino client to see.  That's all there is to using the board package tool to update an Adafruit Arduino board package!

As a last sanity check you should add the Adafruit board package URL back to the Arduino IDE and check the updated package is available and installs correctly.  If you see any errors make sure both the new package .tar.bz2 and updated package_adafruit_index.json were added to the repository in the previous step.  If something is still seriously wrong with the updated package index you can always revert the package_adafruit_index.json file on GitHub and put it back to an older known-working version.

This guide was first published on May 06, 2016. It was last updated on Mar 08, 2024.

This page (Package Update Workflow) was last updated on Mar 08, 2024.

Text editor powered by tinymce.