Anyway. Do you have other debugging ideas I can help you with?
I didn’t know that but i think qmk version is more convenient
1 Like
Is this a general issue folks are seeing, am curious if the newest firmware is good to go?
I have installed the 20250725 revision of the firmware, jumping from stock. According to wev(1) all keys are working except for the volume key, which may just be an issue with my configuration.
On my machine, the upgrade’s added (by my rough estimate) a half-second of lag between trackball motion and input. It’s jarring - the upgrade has also made the trackball motion significantly less jittery, so whereas before I needed to just keep trying if I wanted to land my cursor on a specific pixel, now I only need to move slowly, and have no harder time.
The keyboard backlight is also a little wonky. Before, when Fn+Space were chorded, the backlight would cycle through the appearances of 0%, 50%, and 100% brightness. Now it takes an additional keypress to go from 0% to 50%, so it loops through 0%, 0%, 50%, and 100%. A late edit: the backlight at 50% is modulated now and noticeably flickers.
Still, I really love being able to scroll now.
For the volume key try
Vol = volume down
Shift+vol = volume up
Fn+vol = mute
I’m still on 20240922 so I don’t know if it changed in the recent update.
I am too experiencing keyboard disconnection upon plugging a device to the USB port with QMK 20250725.
What is the current solution besides reverting back to the stock firmware? You, who do not have this issue, are you using some previous version QMK fw?
This issue (where the keyboard won’t connect after USB state has changed) just hit me for the first time as I went to write a reply, which made me have had to plug a keyboard in. I’ve noticed that the supplied USB power seems to fluctuate when USB devices are plugged in; keeping the keyboard light on and plugging in a keyboard and mouse causes the light to flash before dying. Take this unskilled speculation with a grain of salt but it almost looks to me like the device is trying to supply more current than it can.
I have found the tried and true method of “turning it off and turning it back on” is an excellent, free solution to this problem.
1 Like
seems like it possible to programmatically reset usb device from host system: How do you reset a USB device from the command line? - Ask Ubuntu
so someone can write a daemon which will check if keyboard is connected and if not – reset it’s state.
Tried different solutions from askubuntu forum post shared by white-round-square:
usbresetfrom usbutils package:
sudo usbreset 1eaf:0003
Resetting Maple 003 ... ok- unbind-rebind:
echo 1-1.1 | sudo tee /sys/bus/usb/drivers/usb/unbind
sleep 1
echo 1-1.1 | sudo tee /sys/bus/usb/drivers/usb/bind - toggle authorized flag:
sudo sh -c "echo 0 > /sys/bus/usb/devices/1-1.1/authorized"
sudo sh -c "echo 1 > /sys/bus/usb/devices/1-1.1/authorized"
Nothing worked. It just resets the keyboard in bootloader or some other state:
Bus 001 Device 005: ID 1eaf:0003 Leaflabs Maple DFU interface
Could we install a capacitor (or similar hardware mod) on the keyboard’s USB power line to smooth out brief voltage dips?
3 Likes
Hello I’m new to the uConsole, and first off thank you for this QMK keyboard firmware, it’s wonderful. However forgive me if I’ve missed it, but:
Is there any documentation somewhere listing all the default uConsole function keybinds (other than the orange Fn overlays on the actual physical keyboard), and/or the QMK firmware custom keybinds? I see some spread across posts in this thread, but would love to have a complete list. Thanks!
uConsole/Code/uconsole_keyboard/keymaps.ino at master · clockworkpi/uConsole · GitHub ?
on the last official version you can also do fn + ball to scroll vertically
2 Likes
So, I had the stupid idea of messing with something that works just fine and wanted to update the firmware on my keyboard. I had flashed the QMK back at the beginning of this thread but still have the stuck space problem so I grabbed the latest firmware, clockworkpi_uconsole_default.20250725.bin, and ran the command sudo dfu-util -w -d 1eaf:0003 -a 2 -D clockworkpi_uconsole_default.20250725.bin -R (both on the uConsole and through ssh), but when it it reached “Waiting for the device,” hitting fn-esc or LAlt-RAlt-Start did nothing. I would have to remove the batteries to get the keyboard to work again. Am I missing something?
I had the same problem, it seemed frozen after hitting fn-esc. I plugged in my external keyboard to see if I could ctrl-c it from there and plugging it in seemed to kick start it and it worked!
I love this firmware. Select + ball movement is something I just can’t do without. However, I’m noticing now that I’ve updated that whenever I plug a USB device into the uConsole, the keyboard and trackball die until reboot, and this is extremely difficult to live with. I’m running Arch on the machine based off of PotatoMania’s build, and I had hoped that altering the usb_max_current_enable setting and over_voltage=6 would help, but it hasn’t. Just me? I know the post on this and it has a statement saying that it’s not the firmware, but I didn’t have this issue until I reflashed. Looking for any options to get that USB port on the side working.
How would I do that?
I misunderstood this. I had to do the keyboard plug in trick to unstick the loader, thanks all!
I can confirm that keyboard with the latest official firmware gets disconnected too when plugging in a USB device but the official fw re-enumerates back to normal keyboard while QMK fw gets stuck in the DFU.
- 351.962 –
usb 1-1.1(the keyboard) disconnects. - 352.489 → 352.578 – Same port re-enumerates as DFU:
1eaf:0003 "Maple 003"→ the keyboard MCU is in bootloader, not HID. - 352.781 → 352.979 – RTL2832U SDR on
1-1.2initializes. - 354.010 → 354.431 – Keyboard on
1-1.1disconnects again, then re-enumerates as normal composite HID/CDC:1eaf:0024 "ClockworkPI uConsole"and exposesttyACM0.
[ 351.962896] usb 1-1.1: USB disconnect, device number 17
[ 352.489442] usb 1-1.1: new full-speed USB device number 18 using dwc2
[ 352.578367] usb 1-1.1: New USB device found, idVendor=1eaf, idProduct=0003, bcdDevice= 2.01
[ 352.578377] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 352.578380] usb 1-1.1: Product: Maple 003
[ 352.578383] usb 1-1.1: Manufacturer: LeafLabs
[ 352.578386] usb 1-1.1: SerialNumber: LLM 003
[ 352.781055] usb 1-1.2: new high-speed USB device number 19 using dwc2
[ 352.884633] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=2838, bcdDevice= 1.00
[ 352.884642] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 352.884645] usb 1-1.2: Product: NESDR SMArt v5
[ 352.884648] usb 1-1.2: Manufacturer: Nooelec
[ 352.884650] usb 1-1.2: SerialNumber: 72039068
[ 352.891578] usb 1-1.2: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state
[ 352.946119] usb 1-1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 352.946131] dvbdev: DVB: registering new adapter (Realtek RTL2832U reference design)
[ 352.946135] usb 1-1.2: media controller created
[ 352.946396] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 352.949519] i2c i2c-15: Added multiplexed i2c bus 16
[ 352.949526] rtl2832 15-0010: Realtek RTL2832 successfully attached
[ 352.949549] usb 1-1.2: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...
[ 352.949558] dvbdev: dvb_create_media_entity: media entity 'Realtek RTL2832 (DVB-T)' registered.
[ 352.949683] r820t 16-001a: creating new instance
[ 352.956486] r820t 16-001a: Rafael Micro r820t successfully identified, chip type: R820T
[ 352.959004] rtl2832_sdr rtl2832_sdr.3.auto: Registered as swradio0
[ 352.959010] rtl2832_sdr rtl2832_sdr.3.auto: Realtek RTL2832 SDR attached
[ 352.959012] rtl2832_sdr rtl2832_sdr.3.auto: SDR API is still slightly experimental and functionality changes may follow
[ 352.970488] Registered IR keymap rc-empty
[ 352.970538] rc rc2: Realtek RTL2832U reference design as /devices/platform/axi/1000480000.usb/usb1/1-1/1-1.2/rc/rc2
[ 352.970591] rc rc2: lirc_dev: driver dvb_usb_rtl28xxu registered at minor = 0, raw IR receiver, no transmitter
[ 352.970640] input: Realtek RTL2832U reference design as /devices/platform/axi/1000480000.usb/usb1/1-1/1-1.2/rc/rc2/input28
[ 352.970806] usb 1-1.2: dvb_usb_v2: schedule remote query interval to 200 msecs
[ 352.978998] usb 1-1.2: dvb_usb_v2: 'Realtek RTL2832U reference design' successfully initialized and connected
[ 354.010896] usb 1-1.1: USB disconnect, device number 18
[ 354.215330] usb 1-1.1: new full-speed USB device number 20 using dwc2
[ 354.308639] usb 1-1.1: New USB device found, idVendor=1eaf, idProduct=0024, bcdDevice= 2.00
[ 354.308649] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 354.308652] usb 1-1.1: Product: uConsole
[ 354.308655] usb 1-1.1: Manufacturer: ClockworkPI
[ 354.308657] usb 1-1.1: SerialNumber: 20230713
[ 354.310620] input: ClockworkPI uConsole Consumer Control as /devices/platform/axi/1000480000.usb/usb1/1-1/1-1.1/1-1.1:1.0/0003:1EAF:0024.0006/input/input29
[ 354.367321] input: ClockworkPI uConsole Keyboard as /devices/platform/axi/1000480000.usb/usb1/1-1/1-1.1/1-1.1:1.0/0003:1EAF:0024.0006/input/input30
[ 354.431250] input: ClockworkPI uConsole as /devices/platform/axi/1000480000.usb/usb1/1-1/1-1.1/1-1.1:1.0/0003:1EAF:0024.0006/input/input31
[ 354.431352] input: ClockworkPI uConsole Mouse as /devices/platform/axi/1000480000.usb/usb1/1-1/1-1.1/1-1.1:1.0/0003:1EAF:0024.0006/input/input32
[ 354.431453] hid-generic 0003:1EAF:0024.0006: input,hidraw0: USB HID v1.10 Keyboard [ClockworkPI uConsole] on usb-1000480000.usb-1.1/input0
[ 354.431790] cdc_acm 1-1.1:1.1: ttyACM0: USB ACM device
5 Likes
Wow okay so I wonder if this kind of stack trace would be helpful for the QMK team. Maybe it’s a fixable bug!