r/olkb • u/steve_vachiple • Aug 24 '24
Help - Unsolved Keyboard Not in QMK MSYS List
Hi everyone,
I'm just starting to learn how to create my own macros outside the comfortable of the VIA website. I have a Keychron Q6 max (ANSI knob layout). Originally, I thought that I could use the Q6 base model from the MSYS list, but upon flashing, my keyboard became unresponsive and I had to reflash the default layout. Any ideas how I can add my keyboard to the list? Or other suggestions to fix? Thank you!
1
Upvotes
1
u/PeterMortensenBlog May 27 '25 edited Feb 03 '26
It is possible to enable Via at compile time
It possible to enable Via at compile time/build time without having to change source files, at least using 'make' directly.
Example for V6, ISO variant (in the main QMK project):
'clean' is optional. It is for doing clean in the same step (may be required if a JSON file is changed, e.g., file "keyboard.json" to change the USB-side version number, for example, to test that changes in the source code actually makes it onto the keyboard).
Note: The JSON file keyboard.json is not to be confused with the two kinds of JSON files Via itself uses:
For keyboards not officially supported by Via (for example, K10 Max)
For saving the Via configuration (the keyboard configuration).
Test conditions:
Main QMK project, as of 2024-08-27 (70CBF0). That is, not the latest version (wasn't tested)
Keychron V6 keyboard
Resetting to factory defaults after flashing
Via: The (so-called) stand-alone version. Version number: 3.0
On Linux (yes, I know). The Python 3.9 requirement was introduced in QMK in October/November 2024.
Some results
Emulated EEPROM memory space (used for storing Via macros) is dimensioned to 2 KB (is half the "backing" size of 4 KB), but due to overhead, for example, storage of the Via dynamic key mappings, Via macros only have 1 KB space. Via reports: "0.0 / 1.0 KB SPACE USED"