aboutsummaryrefslogtreecommitdiff
path: root/docs/isp_flashing_guide.md
diff options
context:
space:
mode:
authorDrashna Jaelre <drashna@live.com>2020-07-18 13:24:23 -0700
committerGitHub <noreply@github.com>2020-07-18 21:24:23 +0100
commitc4d778a302462929ba71a4746afa1f21f10922c2 (patch)
treea333fbe6d573603696ee5a4cf7c50f5d65f756e0 /docs/isp_flashing_guide.md
parent82dcb173386be1a5dc867401dca63cde6d0e8121 (diff)
downloadqmk_firmware-c4d778a302462929ba71a4746afa1f21f10922c2.tar.gz
qmk_firmware-c4d778a302462929ba71a4746afa1f21f10922c2.zip
[Docs] Update ISP Guide (#9748)
* [Doc] Update ISP Guide Correct the fuses for Caterina, and make the `:production` command more obvious. * fix casing before fauxpark catches it
Diffstat (limited to 'docs/isp_flashing_guide.md')
-rw-r--r--docs/isp_flashing_guide.md12
1 files changed, 7 insertions, 5 deletions
diff --git a/docs/isp_flashing_guide.md b/docs/isp_flashing_guide.md
index 8ee5a40d9..9a65fe115 100644
--- a/docs/isp_flashing_guide.md
+++ b/docs/isp_flashing_guide.md
@@ -141,7 +141,9 @@ To do this manually:
141 141
142?> It's possible to use other bootloaders here in the same way, but __you need a bootloader__, otherwise you'll have to use ISP again to write new firmware to your keyboard. 142?> It's possible to use other bootloaders here in the same way, but __you need a bootloader__, otherwise you'll have to use ISP again to write new firmware to your keyboard.
143 143
144To do this the easy way, you can flash the board using the `:production` target when compiling. This compiles the firmware, then compiles the QMK DFU bootloader, and then creates a combined image. Once this is done, you'll see three files: 144#### Create QMK DFU Bootloader and Production images
145
146You can create the firmware, the QMK DFU Bootloader and the production firmware images for the board using the `:production` target when compiling. Once this is done, you'll see three files:
145* `<keyboard>_<keymap>.hex` 147* `<keyboard>_<keymap>.hex`
146* `<keyboard>_<keymap>_bootloader.hex` 148* `<keyboard>_<keymap>_bootloader.hex`
147* `<keyboard>_<keymap>_production.hex` 149* `<keyboard>_<keymap>_production.hex`
@@ -236,12 +238,12 @@ For Caterina on the `atmega32u4`, these are the fuse settings that you want:
236| Fuse | Setting| 238| Fuse | Setting|
237|----------|--------| 239|----------|--------|
238| Low | `0xFF` | 240| Low | `0xFF` |
239| High | `0xD9` | 241| High | `0xD8` |
240| Extended | `0xC3` | 242| Extended | `0xCB` |
241 243
242To set this add `-U lfuse:w:0xFF:m -U hfuse:w:0xD8:m -U efuse:w:0xC3:m` to your command. So the final command should look something like: 244To set this add `-U lfuse:w:0xFF:m -U hfuse:w:0xD8:m -U efuse:w:0xCB:m` to your command. So the final command should look something like:
243 245
244 avrdude -c avrisp -P COM3 -p atmega32u4 -U flash:w:main.hex:i -U lfuse:w:0xFF:m -U hfuse:w:0xD8:m -U efuse:w:0xC3:m 246 avrdude -c avrisp -P COM3 -p atmega32u4 -U flash:w:main.hex:i -U lfuse:w:0xFF:m -U hfuse:w:0xD8:m -U efuse:w:0xCB:m
245 247
246 248
247If you are using a different controller or want different configuration, you can use [this AVR Fuse Calculator](http://www.engbedded.com/fusecalc/) to find a better value for you. 249If you are using a different controller or want different configuration, you can use [this AVR Fuse Calculator](http://www.engbedded.com/fusecalc/) to find a better value for you.