Development

Get the Move Firmware

Last updated May 18, 2026

This guide pulls the HealthyPi Move firmware source into a Zephyr workspace and opens it in VS Code, ready to build.

Prerequisites

VS Code + nRF Connect Extension Pack installed (see Set up the SDK).
An SDK version + toolchain installed via the nRF Connect panel.
west available in your shell (installed automatically with the toolchain).

1. Initialize the workspace

Create a Zephyr workspace seeded from the HealthyPi Move firmware manifest:

west init -m https://github.com/protocentral/healthypi-move-fw --mr main healthypi-move-workspace

This creates a healthypi-move-workspace/ directory and clones the manifest repo into it. No source code yet — west update does the actual fetch.

2. Fetch dependencies

cd healthypi-move-workspace
west update

west update reads the manifest and clones all the projects it references — including the Zephyr RTOS itself, the nRF Connect SDK, and Move’s own firmware sources. Expect 10–15 minutes on a fresh checkout. The result is several GB of source under zephyr/, nrf/, app/, and various module directories.

To confirm it worked:

ls app/app

You should see source files like main.c and CMakeLists.txt. If app/app is empty, west update didn’t complete — re-run it.

3. Open the application in VS Code

Launch VS Code and open the nRF Connect panel from the sidebar.
Click Open an existing application.
Browse to healthypi-move-workspace/app/app and select it. The HealthyPi Move application appears in the Applications list.

4. Add a build configuration

In the Applications view, click + Add build configuration.
Set Board to healthypi_move/nrf5340/cpuapp. This target is critical — the build won’t resolve without it.
Choose Debug (with symbols) for development or Release (optimized) for production builds.
Click Build Configuration.