#Up to date code for pimoroni trackball with serial communication split keyboad (lily58)

11 messages · Page 1 of 1 (latest)

wind zephyr
#

Hi there, I have found a few examples of people getting the pimoroni trackball to work on a lily58 or similar board, but I can't seem to get the firmware to compile without errors. I think I'm probably having some sort of version mismatch but I can't be sure. Can anyone recommend either an updated source for the firmware or let me know if I should be running a different version of qmk locally?

For reference, I'm trying to get the code referenced in the below post running.

https://github.com/dtwright/lily58-mods

wind zephyr
#

I've realized this is probably just about me reading an outdated guide, it seems like the newest version of qmk is going to work in a much simpler way. Sorry!

brisk patio
#

This is now trivial to do.
In your rules.mk:

POINTING_DEVICE_ENABLE = yes
POINTING_DEVICE_DRIVER = pimoroni_trackball

and in your config.h

#define SPLIT_POINTING_ENABLE
#define POINTING_DEVICE_RIGHT

this will enable the pointing device, set up the code for it, and set up syncing over the split comms, so you can use either side as master. And this sets up the right side to be the one with the trackball

wind zephyr
#

perfect, thanks for confirming!

brisk patio
#

you are very welcome!

#

dasky and I put in a lot of work to make pointing devices super friendly and work well on splits. 🙂

#

also, you may want to add #define MOUSE_EXTENDED_REPOR too. a number of reports that this helps with the pimoroni trackball smoothness and such

wind zephyr
#

it's very much appreciated, i can't imagine how long that all took. just to clarify, i can flash the same code to both halves now?

brisk patio
#

yup

wind zephyr
#

amazing wowee

brisk patio
#

the pointing device left/right/combined define is used to know which side to initialize the device on, and where to handle the reports