Searched refs:these (Results 301 – 325 of 642) sorted by relevance
1...<<11121314151617181920>>...26
/Zephyr-latest/doc/develop/west/ |
D | config.rst | 64 ``--local`` to specify which configuration file to use. Only one of these can 214 trailing whitespace are ignored. That means these example values 222 Any empty elements are ignored. That means these example values are
|
D | build-flash-debug.rst | 175 it the value ``always``. For example, these commands are equivalent:: 184 Using ``--pristine=auto`` makes ``west build`` detect some of these situations 372 You can :ref:`configure <west-config-cmd>` ``west build`` using these options. 410 to resolve the build folder name. Can take these values: 582 If you don't specify the build directory, these commands search for one in 800 support for these features. 830 By default, these West commands rebuild binaries before flashing and 832 targets provided by Zephyr's build system (in fact, that's how these
|
/Zephyr-latest/boards/toradex/colibri_imx7d/doc/ |
D | index.rst | 50 and Colibri Evaluation Board, see these references: 132 The A7 can perform these steps at bootloader level or after the Linux system has 304 #Add these definitions under / { } just before the __symbols__ 459 With these mechanisms, applications for the ``colibri_imx7d/imx7d/m4`` board
|
/Zephyr-latest/soc/nordic/nrf52/ |
D | Kconfig | 110 Due to Anomaly 109 the first byte sent out by these peripherals is
|
/Zephyr-latest/samples/subsys/usb/webusb/ |
D | README.rst | 52 Follow these steps to run the demo on your host system:
|
/Zephyr-latest/samples/tfm_integration/tfm_psa_test/ |
D | README.rst | 21 Only one of these suites can be run at a time, with the test suite set via one
|
/Zephyr-latest/boards/silabs/radio_boards/xg23_rb4210a/doc/ |
D | index.rst | 28 For more information about the EFR32ZG23 SoC and BRD4210A board, refer to these
|
/Zephyr-latest/boards/qemu/cortex_m3/doc/ |
D | index.rst | 8 This configuration provides support for an ARM Cortex-M3 CPU and these devices:
|
/Zephyr-latest/boards/st/stm32g0316_disco/doc/ |
D | index.rst | 23 For more information about the STM32G03x SoC and the STM32G0316-DISCO board, see these ST reference…
|
/Zephyr-latest/boards/native/nrf_bsim/doc/ |
D | nrf54l15bsim.rst | 58 and will use the same drivers as the nrf54l15dk targets for these.
|
/Zephyr-latest/boards/st/steval_fcu001v1/doc/ |
D | index.rst | 33 can be found in these documents:
|
/Zephyr-latest/samples/net/sockets/http_get/ |
D | README.rst | 48 ``overlay-tls.conf`` overlay file enabled, for example, using these commands:
|
/Zephyr-latest/boards/native/native_sim/doc/ |
D | index.rst | 260 command line options. Note that both of these options control the same 270 Note that these 2 options have no meaning when running in non real-time 435 ``libsdl2-dev:i386`` packages, and configure the pkg-config search path with these commands: 450 The EEPROM simulator can also be used in the native targets. In these, you have the added feature 521 Normally these UARTs are connected to new pseudoterminals PTYs, i.e. :file:`/dev/pts{<nbr>}`, 545 You may also chose to automatically attach a terminal emulator to any of these UARTs. 546 To automatically attach one to all these UARTs, pass the command line option ``-attach_uart`` to the 678 these commands:
|
/Zephyr-latest/doc/kernel/usermode/ |
D | memory_domain.rst | 59 know when these overflows happen, as without robust detection logic the system 94 disabled. Regardless of these kconfigs, user threads cannot access 102 directly by user mode. In order to use these system calls, invoking threads 142 a k_heap to draw these allocations from for the target thread. 236 partition. The build system will then coalesce all of these into a single
|
/Zephyr-latest/boards/arm/mps2/doc/ |
D | mps2_armv7m.rst | 11 provides details about the support provided for these three Armv7-m mps2 board targets 22 In addition to enabling actual hardware usage, these board targets can
|
/Zephyr-latest/doc/connectivity/networking/ |
D | net-stack-architecture.rst | 49 You access these protocols by using the 63 Some of these technologies support IPv6 header compression (6Lo),
|
/Zephyr-latest/doc/build/kconfig/ |
D | menuconfig.rst | 42 #. To run the terminal-based ``menuconfig`` interface, use either of these 53 To run the graphical ``guiconfig``, use either of these commands:
|
/Zephyr-latest/boards/technexion/pico_pi/doc/ |
D | index.rst | 38 For more information about the i.MX7 SoC and Pico-Pi i.MX7D, see these references: 110 The A7 can perform these steps at bootloader level or after the Linux system
|
/Zephyr-latest/doc/introduction/ |
D | index.rst | 24 The full list of supported boards based on these architectures can be found :ref:`here <boards>`. 181 combination of these.
|
/Zephyr-latest/doc/kernel/data_structures/ |
D | rbtree.rst | 8 For these situations, Zephyr provides a balanced tree implementation 42 described above, all of these routines are guaranteed to have at most
|
/Zephyr-latest/doc/services/pm/ |
D | device.rst | 190 As mentioned above, device drivers do not directly change between these states. 199 details on how these macros are used. A driver which implements device power 200 management support must provide these macros with arguments that describe its 371 After that devices can lock these state calling
|
/Zephyr-latest/boards/acrn/acrn/doc/ |
D | index.rst | 83 Zephyr distributes itself as an ELF image where these addresses can be 179 Note that these indexes are physical CPUs on the host. When 180 configuring multiple guests, you probably don't want to overlap these
|
/Zephyr-latest/boards/shields/x_nucleo_eeprma2/doc/ |
D | index.rst | 38 and the X-NUCLEO-EEPRMA2 in particular, see these ST Microelectronics documents:
|
/Zephyr-latest/boards/silabs/radio_boards/slwrb4104a/doc/ |
D | index.rst | 26 For more information about the EFR32BG13 SoC and BRD4104A board, refer to these
|
/Zephyr-latest/boards/silabs/radio_boards/slwrb4250b/doc/ |
D | index.rst | 25 For more information about the EFR32FG1 SoC and BRD4250B board, refer to these
|
1...<<11121314151617181920>>...26