OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/doc/kernel/overview/system_fundamentals.rst

30 lines
1.6 KiB
ReStructuredText
Raw Normal View History

doc: Overhaul of Zephyr Kernel Primer overview section A complete rewrite of the Overview section. The revised text provides a more logical and comprehensive introduction to the main concepts and capabilities of Zephyr, without providing an excessive level of detail. (Those details should be provided by the remaining sections of the Kernel Primer.) This rewrite has also resulted in some small changes to the About Zephyr and other Kernel Primer sections. Change-Id: Idd4d5e0f0aabaaee8cd43d12563018ba4d8f7417 Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
2015-08-13 03:46:55 +08:00
.. _system_fundamentals:
System Fundamentals
###################
doc: adding :dfn: syntax where needed Updated as per Allan's comments to correct use of Zephyr kernel in lieu of codename variable Change-Id: Iaf5f8531c5452b6d8fb13318f00050aa63d99200 Signed-off-by: L.S. Cook <leonax.cook@intel.com>
2015-10-09 05:13:05 +08:00
An :dfn:`application image` is a binary that controls the operation
of a hardware system, or of a simulated system running under QEMU.
Each application image contains both the application's code and the Zephyr
kernel code needed to support it. They are compiled as a single,
fully-linked binary.
doc: Overhaul of Zephyr Kernel Primer overview section A complete rewrite of the Overview section. The revised text provides a more logical and comprehensive introduction to the main concepts and capabilities of Zephyr, without providing an excessive level of detail. (Those details should be provided by the remaining sections of the Kernel Primer.) This rewrite has also resulted in some small changes to the About Zephyr and other Kernel Primer sections. Change-Id: Idd4d5e0f0aabaaee8cd43d12563018ba4d8f7417 Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
2015-08-13 03:46:55 +08:00
doc: adding :dfn: syntax where needed Updated as per Allan's comments to correct use of Zephyr kernel in lieu of codename variable Change-Id: Iaf5f8531c5452b6d8fb13318f00050aa63d99200 Signed-off-by: L.S. Cook <leonax.cook@intel.com>
2015-10-09 05:13:05 +08:00
Once an application image has been loaded onto a target system, the image takes control
of the system, initializes it, and runs forever as the system's sole application.
Both application code and kernel code execute as privileged code within a single
shared address space.
doc: Overhaul of Zephyr Kernel Primer overview section A complete rewrite of the Overview section. The revised text provides a more logical and comprehensive introduction to the main concepts and capabilities of Zephyr, without providing an excessive level of detail. (Those details should be provided by the remaining sections of the Kernel Primer.) This rewrite has also resulted in some small changes to the About Zephyr and other Kernel Primer sections. Change-Id: Idd4d5e0f0aabaaee8cd43d12563018ba4d8f7417 Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
2015-08-13 03:46:55 +08:00
doc: Edits to the Overview and kernel primer Fixed typo in system_fundamentals. Acronyms FIFO and LIFO defined with capital letters in kernel_fundamentals. Added bold to paragraph lists to enhance readability in application_fundamentals Added lots of :dfn: syntax for better interlinking to API. Corrected whitespace for sub-bullet directive. Change-Id: If6c5bc78746686d1a4986974f1b56bf9b2caebca Signed-off-by: L.S. Cook <leonax.cook@intel.com>
2015-10-22 03:08:58 +08:00
An :dfn:`application` is a set of user-supplied files that the Zephyr build
doc: adding :dfn: syntax where needed Updated as per Allan's comments to correct use of Zephyr kernel in lieu of codename variable Change-Id: Iaf5f8531c5452b6d8fb13318f00050aa63d99200 Signed-off-by: L.S. Cook <leonax.cook@intel.com>
2015-10-09 05:13:05 +08:00
system processes to generate an application image. The application consists of
application-specific code, a collection of kernel configuration settings, and at
least one Makefile. The application's kernel configuration settings enable the build
system to create a kernel tailor-made to meet the needs of the application
and to make the best use of the system's resources.
doc: codename -> Zephyr Kernel To make the documentation readable from the source I want to get rid of the substitutions for the project name an code name. This does not add any values and makes it unreadable when looking at the text files directly. It also causes some issues when people use those without actually knowing what they represent, resulting in some weird and redundant language. Change-Id: I09e8cbbee7c1141a7a77d3ffff59cdae2b52050c Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-10-21 01:28:33 +08:00
The Zephyr Kernel supports a variety of target systems, known as *platforms*;
doc: adding :dfn: syntax where needed Updated as per Allan's comments to correct use of Zephyr kernel in lieu of codename variable Change-Id: Iaf5f8531c5452b6d8fb13318f00050aa63d99200 Signed-off-by: L.S. Cook <leonax.cook@intel.com>
2015-10-09 05:13:05 +08:00
each :dfn:`platform` has its own set of hardware devices and capabilities. One or more
*platform configurations* are defined for a given platform; each
:dfn:`platform configuration` indicates how the devices that may be present on the
platform are to be used by the kernel. The platform and platform configuration concepts
make it possible to develop a single application that can be used by a set of related
target systems, or even target systems based on different CPU architectures.