Working on the Machenike K500-K61
Opened this issue · 6 comments
Support for this is already in sinowealth-kb-tool, and Rangoli. And so writing a layout shouldn't be hard at all, I just don't own a arduino at the moment to reflash the keyboard (I own several esp32's and rp2040s, but no arduinos) and I'm scared of bricking it at the moment. This will be a placeholder issue untill I either piece together the information from the Royal Kludge software (because, i guess they all use the same software), or I trace all of the traces on the board & buy a Arduino (which I don't wanna do).
Cfg.ini from K500 software (probably very useful): https://pastebin.com/tAKybZS0
For the RK61 the same Cfg.ini looks like this: https://pastebin.com/a5t6LvxF
The K500 software is made only for the K500, so it's Cfg.ini is not combined and it is in app/Cfg.ini, for the RK61 it is combined and it's located in app/Dev/00C7/Cfg.ini.
You can unpack these EXE's via https://github.com/dscharrer/innoextract
Hey, @fucksophie, I would like to help if it is possible I also have a Machenike B61 but I don't have an arduino too, yesterday I tried to trace the board, and here are my finds:
Machenike B61.pdf I don't if helps in something.
I think @carlossless would understand this way better, as I don't know how the whole GPIO part of SMK works.
While digging into this, I wrote a layout.c for the B500-K61. Hopefully it works.
layout.txt
Hey, @fucksophie, I would like to help if it is possible I also have a Machenike B61 but I don't have an arduino too, yesterday I tried to trace the board, and here are my finds:
Machenike B61.pdf I don't if helps in something.
These don't seem to be based on the actual pins for the MCU, such as D1 and P1 and etc. Could you provide a slightly more comprehensive document for these, and I'll be able to implement this for SMK.
Follow the pinout found here: https://www.sinowealth.com/api/pre/json_go/file_xz?tool_id=599&type=2
I just don't own an arduino at the moment to reflash the keyboard
Owning an Arduino isn't going to be enough. There's only a dumper currently openly available, no writers.
i guess they all use the same software
RK does use similar firmware for some of their devices, but the stock fw varies a lot between brands.
or I trace all of the traces on the board & buy a Arduino (which I don't wanna do).
Unless you can reverse the GPIO (and the PWM) pins out of the firmware binary (these ghidra extensions might help), you might still have to resort to tracing things. Unfortunately, these keyboards are not all connected the same way (compare nuphy-air60/kbdef.h and eyooso-z11/kbdef.h.