Building the Magus firmware

OWL Magus
, ,
#141

Click Erase Storage on the device page: OWL Patch Library – Rebel Technology

1 Like
#142

An update with v21: After running Erase Storage I can upload patches again.

Remaining oddities:

  • Everything I upload has the name “Template”. When the patch starts running its name is not printed big the way it used to be.
  • REALLY weird thing I’ve just noticed: I have two USB-B cables, a long one and a short one. I have discovered the Magus cannot talk to or power a USB MIDI keyboard when the MIDI keyboard is plugged in to the Magus HOST port with the short cable. The MIDI keyboard works when I use the long cable. If I plug the Magus into a Macintosh with the short cable via the DEVICE port, this works.

I am uploading with

(cd .. && make patch TOOLROOT= PATCHNAME=PatchNameGoesHere PLATFORM=Magus && ../FirmwareSender/Builds/MacOSX/build/Debug/FirmwareSender -in Build/patch.bin -out OWL-MIDI -run)

In OwlProgram repo 2918c483c53c subfolder PatchSource.

#143

Generally, there’s no need to use FirmwareSender directly - everything you need is doable with makefile. So normally I would just run something like “make patch PATCHNAME=PatchNameGoesHere clean load”.
FirmwareSender can be passed as env variable too, but I prefer to make a symlink in default path (Tools/FirmwareSender). TOOLROOT variable is set to empty string by default in recent versions of OwlProgram.

The requirement to use PLATFORM variable is removed, you can build patches with display without using it. Actually we’ll probably have to reintroduce it later, but for a different purpose - to build patches for other MCU families.

“Template” is default path name value, typically you see it in one particular case - when you have mistyped “PATCHNAME” variable name. Other than that, there’s been a lot of changes to OwlProgram in last few months, there’s no point to troubleshoot its version from October.

I have no idea what’s wrong with that USB cable, but you may be interested to know that serial MIDI output is enabled in latest development branch. Currently it just gets a copy of all MIDI output, but there are plans to allow accessing USB and serial MIDI separately.