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

Issue regarding tri-state lacks bindings #6

Closed
baggiiiie opened this issue Mar 18, 2025 · 5 comments
Closed

Issue regarding tri-state lacks bindings #6

baggiiiie opened this issue Mar 18, 2025 · 5 comments

Comments

@baggiiiie
Copy link

Hi @dhruvinsh,

I have not touched my zmk config for a while and made some changes (not related to tri-state) just now. During build process I received this error:

devicetree error: binding controller <Node /behaviors/swapper_ctrl in '/__w/zmk-config/zmk-config/modules/zephyr/zephyr/misc/empty_file.c'> for <Node /keymap/lower_layer in '/__w/zmk-config/zmk-config/modules/zephyr/zephyr/misc/empty_file.c'> lacks binding
see source git action here

is this related to the recent commit made here? im not well-versed in this matter, and failed to find a solution on zmk's issues and other sources.

Please advice what i should do, or where i should go to seek a solution. fyi this is my tri-state config: https://github.com/baggiiiie/zmk-config/blob/master/config/includes/behaviors_tristate.dtsi

Thanks in advance!

@dhruvinsh
Copy link
Owner

Hey @baggiiiie, I have compiled it locally against my config and it was fine.

I have fired github action against my config, lets see how it goes, here

@dhruvinsh
Copy link
Owner

dhruvinsh commented Mar 18, 2025

Update: looks fine on my side, something must be in your config, specially related to mouse? there are some good amount of changes for mouse (pointing device) on zmk.

Here it your logs,

In file included from /__w/zmk-config/zmk-config/config/corne.keymap:15,
                 from <command-line>:
/__w/zmk-config/zmk-config/config/includes/mouse.dtsi:14: warning: "ZMK_MOUSE_DEFAULT_MOVE_VAL" redefined
   14 | #define ZMK_MOUSE_DEFAULT_MOVE_VAL 2500
      | 
In file included from /__w/zmk-config/zmk-config/config/includes/mouse.dtsi:1:
/__w/zmk-config/zmk-config/zmk/app/include/dt-bindings/zmk/mouse.h:27: note: this is the location of the previous definition
   27 | #define ZMK_MOUSE_DEFAULT_MOVE_VAL 600
      | 
/__w/zmk-config/zmk-config/config/includes/mouse.dtsi:15: warning: "ZMK_MOUSE_DEFAULT_SCRL_VAL" redefined
   15 | #define ZMK_MOUSE_DEFAULT_SCRL_VAL 20
      | 
/__w/zmk-config/zmk-config/zmk/app/include/dt-bindings/zmk/mouse.h:31: note: this is the location of the previous definition
   31 | #define ZMK_MOUSE_DEFAULT_SCRL_VAL 10
      | 
devicetree error: binding controller <Node /behaviors/swapper_ctrl in '/__w/zmk-config/zmk-config/modules/zephyr/zephyr/misc/empty_file.c'> for <Node /keymap/lower_layer in '/__w/zmk-config/zmk-config/modules/zephyr/zephyr/misc/empty_file.c'> lacks binding

@baggiiiie
Copy link
Author

baggiiiie commented Mar 19, 2025

something must be in your config, specially related to mouse?

@dhruvinsh thanks for the quick response!!
the mouse issue only raises a warning, I have fixed the warning, but the build still failed; and the divcetree error related to tri-state still persists and should be what's causing the failure.

from my commit and build history you can see the exact same keymap worked 5 months ago, and i suspects it's what's changing in zmk repo zmkfirmware/zmk#1494 and zmkfirmware/zmk#2409, though im not technical enough to understand this.

Surprised to see your build works thought, despite the way i used tri-state in both behavior definition and keymap are basically the same. Do you have any idea of the cause of this? or who i should go to for this issue?

@dhruvinsh
Copy link
Owner

In last 5 months lot of things have changed on the ZMK side.
Only thing i can think of is try forking tri-state repository, remove my commit and see if that works for you.

@baggiiiie
Copy link
Author

@dhruvinsh thank you so much for your time and replies, i've found the root cause of this after some digging on discord.

this is due to some change at urob i believe. will close this issue now.

have a great day ahead!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants