~ruther/qmk_firmware

746058306b6c3b037fc560a13bb78d088c734401 — Danny Nguyen 6 years ago 50fce7f 
Make sure NOBITS is set on reset_key

Patch from https://github.com/qmk/qmk_firmware/issues/3657#issuecomment-415147411

Long story short, in avr-gcc pre-8.2, reset_key was assigned to a memory area that was in a normal range, but when 8.2 came out, that memory got moved to an out of range area, causing errors like 0x800293 out of range. Apparently, this was fixed up in avr-gcc, but we haven't seen a release with the fix yet (we expected it in 8.3, but that didn't happen for some reason).

What this commit does is move the reset_key back to the original memory location it was in before.
patch browse .tar.gz 
1 files changed, 1 insertions(+), 1 deletions(-)

M tmk_core/common/avr/bootloader.c

M tmk_core/common/avr/bootloader.c => tmk_core/common/avr/bootloader.c +1 -1
@@ 70,7 70,7 @@
 * http://www.fourwalledcubicle.com/files/LUFA/Doc/120730/html/_page__software_bootloader_start.html
 */
#define BOOTLOADER_RESET_KEY 0xB007B007
uint32_t reset_key  __attribute__ ((section (".noinit")));
uint32_t reset_key  __attribute__ ((section (".noinit,\"aw\",@nobits;")));

/** \brief initialize MCU status by watchdog reset
 *