-
-
Notifications
You must be signed in to change notification settings - Fork 385
Configuring & Flashing
Compiling your own firmware may seem like a daunting prosses, but there are many online resources and videos that will give you a step by step of exactly what you need to do. Once you get the concept it is really much simpler than it seems, and the customizability will make it completely worth the effort. If however you still don't want to go through the process of compiling yourself, I provide some precompiled bin files of the most common configurations in the precompiled firmware folder.
In the GitHub releases section I have provided a few of the most common configurations that I have already compiled for you in the case you don't want to compile your own. The file names explain what configuration they are for. Default for basically stock settings, Manual Mesh if you want bed leveling without a probe, BL Touch if you have a probe, etc. They also have different variants relating to grid size for leveling, HS for high speed probing, and v4/v427 for board version.
Flashing the LCD is only to change the icons present on the display. In the screen firmware folder of the source code there is everything you need to flash your screen, modify existing icons, or create entirely new icon packs. At the moment, there are three icon packs to choose from labeled Custom, Gotcha, and Original. Thanks to @gotcha for the contribution of his excellent pack. If you just want to flash new icons, you can grab one of the DWIN_SETs from the firmware sets folder and follow the directions detailed in the ReadMe of the screen firmware folder. If you would like to modify or create your own icons, you can grab any of the existing packs from the icon packs folder and use the tools found in the icon tools folder to create your new .ICO file. Information and tools for font customization can be found on the Dwin Font Tools repo by @Quint097
Note: Screen flashing will never be required, custom icons will simply be substituted with existing ones if you have not flashed your screen. It is also required to enable DWIN_CREALITY_LCD_CUSTOM_ICONS
in configuration.h in order to get -new- icons, that is icons that go to new functions like brightness. Without this defined you can still replace your existing icons using an icon pack.
As it has already been very well documented I am not going to go over the whole process of compiling your own firmware, but I will link a popular video on how to compile firmware for the Ender 3 V2. Of course instead of downloading the main marlin firmware you will need to clone my GitHub branch and edit that. Creality ENDER 3 V2 - How To EDIT & UPLOAD New Firmware
Note for those with 4.2.7 boards: Replace MOTHERBOARD BOARD_CREALITY_V4 with MOTHERBOARD BOARD_CREALITY_V427
If you already have a configuration file, these are the setting that need to be added for full functionality
Configuration.h
Configuration_adv.h
While the video linked above does go over how to flash firmware to the Ender 3 V2, I'll leave a quick step by step here as it's pretty simple.
- Put your firmware file (.bin) onto an SD card
- Put the SD card into your printer
- Turn on the printer
- The boot screen make take up to 10 seconds to appear
- Once booted you have successfully flashed your new firmware