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

[Bug] redox_w's firmware not working whan reconnect the receiver #1136

Closed
sealpp opened this issue Jun 3, 2022 · 3 comments
Closed

[Bug] redox_w's firmware not working whan reconnect the receiver #1136

sealpp opened this issue Jun 3, 2022 · 3 comments
Labels

Comments

@sealpp
Copy link

sealpp commented Jun 3, 2022

Describe the Bug

Precompiled receiver firmware warks fine, but the firmware downloaded form qmk_configurator does not work whan reconnect the receiver.

I must burn the precompiled firmware first and and then the downloaded firmware to work, but once the receiver is restarted(power off or disconnect from my pc), keyboard not responding.

Additional Context?

No response

@sealpp sealpp added the bug label Jun 3, 2022
@yanfali
Copy link
Collaborator

yanfali commented Jun 3, 2022

Qmk doesn't support wireless boards except bluetooth at this time. So not sure how this could work.

https://github.com/mattdibi/redox-keyboard#wireless-implementations

Use zmk or out of tree firmware. Mainline has no support at this time.

@yanfali yanfali closed this as completed Jun 3, 2022
@sigprof
Copy link
Contributor

sigprof commented Jun 3, 2022

Actually this particular board is supported: https://github.com/qmk/qmk_firmware/tree/master/keyboards/redox_w (it uses ATmega32U4 in the receiver board, connected to a nRF51822-based module over UART; the keyboard pieces contain the same nRF51822-based modules, but just report the key state to the receiver dongle).

The underlying problem may be caused by a botched conversion to the UART driver in qmk/qmk_firmware#15479 — this needs some investigation; however, the configurator repo is probably not the proper place for this bug report (the real bug is in the firmware, the configurator just provides a way to build it with a custom keymap).

@sigprof sigprof reopened this Jun 3, 2022
@sigprof
Copy link
Contributor

sigprof commented Jun 3, 2022

Actually the underlying bug was reported at qmk/qmk_firmware#16553, and there is even a suggested fix at qmk/qmk_firmware#17203 — once the fix is merged into the master branch, it would be available in the QMK Configurator too. Please watch the status of that bug instead.

@sigprof sigprof closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants