Development environment for the firmware of Mutable Instruments' products
This configuration file and this shellscript create a Linux (ubuntu) virtual machine configured with all the right tools for compiling and installing the firmware of Mutable Instruments' modules.
The Extension pack consists of a file with the
vbox-extpackextension. On windows, double click on it. On OS X or Linux, the file needs to be installed from the command line with the command:
VBoxManage extpack install
Finally if you are running a Linux operating system you will want to add your user to the
vboxusersgroup so that the virtual machine can access your USB devices. Run the following command:
sudo usermod -a -G vboxusers $USER
Then log out and log back in to make sure the group change takes effect.
First, clone this repository:
git clone https://github.com/pichenettes/mutable-dev-environment.git
To start the VM, open a terminal in the
mutable-dev-environmentdirectory with the Vagrantfile and run:
The first time the VM is started, all tools will be downloaded, and the latest version of the code will be grabbed from github. The process takes about 15 minutes, depending on the speed of your internet connection or computer.
Then, you can log onto the virtual machine by running:
Once in the virtual machine, you can try, for example, to compile Clouds' bootloader and code:
make -f clouds/bootloader/makefile hex make -f clouds/makefile
To write the firmware to the module with an Olimex ARM-USB-OCD-H JTAG adapter, use:
make -f clouds/makefile upload
Using other programmers is of course possible, please see Customization.
Or you can generate a .wav file for the built-in audio updater:
make -f clouds/makefile wav
The firmware update file will be put in
Once you're done with your hacking session, you can leave the VM terminal with:
The virtual machine continues running and can be reaccessed with
vagrant ssh. It can also be suspended with
vagrant suspend, halted with
vagrant halt, and completely destroyed with
vagrant destroy. Note that with this last command, you might lose any files you have created inside the VM's disk image!
By default, the working directory (
eurorack-modules) is installed in the
/vagrantdirectory, which is shared between the VM and the host. You can thus use any text editor on the host to modify the files. Note that any file can be transferred between the VM and the host by being copied in this location.
If you prefer working in a more self-contained environment and leave your host directory clean, you can comment the line
CODE_DIRECTORY=/vagrantand uncomment the line
CODE_DIRECTORY=/home/vagrantbefore setting up the VM. The code will not be installed in the shared directory, and will be accessible only from within the VM.
To pass through USB devices from your real machine to the virtual machine, consult the VirtualBox USB documentation.
To use a programmer other than the default (AVR ISP mkII, ARM-USB-OCD-H) it is no longer necessary to edit the makefiles. Instead, the programmer can be set in the shell for the current session, e.g.
export PGM_INTERFACE=stlink-v2 export PGM_INTERFACE_TYPE=hla
for ARM projects using a JTAG adapter. Similarly for AVR projects, you can use
export PROGRAMMER=stk500 export PROGRAMMER_PORT=/dev/tty.usbserial-xxxxxxxx
Any further calls to
makewill then automatically use these settings. To make them permanent, add the exports to the end of
Another way (e.g. to test if settings are correct) is to just specify the value in the call to
PGM_INTERFACE=ftdi/olimex-arm-usb-tiny-h make -f braids/makefile upload
If you want to build code from your own github fork, you can specify the repository to clone when you create the VM via the
USER_GITHUB_URLenvironment variable, e.g.
USER_GITHUB_URL=https://github.com//eurorack.git vagrant up
The Mutable Instruments' repository is automatically added as the git remote