Open kharrisma opened 9 months ago
PS... the machine DOES read gcode files from the SKR uSD socket, so the socket itself doesn't seem to be an issue.
Try a few different SD cards.
This is the sixth card I've tried, all from different manufacturers (thinking maybe my machine doesn't like one particular flavor of card...) I'm sticking with this one because I used it to successfully re-flash the display, so I know it works (well, works for the display, anyway... no reason it shouldn't work in the control card as well.) I was using larger 32Gb cards until I learned that it's more reliable to use 8Gb or smaller cards, so that's what I'm using. Doesn't seem to matter whether I use el-cheepo cards or more expensive big-name cards... same issue either way. I'm really leaning towards an SKR board failure; I can see no reason why it should be able to read files from the uSD card, but NOT see the "firmware.bin" file and act accordingly. What is it exactly that "sees" the "firmware.bin" and treats it differently than a regular file, anyway? Maybe that's what's corrupted??
Description
Steps to reproduce
Expected behavior
Actual behavior
Additional Information
Configuration.h
or use Pastebin and paste a link in this issue.DESCRIPTION: BTT SKR Mini E3 -v- 2.0 (with BTT TFT35 -v- 3.0 display) will NOT recognize presence of "firmware.bin" and update.
STEPS TO REPRODUCE:
EXPECTED BEHAVIOR: Printer start, dark display, longer than usual boot time, menu comes up and now has BL touch options available, and 'firmware.bin' on SD care renamed to "firmware. cur." None of this happened.
ACTUAL BEHAVIOR: As described above - - machine boots normally in the normal amount of time, completely failing to recognize the presence of a 'firmware.bin' and not introducing BL Touch menu options, and also not renaming "firmware.bin" to "firmware.cur."
firmware-bltouch-for-z-homing.zip Can't really send you my configuration.h since I'm not using one, I'm trying to install pre-configured firmware (included it as a .zip file). PICS / VIDEOS: Not sure what I could send... no error screens, everything is just normal file handling until the machine boots and skips right past updating with the new firmware.