First, I like to use Yocto to keep track of, and implement, the configuration of my Edison,

There are shell scripts available with release 2.1 to configure the I/O for the MCU. For some reason, these scripts have to be downloaded and installed separately - even individually.

It is almost trivial to write a Yocto recipe to include the scripts in the device image. I don't know why this wasn't done for the release, but I find it useful to have them available as part of the "system".

I call the recipe "mcu-scripts", and there are just a few steps to include it in the default image. As written, the recipe will place the scripts in /usr/local/bin.

1. create directories in one of the provided layers to hold the recipe (or, better, put it into your local layer, if you maintain one):

2. Place the recipe into the new mcu-scripts directory. Note that Yocto forces there to be a license, and no license is suggested anywhere in the scirpts or documentation that I could find, so I assumed GPLv2, mostly because it was easy to find a plain text link to an official copy. Feel free to suggest/use something else.

Note that step 3 describes one of at least three ways to get a package into an image. The BSP User's Guide suggests a different method involving .../build/local.conf. One could also place the IMAGE_INSTALL line into a file edison-image.bbappend in the same directory as the recipe. I prefer to have my package install commands centralized.

4. build and deploy the image to include the new package (see the BSP User's Guide)

(edit) Yocto now appears to require a checksum for all downloaded sources.