wally VS qmk_firmware

For context, I have attempted for weeks to install a program called Wally used for keyboard configuration on an ergonomic mechanical keyboard, something I imagine a lot of Linux users are well-acquainted with. In my journey, I've learned a lot about bash commands, which is nice, but I want to edit my fucking keyboard and can't crack this, even with support from ZSA (the keyboard makers themselves).

Hi there, novice Linux user here like many jumping to the Steam Deck as their main machine. I use a ZSA Moonlander keyboard and a piece of software called Wally to flash custom layouts on it. I thought all of the dependencies for Wally had been successfully installed on my machine. Unfortunately, I encountered an error related to a missing shared library:

I *thought* the laptop USB ports weren't powering the Moonlander when I tried to use it. Turns out in Linux it isn't plug and play. You have to follow these instructions. Basically you need UDEV rules to recognise the keyboard and let you use it. After that and a reboot the thing came alive and in colours!

I had already downloaded the firmware through Oryx, (https://configure.zsa.io/ergodox-ez/layouts/) and installed using Wally (https://ergodox-ez.com/pages/wally) and it was giving the same problem.

For me on my moonlander, also on manjaro, it didn't work directly. I didn't check the error so I cannot say if we have the same problem. I followed the todo to install wally ( https://github.com/zsa/wally/wiki/Linux-install ), mainly the udev file. I think I also needed a reboot, but can really remember. Train work after that.

Wails is what Wally is written with

Also Go uses dynamic linking with glibc (at least as of semi-recent versions). They aren't static! When I was running CentOS however long ago I had to build a docker image for one of the projects I use because they built it with a version of glibc that was too new to run on RHEL based distros: https://github.com/zsa/wally/pull/124

Pruning my collection for an upcoming move. Note this Ergodox EZ is from 2016. It does not have the RGB and swappable switches that some newer versions have. It still supports the same firmware configuration and flashing using Oryx/Wally

But when I flash an ergodox .hex file, the keyboard doesn't work. Nothing registers when I press buttons. I tried using both the QMK firmware and Oryx configurator to build the .hex file (according to these instructions: https://www.ergodox.io/#assemble) but neither work. I tried flashing the hex files with the teensy loader from pjrc (https://www.pjrc.com/teensy/first_use.html) and wally (https://ergodox-ez.com/pages/wally). But no combination of .hex + flashing program does anything.

I only use keyboards running QMK or ZMK, so:

My Caps Lock key is a Control/Escape key (when tapped it behave like a Escape, when hold it's Control), and my left Control is a one shot layer switch key [1], which means I tap LCtrl once, and then press Caps Lock + 5 to get Ctrl+F5. Doable with single hand and more ergonomic as I have an unusually small hand.

[1] https://github.com/qmk/qmk_firmware/blob/master/docs/one_sho...

I agree that reduced finger movement is a crucial step in achieving typing efficiency. This is nicely solved by mod tap modifiers in QMK/ZMK[1] where key acts as a char when tapped and as a layer while pressed.

[1]: https://github.com/qmk/qmk_firmware/blob/master/docs/mod_tap...

Separate wireless controller, see the glue code at [0]

[0]: https://github.com/qmk/qmk_firmware/compare/master...nuphy-s...

If you have a keyboard that runs QMK firmware[0] with the VIA[1] feature enabled[2], then there is a convenient testing app available from the same place you customize your keys [3].

[0] https://qmk.fm/

I made a layout that I'm happy with. Spanish is my native language, so it has characters like the accents and 'ñ', but it's meant to be used for programming as well. Visual Studio uses a lot of Ctrl and Ctrl + Shift shortcuts, so I left them in the same place as the default Corne layout so I can press them both with my pinkie finger. Perhaps some of the ideas are useful to you.

Also, it would be possible to do this for the RP2040. However, it needs some work to get working. but for example: https://github.com/qmk/qmk_firmware/pull/20999

Ok, it's an ST7735, not too different from the ST7789. You should be able to get running by looking at their files in the QMK repo and going from there. You should also check their resources page.