| /Zephyr-Core-2.7.6/scripts/ |
| D | requirements-base.txt | 6 # used by various build scripts
9 # used by dts generation to parse binding YAMLs, also used by
10 # twister to parse YAMLs, by west, zephyr_module,...
13 # YAML validation. Used by zephyr_module.
16 # used by west_commands
26 # intelhex used by mergehex.py
|
| D | requirements-extras.txt | 3 # used by twister for --test-tree option
15 # used by scripts/gen_cfb_font_header.py - helper script for user
18 # can be used to sign a Zephyr application binary for consumption by a bootloader
21 # used by nanopb module to generate sources from .proto files
24 # used by scripts/release/bug_bash.py for generating top ten bug squashers
|
| /Zephyr-Core-2.7.6/include/crypto/ |
| D | cipher_structs.h | 113 * cipher operation. To be populated by crypto driver on return from
114 * begin_session() based on the algo/mode chosen by the app.
118 /** To be populated by the app before calling begin_session() */
129 * populated by the begin_session() API.
138 * by the driver on return from begin_session().
143 * completion callback happens for async ops. Totally managed by the
149 * in a session. To be populated by the app before calling
158 /** Cryptographic keylength in bytes. To be populated by the app
165 * To be populated by the app before calling begin_session().
166 * An app can obtain the capability flags supported by a hw/driver
[all …]
|
| /Zephyr-Core-2.7.6/scripts/west_commands/zspdx/ |
| D | licenses.py | 85 "CC-BY-1.0",
86 "CC-BY-2.0",
87 "CC-BY-2.5",
88 "CC-BY-3.0",
89 "CC-BY-3.0-AT",
90 "CC-BY-3.0-US",
91 "CC-BY-4.0",
92 "CC-BY-NC-1.0",
93 "CC-BY-NC-2.0",
94 "CC-BY-NC-2.5",
[all …]
|
| /Zephyr-Core-2.7.6/doc/guides/portability/ |
| D | cmsis_rtos_v2.rst | 21 ``osMutexPrioInherit`` is supported by default and is not configurable,
24 ``osMutexRecursive`` is also supported by default. If this attribute is
37 ``osErrorResource`` (the semaphore specified by parameter
41 ``osErrorResource`` (mutex specified by parameter mutex_id
45 ``osErrorResource`` (the timer specified by parameter timer_id
49 ``osErrorResource`` (the message queue specified by
54 ``osErrorResource`` (the message queue specified by
59 ``osErrorResource`` (the memory pool specified by
64 ``osErrorResource`` (the memory pool specified by
70 and osFlagsErrorResource (Event flags object specified by
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/networking/ |
| D | net_if.rst | 19 Network interfaces are created by ``NET_DEVICE_INIT()`` macro.
25 The network interface can be turned ON by calling ``net_if_up()`` and OFF
26 by calling ``net_if_down()``. When the device is powered ON, the network
27 interface is also turned ON by default.
29 The network interfaces can be referenced either by a ``struct net_if *``
30 pointer or by a network interface index. The network interface can be
31 resolved from its index by calling ``net_if_get_by_index()`` and from interface
32 pointer by calling ``net_if_get_by_iface()``.
36 by DHCPv4, for example. If needed though, the application can set a device's
50 lower priority packets. The traffic class setup can be configured by
|
| /Zephyr-Core-2.7.6/doc/guides/optimizations/ |
| D | footprint.rst | 11 should start the optimization process by reviewing all stack sizes and adjusting
15 Set to 2048 by default
18 Set to 1024 by default
21 Set to 320 by default
24 Set to 1024 by default
27 Set to 1024 by default, depends on userspace feature.
33 Some peripherals are enabled by default. You can disable unused
43 The following options are enabled by default to provide more information about
|
| /Zephyr-Core-2.7.6/samples/arch/smp/pi/ |
| D | README.rst | 13 By changing the value of CONFIG_MP_NUM_CPUS on SMP systems, you
24 This project outputs Pi values calculated by each thread and in the end total time
40 Calculate first 240 digits of Pi independently by 16 threads.
41 Pi value calculated by thread #0: 3141592653589793238462643383279502884197...
42 Pi value calculated by thread #1: 3141592653589793238462643383279502884197...
44 Pi value calculated by thread #14: 314159265358979323846264338327950288419...
45 Pi value calculated by thread #15: 314159265358979323846264338327950288419...
46 All 16 threads executed by 4 cores in 28 msec
|
| /Zephyr-Core-2.7.6/drivers/sensor/lsm6ds0/ |
| D | Kconfig | 20 Enable/disable accelerometer X axis totally by stripping everything
27 Enable/disable accelerometer Y axis totally by stripping everything
34 Enable/disable accelerometer Z axis totally by stripping everything
41 Enable/disable gyroscope X axis totally by stripping everything
48 Enable/disable gyroscope Y axis totally by stripping everything
55 Enable/disable gyroscope Z axis totally by stripping everything
61 Enable/disable temperature totally by stripping everything related in
80 Data rates supported by the chip are 0, 15, 60, 119, 238, 476,
97 Data rates supported by the chip are 0, 10, 50, 119, 238, 476, 952.
|
| /Zephyr-Core-2.7.6/doc/reference/kernel/synchronization/ |
| D | mutexes.rst | 8 an associated hardware or software resource by ensuring mutually exclusive
18 Any number of mutexes can be defined (limited only by available RAM). Each mutex
19 is referenced by its memory address.
24 by the thread that has locked it. A count of zero indicates that the mutex
34 to access it by **locking** the associated mutex. If the mutex is already locked
35 by another thread, the requesting thread may choose to wait for the mutex
45 When the mutex becomes unlocked it is then locked by the highest-priority
49 Mutex objects are *not* designed for use by ISRs.
58 A mutex that is repeatedly locked by a thread must be unlocked an equal number
60 by another thread.
[all …]
|
| D | semaphores.rst | 16 Any number of semaphores can be defined (limited only by available RAM). Each
17 semaphore is referenced by its memory address.
30 A semaphore may be **given** by a thread or an ISR. Giving the semaphore
33 A semaphore may be **taken** by a thread. Taking the semaphore
37 When the semaphore is given, it is taken by the highest priority thread
58 It must then be initialized by calling :c:func:`k_sem_init`.
61 semaphore by setting its count to 0 and its limit to 1.
70 by calling :c:macro:`K_SEM_DEFINE`.
81 A semaphore is given by calling :c:func:`k_sem_give`.
84 indicate that a unit of data is available for processing by a consumer thread.
[all …]
|
| /Zephyr-Core-2.7.6/ |
| D | LICENSE | 10 and distribution as defined by Sections 1 through 9 of this document.
12 "Licensor" shall mean the copyright owner or entity authorized by
16 other entities that control, are controlled by, or are under common
19 direction or management of such entity, whether by contract or
24 exercising permissions granted by this License.
36 Object form, made available under the License, as indicated by a
45 separable from, or merely link (or bind by name) to the interfaces of,
51 submitted to Licensor for inclusion in the Work by the copyright owner
52 or by an individual or Legal Entity authorized to submit on behalf of
57 and issue tracking systems that are managed by, or on behalf of, the
[all …]
|
| /Zephyr-Core-2.7.6/modules/trusted-firmware-m/ |
| D | Kconfig.tfm.crypto_modules | 22 Unset this option if the functionality provided by 'crypto_key.c'
30 Unset this option if the functionality provided by 'crypto_aead.c'
38 Unset this option if the functionality provided by 'crypto_mac.c'
46 Unset this option if the functionality provided by 'crypto_hash.c'
54 Unset this option if the functionality provided by 'crypto_cipher.c'
70 Unset this option if the functionality provided by 'crypto_asymmetric.c'
78 Unset this option if the functionality provided by 'crypto_key_derivation.c'
|
| /Zephyr-Core-2.7.6/dts/bindings/sensor/ |
| D | ti,fdc2x1x.yaml | 15 The SD pin defaults to active high when consumed by the sensor.
23 The INTB pin defaults to active low when produced by the sensor.
37 false = Continuous conversion on the single channel selected by
40 true = Auto-Scan conversions as selected by "rr-sequence"
61 The sensor performs conversion on Channel 0 to 1 by default after
80 The sensor performs continuous conversion on Channel 0 by default after
118 The sensor uses low-power activation mode by default after
124 low-power = the FDC uses the value programmed by "idrive" during
137 The sensor uses the internal clock by default after power-on-reset.
152 The sensor uses normal current drive by default after power-on-reset.
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/data_structures/ |
| D | index.rst | 7 used within the kernel, but useful by application code in general.
13 data structures. The "node" data is the only struct used by the
15 indicate what user data is "owned" by that node. Instead, the
21 allocate node objects because the memory is provided by the user).
24 them is not threadsafe by default. These are data structures, not
26 needed will be provided by the user.
|
| /Zephyr-Core-2.7.6/doc/reference/bluetooth/mesh/ |
| D | access.rst | 8 into elements and models, which are implemented by the application.
13 The functionality of a mesh node is represented by models. A model implements
29 not specified by the Bluetooth SIG are vendor models, and must be tied to a
41 can support any number of opcodes, but each opcode can only be listed by one
46 determined by the special :c:macro:`BT_MESH_MODEL_OP_END` entry. This entry
60 option. The contents of the AppKey list is managed by the
74 configuration option. The contents of the subscription list is managed by the
82 * By specifying a set of message parameters in a :c:struct:`bt_mesh_msg_ctx`,
84 * By setting up a :c:struct:`bt_mesh_model_pub` structure and calling
88 will use the publication parameters configured by the
[all …]
|
| /Zephyr-Core-2.7.6/include/arch/posix/ |
| D | linker.ld | 25 /* Located in generated directory. This file is populated by the
32 /* Located in generated directory. This file is populated by the
37 /* Located in generated directory. This file is populated by the
44 /* Located in generated directory. This file is populated by the
51 /* Located in generated directory. This file is populated by the
58 /* Located in generated directory. This file is populated by the
63 /* Located in generated directory. This file is populated by the
|
| /Zephyr-Core-2.7.6/doc/reference/kernel/data_passing/ |
| D | message_queues.rst | 17 Any number of message queues can be defined (limited only by available RAM).
18 Each message queue is referenced by its memory address.
36 A data item can be **sent** to a message queue by a thread or an ISR.
37 The data item pointed at by the sending thread is copied to a waiting thread,
48 A data item can be **received** from a message queue by a thread.
49 The data item is copied to the area specified by the receiving thread;
60 The data item is copied to the area specified by the receiving thread;
74 It must then be initialized by calling :c:func:`k_msgq_init`.
93 by calling :c:macro:`K_MSGQ_DEFINE`.
106 is divisible by 4.
[all …]
|
| /Zephyr-Core-2.7.6/arch/xtensa/core/ |
| D | README-WINDOWS.rst | 15 The first quad (A0-A3) is pointed to by a special register called
21 window by a immediate number of quads that are added to WINDOWBASE.
28 callee) by 1, 2 or 3 quads. These do not rotate the window
53 will be set by the ENTRY instruction, and remain set after rotations
54 until cleared by a function return (by RETW, see below). Other bits
57 followed by 0, 1 or 2 zero bits that tell you how "big" (how many
65 Likewise, the processor can tell if a high register is "owned" by
66 another call by seeing if there is a one in WINDOWSTART between that
74 the frame bit to detect how many quads are represented by the one
81 be spilled naturally into the stack by using the stack pointers
[all …]
|
| /Zephyr-Core-2.7.6/samples/boards/nrf/nrfx_prs/ |
| D | README.rst | 13 and the lack of possibility to deinitialize a peripheral that is initialized by
17 for other instances of the same peripheral types (UARTE0 is used by the standard
21 - by pressing Button 1 user can request a transfer to be performed using the
23 - by pressing Button 2 user can switch between the two peripherals
31 for the UARTE), it can be checked that what is sent by a given peripheral
32 is also received back. Without such wiring, no data is received by UARTE and
33 all zeros are received by SPIMs. Refer to the overlay files provided in the
35 on the boards supported by the sample are assigned as MOSI/MISO and TX/RX pins.
|
| /Zephyr-Core-2.7.6/doc/security/ |
| D | secure-coding.rst | 34 Zephyr. This is followed by
45 incorporate changes into the Zephyr codebase. This is followed by
46 documentation about how security-sensitive issues are handled by the
68 of the Zephyr project, this can be realized, e.g., by modular code
75 - **Fail-safe defaults** defines that access is restricted by default
76 and permitted only in specific conditions defined by the system
79 to provide maximum security. This corresponds to the "Secure by
95 implemented as a shared library executed by each user and not as a
96 supervisor procedure shared by all users.
99 easy to use by the developers in order to ensure their usage and the
[all …]
|
| /Zephyr-Core-2.7.6/soc/xtensa/intel_adsp/common/bootloader/ |
| D | manifest.h | 56 * Module segment descriptor. Used by ROM - Immutable.
74 * Each module has an entry in the FW header. Used by ROM - Immutable.
92 * Each module has a configuration in the FW header. Used by ROM - Immutable.
116 * The firmware has a standard header that is checked by the ROM on firmware
117 * loading. preload_page_count is used by DMA code loader and is entire
119 * Used by ROM - Immutable.
125 /* number of pages of preloaded image loaded by driver */
144 * configs. Used by ROM - Immutable.
150 * have a variable size array of struct man_module followed by a
162 * Component Descriptor. Used by ROM - Immutable.
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/usermode/ |
| D | overview.rst | 9 User mode threads are considered to be untrusted by Zephyr and are therefore
41 - A user thread will by default have read/write access to its own stack
44 - A user thread will never by default have access to user thread stacks
47 - A user thread will never by default have access to thread stacks owned
48 by a supervisor thread, or thread stacks used to handle system call
59 - By default, program text and read-only data are accessible to all threads
62 - User threads by default are not granted default access to any memory
84 - We prevent invoking system calls to functions excluded by the kernel
93 - We prevent the introduction of new executable code by user mode threads,
94 except to the extent to which this is supported by kernel system calls.
[all …]
|
| /Zephyr-Core-2.7.6/dts/bindings/usb/ |
| D | usb-ep.yaml | 4 # Common fields that give the number of endpoints supported by the USB hardware
13 Number of bi-directional endpoints supported by hardware
20 Number of IN endpoints supported by hardware
27 Number of OUT endpoints supported by hardware
|
| /Zephyr-Core-2.7.6/doc/reference/kernel/other/ |
| D | float.rst | 16 The kernel does not support the use of floating point registers by ISRs.
26 required by an application. Three modes of operation are supported,
46 be used by any thread (initialization in skipped on ARM Cortex-M platforms and
71 by any thread, then saves and restores these registers during
72 context switches to ensure the computations performed by each FPU user
73 or SSE user are not impacted by the computations performed by the other users.
88 Pretag a thread that intends to use the FP registers by
91 * A statically-created ARM thread can be pretagged by passing the
94 * A dynamically-created ARM thread can be pretagged by passing the
125 * Lazy stacking is activated by default on threads that are pretagged with
[all …]
|
