Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[device-report] Royal kludge RK G68 #70

Closed
2 of 5 tasks
Chumet opened this issue Apr 16, 2024 · 1 comment
Closed
2 of 5 tasks

[device-report] Royal kludge RK G68 #70

Chumet opened this issue Apr 16, 2024 · 1 comment

Comments

@Chumet
Copy link

Chumet commented Apr 16, 2024

Device Info

Part Info

firmware_size: 61440
vendor_id: 0x258a
product_id: 0x0049
bootloader_size: 4096 # necessary if not default, otherwise remove this line
page_size: 2048 # necessary if not default, otherwise remove this line
isp_usage_page: 0xff00 # necessary if not default, otherwise remove this line
isp_usage: 0x0001 # necessary if not default, otherwise remove this line
isp_index: 0 # necessary if not default, otherwise remove this line

Operations Tested

  • Read
  • Write

Platforms Tested

  • linux
  • macos
  • windows

Checksums

  • Bootloader MD5: cfc8661da8c9d7e351b36c0a763426aa
  • Stock Firmware MD5: 9dc83b7be7eefd21418c20a129525e3e without ISP

HID Dump

A dump from usbhid-dump, win-hid-dump or mac-hid-dump

HID Tool Output
# Royal Kludge RK G68 using win-hid-dump
...
258A:0049: SINO WEALTH -
PATH:\\?\hid#vid_258a&pid_0049&mi_01&col03#8&269fe19f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
DESCRIPTOR:
  06  00  FF  09  01  A1  01  85  05  15  00  25  01  35  00  45
  01  65  00  55  00  75  01  95  28  B1  03  C1  00
  (29 bytes)
258A:0049: SINO WEALTH - RK Bluetooth Keyboard
PATH:\\?\hid#vid_258a&pid_0049&mi_01&col05#8&269fe19f&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
DESCRIPTOR:
  06  00  FF  09  01  A1  01  85  0A  09  00  15  00  25  FF  35
  00  45  00  65  00  55  00  75  08  95  40  B1  02  C1  00
  (31 bytes)
...

Questions

@carlossless, I have been able to read without problems, now I want to flash the VIA firmware, there is one called rkg68_via.hex here: https://www.caniusevia.com/docs/download_firmware, I can use sinowealth-kb-tool to write this firmware? Do you think I can leave it like a brick? I would like to be able to use the entire VIA or QMK environment. But seeing that there are so many variants of Royal Kludge (68) I don't know if the firmware offered on the VIA website is suitable for my keyboard. Mine is RGB, ANSI layout with Bluetooth, 2.4Ghz and USB-C, in addition to having 2 USB ports. There is another version of this keyboard, the RK68 that does not have those 2 extra USB ports.

IMG_20240413_193610
IMG_20240413_193618
IMG_20240415_011555

@carlossless
Copy link
Owner

carlossless commented Apr 27, 2024

@Chumet thanks for the report! Especially for those PCB pictures. I should make this part of the issue template so that more people are encouraged to provide them :)

I have been able to read without problems, now I want to flash the VIA firmware, there is one called rkg68_via.hex here: https://www.caniusevia.com/docs/download_firmware, I can use sinowealth-kb-tool to write this firmware? Do you think I can leave it like a brick? I would like to be able to use the entire VIA or QMK environment

QMK (with VIA) will most certainly not work as it's designed specifically for ARM and AVR architectures and the SH68F90A is an 8051 based microcontroller. There must be other variants of this keyboard with an ARM mcu (sonix SN32F268?) which can support QMK.

8051 isn't supported by mainstream compilers like gcc or llvm, and the most popular oss compiler that does support it is sdcc, but it lacks many features that QMKs code relies on, making porting it non-trivial (among other issues).

If you're interested in developing firmware for keyboards like this one, you might want to check out smk, but be warned that it's still in experimental/pre-alpha stage, I don't recommend it for general usage and it is provided as-is with no additional support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants