Firmware Update Error  

Page 1 / 2
  RSS
malcinator
(@malcinator)
Trusted Member

Just tried to update the firmware using the OS X Firmware updater, I am using macOS Sierra and the latest Drivers from the Support site. When I try I receive this error...

'Uncaught node.js Error - Error.EROFS, open './fw.hex' at Error (native)

I have included a couple of screenshots which show my settings used in the Firmware Util and the error.

...any help would be great.

...
Posted : 16/10/2016 7:12 am
dkmans44
(@dkmans44)
New Member

I am having the same issue. Do you have yours solved yet?

...
Posted : 19/10/2016 3:37 am
malcinator
(@malcinator)
Trusted Member

I am having the same issue. Do you have yours solved yet?

In a word... no

...
Posted : 19/10/2016 8:57 am
JohnOCFII
(@johnocfii)
Estimable Member

I am having the same issue. Do you have yours solved yet?

Are you both using Sierra? I just used the firmware updater successfully in El Capitan on my MacBook Pro.

https://3dprinting.community/login #Community Discussion for 3D Printing...
Posted : 20/10/2016 9:01 pm
Omikron
(@omikron)
Estimable Member

I recently ran a successful upgrade using macOS Sierra.

It sounds like a Java issue of some sort. Sounds silly, but do do you have the latest version of Java for OS X installed? Usually such dependandcies would be checked automatically, but it wouldn't hurt to check manually.

...
Posted : 20/10/2016 10:48 pm
malcinator
(@malcinator)
Trusted Member

Hi,

Well I have upgraded Java and OSX Java and downloaded the latest Firmware which includes the V2 Firmware util and I get the same error when I try to complete the update.

I resorted to Cura to update the Firmware and ran the recalibration. Everything is functioning and working as it should.

...
Posted : 22/10/2016 1:37 pm
Omikron
(@omikron)
Estimable Member

I'm pretty sure one can also just use the Arduino IDE to upload the hex file, although you'd want to make sure you have the right type of board selected.

...
Posted : 23/10/2016 4:04 am
JohnOCFII
(@johnocfii)
Estimable Member

Hi,

Well I have upgraded Java and OSX Java and downloaded the latest Firmware which includes the V2 Firmware util and I get the same error when I try to complete the update.

I resorted to Cura to update the Firmware and ran the recalibration. Everything is functioning and working as it should.

Do you have a space in the path name of the directory where the firmware is located, or any parent directories? That is a common cause of that node.js error. Someone on the FaceBook forum had a similar issue, and I suggested he look for spaces. He had one. Removed it, and then the updater worked for him.

https://3dprinting.community/login #Community Discussion for 3D Printing...
Posted : 24/10/2016 2:41 am
malcinator
(@malcinator)
Trusted Member

I have read that too and moved the updater & firmware file in to the root of my home directory as such

~/FirmwareUpdaterV2.app
~/1_75mm_MK2-RAMBo13a-E3Dv6full.hex

...and it made no difference. It's not a major problem as I can update through Cura & install custom firmware but it would be nice to use the UpdateFirmware App and remove Cura as I only use it to update firmware.

...
Posted : 24/10/2016 4:40 am
JohnOCFII
(@johnocfii)
Estimable Member

I have read that too and moved the updater & firmware file in to the root of my home directory as such

~/FirmwareUpdaterV2.app
~/1_75mm_MK2-RAMBo13a-E3Dv6full.hex

...and it made no difference. It's not a major problem as I can update through Cura & install custom firmware but it would be nice to use the UpdateFirmware App and remove Cura as I only use it to update firmware.

But what is the path above your home directory? If the root is still called "Macintosh HD" as they used to be called, that may cause an error if spaces are not treated correctly in the Prusa software.

https://3dprinting.community/login #Community Discussion for 3D Printing...
Posted : 24/10/2016 5:00 am
malcinator
(@malcinator)
Trusted Member

I have read that too and moved the updater & firmware file in to the root of my home directory as such

~/FirmwareUpdaterV2.app
~/1_75mm_MK2-RAMBo13a-E3Dv6full.hex

...and it made no difference. It's not a major problem as I can update through Cura & install custom firmware but it would be nice to use the UpdateFirmware App and remove Cura as I only use it to update firmware.

But what is the path above your home directory? If the root is still called "Macintosh HD" as they used to be called, that may cause an error if spaces are not treated correctly in the Prusa software.

That is a good point... I will investigate Thanks!

...
Posted : 24/10/2016 5:41 am
malcinator
(@malcinator)
Trusted Member

I have read that too and moved the updater & firmware file in to the root of my home directory as such

~/FirmwareUpdaterV2.app
~/1_75mm_MK2-RAMBo13a-E3Dv6full.hex

...and it made no difference. It's not a major problem as I can update through Cura & install custom firmware but it would be nice to use the UpdateFirmware App and remove Cura as I only use it to update firmware.

But what is the path above your home directory? If the root is still called "Macintosh HD" as they used to be called, that may cause an error if spaces are not treated correctly in the Prusa software.

That is a good point... I will investigate Thanks!

Problem solved. Renaming 'Macintosh HD' to 'Macintosh.HD' did the trick.

...
Posted : 25/10/2016 6:48 am
jonathan.b4
(@jonathan-b4)
Active Member

Problem solved. Renaming 'Macintosh HD' to 'Macintosh.HD' did the trick.

Renaming the root drive to eliminate the space did not work for me. I am on Sierra.

...
Posted : 29/10/2016 7:35 am
Omikron
(@omikron)
Estimable Member

Problem solved. Renaming 'Macintosh HD' to 'Macintosh.HD' did the trick.

Renaming the root drive to eliminate the space did not work for me. I am on Sierra.

Have you tried downloading the 1.7.4 driver package and running the firmware updater from there? It's an older version that worked for me, whereas the newer version did not.

...
Posted : 29/10/2016 8:52 am
Kaizers
(@kaizers)
Eminent Member

I am running the newest macOS Sierra, and I had the same problem with Firmware V.2, but I simply went back to the original firmware updater in driver package 1.7.4 and it updated to 3.0.9 with no problem!

...
Posted : 08/11/2016 6:30 am
Omikron
(@omikron)
Estimable Member

I am running the newest macOS Sierra, and I had the same problem with Firmware V.2, but I simply went back to the original firmware updater in driver package 1.7.4 and it updated to 3.0.9 with no problem!

I'm glad at least one person was following my advice. I felt like I was just yelling into an empty hole. 🙂

...
Posted : 11/11/2016 9:27 pm
jean-marc bouley.c
(@jean-marc-bouley-c)
New Member

I have read that too and moved the updater & firmware file in to the root of my home directory as such

~/FirmwareUpdaterV2.app
~/1_75mm_MK2-RAMBo13a-E3Dv6full.hex

...and it made no difference. It's not a major problem as I can update through Cura & install custom firmware but it would be nice to use the UpdateFirmware App and remove Cura as I only use it to update firmware.

Thanks. I went trough Cura and very easily I have updated the MK2 firmware.
But I do assume it's not a nice solution ! But that works.

...
Posted : 12/12/2016 5:04 pm
cyberreefguru
(@cyberreefguru)
Eminent Member

I am also on Sierra and 1.75 did not work for me. I tried the 1.74 version and after waiting 10 minutes it eventually timed out. I rebooted and tried it again and it worked - "Firmware updated successfully!". Clicking on support on the LCD and it says 3.0.9 - good times.

Hope this helps others.

-Tom

Engineer. Designer Maker. Fiercely unapologetic. Studying the art of subtle. Failing. Be Inspired. Stock MK2 - Orange because it's cool ;)Visit my channel - https://www.youtube.com/user/cyberreefguru...
Posted : 29/12/2016 7:35 pm
margot.b
(@margot-b)
New Member

I am on Sierra 10.12.2 on the new MacBook Pro. I had the same error come up and didn't see your thread until now... 🙄 I had a friend with a virtual machine running Win10 on an identical MacBook Pro so I had him try it that way and it worked for him. I thought perhaps it was the adapter necessary to use the USB or just a glitch with my laptop but now I see it was probably renaming to Macintosh.HD or just using an older version of the driver.

I really appreciate you guys posting on here and sharing your experiences! I'll keep this noted for the next firmware update. 😀 --Margot

...
Posted : 09/01/2017 10:22 pm
martti.o
(@martti-o)
Active Member

I had the same issue because of disk named "Macintosh HD". I placed the updater and the FW file on another disk (without space in name) and ran it these successfully. Made only the FW .hex file would have been enough.
😎 Martti

...
Posted : 20/02/2017 12:48 pm
Page 1 / 2
Share:

Please Login or Register