This is the best info i can provide to my problem, but i dont even know how to read this, java stacktrace tier file
#mcu 'mcu' serial connection closed
vapid coral
this error is genuinely bigger then the firmware im trying to deploy
The fact it's reporting "no printer.cfg" is weird, because it's there.
A line in my printer.cfg just told me one major reason why it could've fucked up
"Firmware filename must not match the last name of the firmware flashed."
vapid coral
I'll ask in voidstar lab, i guess
slim herald
The fact it's reporting "no printer.cfg" is weird, because it's there.
It isn't reporting that. Remember that log files start with old info at the top, and then it gets newer as you scroll down. The current concern is the one at the bottom. The older stuff about missing printer.cfg is just old stuff, presumably from before you got printer.cfg in place
vapid coral
fair enough
I still don't know why it's messed up
i've tried many different ways to flash the firmware and it just doesnt seem to wanna stick properly
slim herald
That, I fear I have less advice on
From that note about new file names each time, I assume we're playing with some creality board?
vapid coral
...turns out that you absolutely have to add the baud rate to the printer.cfg as well, and not just in the firmware
I wish I knew that sooner because that would have saved so many headaches
vapid coral
From that note about new file names each time, I assume we're playing with some ...
yeah lol, a 4.3.1 512KiB board.
vapid coral
Ah fuck now i gotta new problem