search

prusa3d / Prusa-Firmware-Buddy

Firmware for the Original Prusa MINI, Original Prusa MK4 and the Original Prusa XL 3D printers by Prusa Research.
Other
1.15k stars 221 forks source link

[BUG] Error! #13604 when MK4 powered on #3597

Closed dp250f closed 2 months ago

dp250f commented 9 months ago

Printer type - MK4

Printer firmware version - 5.1.2 release and newer

Original or Custom firmware - Custom (#define HEATER_0_MAXTEMP 320)

Optional upgrades - Micro Swiss CM2 RepRap V5-V6 0.4mm nozzle, silicone hot end sock

USB drive or USB/Octoprint PrusaConnect

Describe the bug Error! #13604 displays when powered on. Printer boots normally when reset with reset button.

How to reproduce Flash firmware. Turn off printer. Turn it back on.

Expected behavior Printer should boot normally

G-code N/A

Crash dump file "No crash dump to save"

Video Please attach a video. It usually helps to solve the problem.

bkerler commented 9 months ago

Haven't tested the 5.1.2 yet, but Error #13604 means : "Firmware file missing in the USB flash!". It could be that the file wasn't written completely or the filesystem on the usb stick could be broken if the printer wasn't shut down properly or wasn't ejected properly from the pc. Also make sure you don't have several fw upgrades in the same root directory on the usb stick.

bkerler commented 9 months ago

Version 5.1.2 says that this issue should be fixed ... so maybe this version introduced an issue instead.

dp250f commented 9 months ago

Reformatted the USB drive. Still displays error on cold boot and not on reset. I also tried without the USB drive and it boots normally.

Other than the error message on cold boot, everything works normally. The only firmware bbf file on USB drive is the one I last flashed (named "mk4_release_boot_5.1.2.bbf")

dp250f commented 9 months ago

Bought a new flash drive, formatted FAT32. Still the same thing happening.

dp250f commented 5 months ago

Built and flashed 6.0.0 release today. Issue persists.

github-actions[bot] commented 2 months ago

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

github-actions[bot] commented 2 months ago

This issue has been closed due to lack of recent activity. Please consider opening a new one if needed.