Searched refs:these (Results 1 – 25 of 642) sorted by relevance
12345678910>>...26
/Zephyr-latest/doc/develop/toolchains/ |
D | designware_arc_mwdt.rst | 15 generation. We used Zephyr SDK as a source of these ARC GNU tools as well. 20 #. :ref:`Set these environment variables <env_vars>`: 31 #. To check that you have set these variables correctly in your current 32 environment, follow these example shell sessions (the
|
D | other_x_compilers.rst | 17 Follow these steps to use one of these toolchains. 32 #. :ref:`Set these environment variables <env_vars>`: 39 #. To check that you have set these variables correctly in your current 40 environment, follow these example shell sessions (the
|
D | gnu_arm_embedded.rst | 22 #. :ref:`Set these environment variables <env_vars>`: 28 #. To check that you have set these variables correctly in your current 29 environment, follow these example shell sessions (the
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | ethernet_mgmt.rst | 14 network interface low level status. The caller of these functions can: 27 The user application can monitor these events if it needs to act
|
/Zephyr-latest/ |
D | .gitignore | 63 # We don't want to record these. 66 # Cargo encourages a .cargo/config.toml file to symlink to a generated file. Don't save these. 70 # sometimes IDEs and such will litter these target directories as well.
|
/Zephyr-latest/doc/develop/west/ |
D | without-west.rst | 8 particular, you will have to do work "by hand" to replace these 13 - specifying the locations of these repositories to the Zephyr build 66 these repositories, the build will still work. 69 of these repositories, you must set :makevar:`ZEPHYR_MODULES` 89 If you want to use these build system targets but do not want to 122 specifically run one of these build system targets with a command 126 flash``. This is because these build system targets depend on an
|
D | sign.rst | 22 parameters desired are the default ones and fairly static, these indirections are 24 all these layers can causes issues typical when the layers don't abstract 29 build logs to find which exact options were used. Copying these options from the 34 To avoid these issues, ``rimage`` parameters can bet set in ``west config``.
|
/Zephyr-latest/scripts/west_commands/ |
D | README.txt | 13 To run these tests locally on Windows, run: 21 Note that these tests are run as part of Zephyr's CI when submitting
|
/Zephyr-latest/boards/shields/arduino_uno_click/boards/ |
D | nrf9160dk_nrf9160_arduino_uno_click_common.dtsi | 10 * pins, but the nRF9160 DK maps these pins to two different pairs of 32 * these pins (only TX/RX are connected on the shield). This keeps RX/TX
|
/Zephyr-latest/subsys/bluetooth/host/ |
D | CMakeLists.txt | 83 message(WARNING "One of these options are enabled: 102 message(WARNING "One or both these options are enabled: 123 # In order to compile Bsim tests with these test features
|
/Zephyr-latest/cmake/linker/ |
D | target_template.cmake | 8 # defining these macros themselves.
|
/Zephyr-latest/tests/bsim/bluetooth/audio/ |
D | Kconfig | 6 # to support these features.
|
/Zephyr-latest/doc/hardware/cache/ |
D | index.rst | 13 :kconfig:option:`CONFIG_CPU_HAS_ICACHE`: these hidden options should be 22 * :kconfig:option:`CONFIG_DCACHE` / :kconfig:option:`CONFIG_ICACHE`: these 24 present and working in zephyr. Note that if these options are disabled, 28 depending on these symbols. When the symbol is set the cache is considered
|
/Zephyr-latest/tests/benchmarks/wait_queues/ |
D | README.rst | 7 the performance of these two implementations vary under varying conditions. 16 By default, these tests show the minimum, maximum, and averages of the measured
|
/Zephyr-latest/tests/drivers/gpio/gpio_basic_api/boards/ |
D | imx8mp_evk_mimx8ml8_a53.overlay | 13 * output GPIO, connect these two pins with a Dupont Line.
|
D | imx8mm_evk_mimx8mm6_a53.overlay | 13 * output GPIO, connect these two pins with a Dupont Line.
|
D | imx8mn_evk_mimx8mn6_a53.overlay | 13 * output GPIO, connect these two pins with a Dupont Line.
|
/Zephyr-latest/samples/subsys/usb/hid-keyboard/ |
D | Kconfig | 5 # device stack. The scope of these options is limited to USB samples in project
|
/Zephyr-latest/samples/subsys/usb/hid-mouse/ |
D | Kconfig | 5 # device stack. The scope of these options is limited to USB samples in project
|
/Zephyr-latest/samples/subsys/usb/midi/ |
D | Kconfig | 5 # device stack. The scope of these options is limited to USB samples in project
|
/Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/ |
D | Kconfig | 5 # device stack. The scope of these options is limited to USB samples in project
|
/Zephyr-latest/samples/subsys/usb/webusb-next/ |
D | Kconfig | 5 # device stack. The scope of these options is limited to USB samples in project
|
/Zephyr-latest/samples/subsys/dap/ |
D | Kconfig | 5 # device stack. The scope of these options is limited to USB samples in project
|
/Zephyr-latest/samples/subsys/usb/cdc_acm/ |
D | Kconfig | 5 # device stack. The scope of these options is limited to USB samples in project
|
/Zephyr-latest/samples/bluetooth/hci_usb/ |
D | Kconfig | 5 # device stack. The scope of these options is limited to USB samples in project
|
12345678910>>...26