Blank blue LCD screen on stock LCD #224
Comments
|
I also have this problem. |
|
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. |
|
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. |
|
I have identical issue to @jhstatewide, except this happened immediately on first print. Returning to seller. |
|
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 |
|
So what exactly are we supposed to do with a bricked board? |
|
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. |
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. |
Toss it in the trash and spend another $40. |
|
Is it definitley bricked? Mine booted up fine once I'd reflashed the original firmware. |
|
Mine was most definitely either a) bricked or b) broken. It also killed two SD cards, so I pretty sure it's the latter. |
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. |
|
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. |
|
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. |
|
@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. |
|
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. |
|
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. |
|
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? |
|
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. |
|
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. |
No visible hardware damage, already sent images to confirm with BTT |
Yeah please share the file, and I will test myself. |
|
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. |
|
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. |
|
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? |
|
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. |
|
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. |
|
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? |
|
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. |
pleace, send me original .bin file. |
|
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... |
|
Me too, please. Thanks!
…On Fri, Sep 18, 2020 at 4:27 PM getz97 ***@***.***> 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
<#224 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APPOOCJBL5NLJOGKAIUQZALSGPGCTANCNFSM4ML5QSNQ>
.
|
|
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. |
Here's the zipped original FIRMWARE.BIN from my original card. |
|
Thank you, but I have no success ;( , still blue screen. |
|
i conect my old screen from ender 3 and it boot, it seems the ""TFT 35 E3 V3.0"" is a problem?!? |
|
I find solution ;)
|
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. |
|
last firmware update show this ""missing bmp files"", that why i use some old file, and it work. |
Can you share the old file please. |
Thank you so much, blhamon!!!! Your are no dumpass but a genius, this was exactly my problem too, and you showed me the solution. |
|
I'm also having this issue. I have nothing connected to the board except power and LCD. When I upload the firmware.bin (confirmed to be 220kb) to the SD and boot the board up, the status LED flickers for a few seconds indicating that it's flashing, and then goes off. the LCD remains blank. My FIRMWARE.bin does get changed to FIRMWARE.cur, so I know that it's flashing, but the LCD remains blank and both octopi/pc continue to not see the board whatsoever, as though it's not plugged in at all. It was working fine for several months, I didn't change anything. I powered up the printer after not using it for a few months and this is the issue I'm having. |
You are my hero! I was doing the exact same thing with downloading the bin files with right click save as from Github and getting ~90KB files and thought I had bricked my SKR mini E3 V2.0 since the screen was stuck on the blank screen no matter what I did and I had wiped the original SD card so I didn't have the old firmware to fall back on. Then I saw this and downloaded from Github by clicking the file and using all caps filename and it worked like a charm with the 2.0.7.2 version. |
|
I've got the exact same problem right now. Tried everything mentioned in here, but nothing worked for me unfortunately. Are there any new insights? Thanks! |
|
What I did was contacted BTT support, who made me run through quite a few
troubleshooting steps. Once it was clear the board was dead they sent me a
new one. The board that died was about 7 months old iirc.
…On Tue, 17 Nov 2020, 03:58 Gertsch, ***@***.***> wrote:
I've got the exact same problem right now.
Printed flawlessly for 6 months and today tried to calibrate again - just
for good measure.
After some initial test octo print lost the connection and the lcd turned
solid blue.
Tried everything mentioned in here, but nothing worked for me
unfortunately.
Are there any new insights?
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#224 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA6HTFFIWMSMHHNBDGKYZ3SQFK3RANCNFSM4ML5QSNQ>
.
|
|
As the BTT support didn't get back to me I purchased a SKR mini E3 V2.0 in the meantime. Worked fine from the beginning and did all the calibration. Did some printing and then again the same issue like with the 1.3 board. I'm a little stuck right now. Any help is greatly appreciated :) |
|
I have the solution to this problem from reading between the lines on this page. The key is the file size. If you go to the firmware.bin on the github page and right-click, save, you save a file of around 95K, this is simply the HTML of the next page, hence why it does not work as this is not firmware !! To correctly get the firmware file, you must click on firmware.bin, which takes you to the download page, then click on "View raw file" and it will save the firmware.bin to your machine, this file will be around 224K. You can also check the files by opening them in notepad. The firmware file will appear as a binary file (unreadable), whereas the 95K one will appear as simple HTML. You will see a line in the start of the file. Just make sure you don't save the file if you open it in notepad as it would corrupt it. You can also check the card is programming by looking at the two LED's. The status LED will flash when its programming the firmware. Correctly downloading and programming resulted in a working machine again. |
|
I found the cause of my problem at least, and have heard form others with the same experience. So if anyone has the same issue with the board as I had (blank screen, no serial connection/octoprint, can't read MC with STLink), it quite possibly came from an ESD and bricked the MCU/electronics.
|
|
The other thing to watch out for is manually moving the table too fast. When you move the table, you turn the motors into generators (dynomo's) and the resulting voltage (reverse EMF) can be far too large for the logic board and therefore permanently damage it. It would be good if SKR had put some clamping networks on the board to protect against this obvious problem, particularly given the need to manually move the bed to perform bed levelling and the risk of the bed moving quickly when turning over the printer to change the logic board. Don't forget that this only has to happen once to spoil your day, so please be careful !!. |
|
Just had this happen after 3 weeks of excellent printing. The 8 bit board worked fine before the upgrade. I have the original screen. Have tried uploading the original BTT firmware, no luck. Thank you for all the posts, have ordered a new board from Amazon, will wait for any results from BTT and post. |
|
What you said here makes sense. I was changing my filament, usually I don't bother with the 'change filament' option in Marlin, I just disable steppers, heat the hotend, hold the extruder clip open and pull the filament out myself. This time I used the menu option to change filament. I did the same procedure, waited for the hotend to heat, pinched the extruder clip and began to pull the filament out. As I did, the extruder stepper motor began to assist. As the filament was coming out of the boden tube I noticed my BTT TFT 3.5 V3 flashed, then a second or so later, went off completely. From there on, it would not power up. I think as the filament cleared the hotend and became easier to withdraw my assistance has overloaded the board. I switched out the screen for the original, it just turns on, glows blue but is blank. I've tried placing a firmware.bin on an SD card, the board doesn't appear to read the card as the file is not renamed firmware.cur.
|
|
Hi everyone, I'll just leave this here, to see if it might help anyone. I just changed this part in "Marlin\src\pins\stm32f1\pins_BTT_SKR_MINI_E3_common.h" #if HAS_WIRED_LCD
#if ENABLED(CR10_STOCKDISPLAY)
#define BEEPER_PIN PB5
#define BTN_ENC EXP1_9to #if HAS_WIRED_LCD
#if ENABLED(CR10_STOCKDISPLAY)
#define BEEPER_PIN -1 // PB5
#define BTN_ENC EXP1_9You'll lose the annoying beeps but you get a working stock display in return. Credit for the hint in the right direction goes to this reddit post - seems like Klipper has the same issue with this board: https://www.reddit.com/r/klippers/comments/msgi7z/ender_3_pro_display_problems_on_skr_mini_e3_v20/ Let me know if this worked for you. |
I am experiencing this issue, and unfortunately, this did not resolve it. |
This is what worked for me. Click on "view raw". Make sure you rename the file to "FIRMWARE". I tried to name it "firmware.bin", that is what gave me the blue screen. I also tried "firmware" and it didnt work. It must be all caps "FIRMWARE" with no ".bin". I hope this helps someone. I know, I gave up even trying for a few weeks. |
|
So far I have tried all the methods listed above, same blue LCD... is there any other method to fixing this issue? |
and others
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
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.
The text was updated successfully, but these errors were encountered: