Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Keyboard] Fixes for PloopyCo mouse and readme #10841

Merged
merged 1 commit into from
Nov 3, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion keyboards/ploopyco/mouse/mouse.c
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ __attribute__((weak)) void process_mouse(report_mouse_t* mouse_report) {
if (debug_mouse) dprintf("Cons] X: %d, Y: %d\n", data.dx, data.dy);
// dprintf("Elapsed:%u, X: %f Y: %\n", i, pgm_read_byte(firmware_data+i));

process_mouse_user(mouse_report, data.dx, data.dy);
process_mouse_user(mouse_report, data.dx, -data.dy);
}
}

Expand Down
27 changes: 1 addition & 26 deletions keyboards/ploopyco/mouse/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,8 @@

![Ploopyco Mouse](https://www.ploopy.co/uploads/1/2/7/6/127652558/s905404500980887952_p10_i19_w1414.jpeg)

It's a DIY, QMK Powered Trackball!!!!
It's a DIY, QMK Powered Mouse!!!!

Everything works. However the scroll wheel has some issues and acts very odd.

* Keyboard Maintainer: [PloopyCo](https://github.com/ploopyco), [Drashna Jael're](https://github.com/drashna/), [Germ](https://github.com/germ/)
* Hardware Supported: ATMega32u4 8MHz(3.3v)
Expand Down Expand Up @@ -51,27 +50,3 @@ To configure/set your own array, there are two defines to use, `PLOOPY_DPI_OPTIO
The `PLOOPY_DPI_OPTIONS` array sets the values that you want to be able to cycle through, and the order they are in. The "default" define lets the firmware know which of these options is the default and should be loaded by default.

The `DPI_CONFIG` macro will cycle through the values in the array, each time you hit it. And it stores this value in persistent memory, so it will load it the next time the device powers up.


# Programming QMK-DFU onto the PloopyCo Mouse

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](https://docs.qmk.fm/#/isp_flashing_guide) the chip with the new bootloader 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` |
2 changes: 1 addition & 1 deletion keyboards/ploopyco/mouse/rules.mk
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ MCU = atmega32u4
F_CPU = 8000000

# Bootloader selection
BOOTLOADER = qmk-dfu
BOOTLOADER = atmel-dfu

# Build Options
# change yes to no to disable
Expand Down
2 changes: 0 additions & 2 deletions keyboards/ploopyco/trackball/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,6 @@

It's a DIY, QMK Powered Trackball!!!!

Everything works. However the scroll wheel has some issues and acts very odd.

* Keyboard Maintainer: [PloopyCo](https://github.com/ploopyco), [Drashna Jael're](https://github.com/drashna/), [Germ](https://github.com/germ/)
* Hardware Supported: ATMega32u4 8MHz(3.3v)
* Hardware Availability: [Store](https://ploopy.co), [GitHub](https://github.com/ploopyco)
Expand Down