If you were one of the owners who updated with the previous beta transitional boot loader update?
I’m referring to this email:
Beta testers who ran the bootlader-updater a couple of weeks ago are in fact using a transitional version of the bootloader, which is identical to the final release version except for a single vulnerability, which we discovered by accidentally sending the bootloader-updater twice in a row. This caused the bootloader to lock up. So, don’t repeat our experiment.
We will need to create a new updated bootloader-updated especially for the beta testers… I will send out another email when this happens, with a link and instructions for the update.
I don’t want to take the chance & update incase something, screws up.
You DO NOT NEED to update the bootloader. You SHOULD NOT update the bootloader. Just send the main firmware update, don’t fool with any bootloader updates.
The only people who should update the bootloader are people who have the first Sub Phatty synths, and have never updated to OS v2 yet (still on OS v1).
If you’re on OS v2 already, you don’t need to update the bootloader. Simple as that.
If you were a beta tester, then you’re on OS v2
also, per my original email to beta testers, it is NOT safe to run the bootloader-updater a second time… it will lock up your Sub Phatty. I think this has already happened to a couple of beta testers who did not get my warning, or who forgot… please don’t be that guy. I’m sorry for creating the room for error in the first place; it won’t happen again.
OK got it, just send the firmware update. So is there still a new boot loader update coming for the v2 bootloader beta testers as stated in the email we received? If not will this affect the beta testers ability to update if there’s firmware coming that requires a bootloader update first?
I already updated the bootloader to v2 with the previous firmware release, as my Sub Phatty is running firmware 2.0.1.
I followed the update instructions before I found this post, which told me to run the bootloader update (again) and update to version 2.0.3 of the firmware. Running the bootloader update again apparently did not ‘lock up’ my Sub Phatty as far as I can tell, since it’s still working, but the latest version of the Sub Phatty Editor (1.1.0) is reporting my Sub Phatty is still on version 2.0.1 of the firmware, so apparently the 2.0.3 update didn’t go through.
What are the exact steps to update to the 2.0.3 firmware for a synth running version 2.0.1?
put the unit in bootloader mode (hold “pitch amt osc2 only” and “hard sync” buttons, press “activate panel” button twice)
send the 2.0.3 firmware sysex from your computer to the synth, using any sysex-sending software and preferably the Phatty’s own USB connection, but any properly-working MIDI interface should do OK as well
Yes it’s looking like we will still do this for the beta testers. I am sorry we weren’t able to get to it prior to releasing a new update; we meant to. We’re getting there though.
I didnt know i wasnt suposed to update de bootloader !
I dont get any response from the unit right now so i guess its locked.
The only thing that is blinking is the LFO rate LED , No sound, and the preset leds are all turned off.
And i cant put it back in shift mode to update it again,
it doesnt have any firmware running now i guess.
you’re probably OK. that state that you are in is the bootloader.
If you plug in USB from the sub to your computer, does your MIDI / sysex software “see” the sub?
if so you’re good, just send the most recent firmware sysex.
if any questions about this, contact moog service (techsupport at moogmusic dot com) for help performing the update.
It’s been almost 1½ years since I asked this & still no sign of a fix of the bootloader for beta testers. Has the Sub Phatty been forgotten about? I hope not because I still love mine, even with the constant stuck notes (I’d be lost without the + - octave panic button) So can we please have some some Sub Phatty Love
I know the Moog team is kept pretty busy & that’s great & nice to see new synths coming (Sub37, Mother 32 etc.) but this whole dodgy bootloader conundrum was replied to over 2 years ago, stating that a fix is on the way but still after 2 years…nothing.
So is there now no fix coming? A clear answer would be very much appreciated Amos please.
