BIGTREETECH-SKR-mini-E3
BIGTREETECH-SKR-mini-E3 copied to clipboard
[BUG] SKR mini E3 V2.0 Can't flash firmware
Description
The board does NOT accept any "firmware.bin" and just refuse to boot when one is inserted in the SD card reader
Steps to reproduce
- compile a "firmware.bin" or download one from the official BTT page
- rename it to "firmware.bin" all lowercase
- insert the micr-sd card in to the printer
- turno on the printer
Expected behavior Board should flash the "firmware.bin" and rename it to "firmware.CUR"
Actual behavior The board does NOT boot, does NOT flash the firmware, does NOT rename it to firmware.CUR
Additional Information
I can't access the microsd on the board, it's not seen and if I press "Attach Media" it say "SD Card Init Fail"
Also, the boot time is inconsistent, sometime it's immediate, sometimes it requires minutes
Configuration.h : https://pastebin.com/raw/Z4156QHf Configuration_adv.h : https://pastebin.com/raw/1gg5uYgK
try a different SD card (formatted as FAT32). Also try compiling the Marlin bugfix-2.0.x version.
Same issue. Wont flash from SD just boots straight up.
I also have this issue. Boots up without updating firmware from firmware.bin file on the SD card.
Contact: [email protected] They get you to jump through hoops, trying allsorts of things that you already have done. They now want a video of trying to flash firmware. they will then consider refunding you or resending the motherboard. I live in hope...
yes, I sended them a 10 minutes video of the flashing process to get a new one
I haven't had a chance to test this yet, but I am wondering if the scenario I describe below might be affecting things. The problem that I'm experiencing is that the firmware is not updating when I put an SD card with "firmware.bin" file on it into the board.
I'm working with the BTT SKR mini E3 V2.0 and have plugged in a BLTouch where the 3 wire dupont connector is plugged into the left 3 Z-Probe pins, and the other 2 wires plugged into the Z-Stop pins. Note that I had to alter the wiring in both the DuPont connector and the Z-Stop connector.
Does anyone else have things wired this way and experiencing the same problem?
I am having the same issue. I've tried 4 different micro SD cards, formatted them all. Compile my firmware just fine and copy it to the SD card, re-name it to firmware.bin > plug it into the board > power on...... no flashing takes place. The board boots like normal and i can see the test gcode on the SD card.... so i am able to see the SD card. I am now on my second board and having the same issue... Exactly the same issue. What am i doing wrong????
Instead of copying th bin file onto the sd card , move it. As I was doing the video to send BIQU it flashed and that was the only thing that I changed. This worked for me . Hope it does for you.
Get Outlook for Androidhttps://aka.ms/ghei36
From: stangjr [email protected] Sent: Tuesday, September 22, 2020 11:22:31 PM To: bigtreetech/BIGTREETECH-SKR-mini-E3 [email protected] Cc: Roguetrooper2k1 [email protected]; Comment [email protected] Subject: Re: [bigtreetech/BIGTREETECH-SKR-mini-E3] [BUG] SKR mini E3 V2.0 Can't flash firmware (#337)
I am having the same issue. I've tried 4 different micro SD cards, formatted them all. Compile my firmware just fine and copy it to the SD card, re-name it to firmware.bin > plug it into the board > power on...... no flashing takes place. The board boots like normal and i can see the test gcode on the SD card.... so i am able to see the SD card. I am now on my second board and having the same issue... Exactly the same issue. What am i doing wrong????
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/issues/337#issuecomment-697013524, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQW2TEHUBS2KD2SLP7WXMZLSHEPSPANCNFSM4PER5Q2A.
@Roguetrooper2k1 thanks for the tip but unfortunately it was un-successful. Im really at a loss here. I've reached out to Bigtreetech support and they are useless.
@Roguetrooper2k1 thanks for the tip but unfortunately it was un-successful. Im really at a loss here. I've reached out to Bigtreetech support and they are useless.
I am very interested in your results as I'm, having the same issue. I've had my board for about 3 weeks and it's starting to look like I'll have to replace it already. This problem is only compounded by the fact I also purchased a BL Touch from Biqu and I can't use it because I can't update the firmware. also my part cooling fan connection does not appear to be working either.
I am having the same issue, I am now on my third board. My first board actually did flash but the bl touch wasn't working properly so I tried different firmware and it bricked, my second board didn't flash at all and now I'm on my third board, the same issue, won't flash, just boots up as normal. I am fed up with this and want to start printing again, looking for any kind of help, please
I am having the same issue, I am now on my third board. My first board actually did flash but the bl touch wasn't working properly so I tried different firmware and it bricked, my second board didn't flash at all and now I'm on my third board, the same issue, won't flash, just boots up as normal. I am fed up with this and want to start printing again, looking for any kind of help, please
I've sent an email to there support line today. Just waiting on a word back.
I am having the same issue, I am now on my third board. My first board actually did flash but the bl touch wasn't working properly so I tried different firmware and it bricked, my second board didn't flash at all and now I'm on my third board, the same issue, won't flash, just boots up as normal. I am fed up with this and want to start printing again, looking for any kind of help, please
I've sent an email to there support line today. Just waiting on a word back.
Looking forward to hearing the results, please let me know so I can be stress free
so i'm not the only apple under this tree.... I'm still what id call new to 3d printing and been doing some upgrades and this has just had me stumped for 3 days now. At first i figured i didn't understand marlin and compiling - then thought it was the new TFT35 screen...... but ive sorted out both of those as not the issue nd it seems my brand new board is just acting like it doesn't know it even has a sd slot......
so i'm not the only apple under this tree.... I'm still what id call new to 3d printing and been doing some upgrades and this has just had me stumped for 3 days now. At first i figured i didn't understand marlin and compiling - then thought it was the new TFT35 screen...... but ive sorted out both of those as not the issue nd it seems my brand new board is just acting like it doesn't know it even has a sd slot......
That's The same with me. I am able to print but I can't get any firmware to upload
Mmmm this is actually starting to sound like a quality control issue.
Mmmm this is actually starting to sound like a quality control issue.
Is it fixable? Or is it a hardware problem
I personally don't like resoldering components to a PCB so I'm going to say no. This opinion is theory based on what's been said in this thread. I have not heard from Biqu yet.
I personally don't like resoldering components to a PCB so I'm going to say no. This opinion is theory based on what's been said in this thread. I have not heard from Biqu yet.
Oh, okay, so since it's a hardware problem what do I do, just keep ordering and returning board from Amazon til I get a working one?
I'm not. I'm think about switch to the Creality 32 silent board actually. That's if Biqu doesn't get back to me soon.
I'm not. I'm think about switch to the Creality 32 silent board actually. That's if Biqu doesn't get back to me soon.
Creality has a new board that they are putting in their ender 3 V2 which will also work in the ender 3 pro and that's what I would recommend getting, I'm thinking about getting one myself if I can't figure out this big tree tech problem
I'm not. I'm think about switch to the Creality 32 silent board actually. That's if Biqu doesn't get back to me soon.
Creality has a new board that they are putting in their ender 3 V2 which will also work in the ender 3 pro and that's what I would recommend getting, I'm thinking about getting one myself if I can't figure out this big tree tech problem
Does that version have active thermal Brun away protection? That's actually one of the main reasons I wanted the skr mini.
Doesn't say on their website, but it is the silent main board 4.2.7
Got the Creality board and everything work. 😊
Got the Creality board and everything work. 😊
Yep, I just got my money back for the SKR board and my creality board should be here tomorrow
Did you order your skr directly from Biqu?
On Fri., Oct. 16, 2020, 1:07 p.m. quadmaster55, [email protected] wrote:
Got the Creality board and everything work. 😊
Yep, I just got my money back for the SKR board and my creality board should be here tomorrow
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/issues/337#issuecomment-710343489, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARIFB7ASN77C33RIKBIZ7NLSLCDXPANCNFSM4PER5Q2A .
Not sure what biqu is but I ordered it from Amazon
hi had the same issue ,change the file name into FIRMWARE.BIN (capital letters) ,worked for me...
hi had the same issue ,change the file name into FIRMWARE.BIN (capital letters) ,worked for me...
I tried your solution, and it worked!
Ive Figured it out finally, you have to enable extensions in windows 10. Just look up how to do that and you shouldnt have to rename the file to Firmware.bin, it should already be set to Firmware.bin
i went through that whole process now and it still didnt change the firmware version. and i used straight from marlin.
I have the same problem on two different boards. None of the work arounds here work. I am done with this board. Makes me never want to buy another BTT motherboard again. Do the 1.4s have this problem also?
Hi all, I've been having this issue and have been working on it for more that 10 hours now. I have accidentally solved my problem and decided to post it here in hopes that it works for someone else. I tried everything mentioned here and nothing worked. I am using the E3 V2.0 board and the TFT35 touchscreen display, Got it from amazon as a bundle, Im thinking that some or most of everyone here probably got the same thing. I also added the BL touch so for me it was not working as well. My accidental fix for me was when I removed my display (printer was OFF and felt a little static shock so be careful) In the process of handling it I hit the reset button on the display, so I decided to just hold it down a few seconds while everything was off, then I restarted the printer. I was immediately greeted with BL touch errors which I have not seen before. Hit the OK that popped up on the screen and the printer did an auto level, After this I am now seeing both SD slots, the one on the main board and the one on the display. Hope this helps someone.
so im hoping this finds everyone well. the solution that has worked for me is really simple but also a duh moment. so the problem isn't with he board,nor the firmware. the problem is windows. when you rename the file to firmware.bin it is actually coming out to firmware.bin.bin that's because when you open the folder in windows if you click on the tab view,you will see 3 boxes unchecked hopefully. they will be item check boxes file name extensions and hidden items. you want to have file name extensions checked. if you already did the rename to firmware.bin then you will see what i mentioned. anyways this solved the problem for me completely. anyways i will post this to all the forums so that way everyone knows. mainly because i found the solution by mistake lol.
oh and also it helps to use the original sd card to load the first batch of firmware. but you don't need to add .bin at the end when file name extensions is checked. that's automatic lol. but you will see a 15-20 second delay in the load up screen when it is just blue and then it will flash the logo. that means that it has applied the firmware and should now show up.
so im hoping this finds everyone well. the solution that has worked for me is really simple but also a duh moment. so the problem isn't with he board,nor the firmware. the problem is windows. when you rename the file to firmware.bin it is actually coming out to firmware.bin.bin that's because when you open the folder in windows if you click on the tab view,you will see 3 boxes unchecked hopefully. they will be item check boxes file name extensions and hidden items. you want to have file name extensions checked. if you already did the rename to firmware.bin then you will see what i mentioned. anyways this solved the problem for me completely. anyways i will post this to all the forums so that way everyone knows. mainly because i found the solution by mistake lol.
oh and also it helps to use the original sd card to load the first batch of firmware. but you don't need to add .bin at the end when file name extensions is checked. that's automatic lol. but you will see a 15-20 second delay in the load up screen when it is just blue and then it will flash the logo. that means that it has applied the firmware and should now show up.
so im hoping this finds everyone well. the solution that has worked for me is really simple but also a duh moment. so the problem isn't with he board,nor the firmware. the problem is windows. when you rename the file to firmware.bin it is actually coming out to firmware.bin.bin that's because when you open the folder in windows if you click on the tab view,you will see 3 boxes unchecked hopefully. they will be item check boxes file name extensions and hidden items. you want to have file name extensions checked. if you already did the rename to firmware.bin then you will see what i mentioned. anyways this solved the problem for me completely. anyways i will post this to all the forums so that way everyone knows. mainly because i found the solution by mistake lol.
Yep exactly what I did, took me a while to figure it out to lol
For what its worth, I had the same issues. Tried various sdcards and sizes. Solution was as aricut stated above, but because windows 10 thinks that firmware.bin=FIRMWARE.BIN it defaults back to lower case. I had to rename it and then change it to FIRMWARE.BIN
Would have been so much easier if instructions actually used uppercase.
Just an update from me as well, exact same issue, uppercase solution worked 👍
Rename:
firmware.bin -> firmware1.bin (add any character cause stupid windows equality comparison) -> FIRMWARE.BIN
Just an update from me as well, exact same issue, uppercase solution worked 👍
Rename:
firmware.bin -> firmware1.bin (add any character cause stupid windows equality comparison) -> FIRMWARE.BIN
Tried just that but with no success. The firmware fil is renamed to .CUR after I tried. What does that mean? When I try the flashing, there is a red diode flashing (for a while) on the board. The green diode next to the card reader is lit when the card is inserted. When powered up, the displays says "No printer connected"...
Ender 3 Pro + BTT skr mini E3 V2 + BTT 3.5 TFT V3.0. It flashed one upgrade to Marlin 2.0.9.1, and all further attempts to flash changes to Marlin result in the firmware.bin file being renamed to FIRMWARE.CUR but no the new firmware.bin is not flashed. Running Ubuntu 2.0.4.2 LTS, and using Pliaformio as an IDE. Firmware.bin files created with platformio build and auto build Marlin. I would try re-flashing the bootloader, but the only link I found requires changing the SWD pin definitions. If I could upload a Marlin file to do that, I wouldn't need to re-flash the bootloader to begin with. Suggestions??
Instead of copying th bin file onto the sd card , move it. As I was doing the video to send BIQU it flashed and that was the only thing that I changed. This worked for me . Hope it does for you. Get Outlook for Androidhttps://aka.ms/ghei36 … ________________________________ From: stangjr [email protected] Sent: Tuesday, September 22, 2020 11:22:31 PM To: bigtreetech/BIGTREETECH-SKR-mini-E3 [email protected] Cc: Roguetrooper2k1 [email protected]; Comment [email protected] Subject: Re: [bigtreetech/BIGTREETECH-SKR-mini-E3] [BUG] SKR mini E3 V2.0 Can't flash firmware (#337) I am having the same issue. I've tried 4 different micro SD cards, formatted them all. Compile my firmware just fine and copy it to the SD card, re-name it to firmware.bin > plug it into the board > power on...... no flashing takes place. The board boots like normal and i can see the test gcode on the SD card.... so i am able to see the SD card. I am now on my second board and having the same issue... Exactly the same issue. What am i doing wrong???? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#337 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQW2TEHUBS2KD2SLP7WXMZLSHEPSPANCNFSM4PER5Q2A.
Thx, this really helped was having the issue and this worked
Just throwing my 2 cents in . I had this exact issue today and it seemed to be solved by my formatting the included SD card as FAT and not FAT32. Once I did that I was golden.
Same kinda issue here. Running Manjaro as a desktop OS so I knew it wasn't some kind of Windows specific behavior. Tried all the different capitalization and file extension configurations - nothing was working. Came down to the bottom of this thread and was going to do as @hernan43 did and format the SD card to FAT but Gparted doesn't offer that. I simply formatted the card to (get this) FAT32 from FAT32 and then it flashed no problem.
Did they accidentally format them as FAT31 before the left the factory or something?
I needed to format my SD card as FAT32 with a MS-DOS partition table. It failed when I used a GPT.
For anyone having this issue on Mac OSX. I am running OSX Big Sur, using a 64GB SD Card... was having same issue. Here's what I did:
Reformat SD Card using Disk Utility to MS-DOS FAT 32. Ex-Fat and all other formats failed for me. Once I formatted to DOS-FAT 32, I saved firmware.bin and it worked for me.
I don't fu...k believe it!!
I went to https://github.com/bigtreetech/BIGTREETECH-SKR-E3-Turbo/tree/master/firmware right click the file on Chrome and save link as frimware.bin
It is saving the HTML.
Anyway the printer didn't load anymore anything. It was creating the FIRMWARE.CUR file and I though why the fuck it is resulting in HTML? Funny way to say I am ok or I am not ok.
I don't know why I didn't clone the God damn repo!
I don't fu...k believe it!!
I went to https://github.com/bigtreetech/BIGTREETECH-SKR-E3-Turbo/tree/master/firmware right click the file on Chrome and save link as frimware.bin
It is saving the HTML.
Anyway the printer didn't load anymore anything. It was creating the FIRMWARE.CUR file and I though why the fuck it is resulting in HTML? Funny way to say I am ok or I am not ok.
I don't know why I didn't clone the God damn repo!
Click to file and in new window you will find DOWNLOAD button )) RTFM ;)
I don't fu...k believe it!! I went to https://github.com/bigtreetech/BIGTREETECH-SKR-E3-Turbo/tree/master/firmware right click the file on Chrome and save link as frimware.bin It is saving the HTML. Anyway the printer didn't load anymore anything. It was creating the FIRMWARE.CUR file and I though why the fuck it is resulting in HTML? Funny way to say I am ok or I am not ok. I don't know why I didn't clone the God damn repo!
Click to file and in new window you will find DOWNLOAD button )) RTFM ;)
Sadly I know, it was a stupid moment and I kept using the same file :\ thanks for the reply btw.
I don't fu...k believe it!! I went to https://github.com/bigtreetech/BIGTREETECH-SKR-E3-Turbo/tree/master/firmware right click the file on Chrome and save link as frimware.bin It is saving the HTML. Anyway the printer didn't load anymore anything. It was creating the FIRMWARE.CUR file and I though why the fuck it is resulting in HTML? Funny way to say I am ok or I am not ok. I don't know why I didn't clone the God damn repo!
Click to file and in new window you will find DOWNLOAD button )) RTFM ;)
Sadly I know, it was a stupid moment and I kept using the same file :\ thanks for the reply btw.
NP )) you are welcom
What you need to do is take a real close look with magnifying glass if u have some at both the top plate and in the slot of the sd card bay and make sure u don't have a bent pin thay are cheap card bays and the way thay tend to end up in relation to the enclosure opening a lot of the time a card gets inserted just slightly off kilter and bends a pint it happened to me lucky I wus able to use a soweing needle and bend/push it back in place wile inserting the card and WA LA after it flashed I shut it down and permanently fixed the pin
For those that have the firmware.bin renamed to firmware.cur, but without it looking like things updated issue, one thing that affected me was EEPROM_SETTINGS
. 😄 If you have EEPROM_SETTINGS
enabled, then re-flashing the firmware will not change any settings in the EEPROM. You have to reset to factory defaults to get the update.
I went through a couple of recompile/re-flash steps and finally changed the CUSTOM_MACHINE_NAME
parameter to ensure it got re-flashed. (Then I Googled 😄 )
Make sure to choose the right board version when downloading the pre-compiled firmware file!
I used the pre-compiled firmware and had the same problem with the firmware.bin getting renamed to firmware.cur (indicating the mainboard at least read the file and tried to upgrade) but with the display board not wanting to connect to the printer afterwards. I.e. the same or similar issues to what most people here seem to have. Tried most suggestions above, nothing worked.. After a lot of head scratching and a cup of coffee later I finally realized that I was actually trying to upgrade with the firmware file for the V3.0 board..
I have the TFT35 V3.0 display board (which came bundled with the main board) which I think was what led me to download the firmware file for the V3.0 board without really thinking about it (my board is V2.0, which I did actually know).
Using the new "firmware.bin" (all lower case) and waiting for 10-20 sec after turning the printer on the TFT-board suddenly beeped and the "No printer attached!" message disappeared. Everything worked!
This might not be the solution for everyone, especially not for those compiling the firmware themselves, but perhaps someone as stupid as me got helped by this or at least found some of it useful :)