Searched refs:these (Results 51 – 75 of 642) sorted by relevance
12345678910>>...26
| /Zephyr-latest/tests/drivers/build_all/modem/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/doc/services/tfm/ |
| D | testsuites.rst | 30 Only one of these suites can be run at a time, with the available test suites
36 The output of these test suites is required to obtain PSA Certification for
|
| /Zephyr-latest/samples/basic/threads/ |
| D | README.rst | 20 When either of these threads toggles its LED, it also pushes information into a
35 You will see one of these errors if you try to build this sample for an
|
| /Zephyr-latest/boards/qemu/cortex_m3/ |
| D | Kconfig.defconfig | 16 # these APIs are provided thougth Mbed TLS. Unfortunately this platform is not
|
| /Zephyr-latest/drivers/gpio/ |
| D | Kconfig.mmio32 | 10 GPIO IP block and these registers are used to control things that
|
| /Zephyr-latest/samples/drivers/mbox/ |
| D | sysbuild.cmake | 27 # For these NXP boards the main core application is dependent on
|
| /Zephyr-latest/doc/build/flashing/ |
| D | configuration.rst | 28 ``--reset`` followed by a list which specifies the settings for each of these commands (these
35 qualifiers are allowed, board names must be omitted from these entries). For ``board.yml``
36 files each set of board targets must be in a ``boards`` key, these are lists containing the
|
| /Zephyr-latest/drivers/sensor/ti/tmp108/ |
| D | Kconfig | 23 see TMP108 spec sheet for more information on how these work.
|
| /Zephyr-latest/tests/drivers/build_all/mfd/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/ |
| D | Kconfig | 15 # device stack. The scope of these options is limited to USB samples in project
|
| /Zephyr-latest/samples/net/zperf/ |
| D | Kconfig | 26 # device stack. The scope of these options is limited to USB samples in project
|
| /Zephyr-latest/samples/bluetooth/hci_uart_async/ |
| D | app.overlay | 20 /* Some boards are by default assigning the &uart0 to these other
|
| /Zephyr-latest/samples/net/vlan/ |
| D | README.rst | 35 Follow these steps to build the VLAN sample application:
45 two virtual LAN networks with these settings:
|
| /Zephyr-latest/doc/build/dts/ |
| D | dt-vs-kconfig.rst | 54 There are **exceptions** to these rules:
57 configuration parameters, such as the size of an internal buffer, these
59 specific to Zephyr drivers and not hardware description or configuration these
|
| /Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/ |
| D | README.txt | 30 Follow these guidelines when enabling test execution on a new target.
47 Support for these flags varies between vendors and products.
70 Support for these options varies between vendors and products.
|
| /Zephyr-latest/arch/arm/core/ |
| D | Kconfig.vfp | 6 # Math coprocessor symbols; these should be selected by the CPU symbol to
25 # VFP type symbols; these should be selected by the SoC symbol to specify the
142 # VFP feature symbols; these are the helper symbols used by the floating-point
197 # Advanced SIMD type symbols; these should be selected by the SoC symbol to
|
| /Zephyr-latest/samples/subsys/usb/dfu-next/ |
| D | Kconfig | 32 # device stack. The scope of these options is limited to USB samples in project
|
| /Zephyr-latest/cmake/linker/ld/ |
| D | target_relocation.cmake | 3 # See root CMakeLists.txt for description and expectations of these macros
|
| D | target_configure.cmake | 3 # See root CMakeLists.txt for description and expectations of these macros
|
| /Zephyr-latest/tests/drivers/build_all/mdio/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/boards/ |
| D | stm32l562e_dk.overlay | 3 /* Comment out these lines to use usart1 as console/shell */
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 50 The main purpose of these bsim boards is to be test-benches for
54 :ref:`POSIX arch based board<posix_arch_rationale>`, but in addition these
75 That comparison applies fully to these boards, but in this section we expand
78 to these boards.
84 these bsim boards.
93 - Integration tests on workstation (what the POSIX arch and these boards enable)
123 these are fully supported with the bsim boards.
154 The basic architecture layering of these boards is as follows:
175 ``inf_clock`` layer to be generic, these were delegated to the board.
290 Any message printed to these APIs, and by extension by default to Zephyr's ``printk``,
[all …]
|
| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 44 In other words a person writing these requirements usually has some knowledge of the Zephyr RTOS
58 UIDs, follow these steps:
66 If there are duplicates in the PR, these need to be resolved by rebasing and re-executing
|
| /Zephyr-latest/samples/subsys/bindesc/hello_bindesc/ |
| D | README.rst | 15 Follow these steps to build the ``hello_bindesc`` sample application:
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.mem_domain | 51 For these reasons, on uniprocessor systems unless memory access
53 tables, these APIs don't need to be implemented as the underlying
|
12345678910>>...26
