Nerves provides a way to combine your Elixir project code with everything else that’s needed to build firmware for embedded devices. Let’s see how to customize one of the provided systems and use it in a firmware build.
This worked as of mid-October 2016, but Nerves is still under development and things may change. Check the official documentation if things don’t seem to be working:
Pick a System
First, decide which of the existing systems you want to customize. In my case, this will be the one for the Raspberry Pi 2, which lives here:
I’ve forked that project and will be using my fork in the rest of the article. This step is not absolutely required unless you want to be able to commit your changes, and it can be done later if you change your mind, so feel free to skip it and just use the repo linked above.
It’s also possible to create a system from scratch, which you may need to do if you’re porting Nerves to new hardware, but that is far beyond the scope of this article.
Because they’re based on Buildroot, Nerves Systems currently have to be built in Linux. Since I’m on OS X, I’m using Docker to create a container with Ubuntu that I can use for this part.
If you already have access to a remote Linux host, that will work, and if you’re using Linux as your development machine, then you probably already know this stuff. :)
The first apt-get line is from the Nerves docs. The second is for things that were assumed to be present in a standard Ubuntu install, but were not included in the Docker image.
Now you have a container with all the necessary stuff installed. This would be a good time to save your work.
This may take a while. When it finishes, you can run
docker images to check that the image is there.
Build an Existing System
To check that everything works, let’s build the un-modified
nerves_system_rpi2 system. Start a container using your new image, and expose a directory for the output:
docker_stuff in my home directory to
/tmp/output inside the container. When the file is copied, it should show up in
This is another good time to save your work in the container as a new image, so that you can start over from here.
Every time you ‘docker run’ it creates a new container based on the specified image. Next time, we’ll start and attach to the container.
Note: I tried to use the docker volume as the output directory to avoid having to copy and expand the .tar.gz file, but I ran into a permissions error. https://gist.github.com/wsmoak/660583ccb387b3ef609af6facc61aa02
Set Up Build Machine
In order to use the newly built system, we’ll need to expand the .tar.gz file. Remember it was copied to a Docker volume at ~/docker_stuff, so check that it’s there, and then:
Now there should be a
nerves_system_rpi2 directory under /tmp with the contents of the .tar.gz file.
Next, set the NERVES_SYSTEM environment variable to this path so that you override Nerves’ default behavior of fetching the ‘official’ system.
And since we’re building for the Raspberry Pi 2, let’s also set NERVES_TARGET which is used in the mix.exs of Nerves projects:
Presumably the reason you wanted a custom system is that you need it to build firmware for your own project. If you don’t have a project, you can use one of the Nerves example projects like blinky or hello_wifi.
Let’s use the hello_wifi project in the nerves-examples repo.
Hopefully that completes with no errors! You should see it download the toolchain, but not the system, since it’s using the local one you built.
You can go ahead and
mix firmware.burn if you’d like to try it on your device.
Modify a System
Now let’s return to the Docker image and use Buildroot to make a modification to the existing RPi2 system.
Note: since you must type
make menuconfig in the output directory, it seems that you must have built the system once before trying to modify it? That doesn’t make sense if you’re creating one from scratch. So probably it’s just because of the relative directory that it uses to copy the nerves-defconfig.
This will pop up the blue-and-gray Buildroot Configuration menu.
/ to search for something… how about the driver for the rtl8188eu wifi adapter?
and now we know that it can be found under Target Packages -> Hardware Handling -> rtl8188eu
Navigate the menus to find it, and press space to enable that option.
Then arrow over to Save, and confirm to save the .config file.
Exit out of the Buildroot Config dialog, and back at the prompt:
This will update the
nerves_defconfig over in
nerves_system_rpi2 by way of a relative directory path.
And this is why I checked out my fork of
nerves_system_rpi2 earlier – so that I can commit that change:
Which you can see here: https://github.com/wsmoak/nerves_system_rpi2/commit/20027bc44cc0a20fb5540fce54962868700a097f
Build Modified System
Now that we have modified the system, let’s build it again:
Remove the directory where you expanded the unmodified custom system, and expand the modified one:
Ideally the modified system would have a different name, or at least a different version number. It’s a really bad idea to build the same artifact name and version number with different contents. You should be able to look at the filename and tell what it contains.
Remember to set the NERVES_SYSTEM environment variable as above, or Nerves will fetch and use the released version of the system rather than your locally built one. And set NERVES_TARGET also if needed.
mix firmware.burn if you want to burn a micro SD card to try it in your device.
Unfortunately, enabling the rtl8188eu driver was not enough to get my wifi adapter to work. I hear that the 8188 and 8192 are problematic on the latest Linux kernel. Which is just super because I have two of each!
So, this offer remains open!
If things aren’t working, try deleting the
rel/hello_wifi directories under the
We’ve seen how to use Buildroot to modify a Nerves system, and how to use that custom system when building firmware.