bolteon:
No mention of the high fuses
MoteinoMEGA.bootloader.high_fuses is the name of the property in boards.txt. That property is used with the -Uhfuse avrdude option used in the first Burn Bootloader command. So you can see this set the high fuses to 0xDE:
bolteon:
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude" -C "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf" -v -patmega1284p -cstk500v2 -Pusb -e -Ulock:w:0x3F:m -Uefuse:w:0xFD:m -Uhfuse:w:0xDE:m -Ulfuse:w:0xDE:m
bolteon:
...actually, I'm guessing it's this boards.txt:C:\Users\User\AppData\Local\Arduino15\packages\Moteino\hardware\avr\1.3.0
That's correct. The active hardware package depends on your selection from the Tools > Board menu and each package has its own boards.txt. When you have a Moteino board selected that is the location of the active boards.txt.
bolteon:
Pretty sure this is the "boards.txt we're discussing?C:\Program Files (x86)\Arduino\hardware\arduino\avr
That path is the location of the Arduino AVR Boards hardware package used for Uno, Mega, Leonardo, etc. but you should note that if you install a different version of Arduino AVR Boards via Boards Manager then the package in the Arduino IDE installation folder is no longer used since all Boards Manager installations are done to the C:\Users\User\AppData\Local\Arduino15\packages folder. Of course Arduino AVR Boards is irrelevant since you're using the Moteino package but it's good information to know if you like to do general tinkering with the Arduino IDE.
bolteon:
Back in a bit, and a heartfelt thank you for the assistance. I've delayed our launch to crowdfunding by 4 weeks in case we couldn't get this figured out in short order, lots left to do and lots of "polish potential" so if I can get this settled, I'll be able to focus on other things over the next 6 weeks.
I'm glad if I can be of assistance. I'm sure that's stressful but running into some speedbumps at the last stretch seems to be common from the stories I've heard from people with successful crowdfunding campaigns.
bolteon:
Here's the boards.txt modifications that were sent over by the first hardware guy... some settings are different than what's in the standard boards.txt when installing the 1.3.0 MoteinoMEGA board setup:
You'll note even in the modified boards.txt entry, there is still MoteinoMEGA.bootloader.high_fuses=0xDE so that would still cause EEPROM to be erased on every Upload Using Programmer (as well as Tools > Burn Bootloader).
avr_fred:
The high fuse bit for preserving EEPROM contents is 0x08 so it’s on with a value of 0xDE.
It's not clear what you mean by "it's on". High fuse set to 0xDE means EEPROM contents are not preserved:
0xD6 means they are preserved: