Searched refs:being (Results 126 – 150 of 357) sorted by relevance
12345678910>>...15
| /Zephyr-latest/modules/hal_gigadevice/ |
| D | CMakeLists.txt | 24 # The HXTAL_VALUE has the possibility of being referenced from any files
|
| /Zephyr-latest/samples/bluetooth/mesh_provisioner/ |
| D | README.rst | 12 to be tested together with a device capable of being provisioned. For
|
| /Zephyr-latest/soc/espressif/common/ |
| D | Kconfig.esptool | 186 Automatic resetting depends on the RTS & DTR signals being
207 Automatic resetting depends on the RTS & DTR signals being
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | smp_protocol.rst | 65 | ``Ver`` (Version) | This indicates the version of the protocol being |
207 response lacks these, the request can be considered as being successful. For SMP version 2,
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 70 debugging why some object was unexpectedly not being tracked. This
168 :c:func:`k_object_access_grant` on each of them. The thread being granted
169 permission, or the object whose access is being granted, do not need to be
190 not being tracked by the kernel will be no-ops. Doing the same from user mode
|
| D | mpu_stack_objects.rst | 61 Size and alignment constraints may result in stack allocations being larger
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 59 The intention being to be able to run tests much faster than real time,
90 test in general not being reproducible, and in many cases failures
91 not being easy to debug.
132 nrf_bsim targets, you are using the `native simulator`_, which is being built together with and
181 Note that the POSIX arch and ``inf_clock`` soc expect a set of APIs being provided by
233 load of the simulation host or by the process execution being "paused"
|
| /Zephyr-latest/subsys/debug/coredump/ |
| D | Kconfig | 90 being performed in total, but consume more memory.
|
| /Zephyr-latest/subsys/dfu/ |
| D | Kconfig | 60 that MCUboot cannot update due to being too large. This should be set from sysbuild, only
|
| /Zephyr-latest/doc/connectivity/usb/host/ |
| D | usbip.rst | 11 connected to the host controller being exported.
|
| /Zephyr-latest/samples/net/prometheus/ |
| D | README.rst | 89 being scraped by checking the Prometheus targets page or querying Prometheus for
|
| /Zephyr-latest/samples/drivers/ipm/ipm_imx/ |
| D | README.rst | 29 The sample requires that data are being sent by the remote core so it can echo
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig | 19 to signal that there is a serial driver. This is being used
86 being active at a time. Setting a new callback to one set of
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_mgmt.rst | 37 implied, and the specific management procedure being requested. The
79 multiple listeners registered, one for each layer being listened.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu_srv.rst | 85 about which image is being updated, as well as the update metadata.
104 ensure that it is ready for being applied. Once the image has been verified, the application calls
|
| D | brg_cfg.rst | 139 update the stored IVISeq before being relayed.
142 as every bridged message must pass through the replay protection mechanism before being relayed.
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 246 shall have the ability to block the change from being merged into the
260 field shall result in the issue only being visible to the Zephyr Security
266 duration, with a default being a project-decided value. However,
286 infrastructure being taken down.
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 73 Obviously, the page table memory being virtual means that the fetch
184 an ASID of zero. This is safe as the code being executed is not
254 being stored twice in the same CPU, wasting transistors that could
258 incoherent! The cache being used for refill reflects the last access
259 on the current CPU only, and not of the underlying memory being
|
| /Zephyr-latest/soc/atmel/sam/common/ |
| D | Kconfig | 24 The main clock is being used to drive the PLL, and thus driving the
|
| /Zephyr-latest/cmake/modules/ |
| D | west.cmake | 14 # WEST_PYTHON not being used.
|
| /Zephyr-latest/doc/services/storage/disk/ |
| D | nvme.rst | 75 At this stage then, it is up to the user to make sure the buffer address being provided to
|
| /Zephyr-latest/boards/olimex/stm32_h405/doc/ |
| D | index.rst | 134 The sample application :zephyr:code-sample:`hello_world` is being used in this tutorial.
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 70 interrupt to your callback function being run. In the work queue
|
| /Zephyr-latest/doc/services/tfm/ |
| D | build.rst | 128 being expanded as a list.
141 The tools run on the final images and give information about size of symbols and code being used in…
|
| /Zephyr-latest/samples/subsys/logging/syst/ |
| D | README.rst | 54 Since the output is being directed to a text file, there will not be
203 are being referenced by identification hashes, and the string arguments
225 Since the output is being directed to a text file, there will not be
|
12345678910>>...15
