-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
IBM 5576-002/003 support #688
Comments
|
Apologies for my dumb questions, I wonder if the ibm 5576-002 has been supported? Can I use the IBMPC-USB Converter (ATmega32U4) preset on an ibm 5576-002 keyboard? |
The latest firmware built has preliminary support for the keyboard but has not been tested. Posting debug log here would be helpful. You can chceck debug prints using |
I can confirm that the firmware mostly worked at IBM, 5576-002 except for some minor issues: The" , " key on the numpad, registering rE0 r41 rE0 rF0 r41 in hid_listen, but it functions as "printscreen" key with the firmware generated on the online editor. (Link to it: https://bit.ly/3B0nFcS) |
And thanks for your awesome work! |
Thanks for your report! I fixed scan code translation of the key. It should work as 'Keypad *' key. This is patch, just for reference.
|
The "," key on the numpad now functions currectly, awesome job! |
Great! Just updated repo at 56e88e8. Online editor should be also fixed soon, you may need to reload browser. Let me know if you have any issue. Thanks |
The keyboard starts up with Code Set 2 by and keeps Japanese specific keys disabled by default.
https://www.win.tue.nl/~aeb/linux/kbd/scancodes-8.html#bradford
To enable the Japanese keys you have to use Code Set 82h and some tweaks.
Code Set 82h: https://github.com/tmk/tmk_keyboard/wiki/IBM-PC-AT-Keyboard-Protocol#ibm-5576-scan-codes-set
Keyboard ID: https://github.com/tmk/tmk_keyboard/wiki/IBM-PC-AT-Keyboard-Protocol#ibm-5576-scan-codes-set
5576-002: AB90
5576-003: AB91
This is related to 5576-001 support. #685
The text was updated successfully, but these errors were encountered: