-
Notifications
You must be signed in to change notification settings - Fork 2.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
cstc40 #517
cstc40 #517
Conversation
Fixed debug key definition on keymap, fixed optional layer indicator on alpha flagged keys code, debounce set on 2
The two versions (daughterboard, single_pcb) need to have a different Vial UID |
keyboards/kprepublic/cstc40/daughterboard/keymaps/default/keymap.c
Outdated
Show resolved
Hide resolved
keyboards/kprepublic/cstc40/daughterboard/keymaps/default/keymap.c
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, you can remove a ton of duplicated boilerplate by moving shared configurations up one level. When I run qmk info -f json
on these two keyboards literally the only differences are the matrix pins:
23,24c23,24
< "cols": ["B15", "B14", "B13", "B10", "B12", "A5", "C4", "A7", "A15", "C10", "C11", "C0"],
< "rows": ["B1", "B0", "C5", "A6"]
---
> "cols": ["C7", "C8", "C9", "A8", "A10", "B10", "A15", "C13", "B6", "B5", "B4", "B3"],
> "rows": ["C12", "C10", "C11", "B0"]
You can move these shared parts into cstc40/config.h
and cstc40/info.json
instead of duplicating it between files. See artemis/paragon
for an example of how this works.
This keyboard fails to build |
I just checked again and i can compile both the default and the vial keymap for the two board variations. What can i do? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, Just for information. We made some modifications to the firmware created by @itsvar8 and tested it with QMK. The pull request was just merged to the QMK project - qmk/qmk_firmware#22154 Regards, |
@xyzz do i need more changes to be merged? |
thanks for the mention! |
No, it looks like it got missed in the queue, sorry about that. |
Ok thanks
Il sab 14 ott 2023, 03:41 xyzz ***@***.***> ha scritto:
… No, it looks like it got missed in the queue, sorry about that.
—
Reply to this email directly, view it on GitHub
<#517 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4TZO7HJLELQ54JT56N273DX7HUVNANCNFSM6AAAAAA3F2BG6M>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
* Create LICENSE * Add files via upload * Add daughterboard version files * Debounce set to 0 to avoid missing registration of quick keypresses * Set debounce to 1 * Update from upstream Fixed debug key definition on keymap, fixed optional layer indicator on alpha flagged keys code, debounce set on 2 * Fixed same UID problem and default keymaps definitions * Fixed daughterboard VIAL keymap * Keymap fixes and tri-layer implementation * Structure rework * Fix rules.mk position * keymap fixes to pass lint check
* Create LICENSE * Add files via upload * Add daughterboard version files * Debounce set to 0 to avoid missing registration of quick keypresses * Set debounce to 1 * Update from upstream Fixed debug key definition on keymap, fixed optional layer indicator on alpha flagged keys code, debounce set on 2 * Fixed same UID problem and default keymaps definitions * Fixed daughterboard VIAL keymap * Keymap fixes and tri-layer implementation * Structure rework * Fix rules.mk position * keymap fixes to pass lint check
* Create LICENSE * Add files via upload * Add daughterboard version files * Debounce set to 0 to avoid missing registration of quick keypresses * Set debounce to 1 * Update from upstream Fixed debug key definition on keymap, fixed optional layer indicator on alpha flagged keys code, debounce set on 2 * Fixed same UID problem and default keymaps definitions * Fixed daughterboard VIAL keymap * Keymap fixes and tri-layer implementation * Structure rework * Fix rules.mk position * keymap fixes to pass lint check
* Create LICENSE * Add files via upload * Add daughterboard version files * Debounce set to 0 to avoid missing registration of quick keypresses * Set debounce to 1 * Update from upstream Fixed debug key definition on keymap, fixed optional layer indicator on alpha flagged keys code, debounce set on 2 * Fixed same UID problem and default keymaps definitions * Fixed daughterboard VIAL keymap * Keymap fixes and tri-layer implementation * Structure rework * Fix rules.mk position * keymap fixes to pass lint check
* Create LICENSE * Add files via upload * Add daughterboard version files * Debounce set to 0 to avoid missing registration of quick keypresses * Set debounce to 1 * Update from upstream Fixed debug key definition on keymap, fixed optional layer indicator on alpha flagged keys code, debounce set on 2 * Fixed same UID problem and default keymaps definitions * Fixed daughterboard VIAL keymap * Keymap fixes and tri-layer implementation * Structure rework * Fix rules.mk position * keymap fixes to pass lint check
Keyboard was shipped with VIAL but the company refused to publish the source so i manually tracked the signle board pcb.
Reddit user u/inigmatics then found out and tested pins for cols and rows of the doughter board version of the pcb.