I’m sure this is a silly question, but is there a simple explanation for why the uConsole’s built-in keyboard isn’t plug and play? Mine still hasn’t arrived sigh, but it’s one of those things I’d like to prepare for.
It seems to be connected internally over USB. Ordinarily, custom USB keyboards don’t need special drivers or kernel tweaks. Unless there’s some sort of hardware limitation, a HID scan code sent over USB should basically work seemlessly on any hardware.
My instinct is to order a GD32 dev board and get started on replacement keyboard firmware, but I’m assuming if it was that easy they wouldn’t have made this strange choice in the first place.
It is just a USB keyboard, no drivers for it. There’s is also firmware available for the keyboard if you’d like to tweak something and reflash the keyboard.
That wasn’t a keyboard problem, it was a kernel problem. The kernel is all worked out now and there is a half a dozen current images available now for the DevTerm/uConsole.
can yougive more details about how to access and update the firmware for the keyboard? I am curious about what options are available for customization.
Good to know! And it looks like the keyboard should be easily hackable in Arduino, which is great!
I’m not going to pretend to understand why you’d need a kernel update to make an internal USB keyboard work, but not an external USB keyboards, but who am I to question!