Bootloader update

Version 4.0 introduces an easier way to update the firmware - directly from your web browser, just like with the mk1. To use this new update method, you’ll first need to update the Electra One bootloader.

The bootloader can be updated by the beta 4.0 (or later) firmware. Thus, in order to update the bootloader, the beta 4.0 must be installed in the usual way using the USB storage. Once you are running the 4.0, you can go to Electra One App to proceed with the bootloader update.

Important
I’ve run quite a few updates and everything worked fine. But since this is a bootloader update, there’s always a small risk of bricking the controller if something goes seriously wrong :slightly_smiling_face:
If you’re on Windows or Linux, we can recover it easily (i.e., un-brick it). If you’re using only a Mac, I’d recommend waiting until a few more users successfully complete the update.

Either way, if something goes wrong and the controller gets bricked, we (Electra One) will make sure it gets fixed.

If you decide to help us with this, feel free to ping me before you start - I’m happy to stand by just in case.

3 Likes

Hi Martin,

I gave this a shot but it seems to do nothing. The device shows “Uploading Firmware image” and the progress bar in the browser is stuck at 0%.
I tried with 4n, 4p and now 4s.

Cheers!

1 Like

Hi @moss,

I just read what I wrote in the original message I an can see that I did not share the link to the bootloader update page :slight_smile:

In order to use the new firmware update, the bootloader needs to be updated first. And in order to update the bootloader, you must run any of 4.0 (the more recent the better).

ie. the steps to take:

  1. do conventional firmware update to 4.0.0… using the USB storage
  2. once the 4.0.0… is running, go to Electra One App and use it to update the bootloader
  3. after it reboots, use beta.electra.one/electra to update the firmware

are you stuck at the boot screen now, or can you boot your controller ok?

That’s exactly what I did. I am stuck on step 2 as described above. But I can reboot the device without a problem.

just to make sure. The page you use in step two is this:

I am double-checking because “Uploading Firmware image” means that the controller wants to do the firmware update, not the bootloader update.

Ah, sorry for the confusion! Yes, I ment Bootloader.


1 Like

This is a set of sysex messages that facilitates the bootloader update. That is what browser sends to the controller to update the bootloader.

Could you try to run with a SysexLibrarian / MidiOX / or similar?

bootloader-update.syx.zip (277.4 KB)

While running, the controller will send back ACK/NACKs and progress report data.

This worked fine with good old MIDI-OX.
Output.txt (181.6 KB)
Input.txt (20.3 KB)

I am on Windows 11 Pro with all patches and used Google Chrome previously (also latest version).

I will give it a try. Thanks for testing it. You should be able to update the firmware directly from beta now - but I am quite sure that you will hit the same issue.

This is the output in the JavaScript console in Chrome when everything goes ok:

EDIT: @moss I was able to reproduce the issue on Windows. No need for you to do / review anything on your side. I will tackle that on my end.

@moss, would you try the bootloader and firmware update now? Windows does not like bigger chunks of MIDI data. Updated beta.electra.one uses smaller chunks now. If you do, make sure you hard-reload the page to make sure nothing is cached.

The upload of the bootloader file does work now but it is now stuck on “Validating update…”. I guess you need to adapt it to the shorter messages?!
Or maybe it is only the text that remains since in the browser it said “Bootloader update has been completed. You can leave this page now.”

I also tried the firmware update: my controller has 4r. Ther update seem to have worked but the browser still says that I need to update it. And it still says its 4r. Is therer a newer one?