Flashing bootloader erases EEPROM by default

[snicker]

Due to the fuses set in boards.txt, the EEPROM is erased when Ariadne is flashed onto the ATMega, not sure if this is intended functionality, but I made it a point to move EEPROM data "out of the way" of the Ariadne settings locations in the EEPROM only to find out it was erased anyways. Patch below maintains existing fuse settings but adds the "don't erase EEPROM" fuse flag

/hardware/ariadne/boards.txt
@@ -7,7 +7,7 @@
 ariadne328.upload.speed=115200

 ariadne328.bootloader.low_fuses=0xFF
-ariadne328.bootloader.high_fuses=0xD8
+ariadne328.bootloader.high_fuses=0xD0
 ariadne328.bootloader.extended_fuses=0x05
 ariadne328.bootloader.path=ariadne
 ariadne328.bootloader.file=ariadne_atmega328.hex
@@ -28,7 +28,7 @@
 ariadne328eth.upload.speed=115200

 ariadne328eth.bootloader.low_fuses=0xFF
-ariadne328eth.bootloader.high_fuses=0xD8
+ariadne328eth.bootloader.high_fuses=0xD0
 ariadne328eth.bootloader.extended_fuses=0x05
 ariadne328eth.bootloader.path=ariadne
 ariadne328eth.bootloader.file=ariadne_atmega328_ethernet.hex

[loathingKernel]

Yes, it is intended that way. It ensures that after a bootloader update everything will be written again in a proper way through the NetEERPOM sketches. This helps avoid any potential problems with relocated keys and settings.

Because upgrading the bootloader isn't something that happens all the time, i believe that this should be the default behavior, even though it is a minor inconvenience,