-
Notifications
You must be signed in to change notification settings - Fork 169
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
Half Without I2C Pull-up Resistors Is Unusable by Itself #98
Comments
I actually have the same problem when configuring the keyboard with I2C and EE_hands, can you elaborate how did you activate the internal pull-ups on PD0 and PD1? Thanks! |
I didn't encountered this behaviour before. Maybe they changed something in the latest version of QMK and internal pull-ups are not activated by default? I'll try and take a look into it. Thank you for pointing this out. |
Sorry for the late reply. I did it this way: yterhorst/qmk_firmware@c92da2d
I looked at the latest version and also previous commits and couldn't find anything that looked like it enabled the internal pull-ups. Keep in mind this issue only surfaces in a scenario where both halves are used together over I2C and also (without reflashing) shall be used independently (for example as game controllers on another layer). |
Hi,
I have built the wired version of the Redox and so far it's really fun to type on. I have found a small quirk however and was able to fix it. It doesn't seem to be referenced anywhere in the documentation. Maybe it would be helpful to add it :)
If I configure
I2C
andEE_HANDS
(other than that I am using the default configuration) in the latest QMK firmware and connect the half without the pull-up resistors to USB without connecting it to the other half, it locks up and barely outputs anything or if it does, multiple key presses.The culprit seems to be the floating I2C bus. Either spreading the resistance over both halves (using 10k resistors in all 4 footprints) or activating the internal pull-ups on PD0 and PD1 fixed the issue for me.
The text was updated successfully, but these errors were encountered: