Searched refs:these (Results 126 – 150 of 642) sorted by relevance
12345678910>>...26
| /Zephyr-latest/samples/net/stats/ |
| D | README.rst | 27 Follow these steps to build the network statistics sample application:
|
| /Zephyr-latest/tests/drivers/build_all/led_strip/ |
| D | app.overlay | 10 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/tests/drivers/build_all/video/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/samples/subsys/canbus/isotp/ |
| D | README.rst | 20 Use these instructions with integrated CAN controller like in the NXP TWR-KE18F
|
| /Zephyr-latest/samples/subsys/usb/common/ |
| D | Kconfig.sample_usbd | 5 # using the new experimental USB device support. The scope of these options is
|
| /Zephyr-latest/tests/lib/devicetree/api/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
64 * At least one of these phandles must refer to
401 /* there should only be one of these */
420 /* there should only be one of these */
456 /* there should only be one of these */
465 /* there should only be one of these */
650 /* there should only be one of these */
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 12 device controllers, and although, there a is clear separation between these
66 In the examples below, you will need to replace these Kconfig options and other
84 descriptors. To instantiate these string descriptors, the application should
236 Internally the implementation uses two ringbuffers, these take over the
245 the implementation of these functions checks in what context they are called
278 All these functions are not directly dependent on the status of the USB device.
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 6 Documentation is available for these Linux distributions:
70 Note that both Ninja and Make are installed with these instructions; you only
103 these. To clear the C/C++ flags among these and fix the Zephyr build, run
227 Follow these steps to install the Zephyr SDK:
276 If you install the Zephyr SDK outside any of these locations, you must
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-upstream.rst | 7 submit to the upstream Zephyr Project. (You don't need to follow these rules
89 Look at all these lines!
92 multi-line descriptions. This in turn makes these long strings
130 :ref:`DTS_ROOT <dts_root>`. The devicetree tooling will respect these
172 Examples of how to write descriptions according to these rules:
|
| /Zephyr-latest/doc/develop/test/ |
| D | bsim.rst | 26 you can find more information about how to build Zephyr targeting these particular boards,
36 necessary to connect them to a physical layer simulation. Thanks to this, these target boards can
44 running, and most, more than 1 simulated device. Due to this, these tests are not build and run
49 these tests in batch.
63 Today these tests include a very significant subset of the BT qualification test suite.
|
| /Zephyr-latest/samples/subsys/usb/mass/ |
| D | Kconfig | 73 # device stack. The scope of these options is limited to USB samples in project
|
| /Zephyr-latest/drivers/spi/ |
| D | Kconfig.max32 | 42 length as these are transformed into normal transceives.
|
| /Zephyr-latest/scripts/dts/ |
| D | README.txt | 26 Code in the zephyr repository which needs these libraries will import
|
| /Zephyr-latest/boards/panasonic/pan1782_evb/doc/ |
| D | index.rst | 15 The PAN1782 evaluation board is closely linked to these other evaluation
|
| /Zephyr-latest/boards/panasonic/pan1781_evb/doc/ |
| D | index.rst | 15 The PAN1781 evaluation board is closely linked to these other evaluation
|
| /Zephyr-latest/boards/nordic/nrf9280pdk/ |
| D | nrf9280pdk_nrf9280_cpurad.dts | 46 /* The following bells on this bellboard are rang by these cores
|
| /Zephyr-latest/tests/drivers/sdhc/ |
| D | README.txt | 25 specification is state based, and testing these portions of the SDHC would
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | app_smem_pinned.ld | 29 * macros, and thus these will not appear in
|
| /Zephyr-latest/tests/kernel/device/boards/ |
| D | hifive_unmatched_fu740_s7.overlay | 12 * with real-world devicetree nodes, to allow these tests to run on
|
| D | hifive_unmatched_fu740_u74.overlay | 12 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/tests/benchmarks/sched_queues/ |
| D | README.rst | 17 By default, these tests show the minimum, maximum, and averages of the measured
|
| /Zephyr-latest/tests/drivers/build_all/eeprom/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/tests/drivers/build_all/led/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/samples/boards/nordic/nrfx_prs/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 53 /* The UARTE1 peripheral share the same ID with SPIM1, hence these two
|
| /Zephyr-latest/samples/boards/nxp/mimxrt1060_evk/system_off/ |
| D | README.rst | 17 A power monitor will be able to distinguish among these states.
|
12345678910>>...26
