Revert "Merge pull request #1 from zmkfirmware/main"
This reverts commit36da21b8e3
, reversing changes made to719db13c41
.
This commit is contained in:
parent
1a492f0f98
commit
5383bdd4df
4 changed files with 1 additions and 7 deletions
Binary file not shown.
Before Width: | Height: | Size: 113 KiB |
|
@ -35,8 +35,6 @@ in the `app/boards/${arch}/${board_name}` directory, e.g. `app/boards/arm/planck
|
|||
|
||||
## Pro Micro Compatible Keyboard
|
||||
|
||||
![Labelled Pro Micro pins](assets/pro-micro/pro-micro-pins-labelled.jpg)
|
||||
|
||||
For keyboards that require a (usually Pro Micro compatible) add-on board to operate, the ZMK integration pieces are places
|
||||
in the _shield_ definition for that keyboard, allowing users to
|
||||
swap in different Pro Micro compatible boards (e.g. Proton-C, or nice!nano) and build a firmware the matches their actual
|
||||
|
|
|
@ -67,10 +67,6 @@ endif
|
|||
|
||||
## Shield Overlay
|
||||
|
||||
![Labelled Pro Micro pins](assets/pro-micro/pro-micro-pins-labelled.jpg)
|
||||
|
||||
ZMK uses the green color coded pin names to generate devicetree node references. For example, to refer to the node `D0` in the devicetree files, use `&pro_micro_d 0` or to refer to `A1`, use `&pro_micro_a 1`.
|
||||
|
||||
The `<shield_name>.overlay` is the devicetree description of the keyboard shield that is merged with the primary board devicetree description before the build. For ZMK, this file at a minimum should include the [chosen]() node named `zmk,kscan` that references a KSCAN driver instance. For a simple 3x3 macropad matrix,
|
||||
this might look something like:
|
||||
|
||||
|
|
Loading…
Reference in a new issue