| /Zephyr-latest/modules/hal_nordic/nrfx/ |
| D | nrfx_config_reserved_resources.h | 10 /** @brief Bitmask that defines GPIOTE130 channels reserved for use outside
17 /** @brief Bitmask that defines GPIOTE131 channels reserved for use outside
24 /** @brief Bitmask that defines EGU instances that are reserved for use outside
29 /** @brief Bitmask that defines TIMER instances that are reserved for use outside
38 * paths so that the file can be included here for all Zephyr libraries that
455 /** @brief Bitmask that defines DPPI channels that are reserved for use outside
462 /** @brief Bitmask that defines DPPI groups that are reserved for use outside
469 /** @brief Bitmask that defines DPPI channels that are reserved for use outside
476 /** @brief Bitmask that defines DPPI groups that are reserved for use outside
483 /** @brief Bitmask that defines DPPI channels that are reserved for use outside
[all …]
|
| /Zephyr-latest/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:struct:`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-latest/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-latest/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
84 Helper that can be used to check if the platform is capable of generating
[all …]
|
| /Zephyr-latest/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-latest/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-latest/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-latest/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-latest/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-latest/tests/benchmarks/thread_metric/ |
| D | Kconfig | 13 These tests measure the total number of RTOS events that can be
19 The baseline basic benchmark consists of a single thread that counts
27 of equal priority that yield to each other and increment counters
37 The interrupt processing benchmark has a single thread that causes
40 takes that semaphore. The sum total of the counters is reported
49 The interrupt preemption benchmark counts the number of times that
64 The message processing benchmark counts the number of times that a
72 of different priorities that suspend and resume each other in a
79 The synchronization benchmark counts the number of times that a
|
| /Zephyr-latest/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-latest/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-latest/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-latest/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-latest/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-latest/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-latest/doc/ |
| D | glossary.rst | 16 The set of user-supplied files that the Zephyr build system uses
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
49 A set of kernel configuration options that specify how the devices
52 for each board it supports. The kernel configuration settings that are
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
77 The full string that can be provided to any of the Zephyr build tools to
103 A system thread that runs when there are no other threads ready to run.
[all …]
|
| /Zephyr-latest/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-latest/drivers/flash/ |
| D | Kconfig | 17 This option is selected by drivers that support flash extended
31 Note that explicit-erase capability does not warrants that
33 it only states that write of a random information will require
36 the unit in Zephyr, that may have different naming in device
39 This option should be selected by drivers that serve devices with
41 paths in code that only serve such devices, and could be
49 a new random value at any location that has been previously
51 Note that the device may have erase-on-write (auto-erase),
58 that would be used to emulate erase.
59 This option should be selected by drivers that serve
[all …]
|
| /Zephyr-latest/tests/boot/with_mcumgr/pytest/ |
| D | test_upgrade.py | 47 Verify that the application can be updated
48 1) Device flashed with MCUboot and an application that contains SMP server
52 5) Restart the device, verify that swapping process is initiated
53 6) Verify that the updated application is booted
55 8) Restart the device, and verify that the new application is still booted
98 Verify that MCUboot will roll back an image that is not confirmed
99 1) Device flashed with MCUboot and an application that contains SMP server
103 5) Restart the device, verify that swapping process is initiated
104 6) Verify that the updated application is booted
106 8) Verify that MCUboot reverts update
[all …]
|
| /Zephyr-latest/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-latest/tests/drivers/watchdog/wdt_error_cases/ |
| D | README.txt | 2 Test scenarios validate that invalid use of the watchdog driver
7 However, it may happen that invalid function call results in
20 These tests were prepared on a target that had a bug in the wdt_disable()
33 target that supports disabling the watchdog.
35 Every test assumes that watchdog is disabled at startup.
36 As a result, executing this test suite on a target that doesn't
41 2. There are three watchdog flags that can be passed to wdt_install_timeout():
56 3. These tests assume that watchdog driver supports multiple timeouts. Set
65 Also, test assumes that minimal allowed watchdog timeout value must be zero.
67 6. There are two watchdog options that can be passed to wdt_setup():
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 20 open-source cryptographic library that provides the underlying
27 special-purpose cryptographic processors that process data with a
39 The PSA Crypto API includes robust key management features that
47 meaning that the specific implementation can be changed without
53 By adhering to cryptographic agility, PSA Crypto ensures that
73 The API provides support for key agreement protocols that are often
87 device state, to the ability to generate a key pair and prove that it
95 with keys that represent that identity.
102 that can fail have the return type ``psa_status_t``. A few functions
111 separate environment from the application, all functions that need
[all …]
|
