Firmware update failing

Hello, All. I have a Maslow 4.1 I think it is. Bought it direct maybe 2 months ago, got it assembled but I’ve not set it up/configured it yet. I’ve put that off but put it off for a while and then saw there was a firmware update and diddled around for over a week before trying to do that. Today’s the day and it’s not working.

After I finished assembling it, I updated the firmware to 1.05. Today I tried 1.06, failed, then saw there was 1.07 available and tried that and failed.

I’m in FluidCNC and I hit the Update the Firmware Wirelessly button, chose the file, and tried to update. The firmware.bin is in its own folder, file extensions are visible, the name is “firmware.bin”. The progress bar reaches 100% and then I get a window telling me that there isn’t enough space.

Searching for answers got me threads from a year ago or regarding the index.html.gz and its need to remain compressed. This is only the firmware.bin file which I’m trying to update.

Upon entering the web interface I see the serial messages which ends with two lines of “error:3”. I don’t know if that’s relevant. I did use the FluidCNC button to restart the unit and tried again but the same error regarding space was received.

I’m attaching the serial messages log as well as the screenshots I took. If there’s a thread which addresses this, I missed it.

–HC

Maslow-serial.log (2.5 KB)



After I posted that I looked around some and that brought me to the files. Here’s the screenshot of the files as listed by FluidCNC. I’ve not uploaded any gcode to the unit but I’m not sure if they’d show on this screen anyway.

–HC

It looks like you are trying to load a later version of the software, but the existing one on your Maslow is the earlier version. You can follow this utube video to upgrade your system;
(1) Installing Firmware 1 0 - YouTube
This will then let you upload to the latest versions
From the FluidNC tab
Click on the green tab to load index.html.gz and maslow.yaml files (don’t always need to reload maslow.yaml, only if your frame has changed usually, but keep a backup copy after Calibrate).
Also from the FluidNC tab but using the Orange button you can update the firmware to the latest vwesion.
Hope this helps.

Thank you for the reply.

The video starts out with explaining that it is to update from prior to 1.xx to those after 1.xx. I already have uploaded 1.05.

I haven’t seen an associated index.html.gz or maslow.yaml file with 1.06 or 1.07; did I miss them somewhere?

–HC

If you go to Maslow Home ( Maslow) then Resouces then Firmware, you will see all the available software. You won’t normally reload your Maslow.yaml file each time.
From the Maslow Setup, click on Test and it will report on the versions of Index html and Firmware version on your machine. This is 2MB on mine.
The reason I think you have the earlier version is the space available is too small

Okay, well, it’s possible I made an error or spaced it off and didn’t update the firmware before but the Serial output indicates the Index.html is 1.05.

Also possible I blew through screens and didn’t read them…maybe the update to 1.05 didn’t take and I just wasn’t paying attention.

I’ll go try the 0.xx to 1.xx steps.

–HC

The change from pre 0.0 to 1.0 gave access to more memory. Use the Test option under Setup menu which will show both version numbers.

Too late. I followed the update video for 0.xx to 1.xx. I’ll go check it now but the html ver is 1.07 now.

Index.html Version: 1.07
[MSG:INFO: Firmware Version: 1.07]

Thank God…I was getting concerned.

Yeah, I’m an idiot. Maybe I just didn’t catch the error message on upload weeks ago when I tried 1.05. I must have done something because the index.html was 1.05.

Mine now shows 2MB storage, too.

Anyway, thank you for your help. Sorry it was a fatal OE.

–HC

We are all learning, glad it helped.

1 Like

the installation ask me to install JAVA… MAC OS 10.14.6…
is that OK?

and yes my USB C to USB A is a data cable

doing the 0.87 to 1.07 FW update via Windows worked as in the Youtube video, why it didnt work on MAC OS? anyway workaround done, Calibration successfully completed…

1 Like