This branch is for the Creality CR-6 SE with stock v4.5.2 motherboard and the stock display.
For other configurations for the Creality CR-6 printer (like BigTreeTech SKR board and optional BTT TFT v3.0 display - please check the branches and development section section below.
Please find official releases in the Releases section. Take the release which belongs to the particular touch screen firmware you are going to flash. Please read the release notes carefully - it contains all the instructions you need.
Ensure you take the right assets: the firmware[suffix].bin. You should not download the Source code archive if you are downloading with the purpose of directly flashing your printer.
Support for the BTT SKR board is available.
At least one CF Release 6 user has confirmed that the v4.5.3 firmware configuration also supports the Creality v1.1.03 (ERA) board.
There are several example configurations available for your convenience which can be found in the config directory. Copy the files from the config subdirectory which reflects the needed hardware configuration to the root of the Marlin directory. To build the firmware Visual Studio Code with the Platform.io plugin installed is needed. Please set the Platform.io environment variable default_envs in the file platformio.ini to the string found in the previous copied file platformio-environment.txt.
Examples for the following hardware configurations are currently available:
- Creality stock TFT with:
- Creality v4.5.2 motherboard (CR-6 SE)
- Creality v4.5.3 motherboard (CR-6 SE and CR-6 MAX)
- BigTreeTech SKR CR-6 (CR-6 SE)
- BigTreeTech SKR CR-6 with BigTreeTech TFT v3.0
Legacy branches:
creality-cr6-merge-attempt- initial branch based on Creality v1.0.3.7 firmware source code release and upgraded until the community firmware 3 release. All new releases are released from theextuibranch.
Original source code tracking:
-
cr6-creality-changes- tracks the changes from the Creality source code dump against Marlin upstream. As of now we have the Creality v1.0.3.7 firmware on this branch, based on Marlin pre-2.0. -
cr6-btt-dump- tracks the changes from the Big Tree Tech SKR board firmware source code (which does not have any git history). It appears the for the moment BTT source code is based on the Creality v1.0.3.7 source code release.
This fork of Marlin is meant for:
- Providing up to date and stable Marlin for the CR-6 SE native and BTT SKR CR6 motherboard
- Expanding the features of the limited Creality CR-6 stock touch screen
Once upstream Marlin supports the strain gauge, currently being whipped into shape in this PR @Sebazzz has submitted, the future of this project will probably be:
- Still expanding the features of the touch screen and merge upstream
- Continuously update this fork to the latest Marlin stable versions
- Provide builds for the CR-6 and SKR boards for the less technically inclined
Get in touch with the developers! We have our own Discord server.
The following CR-6 communities exist:
Communities hosted by Creality:
Other communities:
For general Marlin support, please check:
- Marlin Documentation - Official Marlin documentation
- Marlin Discord - Discuss issues with Marlin users and developers
- Facebook Group "Marlin Firmware"
- RepRap.org Marlin Forum
- Facebook Group "Marlin Firmware for 3D Printers"
- Marlin Configuration on YouTube
- Submit bug fixes as pull requests to the current active default branch (
extui) - Follow the coding standards
- Please submit your questions and concerns in the issue tracker
The current core CR-6 Community firmware dev team consists of:
- Sebastiaan Dammann [@Sebazzz] - Netherlands (Donate (Profile) | Website)
- Juan Rodriguez [@Nushio] - Mexico
- Romain [@grobux] - France (Donate)
- Nick Acker [@nickacker] - USA
- And more...
We stand on the shoulders of giants. Don't forget to send your love upstream too!
Marlin and the Creality CR-6 Community Firmware is published under the GPL license because we believe in open development. The GPL comes with both rights and obligations. Whether you use Marlin firmware as the driver for your open or closed-source product, you must keep Marlin open, and you must provide your compatible Marlin source code to end users upon request. The most straightforward way to comply with the Marlin license is to make a fork of Marlin on Github, perform your modifications, and direct users to your modified fork.
While we can't prevent the use of this code in products (3D printers, CNC, etc.) that are closed source or crippled by a patent, we would prefer that you choose another firmware or, better yet, make your own.