#Getting over it download v1.3 upgrade#

Can anyone explain that?Р”Р„nd one more data point: the original board I had issue with came directly from Creality. I would simply leave it at version 1.0.1 and live with it, but that's not why I 'upgraded.' For one thing firmware version 1.0.1 gives me an error with Octopi indicating that my 'firmware is broken' and will result in communication errors (which I have experienced).Р”Р„nd considering comment that 1.0.1 is the newest version, I'm not following the logic of a version naming convention that has been in place for decades that would all of a sudden deviate to 1.0.1 is newer than 2.0.1. I get the feeling that the bootloader simply does not work on this board. Also I have been using the original 8GB SD card fully reformatted (to 32FAT), and re-partitioned with only a 2GB partition, etc. filename, or naming it firmwarenew.bin, or firmware_1, etc. I've tried many things, including changing the file name from Ender-3-Pro-4.2.7. Inspection of the sd card contents will then show an additional file: 'EEPROM.DAT' with a 4KB size. The screen goes solid blue for about ten seconds, then immediately returns to the usual Ender 3 logo, and whether checked immediately or an hour later, the version showing on the 'About.' screen is version 1.0.1.

I download the 'Ender-3-Pro-4.2.7-Marlin2.0.1-V1.0.1-TMC2225-English.rar' file, extracted it to and empty 8GB SD card and renamed it to 'firmware.bin.' I then put the card into the Ender 3 Pro that I have upgraded with a 4.2.7 motherboard, and turned the machine on.

#Getting over it download v1.3 upgrade#

I'm trying to upgrade the firmware that came with the board (Marlin 1.0.1) to v2.01.