The out-of-tree Zephyr board files repo for the ALP Lab E1M EVKs is now published as a scaffold: alplabai/alp-zephyr-modules.
Why this exists today (before any board file lands)
The repo is a published home for the board URLs already referenced from alp-sdk docs, tests, and the nightly HIL workflow — so those references resolve instead of 404’ing. It declares itself as a Zephyr module (zephyr/module.yml) so a consumer pointing EXTRA_ZEPHYR_MODULES here today gets a no-op module instead of a parse error.
Coming boards (Zephyr v3.7 LTS)
| Board | Carrier + SoM | Status |
|---|---|---|
alp_e1m_evk_aen |
E1M EVK (UG-E1M-001) + E1M-AEN family | board file pending |
alp_e1m_evk_v2n |
E1M-X EVK + E1M-X V2N family | board file pending |
alp_e1m_evk_v2n_m1 |
E1M-X EVK + E1M-X V2N-M1 family | board file pending |
alp_e1m_evk_imx93 |
E1M EVK + E1M-i.MX93 family | board file pending |
Each board ships its .dts, .yaml, _defconfig, board.cmake, and Kconfig.board under boards/alp/<board_name>/ per Zephyr’s v3.7 board layout.
Consuming today
As a Zephyr module — add to your application’s west.yml:
manifest:
projects:
- name: alp-zephyr-modules
url: https://github.com/alplabai/alp-zephyr-modules
revision: main
path: modules/alp-zephyr-modules
Why a separate repo
Board files update on EVK schematic revisions, not SDK API cadence — keeping them out-of-tree lets customers pin alp-sdk and bump their EVK board file independently. Mirrors Zephyr’s own board porting guide recommendation.