| /Zephyr-Core-2.7.6/lib/gui/lvgl/ |
| D | Kconfig.themes | 245 bool "Build-in font size 8"
249 bool "Build-in font size 10"
253 bool "Build-in font size 12"
257 bool "Build-in font size 14"
261 bool "Build-in font size 16"
265 bool "Build-in font size 18"
269 bool "Build-in font size 20"
273 bool "Build-in font size 22"
277 bool "Build-in font size 24"
281 bool "Build-in font size 26"
[all …]
|
| /Zephyr-Core-2.7.6/doc/guides/west/ |
| D | build-flash-debug.rst | 1 .. _west-build-flash-debug:
8 ``build``, ``flash``, ``debug``, ``debugserver`` and ``attach``.
23 Building: ``west build``
26 .. tip:: Run ``west build -h`` for a quick overview.
28 The ``build`` command helps you build Zephyr applications from source. You can
33 - If there is a Zephyr build directory named :file:`build` in your current
35 run ``west build`` from a Zephyr build directory.
37 - Otherwise, if you run ``west build`` from a Zephyr application's source
38 directory and no build directory is found, a new one is created and the
44 The easiest way to use ``west build`` is to go to an application's root
[all …]
|
| D | without-west.rst | 13 - specifying the locations of these repositories to the Zephyr build
27 Otherwise, Zephyr's build system will find it and may try to use
52 You can build a Zephyr application using CMake and Ninja (or make) directly
58 :goals: build
62 When building with west installed, the Zephyr build system will use it to set
63 :ref:`ZEPHYR_MODULES <important-build-vars>`.
66 these repositories, the build will still work.
77 Running build system targets like ``ninja flash``, ``ninja debug``,
79 <west-build-flash-debug>`. For example, ``ninja flash`` calls ``west
85 If you want to use these build system targets but do not want to
[all …]
|
| D | sign.rst | 13 The Zephyr build system has special support for signing binaries for use with
15 developers. You can both build and sign this type of application binary in one
20 build system will do it for you.
29 west build -b YOUR_BOARD -s bootloader/mcuboot/boot/zephyr -d build-mcuboot
30 west build -b YOUR_BOARD -s zephyr/samples/hello_world -d build-hello-signed -- \
34 west flash -d build-mcuboot
35 west flash -d build-hello-signed
47 - :kconfig:`CONFIG_BOOTLOADER_MCUBOOT`: build the application for loading by
57 to run ``pip3 install imgtool``, then retry with a pristine build directory.
61 serial console when you run ``west flash -d build-mcuboot``:
[all …]
|
| D | zephyr-cmds.rst | 60 from source files to the corresponding generated build files.
66 #. Pre-populate a build directory :file:`BUILD_DIR` like this:
72 This step ensures the build directory contains CMake metadata required for
75 #. Build your application using this pre-created build directory, like so:
79 west build -d BUILD_DIR [...]
81 #. Generate SPDX documents using this build directory:
90 - :file:`app.spdx`: BOM for the application source files used for the build
92 the build
93 - :file:`build.spdx`: BOM for the built output files
100 CMake build targets, build targets that are linked together, and
[all …]
|
| /Zephyr-Core-2.7.6/tests/drivers/build_all/pwm/ |
| D | testcase.yaml | 5 drivers.pwm.gecko.build:
9 drivers.pwm.imx.build:
13 drivers.pwm.litex.build:
17 drivers.pwm.mcux.ftm.build:
21 drivers.pwm.mcux.pwt.build:
25 drivers.pwm.mcux.ftm.build:
29 drivers.pwm.mcux.build:
33 drivers.pwm.mcux.sctimer.build:
37 drivers.pwm.rv32m1.tpm.build:
41 drivers.pwm.sifive.build:
[all …]
|
| /Zephyr-Core-2.7.6/tests/drivers/build_all/adc/ |
| D | testcase.yaml | 5 drivers.adc.spi.build:
9 drivers.adc.emul.build:
13 drivers.adc.cc32xx.build:
17 drivers.adc.ite.it8xxx2.build:
21 drivers.adc.mcux.adc12.build:
25 drivers.adc.mcux.adc16.build:
29 drivers.adc.mcux.lpadc.build:
33 drivers.adc.npcx.build:
37 drivers.adc.nrf.build:
41 drivers.adc.nrf.saadc.build:
[all …]
|
| /Zephyr-Core-2.7.6/scripts/west_commands/ |
| D | build_helpers.py | 10 See build.py for the build command itself.
20 DEFAULT_BUILD_DIR = 'build'
21 '''Name of the default Zephyr build directory.'''
27 If the build directory is not given, the default is {}/ unless the
28 build.dir-fmt configuration variable is set. The current directory is
29 checked after that. If either is a Zephyr build directory, it is used.
50 # Guess the build folder by iterating through all sub-folders from the
78 '''Heuristic for finding a build directory.
80 The default build directory is computed by reading the build.dir-fmt
82 be None if the build.dir-fmt configuration option is set but cannot be
[all …]
|
| D | build.py | 23 west build [-h] [-b BOARD] [-d BUILD_DIR]
41 A "pristine" build directory is empty. The -p option controls
42 whether the build directory is made pristine before the build
45 guess if a pristine build may be necessary."""
48 log.inf('-- west build: ' + msg, colorize=True)
51 return config.get('build', option, fallback=fallback)
54 return config.getboolean('build', option, fallback=fallback)
61 class Build(Forceable): class
64 super(Build, self).__init__(
65 'build',
[all …]
|
| D | spdx.py | 15 following the completion of a Zephyr build.
17 Prior to the build, an empty file must be created at
21 calling `west build`."""
39 parser.add_argument('-d', '--build-dir',
40 help="build directory")
56 log.dbg(f" --build-dir is", args.build_dir)
68 log.inf("initializing Cmake file-based API prior to build")
71 log.die("Build directory not specified; call `west spdx --init --build-dir=BUILD_DIR`")
76 log.inf("initialized; run `west build` then run `west spdx`")
83 log.die("Build directory not specified; call `west spdx --build-dir=BUILD_DIR`")
|
| /Zephyr-Core-2.7.6/modules/trusted-firmware-m/ |
| D | Kconfig.tfm | 26 bool "Build with TF-M as the Secure Execution Environment"
35 When enabled, this option instructs the Zephyr build process to
42 them, are generated during the normal Zephyr build process.
78 Build profile used to build tfm_s image. The available values are
83 prompt "TF-M build profile"
87 The TF-M build profile selection. Can be empty (not set),
93 bool "TF-M build profile is not set"
96 bool "TF-M build profile: small"
99 bool "TF-M build profile: medium"
102 bool "TF-M build profile: large"
[all …]
|
| D | Kconfig.tfm.partitions | 13 to be passed to the TF-M build system. Look at 'config_default.cmake'
16 options are handled by the build system in the trusted-firmware-m
24 to be passed to the TF-M build system. Look at 'config_default.cmake'
27 options are handled by the build system in the trusted-firmware-m
35 to be passed to the TF-M build system. Look at 'config_default.cmake'
38 options are handled by the build system in the trusted-firmware-m
46 to be passed to the TF-M build system. Look at 'config_default.cmake'
49 options are handled by the build system in the trusted-firmware-m
57 to be passed to the TF-M build system. Look at 'config_default.cmake'
60 options are handled by the build system in the trusted-firmware-m
[all …]
|
| /Zephyr-Core-2.7.6/samples/tfm_integration/tfm_ipc/ |
| D | README.rst | 36 #. Build Zephyr with a non-secure configuration (``-DBOARD=mps2_an521_ns``).
41 mkdir build
42 cd build
50 $ west build -p -b mps2_an521_ns zephyr/samples/tfm_integration/tfm_ipc
89 As part of the normal build process above, a binary is also produced that can
96 You can also run the binary as part of the ``west`` build process by appending
97 the ``-t run`` flag to the end of your build command, or in the case of
102 $ west build -b mps2_an521_ns zephyr/samples/tfm_integration/tfm_ipc -t run
104 Or, post build:
115 Build Zephyr with a non-secure configuration:
[all …]
|
| /Zephyr-Core-2.7.6/doc/guides/build/ |
| D | index.rst | 3 Build and Configuration Systems
9 Build System (CMake)
13 CMake is used to build your application together with the Zephyr kernel. A
14 CMake build is done in two stages. The first stage is called
15 **configuration**. During configuration, the CMakeLists.txt build scripts are
17 Zephyr build, and can generate build scripts that are native to the host
20 CMake supports generating scripts for several build systems, but only Ninja and
22 **build** stage by executing the generated build scripts. These build scripts
25 be executed again before building. The build scripts can detect some of these
29 Zephyr uses CMake's concept of a 'target' to organize the build. A
[all …]
|
| /Zephyr-Core-2.7.6/tests/drivers/build_all/dac/ |
| D | testcase.yaml | 5 drivers.dac.spi.build:
9 drivers.dac.i2c.build:
13 drivers.dac.mcux.build:
17 drivers.dac.mcux32.build:
21 drivers.dac.sam0.build:
25 drivers.dac.stm32.build:
|
| /Zephyr-Core-2.7.6/doc/application/ |
| D | index.rst | 9 :file:`<home>/app`, and that its **build directory** is
10 :file:`<home>/app/build`.
18 Zephyr's build system is based on `CMake`_.
20 The build system is application-centric, and requires Zephyr-based applications
21 to initiate building the kernel source tree. The application build controls
22 the configuration and build process of both the application and Zephyr itself,
26 configuration options, and its build definitions.
44 * **CMakeLists.txt**: This file tells the build system where to find the other
46 build system. This link provides features supported by Zephyr's build system,
64 known as the **build directory**. Application build artifacts are always
[all …]
|
| /Zephyr-Core-2.7.6/doc/guides/tfm/ |
| D | build.rst | 1 TF-M Build System
6 of TF-M's build system is required in most cases, and the following will
7 build a TF-M and Zephyr image pair, and run it in qemu with no additional
12 $ west build -p auto -t mps2_an521_ns samples/tfm_integration/psa_crypto/ -t run
14 The outputs and certain key steps in this build process are described here,
18 Images Created by the TF-M Build
21 The TF-M build system creates the following executable files:
29 The TF-M build system also creates signed variants of tfm_s and tfm_ns, and a
38 The Zephyr build system usually signs both tfm_s and the Zephyr ns app itself.
97 the CMake arguments passed to the TF-M build.
[all …]
|
| /Zephyr-Core-2.7.6/.github/workflows/ |
| D | doc-build.yml | 4 name: Documentation Build
23 - '.github/workflows/doc-build.yml'
35 doc-build-html:
36 name: "Documentation Build (HTML)"
41 group: doc-build-html-${{ github.ref }}
50 sudo apt-get install -y ninja-build doxygen graphviz
69 - name: build-docs
89 - name: upload-build
112 doc-build-pdf:
113 name: "Documentation Build (PDF)"
[all …]
|
| D | footprint.yml | 49 west build -b frdm_k64f tests/benchmarks/footprints -t ram_report
50 cp build/ram.json ram2.json
51 west build -b frdm_k64f tests/benchmarks/footprints -t rom_report
52 cp build/rom.json rom2.json
56 west build -p always -b frdm_k64f tests/benchmarks/footprints -t ram_report
57 west build -b frdm_k64f tests/benchmarks/footprints -t rom_report
58 cp build/ram.json ram1.json
59 cp build/rom.json rom1.json
|
| /Zephyr-Core-2.7.6/doc/_extensions/zephyr/ |
| D | application.py | 19 of the shell commands needed to manage (build, flash, etc.) an application.
21 For example, to generate commands to build samples/hello_world for
27 :goals: build
36 path to the application to build.
39 path to the application to build, this is an app present in the upstream
43 if set, build instructions are given from within the \:app: folder,
47 which build system to generate. Valid options are
56 if set, the application build will target the given board.
59 if set, the application build will target the given shield.
62 if set, the application build will use the given configuration
[all …]
|
| /Zephyr-Core-2.7.6/cmake/usage/ |
| D | usage.cmake | 15 message(" pristine - Remove all files in the build directory")
22 message(" all - Build a zephyr application")
23 message(" run - Build a zephyr application and run it if the board supports emulation")
28 message(" ram_report - Build and create RAM usage report")
29 message(" rom_report - Build and create ROM usage report")
33 message(" help - Display all build system targets")
35 message("Build flags:")
37 message(" ${generator} ${verbose} [targets] verbose build")
|
| /Zephyr-Core-2.7.6/samples/application_development/external_lib/ |
| D | CMakeLists.txt | 10 # how to build for this platform so we export all the flags used in
11 # this zephyr build to the external build system.
13 # Other external build systems may be self-contained enough that they
14 # do not need any build information from zephyr. Or they may be
28 # Add an external project to be able download and build the third
48 BINARY_DIR ${mylib_src_dir} # This particular build system is invoked from the root
56 INSTALL_COMMAND "" # This particular build system has no install command
|
| /Zephyr-Core-2.7.6/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 33 application should build and run for other platforms with same connectivity.
57 The below steps describe how to build and run the ``UpdateHub`` sample in
67 Step 1: Build/Flash MCUboot
70 The MCUboot can be build following the instructions in the :ref:`mcuboot`
77 :build-dir: mcuboot-frdm_k64f
78 :goals: build flash
157 Step 4: Build UpdateHub App
160 In order to correctly build UpdateHub the overlay files must be use correctly.
161 More information about overlay files in :ref:`important-build-vars`.
168 Step 4.1: Build for Ethernet
[all …]
|
| /Zephyr-Core-2.7.6/ |
| D | Kconfig.zephyr | 48 menu "Build and Link Features"
267 the build.
270 bool "Build as a native host application"
272 Build as a native application that can run on the host and using
327 predefined set of compiler supplied by the build system,
334 Causes the source code to build in "MISRA" mode, which
363 menu "Build Options"
409 from the build process.
415 bool "Build a binary in HEX format"
417 Build an Intel HEX binary zephyr/zephyr.hex in the build directory.
[all …]
|
| /Zephyr-Core-2.7.6/lib/libc/ |
| D | Kconfig | 30 Build with minimal C library.
36 Build with newlib library. The newlib library is expected to be
49 Build with external/user provided C library.
59 bool "Build with newlib-nano C library"
63 Build with newlib-nano library, for small embedded apps.
102 bool "Build with newlib float printf"
104 Build with floating point printf enabled. This will increase the size of
108 bool "Build with newlib float scanf"
110 Build with floating point scanf enabled. This will increase the size of
147 bool "Build with minimal libc long long printf" if !64BIT
[all …]
|
