Keys mapped Incorrectly after flashing hex file

[zzzarfar]

I was following the YouTube tutorial, and after flashing the firmware with the hex file provided and connecting my keyboard to via, most of my keys were mapped to the wrong place (okl' for Wasd, 1 for backspace, etc.). I tried flashing the original firmware I found in the extra folder, but nothing changed. Bought the keyboard literally yesterday off Amazon, and a lot of the recent comments under the YouTube video all report the exact same problem, and I can't seem to find a solution or cause anywhere. I have the wired Rk65 ANSI QMK/VIA model, and I followed every step in the YouTube video. Nothing I try will fix it, including trying to just remap the keys using via.

[Edduaardo]

Try compiling your own firmware.

[Raybo58]

I'm having the same issue.

[jvwdev]

I had the same issue, have a r65 with product id e508.
But I made a backup with wb32-dfu-update_cli before flashing this.

Couldn't get the device into DFU mode and found out that the reset button is just on the right of the space bar key, underneath the foam.

I can share the e508 version dump if anybody needs it.

[jvwdev]

r65-e508.zip

[iamdanielv]

Hopefully that will help the people who are having issues. You rock!

My keyboard is the first gen, I can't test it - so no idea if it works.

[jvwdev]

After some trial and error I found the pins for the matrix, which seem to work fine, even the knob button (mute) is working.

But I can't find the pins for knob/vol up/down, I think I tried all available pins. Could it be that they use extra hardware ?
I don't feel like opening my board, so for now I keep the encoder disabled.

keyboard.json

[jvwdev]

I put my code here: https://github.com/jvwdev/r65

[iamdanielv]

I just looked at https://github.com/jvwdev/r65/blob/master/rk/r65/keyboard.json#L10C1-L10C26

and noticed that encoder is set to false. Maybe a naive question, not sure if you did that on purpose? If it's set to false, the knob will not work.

The pins from the micro controller should be enough to handle without extra hardware, so it should be a matter of seeing what pins are free.

Interesting that they totally changed the col pins, that feels like it would require a big redesign of the PCB. Good job figuring out the new layout of the cols!

[jvwdev]

I disabled the encoder on purpose.

Interesting that they totally changed the col pins, that feels like it would require a big redesign of the PCB. Good job figuring out the new layout of the cols!

Thanks, it took a while!

The pins from the micro controller should be enough to handle without extra hardware, so it should be a matter of seeing what pins are free.

That's what I thought as well, but I tried all GPIO A/B/C, but can't find the correct pins for the encoder. I didn't try the LEDs as extensively, the only LED that works is the 3rd LED, which functions as caps lock.

Maybe it's something with the existing LED pins. I will try that later.

I'm already happy that I can flash my keymap to it, which makes the keyboard much more useful for me :)