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] X-Bows Knight Plus enters reboot loop when setting to Direct mode for OpenRGB with initial RGB values set to 255. #13899

Closed
Inventor22 opened this issue Aug 5, 2021 · 1 comment

Comments

@Inventor22
Copy link

Inventor22 commented Aug 5, 2021

Describe the Bug

System Information

  • Keyboard:
    • Revision (if applicable): X-Bows Knight Plus
  • Operating system:
    • Windows 10 Pro
  • AVR GCC version:
    avr-gcc.exe (GCC) 8.4.0
  • ARM GCC version:
    arm-none-eabi-gcc.exe (GCC) 10.1.0
  • QMK Firmware version:
    0.10.51
  • Any keyboard related software installed?
    No

Additional Context

When entering Direct mode for Knight Plus through either OpenRGB or cycling through RGB modes via the keyboard with Fn+Q, the keyboard will enter a reboot loop until unplugged. The default RGB values when entering Direct mode are 255 for all channels.

If the default values are changed to 254, the keyboard does not reboot continuously.
Default values are modified in the config.mk file by adding the following overrides:

#define OPENRGB_DIRECT_MODE_STARTUP_RED 254
#define OPENRGB_DIRECT_MODE_STARTUP_GREEN 254
#define OPENRGB_DIRECT_MODE_STARTUP_BLUE 254

rules.mk
config.txt

@Inventor22 Inventor22 changed the title [Bug] X-Bows keyb [Bug] X-Bows Knight Plus enters reb Aug 5, 2021
@Inventor22 Inventor22 changed the title [Bug] X-Bows Knight Plus enters reb [Bug] X-Bows Knight Plus enters reboot loop when setting to Direct mode for OpenRGB with initial RGB values set to 255. Aug 5, 2021
@zvecr
Copy link
Member

zvecr commented Aug 6, 2021

OPENRGB support isnt merged, so you will have to seek support on the users fork(https://github.com/Kasper24/QMK-OpenRGB), or maybe their PR (#13036).

@zvecr zvecr closed this as completed Aug 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants