summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorwanleg <32079073+wanleg@users.noreply.github.com>2019-03-22 18:26:21 -0700
committerDrashna Jaelre <drashna@live.com>2019-03-22 18:26:21 -0700
commit1dda671e4ab44b978cf4fa78fd39c5d647b5ab86 (patch)
tree06c6b6d1c2714814e8621c29013e0ceccf97f2c3 /docs
parentf8d5b9f204f97651314b63df6dd33f75788d7ebe (diff)
ISP Flashing Guide - atmega32a info (#4993)
* update isp flashing page * update isp flashing page
Diffstat (limited to 'docs')
-rw-r--r--docs/isp_flashing_guide.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/isp_flashing_guide.md b/docs/isp_flashing_guide.md
index 18f2147846..0f786c5141 100644
--- a/docs/isp_flashing_guide.md
+++ b/docs/isp_flashing_guide.md
@@ -63,6 +63,7 @@ If you just want to get things back to normal, you can flash only a bootloader f
* [`atmega32u4`](https://github.com/qmk/qmk_firmware/blob/master/util/bootloader_atmega32u4_1_0_0.hex) - Most keyboards, Planck Rev 1-5, Preonic Rev 1-2
* [`at90usb1286`](https://github.com/qmk/qmk_firmware/blob/master/util/bootloader_at90usb128x_1_0_1.hex) - Planck Light Rev 1
+* [`atmega32a`](https://github.com/qmk/qmk_firmware/blob/master/util/bootloader_atmega32a_1_0_0.hex) - jj40
If you're not sure what your board uses, look in the `rules.mk` file for the keyboard in QMK. The `MCU =` line will have the value you need. It may differ between different versions of the board.
@@ -113,6 +114,10 @@ Since our keyboard uses an `atmega32u4` (common), that is the chip we'll specify
avrdude -c avrisp -P COM3 -p atmega32u4 -U flash:w:main.hex:i
+If your board uses an `atmega32a` (e.g. on a jj40), the command is this (the extra code at the end sets the fuses correctly):
+
+ avrdude -c avrisp -P COM3 -p atmega32 -U flash:w:main.hex:i -U hfuse:w:0xD0:m -U lfuse:w:0x0F:m
+
You should see a couple of progress bars, then you should see:
avrdude: verifying ...