Forum

 

Notifications
Clear all

ender 3 v2 not accepting firmware

Page 2 / 2

tundrwd
(@tundrwd)
Eminent Member Registered
Joined: 1 year ago
Posts: 42
 
Posted by: @kevin

@enderdragonstone Change filename is to let your printer know the new firmware is different from the current firmware. Otherwise, it will not read. This is a conservative approach.

Then you can doubt the slot or the card. Can the card read other GCODE files properly?

This!  I had the same problem couple days ago.  Had to rename to something like "firmware3.bin".  Make sure card is no larger than 8GB - seems firmware updates get a tad flakey with sizes above that.


ReplyQuote
kevin
(@kevin)
Noble Member Registered
Joined: 1 year ago
Posts: 1045
 

@tundrwd Yes, these are small details that we often overlook.


ReplyQuote
EnderDragonStone
(@enderdragonstone)
Active Member Registered
Joined: 1 year ago
Posts: 5
 

@kevin Yes I'm able to print .GCODE files using that same SD in the same slot.

The slot in the front of the machine is where I'm putting the SD card in.  That is the correct one right? or is there a slot in the motherboard or somewhere else? I know there's a slot in the menu screen, do I need to update the screen first?


ReplyQuote
EnderDragonStone
(@enderdragonstone)
Active Member Registered
Joined: 1 year ago
Posts: 5
 

@tundrwd thanks for the suggestion, 
my SD card is only 4GB

and I tried renaming it to:  firmware.bin      didn't work


ReplyQuote
kevin
(@kevin)
Noble Member Registered
Joined: 1 year ago
Posts: 1045
 

@enderdragonstone  All that's left, it seems a mainboard problem. If you're still under warranty and tell customer service about this and what you did, have them send a new board.


ReplyQuote
llamadash
(@llamadash)
New Member Registered
Joined: 9 months ago
Posts: 2
 

@kevin I seem to be having the same issue when trying to install a new CR Touch. These are the steps I've gone through so wondering which way to turn:

1. Used the 4gb sd card that came with the printer

2. Reformatted the card to ensure it was empty

3. Only copied one *.bin file to it and ensured I renamed it to something like firmware3.bin or firmthree.bin - at least a name I've not used already.

4. Confirmed my motherboard is a v4.2.2 - I had to look in order to plug the CR Touch in.

5. Downloaded Ender-3 V2-Marlin-2.0.1-HW-4.2.2-mainboard-V1.1.2-Compatible with BLTouch and filament detection.zip as I believe this is what I need for my motherboard and the CR Touch. Copied the containing bin file to the SD card.

6. Unplugged the printer and waited 15 seconds or more, inserted the SD Card, plugged in and turned on.

7. At this point the screen turns on and displays a progress bar but I'm still left with Firmware version Ver 1.0.2 and no menu for leveling. The CR touch itself did seem to go through some sort of initialisation.

 

Is there any step I've missed? Before this I was printing really quite well and thought the CR Touch would help improve initial setup troubles but at this point in time it's been money wasted 🙁

 

Many thanks for your time 🙂


ReplyQuote
llamadash
(@llamadash)
New Member Registered
Joined: 9 months ago
Posts: 2
 

I solved my problem in the end by inserting the SD card with the firmware into the printer then using the g-code terminal from OctoPrint I submitted M997 and this triggered the firm update!


ReplyQuote
theconsciousness
(@theconsciousness)
New Member Registered
Joined: 8 months ago
Posts: 1
 
Posted by: @llamadash

I solved my problem in the end by inserting the SD card with the firmware into the printer then using the g-code terminal from OctoPrint I submitted M997 and this triggered the firm update!

Thank you so much! I was pulling my hair out trying to get my Ender to grab the firmware bin that I'd been continuously renaming to no avail.


ReplyQuote
speed
(@speed)
New Member Registered
Joined: 7 months ago
Posts: 2
 

Hi all, thanks for the information on this thread.  Now that you've figured out some solutions, would someone mind putting up a step-by-step for dummies?  My son and I are new to 3D printing, and don't really understand some of the terms used like "g-code terminal" and "M997".  I'm also not clear on which attempts on this thread contributed to the finally successful solution (like renaming, using a small Micro SD card, etc.)

  • we have a standalone E3V2 w/ V4.2.2 mainboard
  • we are trying to add the CR Touch
  • based on the document "CR Touch Firmware Version for 32-bit Motherboard.pdf" on the Creality "Accessory Firmware" site, we have downloaded "Ender-3 V2_Marlin2.0.8_HW_V4.2.2_SW_V2.0.8.4_ALT_Zh_CN_en_20210715.bin"
  • we have saved this on to a freshly-formatted 64GB MicroSD
  • when we insert the card, plug in the printer and switch on, it just boots up as usual and the FW is still V1.0.2
  • we have tried renaming the file to something simple like Ender FW 2.0.8

Does anyone have clear guidance for our next steps?

Thank you! ? 


ReplyQuote
ddb
 ddb
(@ddb)
New Member Registered
Joined: 4 months ago
Posts: 1
 

Hello speed!

What I did when the normal method didn't work was as follows:

put the .bin file on the sd card

create a .gcode file (which is just text) containing only the line "M997" (without the quotes) on the sd card. (Gcode files are what you print with, and contain a list of commands to the printer, usually to move, exude filament, etc, but can be other commands like M997 which is the "update firmware" command.)

put the card in the printer and "print" that .gcode file.  In about 20 seconds it will have installed the firmware and rebooted.


ReplyQuote
lukk555
(@lukk555)
New Member Registered
Joined: 2 months ago
Posts: 1
 

Hi All, if everything in this thread fails try to convert your SD card to MBR disk: 

open diskpart tool in windows, type list disk, then select disk x (where x is the number of your card from the list) then convert mbr. If this passes just create a new partition and a volume with FAT32 file system and 4kb allocation size. 

This finally worked for me when everything else listed here failed. Printing gcode files from this card still worked before, only when attempting the firmware update nothing happened. 


ReplyQuote
Page 2 / 2