search

bigtreetech / BIGTREETECH-SKR-mini-E3

BIGTREETECH SKR-mini-E3 motherboard is a ultra-quiet, low-power, high-quality 3D printing machine control board. It is launched by the 3D printing team of Shenzhen BIGTREE technology co., LTD. This board is specially tailored for Ender 3 printer, perfectly replacing the original Ender3 printer motherboard.
1.99k stars 1.98k forks source link

Blank blue LCD screen on stock LCD #224

Open lassespilling opened 4 years ago

lassespilling commented 4 years ago

I have two boards that were working but now show blue blank screen on stock Ender 3 LCD screen. Board one: Went blank after flashing new firmware. (using firmware.bin from Github), this board seems to flash and renames to firmware.cur succesfully.

Board two: Went blank after just turning power on and off without even flashing or doing anything. Tried to flash after LCD went blank (using firmware.bin from Github), but this board won't rename to firmware.cur so i do not think it is flashing at all.

Steps to reproduce

  1. Downloaded Firmware.bin from BIGTREETECH-SKR-mini-E3 github
  2. Put firmware.bin on card
  3. put card into skr mini e3
  4. turn off and on power

Expected behavior Board powers on and LCD should work

Actual behavior Board powers on, LCD shows blank blue.

I now have two boards i cannot use.

ylexot commented 4 years ago

I also have this problem.

seth995 commented 4 years ago

Check the board. This may not be related to the firmware but rather a hardware failure. I had a similar issue with using stock firmware, but found components in the cluster around Y1( between the reset button and U2) to be burned.

BTT claims I let voltage leak between a thermistor and the hot end or bed heating circuits. I did no such thing.

jhstatewide commented 4 years ago

Same problem here. SKR Mini E3 -- used for a few months with no problems. Was preheating today and suddenly LCD froze. After power cycle stock LCD is blank. Board will not accept new firmware. Power light is on -- no other responses. I checked connections and did not discover anything odd.

I believe the board is dead.

avsmithy commented 4 years ago

I have identical issue to @jhstatewide, except this happened immediately on first print.

Returning to seller.

Shizzy713 commented 4 years ago

I have the same problem as the OP. I installed the board yesterday and flashed the firmware.bin from github on my Ender 3 Pro today and my board is now bricked? FML

sultanjawad commented 4 years ago

So what exactly are we supposed to do with a bricked board?

nmg196 commented 4 years ago

Mine did this exactly this but is was not bricked - it simply had no display (all pixels black). I just reflashed the original firmware from the SD card which came with the BTT board and it came back to life. Let me know if you need the file, but you should already have it on the 128MB micro SD.

nmg196 commented 4 years ago

Same problem here. SKR Mini E3 -- used for a few months with no problems. Was preheating today and suddenly LCD froze. After power cycle stock LCD is blank. Board will not accept new firmware. Power light is on -- no other responses. I checked connections and did not discover anything odd.

I believe the board is dead.

That is not the same problem at all. This thread is a problem about no display after flashing the new firmware, not a failure of the board when you've not touched the firmware.

lassespilling commented 4 years ago

Same problem here. SKR Mini E3 -- used for a few months with no problems. Was preheating today and suddenly LCD froze. After power cycle stock LCD is blank. Board will not accept new firmware. Power light is on -- no other responses. I checked connections and did not discover anything odd. I believe the board is dead.

That is not the same problem at all. This thread is a problem about no display after flashing the new firmware, not a failure of the board when you've not touched the firmware.

If you read my post, this happend on my second board without touching the firmware.

jhstatewide commented 4 years ago

So what exactly are we supposed to do with a bricked board?

Toss it in the trash and spend another $40.

nmg196 commented 4 years ago

Is it definitley bricked? Mine booted up fine once I'd reflashed the original firmware.

avsmithy commented 4 years ago

Mine was most definitely either a) bricked or b) broken. It also killed two SD cards, so I pretty sure it's the latter.

jhstatewide commented 4 years ago

Is it definitley bricked? Mine booted up fine once I'd reflashed the original firmware.

Yes, it will not accept any firmware. Confirmed by keeping my SD card with firmware on it, buying another SKR board and using same card to reflash. The original board is definitely bricked.

arnoldcp commented 4 years ago

I am having exactly the same problem, brand new board, straight out of the box hooked it up and upon boot, simply a blue screen.

Attempted to update the firmware thinking it maybe required an update and upon boot the activity light does flash but still no LCD. Strange.

greenbox6 commented 4 years ago

I'm having the same issue. when I first installed the board everything seemed to be in order. I was able to navigate through menus but when I tried to print from the include gcode file from the sd card the printer just got stayed at 200c temp. so I turned it off, downloaded the v1.2 firmware just like you did and when I turned it on the screen went blank. I've tried multiple different versions firmware.bin compiled from different settings and still nothing. I hate this, when it first booted I should of asked online first on what to do instead of jumping right into the firmware. I waited three months to get this board from aliexpress and I feel crushed; I just wanted quieter prints.

avsmithy commented 4 years ago

@greenbox6 Have you tried the directly complied firmware from BTT?

https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/tree/master/firmware

That did not work for me, but might be worth a try.

I got a replacement from vendor and that is working fine (firmware updated without any issues). It is significantly quieter - now the only noise is from the fans. It was worth the hassle for me.

arnoldcp commented 4 years ago

So I did order a second board from Amazon and I decided to bench test it. I plugged in each connection one at a time with a power cycle between each while it was not in the Ender case. I was able to get it to work and made all the motors cycle and bed and hot end heat.

As soon as I put it in the case I ended up getting a blue screen. I took it out tried to go back to a known state. I went all the way back to just power. Still a blue screen. I walked away for a little and when I came back I decided to remove the SD card and look at the contents. The moment I turned the printer on with no SD card it booted and showed the control screen.

I cannot quite figure out what happened but the original board still does not work. This new board I was able to put in another SD card and got it to work and it is printing.

I have not updated the firmware yet I wanted to have a baseline to get it working. Only conclusion I can come to is that something has shorted when the board was put into the case and corrupted the SD card. I vinyl taped the entire surface under the board and filed the SD card slot open a little more.

TLDR: take the SD card out and see if the board will boot.

avsmithy commented 4 years ago

I unmounted the board from the printer and connected only the essential cables, but didn't have any luck. With or without SD card made no difference either.

federico77 commented 4 years ago

I have a firmware I compiled that is based on Marlin 2.0.x. It ran fine with the board for a few months. Yesterday night I turned the printer off after a quick session but as soon as I turned it back on today I experienced the symptoms described in this thread: printer apparently on, blank screen, no serial connection available (for Octoprint and such).

I shuffled a few firmware versions and SD cards but the printer doesn't even start using the new firmware (.bin->.cur). Should I simply ditch the board for a new one?

greenbox6 commented 4 years ago

ok update here: after taking out the board I examined the sd card slot and turns out one of the pins has been bent back. so now I have to try and bent it back to normal from a tiny enclosure. I've been trying to use a pin but it's frustratingly hard. I wish I could just use the usb slot instead.

ErickFourie commented 4 years ago

Day 2 that my board is in and boom blank screen. Doesn't want change the .bin to a .CUR and absolutely no LED's working on the board. However, heat shrink fan goes on and the electronics fan goes on.

lassespilling commented 4 years ago

Check the board. This may not be related to the firmware but rather a hardware failure. I had a similar issue with using stock firmware, but found components in the cluster around Y1( between the reset button and U2) to be burned.

BTT claims I let voltage leak between a thermistor and the hot end or bed heating circuits. I did no such thing.

No visible hardware damage, already sent images to confirm with BTT

lassespilling commented 4 years ago

Mine did this exactly this but is was not bricked - it simply had no display (all pixels black). I just reflashed the original firmware from the SD card which came with the BTT board and it came back to life. Let me know if you need the file, but you should already have it on the 128MB micro SD.

Yeah please share the file, and I will test myself.

ErickFourie commented 4 years ago

I have tried everything now on the board and there's absolutely no body on the inside. Plugged the board in and even measured a few points and there is definitely components toasted.

rvegele commented 4 years ago

Used my board since Dec 2019. Today after a print the screen just froze. After a power-cycle of the printer the screen is blue-blank.

rvegele commented 4 years ago

Tried replacing the skr mini board with my original ender3 board. And it worked just fine, so not a screen or cable issue I guess. Something's up on the skr board side :/ Any ways to debug this?

zandervix commented 4 years ago

Replaced Creality 1.1.3 board with the SKR (and added a BLTouch). Worked beautifully for about 4 days (printing round-the-clock). Then, going into the next print, the home command ran the nozzle straight into the bed. Turn off and back on, and the screen is on but no boot-up. Tried re-flashing (multiple firmwares) with no luck.

Replaced the board, and it seemed to be DOA (I also tried replacing the screen, ribbon cable, disconnecting the BL, firmwares, new PSU, voltage checks, etc...). Sent that board back and bought another from a different seller. While waiting, put the original 1.1.3 board in, and it worked.

New board (3rd SKR) came today. There is nothing I can do to get this to work.

Giving up and going to try the Creality 1.1.5 silent board. Really wanted this to work, but after 3 boards and weeks of downtime, I'm done.

winstonf commented 4 years ago

I have a Bricked board too. Mine worked well for 3 odd months. But i know the reason it stopped. While trying to clean up the hotend from a filament leak, I accidentally shorted some wires I guess. My mistake :-) . I realized that the STM32 was getting hot just with USB power. I managed to replace the STM32 mcu and I am able to Flash Marlin using a STLINK programmer. But the LCD still does not come up. Just by looking I don't see damaged components. Any Clues as to what more I could check will be helpful.

DarthAlaan commented 4 years ago

I encountered this same problem on both my Ender 3s in the past week after months of no issues with the v1.2. In both cases I was simply preheating and swapping filament and when I looked back I see the screen is froze. I try a power cycle and the screen goes blank. Then it wont accept a flash of the original firmware or a new firmware from sd card as the .bin is never renamed to .cur. Anyone find a good fix yet? Is everyone just chucking these boards and ordering new? If so what, the new Mini E3 V2?

Hunner63 commented 4 years ago

I upgraded to the v2 board and everything appeared to work fine. I decided to upgrade the firmware and now am bricked with a blue screen. I got the firmware from GitHub pre-compiled. I will look around the web and maybe even try compiling from source myself but will send the board back if I can't get it to work.

kozip commented 4 years ago

I just installed a new SKR mini E3 V2 into my ender 3 pro. only blank screen. I put firmware.bin from BTT git on the sd card. On power up you can see the red LED flashing, still just blue screen. when examining the sd card firmware.bin is gone and FIRMWARE.CUR is there. I've tried both bltouch and stock firmware from BTT GIT with no luck....Also I switched back to the creality board and everything works as normal

denisao1998 commented 4 years ago

Hello. I have the same problem: the printer worked with original microSD (original firmware.bin). I put the latest 2.0 firmware.bin and the printer is stucked on blue screen. Can anyone share the original firmware.bin. Thank you

LearnIIBurn commented 4 years ago

Exact same issue. On my second v2.0 board and right as I power it on its a blank screen (all pixels black) and will not flash firmware of any SD card I try. Bought board brand new off Amazon and it did not include a 128MB SD card anywhere in the package which is odd. But none the less this is a very big problem and I'm about to give Bigtreetech the permanent 86 from all my printers.

Hunner63 commented 4 years ago

I was unable to get beyond the blank blue screen after upgrading the firmware. The board appeared to work fine before the upgrade. I eventually re-installed the original 8-bit board and put the new board to the side until this problem gets sorted out

On Fri, Sep 4, 2020 at 6:31 AM Tyler Piderit notifications@github.com wrote:

Exact same issue. On my second v2.0 board and right as I power it on its a blank screen (all pixels black) and will not flash firmware of any SD card I try. Bought board brand new off Amazon and it did not include a 128MB SD card anywhere in the package which is odd. But none the less this is a very big problem and I'm about to give Bigtreetech the permanent 86 from all my printers.

— 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/224#issuecomment-687088267, or unsubscribe https://github.com/notifications/unsubscribe-auth/APPOOCLUZCCYJFGQEFRJCN3SEDFZXANCNFSM4ML5QSNQ .

denisao1998 commented 4 years ago

Hello. I found 2 solutions to bring to life the SKR mini S3 v2 after firmware upgrade (blank blue screen problem):

  1. i downloaded the latest marlin open source project, i modified it for SKR mini S3 v2 (there are guides about this), i compiled it and i used the resulting firmware.bin
  2. i asked bigtreetech support to send me the original microSD firmware.bin

Both solutions are succesufully. In first solution i enabled 3D Touch sensor and it is working.

DTSParsley commented 4 years ago

I have the same problem with my ender 3 pro skr v2.0 and blue screen. I created a firmware for the ender 3 Without pro. When creating the firmware for the ender 3 pro I get errors when compiling. But I managed to get the ender 3 pro to work with the firmware for ender 3 without pro. Has one of the original firmware that was included with the SD card? I'm sorry for my english. Google translator firmware ender3.zip

tthamel commented 4 years ago

Can we stop saying the boards are bricked?

i had the same thing happen, tried to flash the BLTouch version of the firmware. bam, blue screen.

went back and got the original BTT firmware it shipped with and it booted up no problem.. ergo the issue is the BT firmware

my point is, has everyone that is claiming they have a bricked board tried re flashing the original firmware?

LearnIIBurn commented 4 years ago

@tthamel I don't know if everyone is having the same symptoms resulting in just a blue screen with nothing happening, but I know for me that firmware is not flashable at all from the SD card slot. Doesn't matter if it's official from their github, official from Marlin's github, compiled from bugfix branch or the original firmware that came with the board on the 128MB SD card; it just doesn't flash anything. I'd say that calling it a bricked board is quite alright.

kozip commented 4 years ago

Can we stop saying the boards are bricked?

i had the same thing happen, tried to flash the BLTouch version of the firmware. bam, blue screen.

went back and got the original BTT firmware it shipped with and it booted up no problem.. ergo the issue is the BT firmware

my point is, has everyone that is claiming they have a bricked board tried re flashing the original firmware?

I contacted support and theyr sending a new board. I'm not sure why people aren't first contacting BTT through their support email.

SonnyJim commented 4 years ago

Just had this happen to me. Was printing something, went to change the filament using the menu option, when I inserted the new filament and pressed OK it went back to the main status screen, but it had frozen. Dial wouldn't do anything, no beeps. So I power cycled the printer. Now it just sits on a blue screen and tried various different firmwares, nothing loads. No firmware.cur, no lights on the mainboard apart from a single red LED. No damage to the board as far as I can see, it just decided to stop working.

getz97 commented 4 years ago

Mine did this exactly this but is was not bricked - it simply had no display (all pixels black). I just reflashed the original firmware from the SD card which came with the BTT board and it came back to life. Let me know if you need the file, but you should already have it on the 128MB micro SD.

pleace, send me original .bin file.

kabone commented 4 years ago

Same. Ive been printing good for months. Then i turned off and returned on the printer and it just shows black pixels. If i remove tft pins and move to exp1 then it shows pixels. Im at a loss. I just ordered another...

Hunner63 commented 4 years ago

Me too, please. Thanks!

On Fri, Sep 18, 2020 at 4:27 PM getz97 notifications@github.com wrote:

Mine did this exactly this but is was not bricked - it simply had no display (all pixels black). I just reflashed the original firmware from the SD card which came with the BTT board and it came back to life. Let me know if you need the file, but you should already have it on the 128MB micro SD.

pleace, send me original .bin file.

— 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/224#issuecomment-695094121, or unsubscribe https://github.com/notifications/unsubscribe-auth/APPOOCJBL5NLJOGKAIUQZALSGPGCTANCNFSM4ML5QSNQ .

blhamon commented 4 years ago

Ok, I just had this problem, tried tried to flash the firmware, specifically the firmware_bltouch.bin. turned the printer off, inserted SD card, firmware.bin renamed to firmware.cur (finally pulled the card out after waiting 10 minutes). Blue screen, completely blank.

Got a new SD card, tried again, no good, still blank. This time, didn't rename the file.

copied the firmware.bin that came on the SD card. Inserted, nothing. Didn't rename the file. when I looked closer, I noticed that my file was named, FIRMWARE.bin. All caps name, lowercase extension. Made extension all caps, inserted. Flashed back to original firmware that came with the board.

So, that solved my restore problem. making sure the file was FIRMWARE.BIN.

Tried the process again, on the new SD card. Same thing, blank screen. Then I restored back to the original.

Then I noticed that the firmware.bin and firmware_bltouch.bin that I downloaded from github, via right-click, save as was only 82KB. While the firmware that came with the board was 209KB. This didn't seem right, so I went back to github and instead of downloading via right click, I clicked on the firmware_blthouch.bin. This loaded a page that said the file ws 226KB, with a download button. Clicked download. Verified that the file was indeed 226KB when downloaded. Renamed it to FIRMWARE.BIN, inserted into SD Slot, turned on printer. 15 seconds later, the screen loads and says I'm on the newer version of Marlin (2.0.6, I think).

So, I am a bit of a dumbass, but in case it might help others, make sure your downloaded file is 200+KB in size, and not 82KB. And renaming to all caps fixed my restore, so I didn't even try the new firmware.bin file lowercase, I just made it all uppercase.

blhamon commented 4 years ago

Mine did this exactly this but is was not bricked - it simply had no display (all pixels black). I just reflashed the original firmware from the SD card which came with the BTT board and it came back to life. Let me know if you need the file, but you should already have it on the 128MB micro SD.

pleace, send me original .bin file.

Here's the zipped original FIRMWARE.BIN from my original card.

FIRMWARE.zip

getz97 commented 4 years ago

Thank you, but I have no success ;( , still blue screen.

getz97 commented 4 years ago

i conect my old screen from ender 3 and it boot, it seems the ""TFT 35 E3 V3.0"" is a problem?!? How to reset this display? i try with ""RESET"" button on it-no result.

getz97 commented 4 years ago

I find solution ;)

  1. install some old firmware for TFT35 from bigtreetech github.
  2. create a blank file named reset.txt and place in root folder of the sd card. put SD card to TFT sd slot.
  3. power on, it start screen calibration.. some red dot have to touch...
  4. calibration fail to me, i remove sd card and screen boot up Good Luck to everyone ;)
kabone commented 4 years ago

I find solution ;)

  1. install some old firmware for TFT35 from bigtreetech github.
  2. create a blank file named reset.txt and place in root folder of the sd card. put SD card to TFT sd slot.
  3. power on, it start screen calibration.. some red dot have to touch...
  4. calibration fail to me, i remove sd card and screen boot up Good Luck to everyone ;)

Ill have to try this. I did very close to this before and it did not work. But i was having issues with the firmware update and missing bmp files. So now that thats fixed it may work. Will report back later tonight.

getz97 commented 4 years ago

last firmware update show this ""missing bmp files"", that why i use some old file, and it work.