-
-
Notifications
You must be signed in to change notification settings - Fork 39.6k
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] CONVERT_TO
RP2040 targets broken with UART_DRIVER_REQUIRED=yes
#22631
Comments
The real problem here is that The proper way to fix things would be to implement support for the |
Thanks for the feedback.
Not strictly true, although I get your point with the current QMK implementation. I have the serial working with the raw SIO driver in a dedicated branch that we use for our CI/precompiled builds. There are a lot of changes in that branch though and I haven't had the gusto to open a PR to get it into upstream QMK.
That seems enough to add with a preprocessor check and was already have stubbed it out so that the boards compile with the converter in my working branch; happy to explore it further if it's a potential workaround for this. I'm not necessarily looking to drive changes to QMK on behalf of contributors, but rather interested on feedback as to whether there are any changes or workarounds I can take advantage of on my end. |
Code like that is probably not suitable for the upstream QMK as is — it should be moved to
With the current implementation of ifeq ($(strip $(UART_DRIVER_REQUIRED)), yes)
OPT_DEFS += -DHAL_USE_SERIAL=TRUE
QUANTUM_LIB_SRC += uart.c
endif Enabling |
Hey, this issue is affecting me as well. I can't compile qmk for my nullbitsco/snap keyboard because I'm using a Bit-c Pro (which is RP2040-based). What're the next steps here? It seems like the fundamental issue is that |
Related to #17744 |
This should be solved with #22839 being merged to |
Whoa, thanks @KarlK90! #22839 is awesome. The original issue is resolved, but is one step away from working turnkey:
I confirmed changing |
Weirdly enough I'm trying to build the firmware for the 0xCB-Helios and I'm getting the same error message: qmk compile -kb nullbitsco/nibble -km lucasmaffazioli -e CONVERT_TO=helios
|
Describe the Bug
I'm fixing up the Bit-C PRO RP2040 converters and have run into an issue with
UART_DRIVER_REQUIRED
, which has been introduced in the latest breaking change merge. All extra source included inrules.mk
fail to compile with the following error:Keyboard Used
nullbitsco/nibble
Link to product page (if applicable)
No response
Operating System
Ubuntu 22.04
qmk doctor Output
Is AutoHotKey / Karabiner installed
Other keyboard-related software installed
No response
Additional Context
The converter updates are minor changes to resolve missing LED pins during compilation.
The text was updated successfully, but these errors were encountered: