Prusa-Firmware-Buddy
Prusa-Firmware-Buddy copied to clipboard
prusa3d
[BUG] Printer Main screen not loading after firmware update 5.1.2
MK4
5.1.2
Original
USB drive or USB/Octoprint USB
Describe the bug After updating the firmware 5.1.2 the screen freezes on the Prusa Screen Bootloader 2.3.4
How to reproduce Every time I boot the screen
Expected behavior Should load the printer main screen
https://github.com/prusa3d/Prusa-Firmware-Buddy/assets/869951/59104efa-ff14-40c9-ba38-bf4061f625de
Which fw version did you upgrade from ? It might resolve the issue if you downgrade to an older bootloader (5.1.0) and then retry to upgrade. Also make sure you use a different usb stick just to make sure, some people have issues with the prusa usb stick.
I had the same issue with the previous firmware. It helped for me to pull the usb stick after the orange bar reached the middle and stopped. The printer then asked for a stick with the bbf file and i inserted the stick again. The flashing then continued as expected.
Which fw version did you upgrade from ? It might resolve the issue if you downgrade to an older bootloader (5.1.0) and then retry to upgrade. Also make sure you use a different usb stick just to make sure, some people have issues with the prusa usb stick.
I have attempted to upgrade from the previous version 5.1.0 multiple times, even utilizing a new USB stick. Despite several retries and a few instances of downgrading and upgrading, I have not achieved success.
Another possibility for flashing the firmware would be using prusaslicer and a serial usb cable afair
I'm encountering the same issue with firmware version 5.1.2. When I initiate the upgrade process using the "MK4_MK3.9_firmware_5.1.2.bbf" file on a Prusa memory stick, the printer starts upgrading the bootloader and then the firmware. However, it never reaches the main menu. Pressing the reset button or cycling the power does not resolve the issue.
Upon downgrading to firmware version 5.1.0, I was able to access the main menu again. This suggests that the problem is specifically with firmware version 5.1.2. Notably, even though the bootloader was keept as version 2.3.4 during the downgrade process, the printer still functioned normally with firmware 5.1.0.
Seeing something kinda similar on the MINI+, but the behaviour is a bit weird. Already posted on the forum: https://forum.prusa3d.com/forum/hardware-firmware-and-software-help/mini-wont-boot-to-menu-from-cold/
"Since i´ve flashed the 5.1.2 update onto my printer, i have a very weird problem, where the printer won´t boot fully. It will load the firmware (bar goes to 100%), it completes the short fan self test at startup (fans stop spinning), but it w´ont beep and it w´ont go to the menu. An immediate reboot doesn´t fix it, but if i leave the printer in that state for at least a couple minutes it will boot fully, and as far as i can tell, seems fine and prints.
If a USB stick with the 5.1.2 firmware is connected at cold boot, it will reflash that, but still gets stuck when booting. But same as above, if i leave it for a bit, then reboot, it boots to menu as expected without reflashing."
I think i´ll downgrade for now...
This happens on the XL for me, not on the MK4. I ran 4.7.5 -> 5.1 without problems, but with 5.1.2 with the new bootloader, then I couldn't upgrade, the firmware installation was sitting for more than two hours, but nothing finished. After booting it, it gets to 50% like the picture above, and newer boots. Removing the memorystick, replacing the firmware to 5.1.0, it downgrades itself to that version, and it works fine, but if the fw is on the memory stick, it nows flashes the firmware on EVERY boot. This does not happen on my MK4, the fw file is on there (5.1.2 though), and it does not flash it self every boot, so that is stable, but my XL this is tragic. And yes, I don't use the prusa usbstick, that stick is just rubish, so I use an sandisk, have same make&model on both MK4 and XL
This is also discussed in the forums, but it seems that the forums is just a place to let people let out steam, rather than getting any sort of help from Prusa.
I have the same issue on an MK4. Downgrading work. Downgrading to an older version and then upgrading did not worked for me. Still hangs. Awaiting new fw with fix.
I'll add one more to hopefully raise this priority. If my MK4 needs to restart after a 5.1.2 upgrade (power loss, manual power cycle, reset button, etc.), it hangs on the boot screen. Forced to reinstall 5.1.0 to complete a full boot to main screen. If I'm stubborn and try powering off and on a bunch (dozens of times) - it may eventually boot as expected with 5.1.2.
I hate ot just add a me to but I am seeing the same thing.
New MK4, Tried 3 different USB sticks, made sure they where FAT32, downloaded the firmware a few times, but no luck.
5.1.0 installs fine but 5.1.2 hangs after the update at the bootloader screen.
I have the same thing. Been in contact with support for the issue and we tried various things such as factory reset etc. Sometimes it helps when I power down (cut power) after it flashed (and is stuck on 100%), but not always.
One thing that support said should not be happening is that the bootloader flashes non-interactively. Apparently the bootloader should always ask before flashing if there's a firmware file found on the USB stick. Is it interactive with any of you?
They also suggested to change the battery on the motherboard, but I didn't have a CR1220. Anybody here already tried whether replacing the battery helped?
Regarding changing the battery, what data are we loosing then?, need to do full calibration again? (Not so bad on the MK4, but it's tedious on the XL)
Not sure. I removed the battery to check what type it was, but since I didn't have any I placed it back, and I didn't notice any loss of data or settings.
Went to buy a new battery, and unfortunately replacing the battery didn't work.
My Bootloader does not prompt either. If it finds a firmware, it just starts the firmware flash. I thought that was normal, glad to hear it is not but mine is doing the same thing.
I worked with support last night. We tried a number of things and nothing solved it. In the end we flashed 5.1.0 in (that one works) and he was going to pass the problem off to the MK4 firmware team. I haven't heard back yet. He didn't mention the battery but we did to a complete factory reset as well as disconnect all the motors and Nextruder and try it then. Nothing fixed the 5.1.2 hang yet.
This is a bootloader bug or firmware bug. It won’t work until they fix the FW. My guess is that there are some components in the wild that are slightly different in our control boards and they are not compatible with the BL. But then again this is just a guess. It might be many things, but for sure it is a software/firmware issue
there’s not much we can do until they fix it.
I agree, I think it is something in the Bootloader but it must be an interaction of the Bootloader and something in the firmware. 5.1.2 is the only one I see the problem with. With the same bootloader (2.3.4) I have tried firmware 5.1.0, 5.0.0, 4.7.3 and they all work fine.
It would be great if we could move back to an older bootloader to test but it seems that once the bootloader if updated, it stays.
Sounds right. An interaction of the BL with the FW…
it might be possible to downgrade the BL using an older firmware that has a boot loader update in it.. but it’s a guess.
I think we should wait for an update since the cycle of new releases should be close.
Any news if the latest firmware fixes this for everyone? I am in the middle of a large job and can't update for now to check.
Tried the latest 5.1.3. issue still persists... Tried downgrading to an older firmware with boot loader downgrade.. The flashing went smooth but once trying to go back to the latest firmware the issue came back again. Guess has something to do with the UART upgrade process.
Same issue still as well. I tried upgrading to the new 5.1.3 and it still is stuck trying to boot. I see the progress bar move across to 100% and then it just says locked up at that point. The 5.1.3 firmware didn't solve the issue.
Here’s my solution. Factory Reset with “clear all settings and flash firmware with USB” or a similar options. I did that and the 5.1.3 flashed fine for me.
@kikolobo is that a permanent fix? I also did that with the 5.1.2, but it still gets stuck every now and then. Restarting the printer a dozen times usually gets it to boot up. If you leave the firmware on the USB stick, does it automatically flash the firmware again every time the printer starts?
Don’t know if it’s permanent. So far so good. We’ll see what happens on the next update.
it does attempt to refresh every time....
Here’s my solution. Factory Reset with “clear all settings and flash firmware with USB” or a similar options. I did that and the 5.1.3 flashed fine for me.
This solution worked for me. Thank you for bringing this up.
Update: It worked for a while, then the printer stopped booting after a couple of prints. Same issue again. I had to go back to version 5.1.0
Seeing something kinda similar on the MINI+, but the behaviour is a bit weird. Already posted on the forum: https://forum.prusa3d.com/forum/hardware-firmware-and-software-help/mini-wont-boot-to-menu-from-cold/
"Since i´ve flashed the 5.1.2 update onto my printer, i have a very weird problem, where the printer won´t boot fully. It will load the firmware (bar goes to 100%), it completes the short fan self test at startup (fans stop spinning), but it w´ont beep and it w´ont go to the menu. An immediate reboot doesn´t fix it, but if i leave the printer in that state for at least a couple minutes it will boot fully, and as far as i can tell, seems fine and prints. If a USB stick with the 5.1.2 firmware is connected at cold boot, it will reflash that, but still gets stuck when booting. But same as above, if i leave it for a bit, then reboot, it boots to menu as expected without reflashing."
I think i´ll downgrade for now...
Having the same issue on MINI with last firmware. Loading bar at 100% and just freezes. Bought the printer 6 days ago, so no idea about behavior with other FW versions. Mine has done this EVERY time i turned it on (which is 4 in total, i haven't printed a lot, but still 100%), besides first boot after build (had not upgraded FW yet then thought). Haven't figured out what exactly makes it boot eventually. Tried reseting, removing USB, fully pulling the PSU plug. at some point in just boots. Seems like nothing will ever touch an ATmega and Marlin1 for stability...
@theloukou this is a clear indication that there is something wrong in reading the eeprom. This happens if you move from very old to latest firmware versions as it seems. Try to downgrade again to the original firmware and then update the firmware version by version.