To everyone who is having update trouble, I apologize. I wrote some emails to the thread-starter on Friday, which seemed to help; I will post the same info here.
First some background information about the process.
the Step 1 sysex file is just a short command; it erases the main firmware if there is any, and puts the unit in bootloader mode, ready to accept new main firmware.
Corgy wrote:is there something like a "reset-button" on the Sub37 ... like, hold down "key-what-ever-the-combi-might-be" at "power on"?
There is something like a hard-reset for firmware update, which does the same thing as the Step 1 sysex... you turn the Fine Tune and Filter Cutoff knobs both to zero, and then hold the Pitch Bend wheel up (in its maximum bend-up position) while turning on the power. If you do this, then instead of booting normally the unit will boot up to the bootloader, erasing the main firmware if it was present, and will then be ready to accept the main firmware. (this means you can skip sending step 1 if you boot up in this special way)
The step 2 sysex file is the main firmware.
Step 3 and Step 4 comprise the panel firmware. Step 3 is a short command which erases the old panel firmware, if it's present, and sets up the system to receive the new panel firmware. Step 4 is the panel firmware. A small note, the system definitely will not accept Step 4 unless you've just sent Step 3 beforehand. I've made the mistake of restarting the Sub 37 and trying to send Step 4 by itself; this doesn't work, but restarting the unit and sending step 3, then step 4, is OK.
Next I would like to describe what the update process looks like, step by step, in the case where it has already failed and you are trying to get back on track.
First, sending step 1 (or booting using the manual procedure decribed above):
Normally you should see the MIDI LED blink on/off three times, and then go out… this means that the main firmware was probably installed correctly when you sent Step 1. The three blinks means it’s erasing main firmware. If there is not main firmware, then you will only see one red LED blink on sending step 1.
After sending step 1, the MIDI LED should be off (or yellow; the red MIDI LED will be off) and the Arpeggiator Rate LED will be blinking on/off at a medium rate.
Sending step 2:
The red MIDI LED blinks on and off at a medium speed, just a little faster than the Arp Rate LED. So, both these LEDs are blinking, out of sync. When the transfer is finished, all the panel LEDs flicker off for a moment, then all are lit again… red MIDI LED is lit solid, Arp Rate LED is blinking a little faster than before.
Sending step 3:
The Arp Rate LED pauses for an instant, and then blinks a lot faster than before. MIDI LED doesn’t do anything, it’s still solid red.
Sending step 4:
Now the red MIDI LED is blinking on/off again, quickly… faster than the Arp Rate LED… the MIDI LED begins blinking on/off as soon as the step 4 sending begins, and it continues to blink on/off through the whole sending process. Again the Arp Rate LED and MIDI LED should both be blinking but out of sync.
When step 4 is finished, the synth restarts and looks normal again, with LCD and everything working.
If the red MIDI LED stops blinking while the step 4 transfer is still happening, or if the MIDI LED and the Arp Rate LED start flashing on/off in sync with each other (both on/off at the same time) then this indicates a transfer error.
If both LEDs are blinking in sync after step 2… that suggests that actually step 2 is failing.
This means that the sub 37 is never loading its main code completely.
If that’s what is happening, it explains also why the panel update (steps 3 and 4) are not working.
The main code must be running, before the panel can be updated.
There is a bootloader on the main board, which is the thing that is running during step 1 and step 2.
This bootloader can accept a main firmware update, but it can’t do the panel firmware update by itself; main code update must happen successfully first.
OK, sorry for the long post... if you have read this far, there is a payoff
Here is a download which contains a re-packed version of Sub 37 firmware v1.0.6.http://www.moogconnect.net/downloads/su ... adding.zip
For Windows users, you can try the step 1-4 .exe files. These executable files will launch a simple automatic sysex-sending utility; the file will send automatically or you may need to type a number to select Sub 37, and then press Enter to send.
Step 1-4 sysex files are also included.
The other main difference with the files above is that step 4 is a larger file than before, because we added some padding to the data as an extra way to slow down the process. If your update process is failing at step 4, the hope is that this new step 4 with padding will work better. Try it and let me know.
All the best,