Searched refs:needs (Results 101 – 125 of 523) sorted by relevance
12345678910>>...21
| /Zephyr-latest/include/zephyr/linker/ |
| D | app_smem.ld | 24 * hackish needs to be used since CMake does not parse
|
| D | kobject-data.ld | 24 * space needs to be reserved for the rodata that will be
|
| D | app_smem_pinned.ld | 28 * hackish needs to be used since CMake does not parse
|
| /Zephyr-latest/samples/net/sockets/echo_client/boards/ |
| D | mimxrt1020_evk.overlay | 46 * the PHY's mdio interrupt needs to be disabled.
|
| /Zephyr-latest/tests/drivers/regulator/voltage/boards/ |
| D | mimxrt685_evk_mimxrt685s_cm33.overlay | 38 /* Note: LDO2 voltage range needs to be tested first
|
| /Zephyr-latest/modules/hal_rpi_pico/bootloader/ |
| D | CMakeLists.txt | 53 # Therefore, in order to use toolchain.h, it needs to define CONFIG_ARM.
|
| /Zephyr-latest/samples/drivers/eeprom/ |
| D | README.rst | 27 Otherwise either a board specific overlay needs to be defined, or a shield must
|
| /Zephyr-latest/modules/zcbor/ |
| D | Kconfig | 30 needs to be enabled in the state variable
|
| /Zephyr-latest/samples/sensor/th02/ |
| D | README.rst | 31 The LCD display requires 5 volts, so the voltage switch on the shield needs to
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | socket_service.rst | 17 as only one thread needs to be created in the system in this case.
94 The application needs to create the sockets, then register them to the socket
140 The TCP socket needs slightly different logic as we need to add any
|
| D | net_l2.rst | 35 one needs to understand how the L3 layer interacts with it and
45 The L2 stack does what it needs to do with the packet, for example, parsing
96 After all the network data has been received, the device driver needs to
119 which overloads :c:struct:`net_if_api`. This is because 802.15.4 L2 needs more from the device
153 - L1 -> L2: There are several situations in which the driver needs to initiate
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 52 On the host PC, a virtual SocketCAN interface needs to be created and brought up before running the
60 Next, python-can needs to be configured for the ``zcan0`` interface. One option is to use a
101 Next, python-can needs to be configured for the ``can0`` interface. One option is to use a dedicated
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.ipv6 | 89 The value depends on your network needs.
143 The value depends on your network needs. MLD should normally
151 The value depends on your network needs. Neighbor cache should
160 The value depends on your network needs. ND should normally
168 The value depends on your network needs. DAD should normally
187 See RFC 6106 for details. The value depends on your network needs.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | provisioning.rst | 39 needs to be provisioned, call :c:func:`bt_mesh_prov_enable`. The device
92 If the application wants to support public key exchange via OOB, it needs to
104 :kconfig:option:`CONFIG_BT_MESH_PROV_OOB_PUBLIC_KEY` needs to be enabled. The
108 and :c:member:`bt_mesh_prov.private_key_be`. The keys needs to be
|
| /Zephyr-latest/drivers/spi/ |
| D | Kconfig.max32 | 38 API calls use to perform SPI transactions. This queue needs to be as deep
|
| /Zephyr-latest/scripts/dts/ |
| D | README.txt | 26 Code in the zephyr repository which needs these libraries will import
|
| /Zephyr-latest/boards/aspeed/ast1030_evb/doc/ |
| D | index.rst | 7 Aspeed AST10x0 series SOCs. This board needs to be mated with
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.uart | 36 application start. When disabled, the application needs to start
|
| /Zephyr-latest/doc/services/ |
| D | notify.rst | 7 operation is initiated and the application needs to be informed when it
|
| /Zephyr-latest/samples/drivers/misc/grove_display/ |
| D | README.rst | 32 Grove LCD VDD line needs to be connected to the 5V power line, otherwise
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.wncm14a2a | 45 Note that the priority needs to be lower than the net stack
|
| /Zephyr-latest/doc/develop/optimizations/ |
| D | footprint.rst | 58 Depending on your application and platform needs, you can disable MPU/MMU
|
| /Zephyr-latest/samples/subsys/fs/format/ |
| D | README.rst | 24 To build the RAM disk sample, the configuration :file:`prj_ram.conf` needs to be used by setting
|
| /Zephyr-latest/samples/sensor/dht_polling/ |
| D | README.rst | 16 This sample supports up to 10 humidity/temperature sensors. Each sensor needs to
|
| /Zephyr-latest/samples/sensor/tmp116/ |
| D | README.rst | 16 This sample needs a TI TMP116 or TI TMP117 sensor connected to the target board's I2C
|
12345678910>>...21
