Zephyr project

Create a ready-to-use Zephyr RTOS project from the LVGL Pro Editor launcher, pick your board, and build for hardware or the PC simulator.

This feature requires LVGL Pro Editor v2.0 or higher.

The Editor can generate a complete, ready-to-build Zephyr project for you — the same way it creates a VS Code project or a simulator. You don't need to wire up CMake, Kconfig or the devicetree by hand: pick a board on the launcher and the Editor produces a full Zephyr workspace application with your UI already hooked up.

Create a project

On the Editor's home screen, choose Zephyr as the target project and select a development board from the list. That's the only decision you need to make — the board choice pulls in the right Kconfig, devicetree overlays and HAL modules automatically.

The following boards are supported out of the box:

BoardResolutionInterface / Panel
EK-RA8D1 (Renesas)480 × 854MIPI DSI — ILI9806E
EK-RA6M3 (Renesas)480 × 272GLCDC parallel RGB — RTK7EKA6M3B00001BU
EK-RA8D2 (Renesas)1024 × 600GLCDC parallel RGB — RTK-LCD-PAR1S-00001BE
STM32U5G9J-DK2 (ST)800 × 480LTDC parallel RGB — GT911 touch
FRDM-MCXN947 (NXP)480 × 3208080 MIPI DBI — ST7796S
MIMXRT1170-EVK (NXP)720 × 1280MIPI DSI — HX8394
M5Stack Core2 (ESP32)320 × 240SPI — ILI9342C

Your UI is exported into the project's ui/ folder and is picked up automatically — you can keep designing in the Editor and re-export at any time.

Get started

The generated project is a standard Zephyr workspace application driven by west. Its README.md contains the exact build command for the board you picked; the steps below are the general flow.

1. Install the prerequisites

Follow the Zephyr Getting Started Guide to install the host dependencies, west, and the Zephyr SDK.

To run the PC simulator you also need SDL2:

sh
sudo apt install libsdl2-dev   # Debian / Ubuntu

2. Initialize the workspace

From the project folder, fetch Zephyr and the required modules:

sh
west init -l manifest
west update

3. Run on your PC (simulator)

You can try the UI without any hardware:

sh
west build -b native_sim/native/64 -t run

4. Run on your development board

Use the build command from the project's README.md (it's filled in for the board you selected), for example:

sh
west build -p -b ek_ra8d2/r7ka8d2kflcac/cm85

Then flash and debug:

sh
west flash
west debug

Some boards need vendor HAL blobs before the first build, e.g. west blobs fetch hal_renesas (Renesas) or west blobs fetch hal_espressif (ESP32). ESP32 boards also need the esptool package on your PATH. Install it with west packages pip --install. The generated README.md and BOARDS.md list any extra step for your board.

Updating the UI

Design your UI in the Editor and export to the project's ui/ folder. The application detects it automatically and builds it as a library, so re-exporting is all it takes to update the interface — no code changes needed.

Adding another board

The project ships a BOARDS.md with the full list of supported boards, their build commands and display details. To target a board that isn't included:

  1. Add the board's HAL module to the name-allowlist in manifest/west.yml, then run west update.
  2. Optionally add board-specific settings in the boards/ folder (<board>.conf for Kconfig, <board>.overlay for devicetree, <board>.cmake for CMake variables such as a default shield).
  3. Build with west build -p -b <board>.

See BOARDS.md in the generated project for details on the overlay files and how they are applied.

Last updated on

On this page