qmk_toolbox VS keyboards

Flashing custom firmware - the current version QMK tool off the website won't work. You'll most likely get a "USB device connected (NO DRIVER): WB Device in DFU Mode " and not be able to flash anything. You will need the beta version that supports WB32 flashing utility. I grabbed mine from the GMMK guide QMK tool from GMMK

You first have to download QMK toolbox https://github.com/qmk/qmk_toolbox/releases/download/0.2.2/qmk_toolbox.exe. Once downloaded, download this bin file https://github.com/GHv4/Sense75-CAPSLOCK-UNDERGLOW/blob/main/sense75-CAPSLOCK%20UNDERGLOW.bin. Open the QMK toolbox exe file, then hit the open button. Locate the .bin file. Hold Right FN+BACKSPACE until it pops up in QMK Toolbox. Hit flash and wait for it to finish flashing. Via and Vial compatible. YOU'RE WELCOME FRIENDS!!

Flash it with qmk toolbox: https://github.com/qmk/qmk_toolbox/releases

I got things working by using the https://github.com/qmk/qmk_toolbox project, and the firmware file you linked. As you said, my pad now works with Vial, and has 12 layers. Though the layer selector still only traverses between layers 0 through 3.

- QMK MSYS: you'll need it for many things, for compiling your firmware file and for flashing, especially if flashing with QMK Toolbox isn't permitted in firmware settings (in this case QMK Toolbox just won't recognize your keyboard);

I am currently using the QMK online configurator tool to do the compilation and download the resulting .bin file, and then the QMK Toolbox to flash it onto the keyboard.

Check out this site: http://kpchn.com/s/PoHJ. I found it from the AliExpress page and it leads to all the VIA/VIAL configs for the KPRepublic boards. Go into CSTC75 and you'll see a .hex file, that's the firmware. You should be able to use the QMK toolbox: https://github.com/qmk/qmk_toolbox to flash the firmware.

Tool needed to flash your keyboard (QMK Toolbox) can be downloaded here: https://github.com/qmk/qmk_toolbox/releases/tag/0.2.2

When I first plugged them in, my Mac (running 13.1 Ventura) recognized them as a USB storage device. I was trying to use the QMK toolbox to flash the firmware onto them, not realizing that I needed to drag and drop a .uf2 file instead of trying to flash a .hex file.

QMK and VIA out-of-the-box \o/

which doesn't aspire confidence in that happening since even though boards like the JRIS65 and JRIS75 tout "QMK/VIA" support, there are no entries in both, the qmk/firmware repo and the the-via/keyboards repo, and no PRs were raised in both to add support for them. Since the source code for those boards wasn't anywhere to be found, that in of itself was a violation of the GPL 2.0/3.0 License, which QMK and VIA abide by.

for any issues with VIA, you should open issues here: https://github.com/the-via/keyboards/issues

My firmware has the `VIA_ENABLE = yes` on its rules.mk (on my keymap folder), and there's also the via folder on the project which also has it enabled. Using the official preonic keymaps.json on the Design tab of VIA also doesn't work. That makes me think that I'm missing some kind of board identification on my code? QMK Toolbox recognizes the device as a Preonic.

QMK and Need your firmware In the documentation https://docs.qmk.fm/#/keycodes\_basic this is the KC_CAPS_LOCK or KC_CAPS key For ease of copy-paste, look for text mentioning these words and turning on the indication in the firmware of other keyboards on https://github.com/qmk/qmk\_firmware/tree/master/keyboards https://github.com/the-via/keyboards you can start with Keychron keyboards

Create an Android app for https://github.com/the-via/keyboards

Hi y'all. This basically a little PSA that's meant to compliment u/cosmic_c 's post about adding support for the GMMK 2. Although that PR was for the 96% ANSI variant of the GMMK 2, my PR adds support for the ISO variant of the 96%, and both variants (ANSI and ISO) for the 65% version.

The JSON you should use for the design tab to verify is this one. If you can't download it just copy/paste the code into a txt file then change the extension to .json and load it up.

Source.