geekhack Marketplace > Group Buys and Preorders
[GB] F104+SSK+122+62+77+50+Ergo orders now open! Kishsaver+Industrial Model F
xyzzy42:
--- Quote ---Once I had compiled the Leyden Jar Diagnostic Tool on Linux I was able to click Refresh, click Enter Bootloader, and drag-drop the firmware file. After I'd replaced the firmware with the all pads version, the Layout tab was present in Vial..
--- End quote ---
Seems like it should be possible to enter the bootloader via a hotkey sequence, without a need to run some sort of utility to trigger it.
xyzzy42:
--- Quote from: ploxiln on Tue, 30 September 2025, 00:16:25 ---More importantly, you should host mirrors of all the source code yourself (or on your own GitHub account, or GitLab, or SourceHut, or Codeberg, or anywhere reliable).
--- End quote ---
One wonders why the keyboards can't be supported in upstream QMK. It supports hundreds already. It be far better for long term viability that way.
Order are still shipping, and yet the source is already "lost" since pandrew's site went down.
Is a kludge build script that downloads things for specific hosts on the internet and applies patch files going to work in 40 years? Obviously not. It's already broken now!
ploxiln:
--- Quote from: xyzzy42 on Tue, 07 October 2025, 21:39:19 ---One wonders why the keyboards can't be supported in upstream QMK. It supports hundreds already.
--- End quote ---
It's not so easy ... I think upstream is reluctant to add so much code, and probably overwhelmed by all the keyboards they already "support". Anyway, it has been attempted:
https://github.com/qmk/qmk_firmware/pull/21193
https://github.com/qmk/qmk_firmware/pull/21181
--- Quote from: xyzzy42 on Tue, 07 October 2025, 21:39:19 ---Is a kludge build script that downloads things for specific hosts on the internet and applies patch files going to work in 40 years? Obviously not. It's already broken now!
--- End quote ---
Agreed. For what it's worth, you can just replace http://purdea.ro/qmk_firmware with https://github.com/ploxiln/qmk_firmware.git in the build script, it checks-out specific git commit hashes, so if it works it's the same. It does work :)
I also went ahead and made a qmk/vial branch which matches the result of running the build script (confirmed by diff): https://github.com/ploxiln/vial-qmk/tree/nathana_vial_xwhatsit
... with 2 caveats:
* my branch includes pandrew-util-new_kbd_defs_r5.diff but the build script does not (since the build script is for the firmware, not the util, I guess)
* my branch does not yet include the src/layouts/*.json files (which are configs used for actual "qmk compile" commands in the build.sh script) nor the keymaps/ presets (used by the flash scripts to set initial keymap in eeprom)
I was just having trouble deciding where to put these in the qmk/vial repo fork ... looking at most other keyboards in there, it looks like there are a bunch of older or just alternative ways to organize keymaps and layouts, and for the xwhatsit dir in particular there may be a lot that are generated boilerplate or vestigial, it's kinda confusing. I'm not really familiar with QMK or Vial firmware (just software development and source-code wrangling in general) so I'm really not sure what direction we should even go to make this more well-organized and upstreamable, what could or should be "cleaned up" from the xwhatsit keyboards tree...
So anyway, I'll shortly just pick some reasonable arrangement and go with it, and add a very short script to do the compile and flash stand-alone from my fork/branch, and then iterate from there if there is some good motivation/advice.
Ellipse:
jtd-my note was that it is not necessary to perform all those steps. To flash to the default ISO, one can use the key combination Fn+Spacebar+R or Leyden Jar diagnostic tool to enter the bootloader, and then copy and paste the firmware uf2 file to the empty drive that appears in the Explorer/File Manager.
Rico is currently working on an updated firmware to fix the all pads splitting not saving some changes, as well as the calibration bin issue introduced with a recent beta firmware (my recommendation is that everyone stay with the latest May 2025 firmware unless you'd like to help with the beta testing).
Thanks for your updates ploxiln. If you come up with any recommendations to combine the Leyden Jar/NathanA/pandrew files into one, please let me know. Maybe I can make my github page the official one and add NathanA and Rico as admins so they can update everything (while keeping the git history)? I know that the NathanA and Rico firmwares run on different versions of QMK/Vial. This would likely involve updating my github to incorporate your source files and copy to my github, so that there are no outside files needed.
Ellipse:
With permission I am sharing a custom "all pads" layout with the custom 3x5 cut out mod. These mods were first suggested by this user, who is nicknaming this version the F138; now several others have ordered this mod for their F122 (you don't have to use all pads with the 3x5 cut out mod - you can have a regular ANSI/ISO/split shift layout just with 5 keys added above your cursor keys). I still have some cut out cases but they are only available in certain colors (beige and others, no more black cut out cases). Please email me if interested in ordering one.
With this layout, every available pad is used for a key. Each key can be configured in Vial as there is a working pad for each one.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version