To Whom it May Concern
With the keyclicks maintainer currently MIA and the only existing source code hosted in this repository currently being broken when working with latest versions of qmk & vial-qmk (at the time of writing), I wanted to leave a message for anyone who might be running into the same problems as I did when wanting to update the firmware on their board.
Note that I'm referring exclusively to the QMK firmware, and NOT the nRF firmware for the wireless connectivity chips. If you have problems with wireless connectivity (as some people report in the discord server), you might try the your luck with the method for updating the wireless chips in boards and dongle that's described in the keyclicks docs. But I haven't had issues and haven't performed these steps myself.
For context: I got a second-hand w-corne-choc with the 2.4GHz receiver dongle and wanted to access vial features that appeared to be disabled on my board (in particular space-cadet keys).
The Gist of It
I will point anyone to my fork of qmk-vial (you might have to look for the keyclicks-w-corne-choc branch), where I merged the keyboards folder with the one in this KeyClicks/Split-Keyboard repo, and updated the keyclicks definitions for the w-corne-choc-v3 in order to make it compile with my preferred settings (currently only enabling space-cadet keys in /keymaps/vial/rules.mk).
In the commit history you will find the individual steps I had to undertake to get it working.
In the readme.md of the w-corne-choc-v3 you will find some notes of mine regarding my changes and elaborated instructions that I hope might help you to safely flash your boards (or rather the dongle, because the QMK/vial software appears to run exclusively on the dongle, not the boards themselves).
Note that the dongle (at least mine) appears to employ the STM32F103 chip, which has limited capacity for your configurations. I believe it has a 64kB capacity, but don't quote me on that. The firmware available on the keyclicks website sits around 37kB and my configuration compiled to around 42kB.
Discord
There is also a discord server (not very active) for keyclicks board owners where you may also be able to ask your questions to the community. The invite link is not available on the website, but can be found in an old reddit post by the keyclicks account. I'll also share it here:
https://discord.com/invite/5RfE9gKTMP
Or if you don't trust me but do trust the keyclicks reddit account, you can find it here.
Disclaimer
I must mention that you're doing anything at your own risk and I cannot and do not provide guarantees about the consequences of your actions. I have successfully compiled and flashed using the currently available qmk & vial-qmk build environment and the changes in my fork, but your environment or keyboard may be different and I cannot and do not take responsibility if something fails.
Furthermore, I am far from a qmk or vial expert and will not pretend that my changes are infallible or complete. I just had to go through a bit of a frustrating process and I'd like to prevent others from having to go through the same if it can be prevented.
To Whom it May Concern
With the keyclicks maintainer currently MIA and the only existing source code hosted in this repository currently being broken when working with latest versions of qmk & vial-qmk (at the time of writing), I wanted to leave a message for anyone who might be running into the same problems as I did when wanting to update the firmware on their board.
Note that I'm referring exclusively to the QMK firmware, and NOT the nRF firmware for the wireless connectivity chips. If you have problems with wireless connectivity (as some people report in the discord server), you might try the your luck with the method for updating the wireless chips in boards and dongle that's described in the keyclicks docs. But I haven't had issues and haven't performed these steps myself.
For context: I got a second-hand w-corne-choc with the 2.4GHz receiver dongle and wanted to access vial features that appeared to be disabled on my board (in particular space-cadet keys).
The Gist of It
I will point anyone to my fork of qmk-vial (you might have to look for the
keyclicks-w-corne-chocbranch), where I merged thekeyboardsfolder with the one in thisKeyClicks/Split-Keyboardrepo, and updated the keyclicks definitions for the w-corne-choc-v3 in order to make it compile with my preferred settings (currently only enabling space-cadet keys in/keymaps/vial/rules.mk).In the commit history you will find the individual steps I had to undertake to get it working.
In the
readme.mdof thew-corne-choc-v3you will find some notes of mine regarding my changes and elaborated instructions that I hope might help you to safely flash your boards (or rather the dongle, because the QMK/vial software appears to run exclusively on the dongle, not the boards themselves).Note that the dongle (at least mine) appears to employ the STM32F103 chip, which has limited capacity for your configurations. I believe it has a 64kB capacity, but don't quote me on that. The firmware available on the keyclicks website sits around 37kB and my configuration compiled to around 42kB.
Discord
There is also a discord server (not very active) for keyclicks board owners where you may also be able to ask your questions to the community. The invite link is not available on the website, but can be found in an old reddit post by the keyclicks account. I'll also share it here:
https://discord.com/invite/5RfE9gKTMP
Or if you don't trust me but do trust the keyclicks reddit account, you can find it here.
Disclaimer
I must mention that you're doing anything at your own risk and I cannot and do not provide guarantees about the consequences of your actions. I have successfully compiled and flashed using the currently available qmk & vial-qmk build environment and the changes in my fork, but your environment or keyboard may be different and I cannot and do not take responsibility if something fails.
Furthermore, I am far from a qmk or vial expert and will not pretend that my changes are infallible or complete. I just had to go through a bit of a frustrating process and I'd like to prevent others from having to go through the same if it can be prevented.