-
Notifications
You must be signed in to change notification settings - Fork 85
Appendix C: QMK Firmware Programming
This guide is strictly for Ploopy devices that come preloaded with QMK. How do you know if your device has QMK on it? The fastest way is by using a piece of software such as QMK Toolbox. If you're running that program and plug in your Ploopy device, it'll show up as a QMK device.
You can also try jumping into the bootloader:
- If you've got a right-handed Ploopy Classic, hold the "back" button and plug in the trackball. If moving the ball doesn't move the cursor, then you've got QMK. (Try unplugging and plugging it back in without holding the forward button just to make sure that moving the ball still works as normal.)
- If you've got a left-handed Ploopy Classic, hold the "forward" button and plug in the trackball. If moving the ball doesn't move the cursor, then you've got QMK. (Try unplugging and plugging it back in without holding the back button just to make sure that moving the ball still works as normal.)
You can reprogram your older Ploopy device with new QMK firmware. The instructions for doing so are in Appendix D: Programming QMK on Older Ploopy Devices.
The Ploopy Trackball is fairly easy to program and reprogram, thanks to the excellent work by all of the developers and maintainers of the QMK firmware suite. This guide will focus specifically on flashing firmware to the Ploopy Trackball.
If you have never used QMK before, go through all of the steps in the QMK guide to set up your environment.
QMK was built for keyboards, so you'll see lots of references to code that looks like the following:
-kb <keyboard>
Whenever you see that, use the following syntax:
-kb ploopyco/trackball/rev1_005
and you'll be fine.
Look for some writing on the base PCB (it sits flat against the bottom of the case, and it holds the microcontroller and the sensor optic). If you see that it has a version of "R1.005" or higher, use the rev1_005
firmware. If it's "R1.004" or lower, use the rev1
firmware.
LEFTIES ONLY:
- If you're compiling from source, use the
rev1
version of the firmware. Make sure to change therev1/rules.mk
configuration file to have the lineBOOTLOADER=atmel-dfu
instead ofBOOTLOADER=caterina
. - If you don't want to be bothered with all that, a precompiled hex file is available for you right here. It comes with VIA already configured.
With your terminal window open and pointed at your QMK build environment, compile the firmware with the following command:
qmk compile -kb ploopyco/trackball/rev1_005 -km via
Alternatively, you can invoke the Makefile directly with the following:
make ploopyco/trackball/rev1_005:via
If you wish, you can use the default keymap (with qmk compile -kb ploopyco/trackball/rev1_005 -km default
or make ploopyco/trackball/rev1_005:default
). However, the VIA keymap is particularly interesting because it allows for customization of the trackball's functions without reflashing the firmware, through the use of the convenient VIA software package. It's incredibly handy, so definitely check it out.
For more details on building QMK firmware in general, see the QMK firmware guide.
Putting the Ploopy Trackball into bootloader mode is very easy.
- Unplug it from your computer.
- If you're using a right-handed Ploopy Classic, hold the "back" button. This is the button just to the right of the ball; it normally sits under your ring (fourth) finger. If you're using a left-handed Ploopy Classic, hold the "forward" button.
- While holding the button, plug the Ploopy Trackball into your computer. If you're using QMK Toolbox, it should show up in the console. If using
dmesg
, it'll show up as an Atmel DFU device.
And that's it. While plugged in this way, the Ploopy Trackball will accept new firmware.
Use your preferred method of flashing QMK firmware.
- QMK Toolbox has been verified as working.
- Using
dfu-programmer
from a terminal window has also been verified as working.
For more details, see the QMK guide on flashing firmware.
Unplug it, replug it in, and you should be good to go!
Happy customizing!
Copyright (C) 2020, Ploopy Corporation.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".