Creality CR-10S Mini/S4/S5/Pro, CR-20, CRX, Ender 3/5/5 Plus Firmware | V2.X (2560) Board
Do you have a Creality machine with the V2.x (2560 CPU) based board and want a stable firmware with the latest features? Also works with the original “V1” boards with the 2560 CPU.
What is a “2560” Board?
These are the boards with the Atmel 2560 CPU on them. These boards came with the bootloader preinstalled and these machines typically have a filament sensor preinstalled on the machine (with the exception of the CR-20 and CRX). The current versions of these boards have a number of V2.X on them and the original ones had no model number on them and were green or black in color.
This firmware is also for our Creality Dual Extrusion Board as well and it’s supported printers.
Printers Supported with the Creality 2560 Board
- CR-10S Mini
- CR-10S S4
- CR-10S S5
- Ender 5 Plus
Dual Extrusion Board Supported Printers
- CR-10 Mini
- CR-10 S4
- CR-10 S5
- CR-10S Mini
- CR-10S S4
- CR-10S S5
- Ender 3/3 Pro
- Ender 5/5 Pro
Board Limitations Note: Due to the design of the Creality boards with TMC drivers Linear Advance will probably not work correctly. The feature is available but use at your own risk.
Touch Screen Models Note: The CRX, CR-10S Pro, and Ender 5 Plus all came with factory touch screens that are not able to be controlled by Marlin. These printers are only compatible with this firmware when they have been upgraded with our LCD conversion kits.
- Ender 5 Plus LCD Kit: https://www.th3dstudio.com/product/ender-5-plus-12864-lcd-upgrade-kit/
- CRX LCD Kit: https://www.th3dstudio.com/product/cr-x-12864-lcd-upgrade-kit/
- CR-10S Pro LCD Kit: https://www.th3dstudio.com/product/cr-10s-pro-lcd-ezabl-upgrade-kit/
Maybe you’re adding our EZABL kit to the machine. This is the download for you. Directions are below.
Supports our EZABL Pro Auto Bed Leveling Kit – sensor mount STL file included in download.
1 – Printer Board Firmware Update
NOTE: These printers update over the USB cable from your PC to the printer. Make sure to have a USB cable ready.
1.a – Download the firmware
1.b – Extract the files to a folder on your computer
1.c – Open the folder labeled “Firmware” in VSCode
1.d – Open the Configuration.h file that is located under the “Marlin” folder on the left side of the VSCode screen
1.e – In the Configuration.h file, uncomment (remove the 2 / in front of #define) the printer model line for your machine in the “CREALITY PRINTERS 2560 CPU BOARD” section and any other options you are going to use in the firmware.
1.f – Click the ✓ at the bottom of VSCode to compile the firmware. The firmware will compile. This may take 1-5 minutes depending on the speed of your computer and internet connection
1.g – If the build succeeds plug in your printer to your computer with the USB cable.
1.h – Now click the arrow (right pointing) to upload to the printer board.
Make sure ALL slicers or other programs that connect to your printer board are CLOSED before trying to upload to your printer.
Please note that on machines with multiple COM ports you may have to select the COM port manually. Please see our VSCode COM port selection article to see how to do that.
1.i – The firmware will upload to the printer board over USB.
DO NOT UNPLUG THE PRINTER OR RESET YOUR COMPUTER.
Interrupting the flashing can “brick” your board and if this happens you will need to reflash the bootloader with a programmer (like an Ardiuno UNO) before you can flash again.
1.j – When the printer boots you will see the TH3D logo on your LCD. Make sure to reset your EEPROM on your printer after flashing any firmware. You can do this from your printer LCD or by sending a M502 followed by M500 with your favorite Gcode sender application.
THIS FIRMWARE AND ALL OTHER FILES IN THE DOWNLOAD ARE PROVIDED FREE OF CHARGE WITH NO WARRANTY OR GUARANTEE FROM TH3D STUDIO LLC. SUPPORT IS NOT INCLUDED JUST BECAUSE YOU DOWNLOADED THE FIRMWARE.
TH3D STUDIO LLC IS NOT LIABLE FOR ANY DAMAGE TO YOUR PRINTER, PERSON, OR ANY OTHER PROPERTY DUE TO USE OF THIS FIRMWARE. IF YOU DO NOT AGREE TO THESE TERMS THEN DO NOT USE THE FIRMWARE.
We do not maintain a full change log for this firmware. However, you can track all changes and modifications to our firmware code on the GitHub repo for Unified 2 Firmware.