<p>It wasn't advised to use the version 2.x because it was in development for 32-bit micro processors. Now that it has been released as the official version, you can use it for 8-bit micro processors.</p>

<p>But, it totally depends on the amount of options in Marlin you activate (bed leveling, advanced menu, <code>M5xx</code>, etc.). Luckily you can see how large the installation is after you have built it e.g. in PlatformIO. Also, in the configuration files frequently is mentioned how much extra storage activating an option costs (search for <code>PROGMEM</code> in the <a href="https://github.com/MarlinFirmware/Marlin" rel="nofollow noreferrer">Marlin sources</a>). Unless you want all options active, you'll be fine. I'm running it on an AVR (MEGA2560) for a CoreXY with bed leveling and some more options; it runs fine.</p>

CC BY-SA 4.0
2020-01-16T07:34:11.077Z
It always worked well for 8-bit controllers too. I found that, using the example config files for the same printer, Marlin 2.0 also compiles to about 7% less space - but that was just one data point.
towe
CC BY-SA 4.0
2020-01-16T07:40:56.860Z
@towe Yes it always worked, but it was not advised as it was a development version! :-)
0scar
CC BY-SA 4.0
2020-01-15T18:47:58.090Z
2020-01-15T19:06:12.820Z
2020-01-15T19:06:12.820Z
0scar
<p>I was just informed via a comment that the TH3D Unified firmware a version of Marlin that's no longer updated and considered obsolete (1.9.X in this case) and that, since I'm flashing my firmware to fix my default e-step settings, I might as well flash a non-obsolete firmware.</p>

<p>However, something in the back of my mind is telling me that I can't use Marlin 2.0 because of some hardware limitation.</p>

<p>I'm using the Creality CR-10S printer (with the Creality 2.0 board, I believe) which is an 8-bit CPU. What should I look out for before upgrading to Marlin 2.0?</p>

<p><a href="http://marlinfw.org/docs/basics/install.html" rel="nofollow noreferrer">Marlin's Install website</a> suggests that 8-bit AVR printers can use it (flashing via Arduino IDE). SO I guess I'm double checking before I do something that could potentially brick my printer.</p>

CC BY-SA 4.0
2020-01-15T17:02:47.990Z
@Trish I've edited my question to include that info. Thanks!
Lux Claridge
CC BY-SA 4.0
2020-01-15T17:14:05.467Z
Not sufficient for an answer, but I'd start by backing up the existing firmware in case you find that the new one doesn't work or has bugs/misfeatures you don't like.
R.. GitHub STOP HELPING ICE
<marlin><creality-cr-10>
What precautions to take when flashing Marlin 2.0?
Lux Claridge
# What precautions to take when flashing Marlin 2.0?

(Asked by: username_0 on 2020-01-15)

I was just informed via a comment that the TH3D Unified firmware a version of Marlin that's no longer updated and considered obsolete (1.9.X in this case) and that, since I'm flashing my firmware to fix my default e-step settings, I might as well flash a non-obsolete firmware.

However, something in the back of my mind is telling me that I can't use Marlin 2.0 because of some hardware limitation.

I'm using the Creality CR-10S printer (with the Creality 2.0 board, I believe) which is an 8-bit CPU. What should I look out for before upgrading to Marlin 2.0?

[Marlin's Install website](http://marlinfw.org/docs/basics/install.html) suggests that 8-bit AVR printers can use it (flashing via Arduino IDE). SO I guess I'm double checking before I do something that could potentially brick my printer.

**Tags:** marlin, creality-cr-10
> **Comments:**
> **username_0**: @Trish I've edited my question to include that info. Thanks!  
> **username_1**: Not sufficient for an answer, but I'd start by backing up the existing firmware in case you find that the new one doesn't work or has bugs/misfeatures you don't like.  

---

## 1 answers

### Answer by username_2 on 2020-01-15. Score: 1 | Accepted answer

It wasn't advised to use the version 2.x because it was in development for 32-bit micro processors. Now that it has been released as the official version, you can use it for 8-bit micro processors.

But, it totally depends on the amount of options in Marlin you activate (bed leveling, advanced menu, `M5xx`, etc.). Luckily you can see how large the installation is after you have built it e.g. in PlatformIO. Also, in the configuration files frequently is mentioned how much extra storage activating an option costs (search for `PROGMEM` in the [Marlin sources](https://github.com/MarlinFirmware/Marlin)). Unless you want all options active, you'll be fine. I'm running it on an AVR (MEGA2560) for a CoreXY with bed leveling and some more options; it runs fine.

> **Comments:**
> **username_3**: It always worked well for 8-bit controllers too. I found that, using the example config files for the same printer, Marlin 2.0 also compiles to about 7% less space - but that was just one data point.  
> **username_2**: @towe Yes it always worked, but it was not advised as it was a development version! :-)  

---

