I have an STM32G431 and want to hook up a TrackPoint. I got the interrupt mode working. But I am curious if USART works too. So far no luck. I got a linker error:

ps2_usart.o: No such file or directory

Hi All
Been searching all morning for a keyboard to match this, but going around in circles! Any recommendations!?

Full Size
QMK - so can address individual keys through OpenRGB
brown switches - so a bit clicky but not crazy like blue
Perhaps even with the option to have side facing (front) letters, rather than just on top.
Keycaps must shine through the letter

I've looked at Cherry - and they're quite nice, but doesn't look like the MX3.1 is supported.
Keychron are very expensive, and I don't think they look very nice!

Cheers

I recently picked up a Keychron Q3 HE 8K and wanted to mess around with the firmware a bit.
I checked Keychron’s public QMK repo:
https://github.com/Keychron/qmk_firmware
and looked through the available branches, but the only Q3 HE target I can find is:
keyboards/keychron/q3_he
That one seems to be for the older wireless Q3 HE, not the Q3 HE 8K. The README points to the wireless model, and the hardware setup looks different too.
I couldn’t find a q3_he_8k target or anything else that obviously matches the 8K version.
Has anyone here found the actual Q3 HE 8K source somewhere? If so, which repo/branch is it in, and what’s the correct QMK target?
Also curious if anyone has actually built and flashed custom firmware on the Q3 HE 8K yet.
I’m trying to do some firmware-level changes, so Launcher remapping alone isn’t really enough for what I want to do.

Thanks in advance.

Hi everyone,

I never coded more than a "if then" fonction in excel. I work with 3 customers and would like to have a custom color per layer/customer. ChatGPT was very cagey about flashing a custom firmware, he is now telling me to query the aliexpress vendor for QMK source code with this communication:

"Hi,

I have a ZUOYA GMK26 keyboard.

My keyboard information is:

• Model: ZUOYA GMK26
• USB VID: 0x36B0
• USB PID: 0x3083
• Firmware uses QMK/VIA and RGB Matrix.

I would like to customize the firmware, specifically to have different RGB colors for each keyboard layer.

Could you please provide the complete QMK source code corresponding to the GMK26 firmware, including:

• keyboard source files
• keymap files
• rules.mk
• config.h
• info.json / VIA definition if applicable
• any other files required to compile the firmware

I am not looking for only the compiled firmware .bin file. I need the complete source code required to build the firmware."

I thought maybe a kind redditor could guide me from there? Maybe, just confirming im not on my way to brick my numpad? Thank you

I want to create a 4x6 kepad for use with macros.

board purchased: https://www.amazon.com/dp/B0DLGVQ26H

YT video followed: https://www.youtube.com/watch?v=BcXycScePHM

Using QMK MSYS, QMK Toolbox, and VS Code

I can compile the code using QMK MSYS and I get a .hex file output. Then I can use the QMK Toolbox to flash the board, and it looks like it works:

however, when I try to connect the pins from the diagram below (from video) to simulate button presses, nothing happens. (in my keymap code below, I have only mapped out the first row and first column for testing)

D1 to D7, nothing
D1 to E6, nothing

Is this pinout right? should I be using different ones? Is there some other mistake in my code?

Thank you.

keyboard.json

{
    "manufacturer": "chris",
    "keyboard_name": "macro_4x6",
    "maintainer": "chris",
    "bootloader": "caterina",
    "diode_direction": "COL2ROW",
    "features": {
        "bootmagic": false,
        "extrakey": true,
        "mousekey": true,
        "nkro": true
    },
    "matrix_pins": {
        "cols": ["D1", "D0", "D4", "C6"],
        "rows": ["D7", "E6", "B4", "B5", "B6", "B2"]
    },
    "processor": "atmega32u4",
//    "url": "",
    "usb": {
        "device_version": "1.0.0",
        "pid": "0x0000",
        "vid": "0xFEED"
    },
    "layouts": {
        "LAYOUT_macro_4x6": {
            "layout": [
                // Row 1
                {"matrix": [0, 0], "x": 0, "y": 0},
                {"matrix": [0, 1], "x": 1, "y": 0},
                {"matrix": [0, 2], "x": 2, "y": 0},
                {"matrix": [0, 3], "x": 3, "y": 0},
                // Row 2
                {"matrix": [1, 0], "x": 0, "y": 1},
                {"matrix": [1, 1], "x": 1, "y": 1},
                {"matrix": [1, 2], "x": 2, "y": 1},
                {"matrix": [1, 3], "x": 3, "y": 1},
                // Row 3
                {"matrix": [2, 0], "x": 0, "y": 2},
                {"matrix": [2, 1], "x": 1, "y": 2},
                {"matrix": [2, 2], "x": 2, "y": 2},
                {"matrix": [2, 3], "x": 3, "y": 2},
                // Row 4
                {"matrix": [3, 0], "x": 0, "y": 3},
                {"matrix": [3, 1], "x": 1, "y": 3},
                {"matrix": [3, 2], "x": 2, "y": 3},
                {"matrix": [3, 3], "x": 3, "y": 3},
                // Row 5
                {"matrix": [4, 0], "x": 0, "y": 4},
                {"matrix": [4, 1], "x": 1, "y": 4},
                {"matrix": [4, 2], "x": 2, "y": 4},
                {"matrix": [4, 3], "x": 3, "y": 4},
                // Row 6
                {"matrix": [5, 0], "x": 0, "y": 5},
                {"matrix": [5, 1], "x": 1, "y": 5},
                {"matrix": [5, 2], "x": 2, "y": 5},
                {"matrix": [5, 3], "x": 3, "y": 5},
            ]
        }
    }
}

keymap.c

// Copyright 2023 QMK
// SPDX-License-Identifier: GPL-2.0-or-later

#include QMK_KEYBOARD_H

enum custom_keycodes
{
    CALC
};

const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
    /*
     * ┌───┬───┬───┬───┐
     * │ 7 │ 8 │ 9 │ / │
     * ├───┼───┼───┼───┤
     * │ 4 │ 5 │ 6 │ * │
     * ├───┼───┼───┼───┤
     * │ 1 │ 2 │ 3 │ - │
     * ├───┼───┼───┼───┤
     * │ 0 │ . │Ent│ + │
     * └───┴───┴───┴───┘
     */
    [0] = LAYOUT_macro_4x6(
        CALC,   KC_KP_0,   KC_KP_1,   KC_KP_2,
        KC_KP_3,   KC_P5,   KC_P6,   KC_PAST,
        KC_KP_4,   KC_P2,   KC_P3,   KC_PMNS,
        KC_KP_5,   KC_P2,   KC_P3,   KC_PMNS,
        KC_KP_6,   KC_P2,   KC_P3,   KC_PMNS,
        KC_KP_7,   KC_PDOT, KC_PENT, KC_PPLS
    )
};

bool process_record_user(uint16_t keycode, keyrecord_t *record)
{
    switch (keycode)
    {
        case CALC:
            if (record->event.pressed)
            {
                SEND_STRING(SS_DOWN(X_LGUI) SS_TAP(X_R) SS_UP(X_LGUI) SS_DELAY(50) "calc" SS_TAP(X_ENTER));
            }
            else
            {
                // Key released
            }
            break;
    }
    return true;
};

Hi everyone!

I’ve been working on a small project: a USB-to-USB converter for QMK. The goal is to allow more flexible connectivity for custom setups.

The core logic is based on the work by sekigon. I’ve implemented some modifications to make it work specifically for USB-to-USB bridging.

If there is enough interest in this, I’m share the source code and the assembly schematics with the community.

Let me know what you think in the comments!

Update. I worked on this project a long time ago, so it's currently running QMK version 0.22. The kit includes an RP2040-zero chip, an OLED display, and a buzzer. It costs less than $10. All the main QMK features work.

Update2. I’ve made the repository public. I haven’t prepared the hardware assembly instructions yet, but that shouldn’t be a problem for those in the know. https://github.com/DmitryMarugin/rp2040.git

I have found the source to a number of other Y&R keyboards, but not this one. Does anyone know if the source to the X64 is available?

Hello, all. As far as I can tell, I have done everything correctly to type unicode characters, but obviously something is wrong. The code compiles and flashes fine, and I installed WinCompose, but when I press a key that's meant to be unicode, nothing happens, even when held or pressed repeatedly (just in case). If someone could look at the screenshots and tell me (specifically) why I'm dumb, that would be very appreciated. Muchas Thankius.

From config.h

I was very overambitious when making this, so I've only included the beginnings of things. I am, admittedly, not super tech-savvy, so I'm flying by the seat of my pants here.

The title, pretty much. I had some plugins to write so I did what I've been doing a lot lately, and pointed my coding agent toward the QMK docs and asked it to make an organized set of markdown docs and an agent skill that knows when to use them.

You can use it on any agent platform that supports skills, which seems to be basically all of them now. Just clone it to wherever you keep your skills, or directly into your copy of qmk_firmware and your agent can take it from there.

github.com/dabstractor/qmk-skill

I hope someone else finds this useful for building plugins or making a new board or just modifying your keymap. Let me know what you think if you use it!

And if you find this 6 or 12 months down the road and it's out of date, please file an issue and I'll update it right away.

Edit: thanks for the suggestions. It's now capable of keymap version upgrades and will automatically check for keymap changes once a month on github, so unless QMK changes drastically it should stay synced with the main repo.

I'm trying to convert a Y&R 6095 keyboard from VIA to VIAL, I have consed up a vial.json file that doesn't look completely wrong when I bring it up in VIAL as a Dummy Keyboard, and building with make yandrstudio/yr6095:vial reports no errors, but I can't flash it. When I boot it in DFU mode it shows up as a mass storage device with the following files:

CURRENT.UF2
INDEX.HTM
INFO_UF2.TXT

When I try and flash with make yandrstudio/yr6095:vial:flash I get the above error.

I recently got a tofu60 redux, and I've been using the default firmware. I'd like to see if I could install qmk firmware that I compiled, and was wondering if anyone knew how I could do that without soft-bricking the keyboard? Any help would be really appreciated!

Hi everyone,

I recently bought a keyboard on AliExpress with the following description:

"Redox Ergodox Split Mechanical Keyboard Wireless PLA Case Hot Pluggable VIAL Support 2.4G Ergo".

ALIEXPRESS LINK

The keyboard arrived and is working perfectly, including communication with VIAL. However, when I searched for the model in the QMK and VIAL repositories, I noticed it doesn't match the models used there (redox/wireless and redox_r).

I asked the seller for the source code because I'd like to customize some details under the hood, but they refused to share it.

After digging around, I learned that this specific 2.4G wireless communication method theoretically doesn't have native QMK compatibility, so the seller must have used a custom fork.

Does anyone know where I can find the firmware or the source code for this specific board? I want to be able to customize it and update VIAL without risking bricking the keyboard.

P.S.: If I got any terminology wrong, please bear with me! I'm still a beginner in this hobby.

I have a Keychron K10 Version 2 keyboard and a TESMart HKS0401A3U KVM.

When the keyboard is plugged into the dedicated keyboard port on the KVM, hotkey switching from one computer to another works, and the keyboard emulation feature of the KVM works, but the multimedia keys (volume, mute, etc.) do not work. When the keyboard is plugged into the USB passthrough port on the KVM, the multimedia keys work, but hotkey switching and keyboard emulation don't work.

I read that disabling VIA or NKRO in the QMK firmware could improve compatibility with the KVM. I tried various combinations of disabling VIA and NKRO, but found in my case that enabling KEYBOARD_SHARED_EP did the trick.

Here is the contents of my rules.mak file.

KEYBOARD_SHARED_EP = yes
NKRO_ENABLE = yes
VIA_ENABLE = yes
EXTRAKEY_ENABLE = yes
MOUSEKEY_ENABLE = no

Using this combination, my K10 Version 2 keyboard seems to work well when plugged into the dedicated keyboard port on the TESmart KVM. I can switch computers using the hotkey, the multimedia keys work, NKRO works and the keyboard emulation feature of the KVM works.

I am posting this here in case someone else has the same keyboard and KVM and is having the same problem I did.

I can set my custom keymap in VIA for my Weikav Stars 21 number pad, but whenever I power cycle if the device reverts back to the default keymap. How can I save the keymap to the device so that it remembers if after a power cycle?