.github: workflows: bump windows image version
Update windows image from windows-2022 to windows-2025 as this is the current LTSC version.
Signed-off-by: Benjamin Cabé benjamin@zephyrproject.org
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
Zephyr Example Application
This repository contains a Zephyr example application. The main purpose of this repository is to serve as a reference on how to structure Zephyr-based applications. Some of the features demonstrated in this example are:
This repository is versioned together with the Zephyr main tree. This means that every time that Zephyr is tagged, this repository is tagged as well with the same version number, and the manifest entry for
zephyrwill point to the corresponding Zephyr tag. For example, theexample-applicationv2.6.0 will point to Zephyr v2.6.0. Note that themainbranch always points to the development branch of Zephyr, alsomain.Getting Started
Before getting started, make sure you have a proper Zephyr development environment. Follow the official Zephyr Getting Started Guide.
Initialization
The first step is to initialize the workspace folder (
my-workspace) where theexample-applicationand all Zephyr modules will be cloned. Run the following command:Building and running
To build the application, run the following command:
where
$BOARDis the target board.You can use the
custom_plankboard found in this repository. Note that Zephyr sample boards may be used if an appropriate overlay is provided (seeapp/boards).A sample debug configuration is also provided. To apply it, run the following command:
Once you have built the application, run the following command to flash it:
Testing
To execute Twister integration tests, run the following command:
Documentation
A minimal documentation setup is provided for Doxygen and Sphinx. To build the documentation first change to the
docfolder:Before continuing, check if you have Doxygen installed. It is recommended to use the same Doxygen version used in CI. To install Sphinx, make sure you have a Python installation in place and run:
API documentation (Doxygen) can be built using the following command:
The output will be stored in the
_build_doxygenfolder. Similarly, the Sphinx documentation (HTML) can be built using the following command:The output will be stored in the
_build_sphinxfolder. You may check for other output formats other than HTML by runningmake help.