Details about how to use the firmware are located in our help center here:
- Creality CR-10/CR-10S Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
- Creality CR-10/CR-10S Mini Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
- Creality CR-10/CR-10S S4 Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
- Creality CR-10/CR-10S S5 Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
- Creality Ender 3 Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
- Creality Ender 3 Pro Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
- Creality Ender 3 MAX Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
- Creality Ender 5 Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
- Creality Ender 5 Pro Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
- Creality Ender 5 Plus Firmware – SKR E3 Mini V1/V1.2/V2 Board – TH3D Studio Help Center
CPUs Supported
- STM32F103RCT6
- STM32F103RET6
This is our Unified 2 Firmware for the BigTreeTech SKR E3 Mini V1/V1.2/V2.0 boards. Included is the full source code for compiling on your computer with Visual Studio Code. This firmware is tested by us on these actual boards and works. Your purchase helps fund the development of the firmware for this board and others.
Download Terms & Information
How long will I get updates for?
You will get download access for 6 months from the date of purchase.
How long will it take to get the firmware?
The firmware will be granted instantly once your payment clears. This is usually instantly unless your payment is held or fails to process.
Is Technical Support included?
There is NO technical support included with the purchase of this firmware. Technical support can be purchased separately by contacting our support team here: Contact Us.Â
What license is the firmware release under?
This firmware is released under the GPL V3 License.
Is the full source code included?
Yes. The download contains the FULL source code to build the firmware with Visual Studio Code. See the links above for your particular printer on how to setup Visual Studio Code and how to use the firmware.
What is the refund policy on digital downloads?
We do not offer refunds on digital downloads.
Question
bauerdr –
Before I purchase the firmware for this board I just wanted to verify it will work for a 2017 model CR10? I have already installed the mini E3 V2 board. Thanks.
(0) (0) Watch Unwatch
Tim Hoogland (verified owner) –
Yes, it will. The year doesn’t matter much, as long as you have everything connected up correctly to the board.
(1) (0)
Question
bauerdr –
Will this firmware work with TFT35 E3 V3.0.1 Touch Screen Display? I have also installed that with the mini E3 V2 board in my CR10 (2017 model). Thanks.
(0) (0) Watch Unwatch
Tim Hoogland (verified owner) –
It should be as we have the 2nd serial port enabled in the firmware, which is what it needs. The baud rate is set to 115200 by default for the USB and the TFT Serial.
(1) (0)
Question
bauerdr –
With the mini e3 v2 board on a cr10, what ABL is the best route to take ?
(0) (0) Watch Unwatch
Tim Hoogland (verified owner) –
We may be biased but we think our EZABL is a lot better than a probe like a BLTouch. No moving parts and tech support is included if you need help. It’s also easier to connect up to your board as well. The firmware supports both the EZABL and BLTouch but you wont get any tech support on the BLTouch, just on our EZABL.
(1) (0)
Question
Fr3chdaxx –
Kann ich die FW auch beim Ender 2 Pro mit einem SKR E3 Mini 2.0 verwenden ??
(0) (0) Watch Unwatch
Tim Hoogland (verified owner) –
The Ender 2 Pro is only supported on the V3 version of this board along with our EZBoards and the Creality V4.2.7.
(0) (0)
Question
arg.coder –
Good morning, can the logic of the Endstops be inverted? In particular the Z Axis. Thank you very much in advance.
(0) (0) Watch Unwatch
Tim Hoogland (verified owner) –
Yes, you can make any changes to the code you wish. All the source code is provided. The endstop logic for standard endstops is located in the configuration.h file and if you are using an ABL sensor those will be set in the configuration_backend.h file.
(0) (0)