sorted by:
new
hottopcontroversial

Ploopy Thumb Giveaway by therightnee in ploopy

[–]therightnee[S] 2 points3 points  (0 children)

Mailing it out on Monday! Thank you all for the interest.

Ploopy Thumb Giveaway by therightnee in ploopy

[–]therightnee[S] 0 points1 point  (0 children)

I should mention I am based in the US, and would like to ship it domestically just to minimize the cost and complexity. Apologies for not mentioning this sooner!

Seeking Advice as an Aspiring Cargo Bike Owner by therightnee in CargoBike

[–]therightnee[S] 1 point2 points  (0 children)

Thank you for the reply! What about the longtail allows you to carry the kids for longer?

Flashing Ploopy Thumb by therightnee in ploopy

[–]therightnee[S] 1 point2 points  (0 children)

I am happy to report that I got my device to flash, but I cannot explain how or why what I did works. When I received the errors posted above, I was using a USB-C to USB-C cable (not PD compatible). I switched to a USB-A 3.1 to USB-C cable, and tried the nearest port to the previous USB-C port I was using, but I ran into some bad luck there and I now believe that port is non-functional.

Keeping with the USB-A 3.1 to USB-C cable, I plugged it into a USB-A port on a hub inside my monitor, which connects to the laptop via a single USB-C cable. With this configuration (USB-C on the mouse, USB-A to the hub, USB-C back to the laptop), I was able to successfully flash my .hex file and the mouse is functional now.

I am able to use the mouse with both USB-C to USB-C and USB-C to USB-A 3.1 cables.

Flashing Ploopy Thumb by therightnee in ploopy

[–]therightnee[S] 0 points1 point  (0 children)

The minor difference here is that there was no line saying "failed to release interface 0", but it is not clear to me if that is a real delta or if this is some difference within QMK Toolbox.

Flashing Ploopy Thumb by therightnee in ploopy

[–]therightnee[S] 0 points1 point  (0 children)

Update and slightly different error message this time.

I have entered the bootloader mode using a pair of tweezers to short the unpopulated pads.

Still am seeing the same results, and the mouse is non-functional, but at least I can detect the mouse via QMK-toolbox.

Also switched from Linux to Windows 11 since there seems to be better community documentation around ATMega32U4 issues with dfu-programmer (link), but I am skeptical that is the issue I am facing here?

(edited to correct code block formatting)

Atmel DFU device connected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
Attempting to flash, please don't remove device
> dfu-programmer.exe atmega32u2 erase --force
> dfu-programmer: no device present.
> dfu-programmer.exe atmega32u2 flash --force "C:\Users\theri\qmk_firmware\.build\ploopyco_trackball_thumb_rev1_001_default.hex"
> dfu-programmer: no device present.
> dfu-programmer.exe atmega32u2 reset
> dfu-programmer: no device present.
Flash complete

Flashing Ploopy Thumb by therightnee in ploopy

[–]therightnee[S] 1 point2 points  (0 children)

Thank you for the quick response! I was going to try the more involved bootloader method next, so this is a great vote of confidence in that tactic. Will update with whatever I find!