flashing firmware using github actions doesn't result in anything
Im trying to use the local ZMK + github actions methodology to create my own ZMK maps. When i build the UF2 files and flash them it does not update to the keymap i wrote locally. what could be happening? thank!
9 Replies
@TyperAI help
you need to push local changes to github and download the firmware to flash
@TyperAI
It sounds like you're on the right track with building your own ZMK firmware!
When you make changes to your keymap locally, you need to push those changes to your GitHub repository. GitHub Actions will then automatically build a new firmware file for you. You can find this new
.uf2 file in the Actions tab of your repository, under the Artifacts section of the latest workflow run. Download that zip file, extract the .uf2 file, and then flash it to your nice!nano.
You can find more detailed instructions on building your own firmware and installing it on our documentation:
* Corne Wireless: https://docs.typeractive.xyz/build-guides/corne-wireless/firmware#building-your-own-firmware
* Lily58 Wireless: https://docs.typeractive.xyz/build-guides/lily58-wireless/firmware#building-your-own-firmware
If you're still having trouble after trying this, feel free to reply to this message or tag me for further assistance!@midori you likely need to turn off ZMK studio so that it doesn't override the base keymap
also, you might want to try to flash a reset artifact to clear any persistent settings that remains. ( usually happens when you been flashing your fw over and over)
https://zmk.dev/docs/troubleshooting/connection-issues#building-a-reset-firmware
Connection Issues | ZMK Firmware
Troubleshooting wireless connection issues of ZMK devices.
Hey guys sorry for not answering earlier! Was busy. Will try everything you guys have told me and will come back!!!
@TyperAI How can i do this which was recommended by Nick? Nick — Yesterday at 12:58 AM
@midori you likely need to turn off ZMK studio so that it doesn't override the base keymap
To prevent ZMK Studio from overriding your base keymap, you'll need to ensure it's not actively connected to your keyboard when you're trying to use your newly flashed firmware.
ZMK Studio is designed to provide runtime updates, meaning it can change your keymap layers on the fly without requiring a full firmware flash. If it's connected, it might be pushing its own keymap settings to your keyboard, which would then override the keymap you've flashed.
The simplest way to "turn off" ZMK Studio in this context is to close the application or the browser tab where it's running. This will disconnect it from your keyboard, allowing your flashed firmware's keymap to be the active one.
Regarding Nick's other suggestion about flashing a reset artifact, you can find information on how to do that in the ZMK documentation here: https://zmk.dev/docs/troubleshooting/connection-issues#building-a-reset-firmware. This can be helpful for clearing persistent settings.
Let me know if you have any more questions after trying these steps!
Connection Issues | ZMK Firmware
Troubleshooting wireless connection issues of ZMK devices.
This solution worked! thanks everyone!
(Using the reset module)