Blue screen on startup
I have sometimes the attached message powering up my C1. You see firmware version, message did not appear before.
Microsoft style blue death screen, is Prusa mimicing Redmond giant with color and "unknown error" message label :)?
More seriously, is the sub=version correct?
Anyone having same behaviour?
When flipping power, everything goes as normal.
This is not systematic, once over 10 startup maybe.
My printer is in a cold place (10°c) and of course this is the temp of electronics at cold start.
Any idea?
RE: Blue screen on startup
Jeps, that's normal. Wants to sleep a little longer.
RE: Blue screen on startup
That’s what I think. My C1 is a lazy printer but it has some reason...
Working 16 hours a day without complainig nor missing anything since 5 months would probably put any human in a deadly state.
Reason why I forgive it ...
RE: Blue screen on startup
Well... boredom requires a certain minimal level of intelligence and arguably, Core One isn't there yet (*). Like a gold fish in its glass, every round is new and exciting.
Rumor has it that in the dead of night, Core One's microcontroller sneaks out of its box to discuss existential matters with its smarter little brother (the $4 ESP32 that has been slapped on as afterthought for WIFI).
(*) and with AI everywhere, down to the toothbrush and beyond, this is not necessarily a bad thing.
RE: Blue screen on startup
I just want a Core One with Klipper 😪 ... Marlin needs to be taken behind the barn and shot
Page 6 of your 3D Printing Handbook:
Operating Temperature Range: 18 °C - 38 °C
Cheerio,
RE:
Page 6 of your 3D Printing Handbook:
Operating Temperature Range: 18 °C - 38 °C
Cheerio,
My ambient room temperature is 19-22° and I occasionally get this at startup as well since the 2.5.0 boot loader was released. In my view, it's simply a bug loading the firmware.
Also, I think the 18° lower limit is way to conservative. Until I moved my printer back inside I was routinely using it (except for engineering plastics) in a 8-10° garage.
RE: Blue screen on startup
My hobby room gets down to 14 C in the winter and I haven't had a problem yet. Just running PLA and PETG.
RE: Blue screen on startup
The garage where mine lives is generally 25-30C and I get this periodically too. I presumed it wasn't environmental since it's transient, and pressing reset will make it boot fine. I'd love to know why but I've yet to be able to replicate.
RE: Blue screen on startup
This did not start happening until the bootloader was updated. It was reported back in August and a JIRA ticket was assigned to it. It's simply a bootloader bug
RE: Blue screen on startup
6.4.0 Same thing at cold start from time to time. Just hit reset and away it goes.
RE: Blue screen on startup
I've had the same problem. Happens on cold start, works fine on restart. Printer is inside the house, so ambient temperature is not an issue. Hopefully it is just a bootloader bug and not a hardware issue.
RE: Blue screen on startup
It's not a hardware issue. It's strictly a bootloader issue.
RE: Blue screen on startup
I've had the same problem. Happens on cold start, works fine on restart. Printer is inside the house, so ambient temperature is not an issue. Hopefully it is just a bootloader bug and not a hardware issue.
Exact same here as well. Hitting the reset button always boots normally after the BSOD. Understood that the problem started after a bootloader version update.
A fundamental difference between a cold start and the reset button is all of the DC supplies are stable on the button push. So, the BL is likely enabling HW resources too quickly or too close to each other causing a voltage dip and crash on a cold ramp-up. Boot time is always power hungry. Hopefully they sort out a cleaner BL sequence on a future release.
If this truly is the scenario, one can monitor supply rails at startup look for dips and add delays but issues like this are labor intensive to find. The Jira was open since August so not high on anyone's list. So, it's just a minor nuisance every handful of startups.
RE: Blue screen on startup
Hello,
i have the same problem.
sometimes it happened 2-3 times a day but the most time it´s all normal.
RE: Blue screen on startup
After dealing this occasional blue screen for several months at cold starts, I finally got around to doing this experiment I've wanted to try.
Hitting the reset button always fixed the problem but I've wondered if was truly "always".
Powered up and waited for a full startup, including network connections.
Went through a series of 30 reset button only boots w/full startup to see if the blue screen would show up. Never did. Why 30? Well > 1 and was done while working on another activity in the same room. I just would hit the button, tick off the count on paper, and get back to my other activity. Thirty was also a round number and the limit to my patience and distraction time.
Not 100% conclusive, but with the 6.4.0 bootloader FW, I'd get 2 or 3 blue screens a month over the ~25 times it would be cold powered on over the same period.
Wondering if anyone has seen the case where a second blue screen showed up on the reset push? I never have and hence the earlier speculation that it's just resource sequencing as the supplies are stabilizing for this version of BL FW.
Also, I've never seen the case where a quick toggle of the power switch didn't fix it either. I did that a handful of times early on but realized the reset button was softer.
RE:
maybe the reset does just an os restart but not an bios/bootloader restart like turning off and then on the printer
RE: Blue screen on startup
Just rechecked and the reset button has the graphical bootloader screen with the progress bar. In the pic from the OP, the blue screen refers to the same bootloader version that's buggy. The schematics are open source, so I'll take a look to see how the reset is routed. Understood that a reset button could be separate from the power-on-reset circuit but typically it's in parallel to mimic the power on. Otherwise, you could get a crash that's un-recoverable via the reset button.
Funny thing is, just before replying, I tried a quick check ... first power switch on, got a blue screen.
It'll be nice when they fix this. I recall in earlier versions of the FW, other more informative messages about fails in the boot process and initialization would come up. As those were fixed, mostly it's down to this one blue screen that happens very immediately after the power on.
RE: Blue screen on startup
The schematics are open source, so I'll take a look to see how the reset is routed. Understood that a reset button could be separate from the power-on-reset circuit but typically it's in parallel to mimic the power on. Otherwise, you could get a crash that's un-recoverable via the reset button.
[...]
I recall in earlier versions of the FW, other more informative messages about fails in the boot process and initialization would come up. As those were fixed, mostly it's down to this one blue screen that happens very immediately after the power on.
I don't expect you to find that the Reset button works in some unexpected way. The difference in behavior between power-on reset and reset button (one causing sporadic blue screens, but not the other) is more likely due to the fact that some component in the overall system has not come fully alive right after the power-up.
The present blue screen is not a firmware error, but occurs in the boot loader. That's why the error message is so rudimentary and no dump file is written.
RE: Blue screen on startup
@jurgen, very much agreed on "more likely due to the fact that some component in the overall system has not come fully alive right after the power-up".
Thanks for the correction on my referral to the bootloader not being the firmware. Two separate and distinct sets of code and purposes.
Tracing the reset button circuit through the xLCD board to the xBuddy board and finally to the STM32F427ZI, it's directly to the MCU NRST pin. The key difference is, supplies would have been up and stable when the user hits the button. The MCU datasheet shows the NRST pin as optional and the MCU has a supply supervisor. So basically, the NRST and supply supervisor are AND'ed for startup, monitoring, and manual resets.
Potentially a system component not fully voltage stabilized (i.e. voltage near the threshold of operation), but then overall boot activity in this bootloader version nails one of the supply rails and causes a timeout.
As a side note in looking through the schematics, ESD diodes and opto-isolators were used between the between the xLCD and xBuddy board. Very properly designed from a HW standpoint for robustness. Good to see.
This BSOD is a nuisance but likely low on the developer fix list. Developers figure most people will be standing in front of the printer at power-up, so they can just hit the reset button anyway. For me (at least) the belt tensioning wizard was a much better use of developer time.