Marlin's continued existence would not be possible without them. Huge thanks are due to all the contributors who regularly patch up bugs, help direct traffic, and basically keep Marlin from falling apart. Marlin is constantly improving thanks to a huge number of contributors from all over the world bringing their specialties and talents. Facebook Group "Marlin Firmware for 3D Printers".Marlin Discord - Discuss issues with Marlin users and developers.Marlin Documentation - Official Marlin documentation.To get help with configuration and troubleshooting, please use the following resources: The Issue Queue is reserved for Bug Reports and Feature Requests. If you prefer Docker you can use make tests-all-local-docker or make tests-all-local-docker TEST_TARGET=.You can use make tests-all-local or make tests-single-local TEST_TARGET=. ![]() If you're running the tests on Linux (or on WSL with the code on a Linux volume) the speed is much faster.It's optional: Running all the tests on Windows might take a long time, and they will run anyway on GitHub.Whenever you add new features, be sure to add tests to buildroot/tests and then run your tests locally, if possible.Please submit Feature Requests and Bug Reports to the Issue Queue.Follow the Coding Standards to gain points with the maintainers.This branch is for fixing bugs and integrating any new features for the duration of the Marlin 2.0.x life-cycle.Proposed patches should be submitted as a Pull Request against the ( bugfix-2.1.x) branch. Malyan M200, GTM32 Pro, MKS Robin, BTT SKR MiniĪRMED, Rumba32, SKR Pro, Lerdge, FYSETC S6, Artillery RubyīigTreeTech SKR V3.0, SKR EZ V3.0, SKR SE BX V2.0/V3.0 Smoothieboard, Azteeg X5 mini, TH3D EZBoard ![]() Retaining AVR compatibility and a single code-base is important to us, because we want to make sure that features and patches get as much testing and attention as possible, and that all platforms always benefit from the latest improvements. Marlin 2.0 introduced a layer of abstraction to allow all the existing high-level code to be built for 32-bit platforms while still retaining full 8-bit AVR compatibility. We've posted detailed instructions on Building Marlin with Arduino and Building Marlin with PlatformIO for ReArm (which applies well to other 32-bit boards). To build Marlin 2.1 you'll need Arduino IDE 1.8.8 or newer or PlatformIO. Visit the MarlinFirmware/Configurations repository to find the right configuration for your hardware. Marlin users have contributed dozens of tested example configurations to get you started. Your vendor should have already provided source code with configurations for the installed firmware, but if you ever decide to upgrade you'll need updated configuration files. Example Configurationsīefore building Marlin you'll need to configure it for your specific hardware. Periodically this branch will form the basis for the next minor 2.1.x release.ĭownload earlier versions of Marlin on the Releases page. ![]() ![]() This branch is for patches to the latest 2.1.x release version. Read about Marlin's decision to use a "Hardware Abstraction Layer" below. Marlin 2.1 takes this popular RepRap firmware to the next level by adding support for much faster 32-bit and ARM-based boards while improving support for 8-bit AVR boards. Volunteers are standing by! Marlin 2.1 Bugfix Branch Please test this firmware and let us know if it misbehaves in any way. Additional documentation can be found at the Marlin Home Page.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |