Improved dev setup docs.
This commit is contained in:
parent
1ba66e7dbe
commit
7cb7d705d6
1 changed files with 106 additions and 6 deletions
|
@ -4,9 +4,109 @@ title: Basic Setup
|
|||
sidebar_label: Basic Setup
|
||||
---
|
||||
|
||||
1. Install `west` from pip.
|
||||
1. Install the ARM SDK from Zephyr project.
|
||||
1. (Optional) Install 32-bit libs for building and testing locally.
|
||||
1. `west init -l zmk`
|
||||
1. Build it.
|
||||
1. Flash it.
|
||||
## Preprequisites
|
||||
|
||||
A unix-like environment with Python 3 installed. So far this has been tested on Fedora and Debian. Further testing is required for macOS and WSL.
|
||||
|
||||
## Setup
|
||||
|
||||
### West Build Command
|
||||
|
||||
`west` is the [Zephyr meta-tool](https://docs.zephyrproject.org/latest/guides/west/index.html) used to configure and build Zephyr applications. It can be installed by using the `pip` python package manager:
|
||||
|
||||
```bash
|
||||
pip install --user west
|
||||
```
|
||||
|
||||
:::note
|
||||
If you don't already have it configured, you may need to update your
|
||||
`PATH` to include the pip install path. See [User Installs](https://pip.pypa.io/en/stable/user_guide/#user-installs) and (Stack Overflow)[https://stackoverflow.com/questions/38112756/how-do-i-access-packages-installed-by-pip-user] for more details.
|
||||
:::
|
||||
|
||||
### Zephyr ARM SDK
|
||||
|
||||
To build firmwares for the ARM architecture (all supported MCUs/keyboards at this point), you'll need to install the Zephyr ARM SDK to your system:
|
||||
|
||||
```
|
||||
export ZSDK_VERSION=0.11.3
|
||||
wget -q "https://github.com/zephyrproject-rtos/sdk-ng/releases/download/v${ZSDK_VERSION}/zephyr-toolchain-arm-${ZSDK_VERSION}-setup.run" && \
|
||||
sh "zephyr-toolchain-arm-${ZSDK_VERSION}-setup.run" --quiet -- -d /opt/toolchains/zephyr-sdk-${ZSDK_VERSION} && \
|
||||
rm "zephyr-toolchain-arm-${ZSDK_VERSION}-setup.run"
|
||||
```
|
||||
|
||||
### Source Code
|
||||
|
||||
Next, you'll need to clone the ZMK source repository if you haven't already:
|
||||
|
||||
```
|
||||
git clone https://github.com/zmkfirmware/zmk.git
|
||||
```
|
||||
|
||||
### Initialize & Update Zephy Workspace
|
||||
|
||||
Since ZMK is build as a Zephyr application, the next step is
|
||||
to use `west` to initialize and update your workspace. The ZMK
|
||||
Zephyr application is in the `app/` source directory:
|
||||
|
||||
#### Initialize West
|
||||
|
||||
```bash
|
||||
west init -l app/
|
||||
```
|
||||
|
||||
#### Update To Fetch Modules
|
||||
|
||||
```bash
|
||||
west update
|
||||
```
|
||||
|
||||
#### Export Zephyr Core
|
||||
|
||||
```bash
|
||||
west zephyr-export
|
||||
```
|
||||
|
||||
## Build
|
||||
|
||||
To build for your particular keyboard, the behaviour varies slightly depending on if you are building for a keyboard with
|
||||
an onboard MCU, or one that uses a MCU board addon.
|
||||
|
||||
### Keyboard (Shield) + MCU Board
|
||||
|
||||
ZMK treats keyboards that take a MCU addon board as [shields](https://docs.zephyrproject.org/latest/guides/porting/shields.html), and treats the smaller MCU board as the true [board](https://docs.zephyrproject.org/latest/guides/porting/board_porting.html)
|
||||
|
||||
Given the following:
|
||||
|
||||
- MCU Board: Proton-C
|
||||
- Keyboard PCB: kyria
|
||||
- Keymap: default
|
||||
|
||||
You can build ZMK with the following:
|
||||
|
||||
```bash
|
||||
west build -b proton_c -- -DSHIELD=kyria -DKEYMAP=default
|
||||
```
|
||||
|
||||
### Keyboard With Onboard MCU
|
||||
|
||||
Keyboards with onboard MCU chips are simply treated as the [board](https://docs.zephyrproject.org/latest/guides/porting/board_porting.html) as far as Zephyr is concerned.
|
||||
|
||||
Given the following:
|
||||
|
||||
- Keyboard: Planck
|
||||
- Keymap: default
|
||||
|
||||
you can build ZMK with the following:
|
||||
|
||||
```bash
|
||||
west build -b planck -- -DKEYMAP=default
|
||||
```
|
||||
|
||||
## Flashing
|
||||
|
||||
Once built, the previously supplied parameters will be remember, so you can simply run the following to flash your
|
||||
board, with it in bootloader mode:
|
||||
|
||||
```
|
||||
west flash
|
||||
```
|
||||
|
|
Loading…
Reference in a new issue