Lines Matching full:a
12 (Application Program Interface) A defined set of routines and protocols for
17 to build an application image for a specified board configuration.
21 to create a custom kernel that makes efficient use of the board's
28 A binary file that is loaded and executed by the board for which
31 Zephyr kernel code needed to support it. They are compiled as a single,
33 Once an application image is loaded onto a board, the image takes control
36 within a single shared address space.
39 An instruction set architecture (ISA) along with a programming model.
42 A target system with a defined set of devices and capabilities,
44 hardware system or a simulated system running under QEMU. A board can
46 The Zephyr kernel supports a :ref:`variety of boards <boards>`.
49 A set of kernel configuration options that specify how the devices
50 present on a board are used by the kernel.
57 The human-readable name of a :term:`board`. Uniquely and descriptively
58 identifies a particular system, but does not include additional
59 information that may be required to actually build a Zephyr image for it.
63 The set of additional tokens, separated by a forward slash (``/``) that
70 An optional version string that identifies a particular revision of a
72 whenever small changes are introduced to a hardware system.
78 compile and link an image for a particular hardware system. This string
84 A group of one or more :term:`CPU cores <CPU core>`, all executing the same image
85 within the same address space and in a symmetrical (SMP) configuration.
86 Only :term:`CPU cores <CPU core>` of the same :term:`architecture` can be in a single
91 A single processing unit, with its own Program Counter, executing program
92 instructions sequentially. CPU cores are part of a :term:`CPU cluster`,
103 A system thread that runs when there are no other threads ready to run.
106 (Interrupt Descriptor Table) a data structure used by the x86
112 is a callback function whose execution is triggered by a hardware
122 A power domain is a collection of devices for which power is
123 applied and removed collectively in a single action. Power
131 A `System on a chip`_, that is, an integrated circuit that contains at
137 in common to consider them related and under a single family denomination.
140 A number of different :term:`SoCs <SoC>` that share similar characteristics and
144 A subsystem refers to a logically distinct part of the operating system
148 System power states describe the power consumption of the system as a
152 In the context of :term:`board qualifiers`, a variant designates a
153 particular type or configuration of a build for a combination of :term:`SoC`
156 Execution Environment support, or selecting the type of RAM used in a
160 A multi-repo meta-tool developed for the Zephyr project. See :ref:`west`.
163 An obsolete term for a :term:`west workspace` used prior to west 0.7.
166 A YAML file, usually named :file:`west.yml`, which describes projects, or
167 the Git repositories which make up a :term:`west workspace`, along with
172 The Git repository in a :term:`west workspace` which contains the
177 Each of the entries in a :term:`west manifest`, which describe a Git
179 corresponding :term:`west manifest repository`. Note that a west project
180 is different from a :term:`zephyr module`, although many projects are also
184 A folder on your system with a :file:`.west` subdirectory and a
187 system by creating a west workspace using the ``west init`` command. See
191 (eXecute In Place) a method of executing programs directly from long
196 A Git repository containing a :file:`zephyr/module.yml` file, used by the
198 of the module into a regular Zephyr build. Zephyr modules may be west
202 .. _System on a chip: https://en.wikipedia.org/wiki/System_on_a_chip