Marlin supports a wide variety of 3D printers, including all RAMPS variants, and is adaptable to virtually any Arduino/Genuino-based electronics through pin-mapping - associating pins with their functions. With the addition of a hardware abstraction layer, Marlin 1.2 will address an even wider variety of boards.
Several files in the Marlin source code provide hardware support, but the files supporting the core electronics are:
| ||Contains the full list of boards supported by Marlin. Set |
| ||Manages pin definitions, including the appropriate |
| ||Each of these files contains the pin definitions for a single board. Some pins files form the basis for other pins files, most notably |
To build Marlin for a specific board, set the
MOTHERBOARD option in
Configuration.h. This example selects a RAMPS 1.4 board with the 12V power MOSFET connectors arranged in Extruder, Fan, Bed (EFB) order:
#define MOTHERBOARD BOARD_RAMPS_EFB
See the boards list at the bottom of this page for a complete list of boards supported in the latest release of Marlin.
FastIO and Pin Mapping
FastIO is a set of macros that allows Marlin to read and write pins quickly, using the same code on all processors. Marlin uses FastIO macros whenever possible because direct port manipulation is many times faster than the pin functions provided by
Pin Mapping refers to the relationship between assigned “pin numbers” and the actual hardware ports on the CPU. For example, pins might be mapped starting with 0 to represent Port A Pin 0, then numbered sequentially up to Port L Pin 15.
FastIO allows Marlin to use any pin mapping imaginable, but we’ve decided that the “Arduino mapping” as used by the Arduino headers is the best choice for several reasons. Most importantly, all standard Arduino code uses this mapping, and the mapping smartly uses the documented DIO pin numbers.
Note: When writing code for Marlin, never use
Since version 1.1.4, Marlin also uses Arduino pin mapping for Teensy++, Sanguino, and other AT90USB-based processors, so we can still use the documented digital pin numbers even in the Teenyduino build environment. Previous versions of Marlin provided an option to use either Teensyduino or Arduino mapping, depending on the what the active pins file supported.
Analog inputs are always assigned using an index from 0-15. Marlin doesn’t need to know their digital pin numbers.
Adding a new board
The easiest way to add a new board to Marlin is to start with one of the existing pins files that has pin mappings similar to the new board, make a copy, and modify the pins that differ. Once your pins file is ready, simply add a new define to the
boards.h file and a conditional include to
pins.h. And you’re done! Submit a PR to share it with the world.
If you’re developing a custom Arduino-based board, try to use standard RAMPS 1.4 pinouts as much as possible, or choose a pin-mapping similar to another board Marlin supports. The more a new board resembles an existing board, the easier it will be to integrate.