diff options
| author | Danny Nguyen <danny@keeb.io> | 2019-03-20 17:45:45 -0400 |
|---|---|---|
| committer | skullydazed <skullydazed@users.noreply.github.com> | 2019-04-19 14:44:16 -0700 |
| commit | 746058306b6c3b037fc560a13bb78d088c734401 (patch) | |
| tree | 8b5295ba80eb632f84e709355d4d3fea86466f29 /docs/feature_layouts.md | |
| parent | 50fce7f255fa39c90239c6406f9c6b3ca2050114 (diff) | |
| download | firmware-746058306b6c3b037fc560a13bb78d088c734401.tar.gz firmware-746058306b6c3b037fc560a13bb78d088c734401.tar.bz2 firmware-746058306b6c3b037fc560a13bb78d088c734401.zip | |
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.
Diffstat (limited to 'docs/feature_layouts.md')
0 files changed, 0 insertions, 0 deletions