diff options
| -rw-r--r-- | Memory-write-error,-use-debug-for-more-info.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/Memory-write-error,-use-debug-for-more-info.md b/Memory-write-error,-use-debug-for-more-info.md new file mode 100644 index 0000000000..01eb99211d --- /dev/null +++ b/Memory-write-error,-use-debug-for-more-info.md @@ -0,0 +1,14 @@ +In rare circumstances, your keyboard/device can become unwritable, and dfu-programmer will give you an error like this: + + Erasing flash... Success + Checking memory from 0x0 to 0x6FFF... Empty. + Checking memory from 0x0 to 0x607F... Empty. + 0% 100% Programming 0x6080 bytes... + [ X ERROR + Memory write error, use debug for more info. + +Currently the only way to solve this is to [reprogram the chip via ISP](https://www.reddit.com/r/olkb/comments/4rjzen/flashing_error_on_mac_os_x/d52rj8o/). This requires another device to be hooked-up to a couple exposed pins on the PCB. There is a guide on how to do this [here](https://learn.sparkfun.com/tutorials/installing-an-arduino-bootloader), and [this is where things are on the Planck PCB](http://imgur.com/lvbxbHt). + +An example command to flash the board once things are hooked up is: + + avrdude -c usbtiny -p m32u4 -U flash:w:planck_default_rev4.hex
\ No newline at end of file |