qmk_firmware/keyboards/ploopyco/trackball/rev1
Drashna Jaelre 88a783a8a7
[Keyboard] PloopyCo update and fixes (#10936)
This is based on feedback talking with crop_octagon about the device.  Future trackballs will ship with ATMEL DFU for simplicity.  This also includes some fixes and optimizations based on code review and tinkering on my own devices.
2020-11-18 23:20:29 +01:00
..
config.h [Keyboard] Bug fixes and improvements to PloopyCo devices (#10573) 2020-10-27 17:09:11 +11:00
readme.md [Keyboard] PloopyCo update and fixes (#10936) 2020-11-18 23:20:29 +01:00
rev1.h [Keyboard] Bug fixes and improvements to PloopyCo devices (#10573) 2020-10-27 17:09:11 +11:00
rules.mk [Keyboard] PloopyCo update and fixes (#10936) 2020-11-18 23:20:29 +01:00

See the main readme for more details.

This is just the rev 1.001-1.004 trackball

Programming QMK-DFU onto the PloopyCo Trackball (Advanced)

If you would rather have DFU on this board, you can use the QMK-DFU bootloader on the device. To do so, you want to run:

make ploopyco/trackball:default:production

Once you have that, you'll need to ISP Flash the chip with the new "production" hex file created (or the production hex), and set the fuses:

Fuse Setting
Low 0xDF
High 0xD8 or 0x98
Extended 0xCB

Original (Caterina) settings:

Fuse Setting
Low 0xFF
High 0xD8
Extended 0xFE

If you're using QMK DFU, you'll also need to add BOOTLOADER=qmk-dfu to your keymap's rules.mk file, to ensure that the reboot/reset works correctly. Otherwise, it will jump right back into the firmware, like nothing happened.

Additionally, once you've flashed the qmk-dfu bootloader onto your device, you will no longer be able to use the Arduino IDE to flash the board. You'll need to use the command line or QMK Toolbox to flash it.