You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
teemuatlut f3e562e46e HAL for 32-bit Teensy (3.5, 3.6) architecture 7 years ago
.github Give a more detailed issue template 8 years ago
Marlin HAL for 32-bit Teensy (3.5, 3.6) architecture 7 years ago
buildroot HAL for 32-bit Teensy (3.5, 3.6) architecture 7 years ago
.gitattributes Add hidden option to output Bilinear grids in JSON 8 years ago
.gitignore Implement HAL and apply macros across code-base 7 years ago
.travis.yml HAL for 32-bit Teensy (3.5, 3.6) architecture 7 years ago
LICENSE Update LICENSE 9 years ago
README.md Marlin bugfix-2.0.x Version/README 7 years ago
platformio.ini HAL for 32-bit Teensy (3.5, 3.6) architecture 7 years ago

README.md

Marlin 3D Printer Firmware

Build Status Coverity Scan Build Status

Additional documentation can be found at the Marlin Home Page. Please test this firmware and let us know if it misbehaves in any way. Volunteers are standing by!

Marlin 2.0 Bugfix Branch

Not for production use. Use with caution!

This branch is used to accumulate patches to the latest 2.0.x release version. Periodically this branch will form the basis for the next minor 2.0.x release.

Download earlier versions of Marlin on the Releases page.

Recent Changes

  • Add a Hardware Abstraction Layer (HAL) supporting current AVR platforms
  • Planning a HAL for Re:Arm
  • Planning a HAL for STM32

Submitting Patches

Proposed patches should be submitted as a Pull Request against this branch (bugfix-2.0.x).

  • This branch is for fixing bugs and integrating any new features for the duration of the Marlin 2.0.x life-cycle.
  • Follow the Coding Standards to gain points with the maintainers.
  • Please submit your questions and concerns to the Issue Queue.

RepRap.org Wiki Page

Credits

The current Marlin dev team consists of:

License

Marlin 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.