After successfully burning the software to the ARM chip on the clouds module I thought Id better collect all the instructions down in one place. I still havent gotten Braids to work, but Im not deterred, Id still like to make Frames, Grids, Edges and.. er that new morphing modulator one.. forgotten..
Anyway here it is…
Go to the MI git repository at https://github.com/pichenettes/eurorack
and click DOWNLOAD zip (you unless you know what you are doing with github, which I don’t)
This folder is your MASTER directory for MI building. it is called:
In it you will see, loose a file called
In order to run vagrant your computer must be able to see that file, that means navigating to this folder via Terminal.
Starting Vagrant (these instructions copied from https://github.com/pichenettes/mutable-dev-environment)
Hard to describe how to do this without knowing where you have saved your folder. But you need some knowledge of command line navigation. Either:
you know it
You go to https://wwwcodecademy.com/ and take the Learn the Command Line course (recommended)
wing it… heres some hints
Command line 101
ls to show a list of files and/or directory that are in the current directory
cd to change directory so
cd documents will put you in the documents folder, then you can run another
ls and see what the contents there are. hopefully, you saved the mutable stuff there, and all you need to do is
cd mutable-dev-environment-master and you are in the right place
cd.. to go up one level, just incase you go in the wrong folder
Type the terminal command to start up Vagrant. That is:
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 login to Vagrant (again in the terminal, NEVER in the black terminal lookalike window that Virtual box throws up, was a mistake of mine)Type:
You then need to change a few lines in one file, this is to tell it to upload via StLink (I think)
So look in the main eurorack-modules folder,
open the stmlib folder
Then try to open makefile.inc
You probably need to use a very simple text editor, like Text Edit. But it wont recognise the filetype .inc but will open.
The relevant lines should look like this (ignore those starting with #, they are just comments):
# Supported: arm-usb-ocd, arm-usb-ocd-h, arm-usb-tiny-h, stlink-v2
# PGM_INTERFACE ?= arm-usb-ocd-h
PGM_INTERFACE = stlink-v2
# hla for stlink-v2 ; jtag otherwise
# PGM_INTERFACE_TYPE ?= jtag
PGM_INTERFACE_TYPE = hla
Leave no spaces at the end of lines
Now back in terminal
You can begin to build things
Do these one at a time.
to clean the area reserved for the bootloader
make -f clouds/bootloader/makefile clean
to clean the area reserved for the software
make -f clouds/makefile clean
to build the bootloader
make -f clouds/bootloader/makefile hex
to build the software
make -f clouds/makefile hex
That should be it, but there’s an option to do both at once.. not sure if it worked for me
to upload both in one package to the chip
make -f clouds/makefile upload_combo_jtag
Also found in the make file..
make -f clouds/makefile upload_combo_jtag_erase_first
something gbiz suggested when trying to get Braids to work…
openocd -f interface/stlink-v2.cfg -f target/stm32f1x_stlink.cfg -c init -c halt -c "flash write_bank 0 build/braids/braids_bootloader_combo.bin 0x0"
“It’s most of the command that make runs to flash the binary, less a couple of configure options. I doubt it’ll help, but it’s worth a try.”
and I dont think it did…