Compile errors

[Raybo58]

I have followed these instructions to the letter, but I keep getting a long string of error messages. As follows....

Generating: .build/obj_rk_r65_via/src/info_config.h [OK]
Generating: .build/obj_rk_r65_via/src/default_keyboard.c [OK]
Generating: .build/obj_rk_r65_via/src/default_keyboard.h [OK]
Compiling: keyboards/rk/r65/r65.c [OK]
Compiling: .build/obj_rk_r65_via/src/default_keyboard.c [OK]
Compiling: quantum/keymap_introspection.c In file included from ./keyboards/rk/r65/keymaps/via
from quantum/keymap_introspection.c:9:
./keyboards/rk/r65/keymaps/via/keymap.c:74:117: error: 'RGB_MOD' undeclared here (not in a function); did you mean 'RGB_M_T'?
74 | _______, _______, _______, _______, _______, _______, _______, _______, _______, MO(8), _______, KC_HOME, KC_SCRL, RGB_MOD, KC_INS,
| ^~~~~~~
./.build/obj_rk_r65_via/src/default_keyboard.h:36:72: note: in definition of macro 'LAYOUT'
36 | { k1A, k1B, k1C, k1D, k1E, k1F, k1G, k1H, k1I, k1J, k1K, k1L, k1M, k1N, k1O }, \
| ^~~
./keyboards/rk/r65/keymaps/via/keymap.c:76:74: error: 'RGB_HUI' undeclared here (not in a function)
76 | _______, _______, _______, _______, _______, NK_TOGG, _______, _______, RGB_HUI, _______, _______, MO(8), RGB_VAI, KC_END,
| ^~~~~~~
./.build/obj_rk_r65_via/src/default_keyboard.h:38:47: note: in definition of macro 'LAYOUT'
38 | { k3A, k3B, k3C, k3D, k3E, k3F, k3G, k3H, k3I, k3J, k3K, k3L, XXX, k3N, k3O }, \
| ^~~
./keyboards/rk/r65/keymaps/via/keymap.c:76:108: error: 'RGB_VAI' undeclared here (not in a function)
76 | _______, _______, _______, _______, _______, NK_TOGG, _______, _______, RGB_HUI, _______, _______, MO(8), RGB_VAI, KC_END,
| ^~~~~~~
./.build/obj_rk_r65_via/src/default_keyboard.h:38:72: note: in definition of macro 'LAYOUT'
38 | { k3A, k3B, k3C, k3D, k3E, k3F, k3G, k3H, k3I, k3J, k3K, k3L, XXX, k3N, k3O }, \
| ^~~
./keyboards/rk/r65/keymaps/via/keymap.c:77:57: error: 'RGB_SPD' undeclared here (not in a function); did you mean 'RGB_RED'?
77 | SWITCH_FN, GU_TOGG, _______, EE_CLR, _______, _______, RGB_SPD, RGB_VAD, RGB_SPI
| ^~~~~~~
./.build/obj_rk_r65_via/src/default_keyboard.h:39:62: note: in definition of macro 'LAYOUT'
39 | { k4A, k4B, k4C, XXX, XXX, k4F, XXX, XXX, k4I, k4J, XXX, k4L, XXX, k4N, k4O } \
| ^~~
./keyboards/rk/r65/keymaps/via/keymap.c:77:66: error: 'RGB_VAD' undeclared here (not in a function); did you mean 'RGB_RED'?
77 | SWITCH_FN, GU_TOGG, _______, EE_CLR, _______, _______, RGB_SPD, RGB_VAD, RGB_SPI
| ^~~~~~~
./.build/obj_rk_r65_via/src/default_keyboard.h:39:72: note: in definition of macro 'LAYOUT'
39 | { k4A, k4B, k4C, XXX, XXX, k4F, XXX, XXX, k4I, k4J, XXX, k4L, XXX, k4N, k4O } \
| ^~~
./keyboards/rk/r65/keymaps/via/keymap.c:77:75: error: 'RGB_SPI' undeclared here (not in a function)
77 | SWITCH_FN, GU_TOGG, _______, EE_CLR, _______, _______, RGB_SPD, RGB_VAD, RGB_SPI
| ^~~~~~~
./.build/obj_rk_r65_via/src/default_keyboard.h:39:77: note: in definition of macro 'LAYOUT'
39 | { k4A, k4B, k4C, XXX, XXX, k4F, XXX, XXX, k4I, k4J, XXX, k4L, XXX, k4N, k4O } \
| ^~~
In file included from platforms/chibios/chibios_config.h:18,
from platforms/chibios/platform_deps.h:19,
from quantum/quantum.h:18,
from ./.build/obj_rk_r65_via/src/default_keyboard.h:28:
quantum/compiler_support.h:13:31: error: static assertion failed: "Number of encoder_map layers doesn't match the number of keymap layers"
13 | # define STATIC_ASSERT _Static_assert
| ^~~~~~~~~~~~~~
quantum/keymap_introspection.c:65:1: note: in expansion of macro 'STATIC_ASSERT'
65 | STATIC_ASSERT(NUM_KEYMAP_LAYERS_RAW == NUM_ENCODERMAP_LAYERS_RAW, "Number of encoder_map layers doesn't match the number of keymap layers");
| ^~~~~~~~~~~~~
[ERRORS]
|
|
|
make: *** [builddefs/common_rules.mk:362: .build/obj_rk_r65_via/quantum/keymap_introspection.o] Error 1

[iamdanielv]

If you are using the latest version of QMK, the RGB key codes have changed.

Check out the documentation:
https://docs.qmk.fm/features/rgb_matrix

The important ones are:
RM_HUEU Cycle through hue
RM_HUED Cycle through hue in reverse
RM_SATU Increase the saturation
RM_SATD Decrease the saturation
RM_VALU Increase the brightness level
RM_VALD Decrease the brightness level

[Raybo58]

My coding skills are rather limited. I wouldn't even know where to start with replacing these references. I'm just trying to get the keyboard I just bought working again. I'm hoping that infanjmdn will update the code.

[iamdanielv]

If you already flashed the firmware from the extras folder, then you might have a different version of the PCB. Even if he fixed the RGB error it wouldn't help.

It seems that some of the physical pis might be connected differently. We were working off of the original PCB, but it seems there is a new version out. Without having a new version, there is not much we can do, since we need to know what has changed.

[Raybo58]

So, you're saying there are multiple versions of the QMK VIA ANSI keyboard with the 342D:E453 hardware IDs? I mean the keyboard actually works, to some extent. I can connect to VIA and configure the backlighting any way I wish, but the key mapping is all wrong. The function key, the Escape key, and Control keys don't work. If I type A S D, it outputs K L and the apostrophe instead. If I try to remap them, nothing actually changes. The problem started when I flashed firmware with VIA and SignalRGB support. The only reason I need to compile the original firmware is to restore the proper keyboard layout. I've tried flashing 3 other firmware, but I always get this result.

[iamdanielv]

@Raybo58 Yeah, probably the Row / Columns are connected differently.

The pins are specified in the keyboard.json file:

    "matrix_pins": {
        "cols": ["C9", "C8", "C7", "A8", "C6", "B14", "B13", "B12", "C1", "C2", "A10", "C3", "A6", "C4", "C5"],
        "rows": ["A1", "A2", "A3", "A4", "C13"]
    },

The way the firmware works is it scans rows and columns to know what character to output. If the new PCB has a different order, it would output a different key than what we originally had. This matches your statement: "If I type A S D, it outputs K L and the apostrophe instead."

More details in the documentation (this is very hardware specific): https://docs.qmk.fm/porting_your_keyboard_to_qmk#matrix-configuration

"The only reason I need to compile the original firmware is to restore the proper keyboard layout." <-- the extras folder has the original firmware for the version of the PCB we have and how it has the pins wired. If your PCB is different, you are back to square one, the original firmware was for the version of the PCB we had, you seem to have a different PCB.

TL;DR:
The pins seem to be wired differently, would need to figure out what has changed

[EmosTerea]

Thanks for the clarification!
Is there a way to at least revert it to the original state until its resolved?

[iamdanielv]

@EmosTerea You would have to reach out to RK and ask them to provide the updated firmware.

I went to their site, but couldn't find the firmware: https://rkgamingstore.com/products/r65-wired-gaming-mechanical-keyboard

You might have better luck emailing them.

[Raybo58]

I've been exchanging emails with them for the last two weeks. They spent the first 10 days asking me to submit the same information over and over again, after I'd submitted everything they asked for and more. They finally sent me a beta version of the QMK Toolbox and an updated firmware file. All it did was change the PID I was detecting from E453 to E481. The keyboard layout issues still persist. I sent them a detailed report of my results last Tuesday and they have yet to respond.

…

________________________________ From: Daniel ***@***.***> Sent: Sunday, December 28, 2025 2:07 AM To: irfanjmdn/r65 ***@***.***> Cc: Raymond ***@***.***>; Mention ***@***.***> Subject: Re: [irfanjmdn/r65] Compile errors (Issue #11) [https://avatars.githubusercontent.com/u/1767914?s=20&v=4]iamdanielv left a comment (irfanjmdn/r65#11)<#11 (comment)> @EmosTerea<https://github.com/EmosTerea> You would have to reach out to RK and ask them to provide the updated firmware. I went to their site, but couldn't find the firmware: https://rkgamingstore.com/products/r65-wired-gaming-mechanical-keyboard You might have better luck emailing them. — Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGFVP5WCFGVCC7DUBWRKAYL4D6TUXAVCNFSM6AAAAACPLRPHUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOJUGYZDIMBSGA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[EmosTerea]

they have sent me this:
https://drive.google.com/file/d/1Zh2henr0_1Yb6fjSYCCE8FBJJNb-5flw/view

[iamdanielv]

@EmosTerea how'd it go with that file? Did that get your KB working again?

[EmosTerea]

@iamdanielv nope, it didin't work

[jvwdev]

@EmosTerea you can try my original/stock firmware i dumped for the the new revision of the r65: https://github.com/jvwdev/r65/raw/refs/heads/master/stock_firmware.bin

[EmosTerea]

@jvwdev this worked! Thanks! Do you have any idea how to make VIA work now?

[jvwdev]

@EmosTerea I couldn't find the correct via json file for the stock firmware.

If you don't mind a few missing features (rotary encoder / status leds);
I added support for VIA in my repo. It's my personal keymap, but you can tweak it with VIA.