Searched refs:could (Results 26 – 50 of 320) sorted by relevance
12345678910>>...13
| /Zephyr-latest/boards/shields/x_nucleo_bnrg2a1/doc/ |
| D | index.rst | 38 Shield configuration could be modified by moving resistors or changing jumper as
44 expansion board could be made:
|
| /Zephyr-latest/tests/subsys/logging/log_blocking/ |
| D | REAME.md | 64 ideal scenario. In reality, it is not. The rates could be matched, but a
65 sustained increase (or several small increases) in the input log rate, could
96 Remediation could involve disabling the log backend and freeing any in-use
|
| /Zephyr-latest/cmake/modules/ |
| D | python.cmake | 25 # cause just using find_program directly could result in a python2.7 as python,
|
| /Zephyr-latest/samples/drivers/uart/echo_bot/ |
| D | README.rst | 15 for receiving, so that in theory the thread could do something else
|
| /Zephyr-latest/boards/shields/seeed_xiao_expansion_board/doc/ |
| D | index.rst | 12 peripherals, you could explore the infinite possibilities of Seeed Studio
|
| /Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32u5_devices/boards/ |
| D | core_init.overlay | 8 * Warning: This overlay clears clocks back to a state equivalent to what could
|
| /Zephyr-latest/samples/drivers/i2c/rtio_loopback/ |
| D | README.rst | 34 that this could be the same controller. This is done using the devicetree
|
| /Zephyr-latest/doc/services/binary_descriptors/ |
| D | index.rst | 20 ``my_string`` could then be accessed using:
26 But it could also be retrieved by ``west bindesc``:
90 Some descriptors might be trivial to implement, and could therefore be implemented
91 in a standard way in upstream Zephyr. These could then be enabled via Kconfig, instead
|
| /Zephyr-latest/soc/espressif/ |
| D | Kconfig | 62 If the crystal could not start, it will be switched to internal RC.
|
| /Zephyr-latest/subsys/net/ |
| D | Kconfig.hostname | 39 hostname. For example, zephyr00005e005357 could be the hostname
|
| /Zephyr-latest/samples/net/lwm2m_client/ |
| D | Kconfig | 40 When DNS resolver is enabled, DNS domain names could be used as well.
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt118x/ |
| D | Kconfig | 56 value, this will make ROM could get the user image start address.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_hostname.rst | 28 ``01:02:03:04:05:06``, then the unique hostname could be
|
| D | net_pkt.rst | 85 the time of buffer allocation. Then one could do:
91 Where proto could be 0 if unknown (there is no IPPROTO_UNSPEC).
205 length, which means no valid data is in its buffer. One could verify
313 fit in a net_buf of 128 bytes (for instance, though 64 bytes could be
352 updated. Note that :c:func:`net_pkt_set_data` could be used in the RX
|
| /Zephyr-latest/samples/sensor/6dof_motion_drdy/ |
| D | README.rst | 13 Trigger options could be configured through KConfig.
|
| /Zephyr-latest/samples/drivers/can/counter/ |
| D | README.rst | 19 In loopback mode, the board receives its own messages. This could be used for
|
| /Zephyr-latest/cmake/bintools/arcmwdt/ |
| D | elfconvert_command.cmake | 46 # There could be more than one, so need to check all args.
|
| /Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32h7_devices/boards/ |
| D | core_init.overlay | 8 * Warning: This overlay clears clocks back to a state equivalent to what could
|
| /Zephyr-latest/doc/security/ |
| D | hardening-tool.rst | 33 could lead to a security vulnerability, the table will propose a recommended value that should be
|
| /Zephyr-latest/samples/subsys/llext/edk/ |
| D | README.rst | 40 One could build the extensions in different directories, not related to the
42 limit, one could even imagine a scenario where the extensions are built by
|
| /Zephyr-latest/boards/adi/sdp_k1/ |
| D | adi_sdp_120pin_connector.dtsi | 55 <84 0 &gpiob 6 0>, /* SPI_SEL_A_N - could be PB6 or PB9 */
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 89 This ATE could be at any position of the sector.
160 could slow down the calling thread.
187 When calling ZMS to make a write, the current sector could be almost full such that ZMS needs to
192 The application could then decide when to switch to the next sector if the current one is almost
218 (this could change in future versions of ZMS).
260 Total data that could be stored in this partition for this case is :math:`11 \times 3 \times 64 = 2…
280 data (including headers) that could be written in the storage.
395 verified to make sure that the application could work with one subsystem or the other, then if
396 both solutions could be implemented, the best choice should be based on the calculations of the
|
| /Zephyr-latest/subsys/net/l2/ieee802154/ |
| D | Kconfig.radio | 19 replying it could not send the packet (MAC PIB attribute:
|
| /Zephyr-latest/lib/posix/options/getopt/ |
| D | README | 22 in the FreeBSD project. I had to modify it so that it could be used
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | networking_with_multiple_instances.rst | 11 Zephyr instances. The Zephyr instances could be running inside QEMU
12 or could be native_sim board processes. The Linux host can be used
|
12345678910>>...13
