| /Zephyr-Core-3.6.0/doc/develop/api/ |
| D | terminology.rst | 22 initialized and will have its specified effect when invoked from that
40 The reschedule attribute is used on a function that can reach a
46 The significance of this attribute is that when a rescheduling function
47 is invoked by a thread it is possible for that thread to be suspended as
53 Note that in the case of timeslicing, or reschedule points executed from
56 Functions that are not **reschedule** may be invoked from either thread
59 Functions that are **reschedule** may be invoked from thread context.
61 Functions that are **reschedule** but not **sleep** may be invoked from
69 The sleep attribute is used on a function that can cause the invoking
76 applications that use only non-preemptible threads, because the kernel
[all …]
|
| D | design_guidelines.rst | 7 maintenance and enhancements there are some general policies that should
20 pointer to another object that was referenced when the callback was
28 context that allows a shared callback function to locate additional
32 allowed when the callback itself was provided through a structure that
35 specific to the code that also defines the callback function. In those
48 The assumption here, as with :c:type:`gpio_callback`, is that the
50 :c:macro:`CONTAINER_OF` that can provide additional context to the
71 APIs and libraries may provide features that are expensive in RAM or
72 code size but are optional in the sense that some applications can be
82 * Any data that is accessed only when the feature is enabled should be
[all …]
|
| /Zephyr-Core-3.6.0/arch/arm/core/ |
| D | Kconfig.vfp | 7 # indicate that the CPU core can be configured with the specified
35 that supports only single-precision operations with 16 double-word
46 that supports half- and single-precision operations with 16
58 that supports half- and single-precision operations (including fused
69 that supports single- and double-precision operations with 16
81 that supports half-, single- and double-precision operations with 16
94 that supports half-, single- and double-precision operations
108 that supports half-, single-, double-precision operations (including
122 that supports half-, single- and double-precision operations
136 that supports half-, single-, double-precision operations (including
[all …]
|
| /Zephyr-Core-3.6.0/doc/kernel/services/smp/ |
| D | smp.rst | 8 "symmetric" in the sense that no specific CPU is treated specially by
22 number of available CPUs on the platform and it is not expected that
40 does not: the fact that your CPU will not be interrupted while you are
49 that not only masks interrupts locally, as done by :c:func:`irq_lock`, but
50 also atomically validates that a shared lock variable has been
58 One important difference between IRQ locks and spinlocks is that the
63 single global resource. But that means that spinlocks must not be
64 used recursively. Code that holds a specific lock must not try to
83 threads. The kernel will ensure that only one thread across all CPUs
84 can hold the lock at any time, that it is released on context switch,
[all …]
|
| /Zephyr-Core-3.6.0/arch/xtensa/core/ |
| D | README_WINDOWS.rst | 4 Zephyr plays some tricks here that require understanding the base
20 There is a ROTW instruction that can be used to manually rotate the
21 window by a immediate number of quads that are added to WINDOWBASE.
23 (i.e. after "ROTW 1" the register that used to be called A4 is now
33 There is an ENTRY instruction that does the rotation. It adds CALLINC
38 There is a RETW instruction that undoes the rotation. It reads the
39 top two bits from the return address in A0 and subtracts that value
42 many calls, so they need to be GPR data that lives in registers and
47 Note that we still don't know how to detect when the register file has
56 each call frame that is live in hardware registers, and it will be
[all …]
|
| D | README_MMU.txt | 34 their ring field of the PTE that loaded them, via a simple translation
35 specified in the RASID special register. The intent is that each
37 such that you can switch between them without a TLB flush. The ASID
42 attribute value that can be used in a PTE).
57 This is extremely simple (just one extra hardware state that does just
64 physical address. Which means that the page tables occupy a 4M region
66 occupied by the running code. The 1024 pages in that range (not all
69 virtual memory. Note especially that exactly one of those pages
73 Obviously, the page table memory being virtual means that the fetch
78 already know we're missing that TLB entry), the hardware has exactly
[all …]
|
| /Zephyr-Core-3.6.0/dts/bindings/mtd/ |
| D | jedec,spi-nor-common.yaml | 9 # that may be specific to the vendor of a M25P80-compatible device and
10 # only supported in certain drivers. Any information that can be
23 protection register that initializes to write-protected. Use this
24 property to indicate that the BPR must be unlocked before write
33 Power-Down mode that is entered by command 0xB9 to reduce power
35 implies that the RDPD (0xAB) Release from Deep Power Down command
52 Absence of this property indicates that the RDPD command should be
60 This provides the duration, in nanoseconds, that CSn must be
71 This provides the duration, in nanoseconds, that CSn must be
80 Bit mask of bits of the status register that should be cleared on
[all …]
|
| /Zephyr-Core-3.6.0/subsys/random/ |
| D | Kconfig | 11 This option signifies that a non-random number generator is allowed to
13 values that are not truly random.
20 configurations (e.g. in tests and samples) to indicate that the
21 application is allowed to run with a random number generator that is not
26 Note that this option does not imply that a non-random number generator
27 is selected -- that is indicated by RNG_GENERATOR_CHOICE. An entropy
48 to support random request then select that. Otherwise, select the
63 Enables a random number generator that uses the enabled hardware
72 Enables the Xoshiro128++ pseudo-random number generator, that uses
95 performance to support CSRNG then select that. Otherwise, select
[all …]
|
| /Zephyr-Core-3.6.0/tests/kernel/device/src/ |
| D | mmio.c | 47 * We show that we can make mapping calls and that the address returned by
48 * DEVICE_MMIO_GET() is not NULL, indicating that the kernel mapped
52 * - If MMIO addresses are maintained in RAM, check that the ROM struct
54 * - If MMIO addresses are maintained in ROM, check that the DTS info,
56 * point to the same address. We show that no extra memory is used in
72 /* A sign that something didn't get initialized, shouldn't ever in ZTEST()
79 * The best we can check with 'regs' is that it's nonzero, as if in ZTEST()
82 * prove that k_map() actually works. in ZTEST()
141 * We show that we can make mapping calls and that the address returned by
142 * DEVICE_MMIO_NAMED_GET() is not NULL, indicating that the kernel mapped
[all …]
|
| /Zephyr-Core-3.6.0/tests/subsys/shell/shell_history/src/ |
| D | shell_history_test.c | 59 * - read line and verify that it is the one that was put.
78 /* Test verifies that after purging there is no line in the history. */
100 * - get in up direction a line and verify that it's the last one added (3).
101 * - get next line in up direction and verify that it's line 2.
102 * - get next line in up direction and verify that it's line 1.
103 * - get next line in down direction and verify that it's line 2.
104 * - get next line in up direction and verify that it's line 1.
105 * - get next line in down direction and verify that it's line 2.
106 * - get next line in down direction and verify that it's line 3.
107 * - attempt to get next line in down direction and verify that there is no
[all …]
|
| /Zephyr-Core-3.6.0/tests/drivers/sdhc/ |
| D | README.txt | 5 SD host controller API. It requires that an SD card be present on the SD bus
9 This primarily tests that the driver returns zero for this call, although if
12 * Host props: Get host properties structure from SDHC. This verifies that
16 * Set_IO test: Verify that the SDHC will reject clock frequencies outside of
19 * Card presence test. Verify that the SDHC detects card presence.
22 and verify that valid data is returned.
24 Note that this test does not verify the tuning or card busy api, as the SD
|
| /Zephyr-Core-3.6.0/doc/kernel/services/timing/ |
| D | clocks.rst | 23 and :c:func:`k_cycle_get_64` APIs. The intent is that this counter
24 represents the fastest cycle counter that the operating system is able
25 to present to the user (for example, a CPU cycle counter) and that the
26 read operation is very fast. The expectation is that very sensitive
31 platforms is a runtime constant that evaluates to
40 hardware platforms (ones that support setting arbitrary interrupt
80 Apps with precise timing requirements (that are willing to do their
102 an opaque struct type that must be initialized using one of a family
112 time" will already have advanced. This is to ensure that timers scheduled from
123 :c:macro:`K_CYC()` specify timeout values that will expire after specified
[all …]
|
| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/mesh/tests_scripts/op_agg/ |
| D | model_coex.sh | 7 # Test that Opcode aggregator server and client can coexist on the same device.
9 # Aggregator client model that is interrupted by an incoming sequence to the Opcode
10 # Aggregator server model. The test verifies that both the incoming and outgoing
17 # 3. The DUT device waits, and verifies that the sequence is correctly received.
19 # 4. The Tester device confirms that it received all status messages related to its
20 # own aggregated sequence from the DUT device, then it verifies that the
22 # 5. Finally, the DUT device waits and confirms that it received all status messages
|
| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/mesh/tests_scripts/priv_beacon/ |
| D | proxy_adv_multi_subnet_coex.sh | 12 # the RX device scans and verifies that the correct proxy adv messages of
16 # in this scenario is 10 seconds when there is more than one subnet that
26 # network beacons. This allows to check that proxy goes back to normal
31 # Proxy enabled. RX device verifies that the single subnet has exclusive
34 # device checks that the subnets are sharing the adv medium, advertising
37 # checks that NODE_ID is advertised by this subnet, and that the two
40 # checks that PRIVATE_NET_ID is advertised by these subnets.
42 # device. RX device verifies that the single subnet has exclusive access
|
| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/mesh/tests_scripts/advertiser/ |
| D | disable.sh | 7 # The test checks that both advertisers, the legacy and the extended, behave identically.
9 # - `bt_mesh_send_cb.end` callback with error code `0` is called for the advertisement that the
11 # - `bt_mesh_send_cb.start` callback with error `-ENODEV` is called for every advertisement that
22 # 4. Tx device checks that for the first adv the `bt_mesh_send_cb.end` callback is called with the
24 # 5. Tx device checks that for the consecutive advs the `bt_mesh_send_cb.start` is called with error
26 # 6. Tx device checks that no more advs can be created using `bt_mesh_adv_create` function.
28 # 8. Tx device expects that all advs are sent.
31 # 1. Rx devices listens all the time while tx device sends advs and ensure that no new advs were
|
| /Zephyr-Core-3.6.0/cmake/bintools/ |
| D | bintools_template.cmake | 18 # - <tool>_flag : Flags that must always be used with this command
28 # only set those flags that a given set of tools support.
31 # This is done, so that unexpected calls to non-implemented command can be easily detected.
35 # The bintools properties are made generic so that implementing support for an
56 # memusage_flag : Flags that must always be applied when calling memusage command
57 # memusage_flag_final : Flags that must always be applied last at the memusage command
65 # elfconvert_flag : Flags that must always be applied when calling elfconvert comma…
66 # elfconvert_flag_final : Flags that must always be applied last at the elfconvert command
67 # elfconvert_flag_strip_all : Flag that is used for stripping all symbols when converting
68 # elfconvert_flag_strip_debug : Flag that is used to strip debug symbols when converting
[all …]
|
| /Zephyr-Core-3.6.0/dts/bindings/pinctrl/ |
| D | espressif,esp32-pinctrl.yaml | 17 that board's original device tree source file (i.e., 'esp_wrover_kit.dts'),
18 you'll notice that the I2C_0 node is already assigned to a pre-defined state.
19 Below is highlighted the information that most interests us on that file
34 Check below the excerpt describing I2C_0's default state on that file
59 Note that replacing 'I2C0_SDA_GPIO21' by 'I2C0_SDA_GPIO33' is very tempting and
61 it is not recommended. That's because there are no guarantees that a particular
71 The ESP-WROVER-KIT board is based on the ESP32 SoC, in that case, we search
73 one definition on that file that corresponds to our needs
81 on that file (or replace/update the one already defined) using the pinmux macro
99 Note: Not all pins are available for a given peripheral, it depends if that
[all …]
|
| /Zephyr-Core-3.6.0/tests/boot/with_mcumgr/pytest/ |
| D | test_upgrade.py | 53 Verify that the application can be updated
54 1) Device flashed with MCUboot and an application that contains SMP server
58 5) Restart the device, verify that swapping process is initiated
59 6) Verify that the updated application is booted
61 8) Restart the device, and verify that the new application is still booted
103 Verify that MCUboot will roll back an image that is not confirmed
104 1) Device flashed with MCUboot and an application that contains SMP server
108 5) Restart the device, verify that swapping process is initiated
109 6) Verify that the updated application is booted
111 8) Verify that MCUboot reverts update
[all …]
|
| /Zephyr-Core-3.6.0/subsys/mgmt/mcumgr/grp/img_mgmt/ |
| D | Kconfig | 12 # When adding Kconfig options, that control the same feature,
36 the CONFIG_IMG_BLOCK_BUF_SIZE size and additional fields that hold the state information
39 Make sure with testing, when enabling the option, that the heap has enough size
42 operation, an issue that should also be addressed within application.
54 needs to be set to the same value; this is due to the fact that the MCUmgr uses
56 by that library.
71 image, via MCUmgr commands, to prevent confirming something that is
81 image, via MCUmgr commands, to prevent confirming something that is
90 erasing slots that have been set for next boot but the device has not
103 behaviour is, when image is not selected, to upload to image that represents secondary
[all …]
|
| /Zephyr-Core-3.6.0/doc/ |
| D | zephyr.doxyfile.in | 14 # Values that contain spaces should be placed between quotes (\" \").
31 # file that follow. The default is UTF-8 which is also the encoding used for all
40 # double-quotes, unless you are using Doxywizard) that should identify the
54 # for a project that appears at the top of each page and should give viewer a
59 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
84 # Controls the number of sub-directories that will be created when
91 # This tag requires that the tag CREATE_SUBDIRS is set to YES.
119 # descriptions after the members that are listed in the file and class
134 # This tag implements a quasi-intelligent brief description abbreviator that is
153 # inherited members of a class in the documentation of that class as if those
[all …]
|
| /Zephyr-Core-3.6.0/doc/contribute/ |
| D | external.rst | 7 order to avoid re-implementing basic functionality or features that are readily
11 imported into Zephyr, and the process that governs the inclusion.
13 There are three main factors that will be considered during the inclusion
17 Note that most of this page deals with external components that end up being
19 hardware. For external tooling that is only used during compilation,
31 Integrating code into the Zephyr Project from other projects that use a license
34 `Zephyr project charter`_. The board will automatically reject licenses that
48 for contributed code, we ensure that the Zephyr community can develop products
54 Just like with any other regular contribution, one that contains external code
55 needs to be evaluated for merit. However, in the particular case of code that
[all …]
|
| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/mesh/tests_scripts/friendship/ |
| D | lpn_disable.sh | 7 # Check that disabling LPN gives correct behaviour.
10 # disables it again. Then we check that that the lpn node is actually in a
11 # disabled state. This test ensures that a lpn disable call is not overwritten
13 # internal callback structures that might produce incorrect internal state
|
| /Zephyr-Core-3.6.0/dts/bindings/sd/ |
| D | zephyr,sdmmc-disk.yaml | 3 host controller device node indicates that an SDMMC disk is attached to that
4 SD bus. This binding will enable that disk to be used with the disk driver
5 API and any subsystems that utilize it.
|
| /Zephyr-Core-3.6.0/include/zephyr/bluetooth/mesh/ |
| D | statistic.h | 27 /** The structure that keeps statistics of mesh frames handling. */
38 /** Counter of frames that were initiated to relay over advertiser bearer. */
40 /** Counter of frames that succeeded relaying over advertiser bearer. */
42 /** Counter of frames that were initiated to send over advertiser bearer locally. */
44 /** Counter of frames that succeeded to send over advertiser bearer locally. */
46 /** Counter of frames that were initiated to send over friend bearer. */
48 /** Counter of frames that succeeded to send over friend bearer. */
|
| /Zephyr-Core-3.6.0/tests/drivers/disk/disk_access/ |
| D | README.txt | 8 * Setup test: Verifies that disk initialization works, as well as testing
10 Note that this test also verifies the memory buffers reserved for read/write
14 * Read test: Verifies that the driver can consistently read sectors. This test
20 location, to verify that the data being returned is the same.
22 * Write test: Verifies that the driver can consistently write sectors. This test
26 writes that would be outside the bounds of the disk), then performs multiple
|
