[device-report] GIBKEY G68 #95
Comments
|
Updated my original post with images and IC info. I can't get a dump from this keyboard.
sinowealth-kb-tool read ouput on SteamOSHere's the list output (keep in mind I have 2 keyboards connected): sinowealth-kb-tool list output on SteamOSHope you can help with this. 🙏 |
|
@mpaterakis there's no collection with On one of your machines, try either: sinowealth-kb-tool read --vendor_id 0x258A --product_id 0x0049 --firmware_size 61440 --isp_usage 0x00 --isp_iface_num 0 dump.hex
# or
sinowealth-kb-tool read --vendor_id 0x258A --product_id 0x0049 --firmware_size 61440 --isp_usage 0x00 dump.hex
What's the error you got? |
|
Thank you so much for the quick reply! I tried your suggestion on all my systems, and here are the results:
Note: Ubuntu 24 LTS was throwing |
|
Not sure if it helps, but here's the |
|
I now noticed the updated IC label which I haven't seen before, which makes me think that the mcu is unlikely a sinowealth part and less so that includes a ISP bootloader that could be interacted with by this tool. Nevertheless, I made some changes in https://github.com/carlossless/sinowealth-kb-tool/tree/device/gibkey-g68 that you can build and try testing with: |
|
Thank you for the changes, I will be trying them tomorrow! I assumed the PID & VID matching the SH68xxxx chips would make it a sinowealth part too, didn't know it could match those by just having an ISP bootloader. BIG sidenote inside, strap in:Googling the IC code results in only 1 review of another keyboard, entirely in Russian, where the reviewer is just as confused about this chip as I am. So I decided to email the address I found on the manual and ask about the part, any firmware files etc but never got a reply. I asked the seller the same thing and they told me the manufacturer refused to send them anything besides the Windows drivers (which is just a utility for remappping the keys and set lighting effects). I asked for the name of the actual manufacturer but haven't gotten a reply. I expect them to be just a random chinese factory though. Finally, I tried using the Arduino dumper, but since the board doesn't have a clear JTAG header, (as you can see in the images) I tried tracing the chip pins to the ones that are at least exposed on it. I couldn't get a match to those, and I also found some weird ground pins on the chip (the right-most bottom pin, in particular) that I couldn't match to any of the sinowealth 8051 schematics out there. I don't know if it's just my lack of experience but it has been a bizzare journey, and your assumption holds quite some weight here. |
|
Well yeah, the fact that it's using sinowealths registered VID could suggest that it's actually a sinowealth part, but the HID descriptor still lacks the ISP report (at least it does not appears how it does on all other devices encountered so far).
This is what I am guessing the HID report id 0x02 is for, making it less likely that it could trigger ISP mode :(
If it's a sinowealth part, I would guess CON3 is JTAG. Are you sure they don't connect to any pins on the chip? Perhaps there are some passives in between? I've seen many sinowealth keyboard (and mice) PCBs use the same ordering of pins, so my guess, if CON3 is JTAG, the pins could be (from left to right, as seen on the picture you shared):
|
|
I used the artifacts from the github actions. So here are the results of the test: SteamOS and Ubuntu: No difference compared to before. "Regular device found" then doesn't find the ISP and keeps retrying. ...and so on.
All of the CON3 pins (except for one, which I confirmed to be VDD) connect to chip pins, that's how I found the weird ground pins I mentioned before too. But I couldn't figure out what was what, the pin locations I was getting didn't match any pinout I found online. |
|
Tested the arduino dumper and nothing. I even tried changing the pins around but nothing. I'll stop experimenting with that so I don't destroy my board though. 😅 |
|
I looked into the drivers for this thing and noticed that it always tries to use "MI_02". To be completely honest I have no idea what that is, I'm not well versed in USB stuff, but the program calls Let me know if this confirms that this chip is a dead end. Appreciate your effort tons, still. 🙏 |
|
According to https://learn.microsoft.com/en-us/windows-hardware/drivers/hid/hidclass-hardware-ids-for-top-level-collections MI_02 should refer to the interface number, so it's targeting a different report than where Report ID = 2 resides (it's in interface 1). For both of our reference, the HID descriptor for the 02 interface is: |
|
First of all, happy new year! In case someone else stumbles across this thread, I made a fully functional, open source alternative to the official configuration software for this keyboard. The official software is riddled with bugs and GIBKEY support refused to give me any source code or schematics. So I did it myself: https://github.com/mpaterakis/GIBKEY-G68-Config I understand that this not really related to the dumper, but at least it's a solution to my own problem and wanted to mention it. |
Device Info
???YJX1064Part Info
Operations Tested
Platforms Tested
Checksums
deadbeefdeadbeefdeadbeefdeadbeefbeefcafebeefcafebeefcafebeefcafe(shown when runningsinowealth-kb-tool read -b ...)HID Dump
HID Tool Output
PCB Photos
PCB Photo Dump
The text was updated successfully, but these errors were encountered: