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 A target system with a defined set of devices and capabilities,
41 hardware system or a simulated system running under QEMU.
42 The Zephyr kernel supports a :ref:`variety of boards <boards>`.
45 A set of kernel configuration options that specify how the devices
46 present on a board are used by the kernel.
60 A system thread that runs when there are no other threads ready to run.
63 (Interrupt Descriptor Table) a data structure used by the x86
69 is a callback function whose execution is triggered by a hardware
79 A power domain is a collection of devices for which power is
80 applied and removed collectively in a single action. Power
88 `System on a chip`_
91 System power states describe the power consumption of the system as a
95 A multi-repo meta-tool developed for the Zephyr project. See :ref:`west`.
98 An obsolete term for a :term:`west workspace` used prior to west 0.7.
101 A YAML file, usually named :file:`west.yml`, which describes projects, or
102 the Git repositories which make up a :term:`west workspace`, along with
107 The Git repository in a :term:`west workspace` which contains the
112 A directory on your system with a :file:`.west` subdirectory and
113 a :term:`west manifest repository`. You clone the Zephyr source
114 code onto your system by creating a west workspace using the
118 (eXecute In Place) a method of executing programs directly from long
122 .. _System on a chip: https://en.wikipedia.org/wiki/System_on_a_chip