You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Pete Johanson
ebd3634372
|
5 years ago | |
---|---|---|
boards | 5 years ago | |
dts/bindings | 5 years ago | |
include/dt-bindings/zmk | 5 years ago | |
src | 5 years ago | |
.gitignore | 5 years ago | |
.gitlab-ci.yml | 5 years ago | |
CMakeLists.txt | 5 years ago | |
Dockerfile | 5 years ago | |
Kconfig | 5 years ago | |
LICENSE | 5 years ago | |
README.md | 5 years ago | |
prj.conf | 5 years ago | |
west.yml | 5 years ago |
README.md
Zephyr Mechanical Keyboard (ZMK) Firmware
This project is a complete work in progress, with absolutely nothing functioning yet. The goal is to explore a new MK firmware with a less restritive license and better BLE support, built on top of the Zephyr Project
TODO
- Debouncing in the kscan driver itself? Only some GPIO drivers in Zephyr support it "natively"
- Better DTS overlay setup for keymaps. Current use of SHIELDs works, but perhaps would be better with something more integrated.
- Move most Kconfig setings to the board/keymap defconfigs and out of the toplevel
prj.conf
file. - Merge the Kscan GPIO driver upstream, or integrate it locally, to avoid use of Zephyr branch.
- BLE SC by typing in the # prompted on the host.
- Store the connection being authenticated.
- Hook into endpoint flow to detect keypresses and store/send them to the connection once 6 are typed.
- Display support, including displaying BLE SC auth numbers for "numeric comparison" mode if we have the screen.
- Fix BT settings to work w/ Zephyr. Do we really need them?
- Tests?
Long Term
- Tool to convert keymap
info.json
files into a DTS keymap file? - Firmware build service?