#encoders y specific buttons into a custom shield nrf52840

1 messages · Page 1 of 1 (latest)

karmic elm
#

did tried to config the encoders first in the .dts, but seems that have less issues in the .overlay to set the hardware and basic labels, to control it from the .keymap, acutally the code can compile and run the firmware but doesnt work

crimson umbra
#

you can just delete the .dts file. if you look through your build logs, you can see it isn't being used

you'll want to read the documentation for how to set up the encoder turns. looks like some LLM might have led you astray here, [strongly suggest not using those](#help message). instead work through the new keyboard shield page, and if you'd like more examples of shields to look at you can check the ZMK repository

as for the switches that are wired to ground instead of being part of your matrix: you'll have to create a direct pin kscan for those, and combine the matrix kscan with the direct pin kscan using a composite kscan. if you can, I'd rewire these to use the pins in your matrix—row 3 pin plus whichever open column pins are most convenient. then you could just use the one matrix kscan for everything

karmic elm
# crimson umbra you can just delete the `.dts` file. [if you look through your build logs, you c...

is not used actually, but was taking it in count still if ever work, since seems that the dts will play over the normal shield info to rewritte, so was an option, did both, used the documentation to the base configuration, mostly to do the overlay wihout the encoders and define the tree and the basics to combos and keymap layers, but also checked LLM to try find a way to the encoders, is my first firmware try and found the docs, kinda hard to find the specific stuff for custom shields out of the basics, the .dts since rewrite how the codes are stacked to the west compilation, was taking it in count while found a proper way to define the encoder data, still not sure how to define the things i need to the encoders and the custom buttons on the overlay, so was an option if it doesn´t let me. seems that most zmk config run into plane text, so yeah out of find the things did tried LLM and to fix systax error, for example not sure yet the proper way to define gpios out of the main matrix or so into the overlay

#

will check those things that you linked and may find any interesting repo to learn the misses that i still have, ty for reply tho

karmic elm
#

there are still confusion doubts for new people like me over file structures, like the encoders labels definition, must the be into the overlay node or out, out give me scope issues, under or before the self encoder definitions, so i do try in both to fast check

karmic elm
karmic elm
#

well in a next build will attach those buttons to the actual matrix, must do another changes aswell