Visual Studio Code tools for working with ZMK Firmware.
It is primarily intended for editing keymaps in a ZMK user config repo, but it also works in the main ZMK repo.
If you do not yet have a repo:
- Open the ZMK config template repo on GitHub.
- Click the Use this template button and follow the instructions to create your own repo.
(If you don't know what to name it,
zmk-configis a good default name.)
Next, open the repo in VS Code using one of the options below:
Using github.dev you can edit your repo completely within your web browser.
-
Open a web browser to your repo in GitHub, then press the
.(period) key to open the repo in github.dev. -
If you have not installed this extension in github.dev before, press
Ctrl+Pand enter this command:ext install spadin.zmk-tools
Using an extension, you can run VS Code locally but edit the repo remotely without cloning it.
-
Install the GitHub Repositories extension.
-
Click the green Open a Remote Window button at the lower-left corner of the window.
-
Select Open Remote Repository...
-
Select Open Repository from GitHub.
-
Select your repository from the list.
-
If you have not installed this extension in a GitHub remote window before, press
Ctrl+Pand enter this command:ext install spadin.zmk-tools
Clone the repo to your computer and open it in VS Code.
If you don't know how to do this, check Learn the Basics of Git in Under 10 Minutes or try one of the options above instead.
Once the repo is open in VS Code, you can run the Add Keyboard command to add a keyboard:
- Press F1 and run the ZMK: Add keyboard command.
- Follow the prompts to select a keyboard. ZMK Tools will copy the necessary files into your repo and add it to your
build.yamlfile so GitHub will build it for you. - Edit your
.keymapand/or.conffiles. See the ZMK docs for help. - Select the Source Control tab on the side bar.
- Hover over the header for the Changes list and click the Stage All Changes button (plus icon).
- Enter a commit message and press
Ctrl+Enteror click the Commit button (checkmark icon) to save your changes.- If you are editing the repo locally, click the Sync Changes button to push your changes to GitHub.
Ever time you commit a change, GitHub will automatically build the firmware for you. Open a web browser to your repo in GitHub and click the Actions tab at the top, then click the latest build (at the top of the list).
If the build succeeded, you can download the firmware from the Artifacts section.
If the build failed, click the failed job from the list on the left, then look for the error message. Correct the error, then repeat steps 3-6 above.
The error probably looks something like Error: nice_nano.dts.pre.tmp:760.12-13 syntax error.
If so, the following step of the build (named <board> DTS File) shows the .dts.pre.tmp file,
which is a combination of your .keymap and a few other files.
Match the line number from the error (760 in this example) to a line in the file,
using the right-most column of line numbers. There is probably a typo on that line.
Find the line in your .keymap and fix it.
- Syntax highlighting
- Code completion in
bindingsandsensor-bindingsproperties. - Very basic syntax checking (as of this writing, Tree-sitter does not provide useful error messages).
- This extension marks
.overlayfiles as DeviceTree files so the DeviceTree extension will provide syntax highlighting if it is installed.
If you run into an issue or you have an idea for something to add to this extension, let me know by creating an issue or joining the ZMK Discord server (see the Discord link at the bottom of the ZMK Firmware homepage.)
- Keymap parsing uses the amazing Tree-sitter library.
- Some parsing code is adapted from Tree Sitter for VSCode (Copyright © 2016 George Fraser, MIT license).
- Syntax highlighting of
.keymapfiles is taken from vscode-devicetree (Copyright © 2017 Pietro Lorefice, MIT license). - The ZMK logo is part of the ZMK documentation and is licensed CC-BY-NC-SA.
