Searched refs:either (Results 126 – 150 of 370) sorted by relevance
12345678910>>...15
| /Zephyr-4.1.0/dts/arm/nxp/ |
| D | nxp_rw6xx_common.dtsi | 78 /* RW6XX SRAM can be access by either code or data bus, determined
80 * Applications can override the reg properties of either
|
| /Zephyr-4.1.0/boards/st/stm32h745i_disco/doc/ |
| D | index.rst | 113 using either ``stm32h745i_disco/stm32h745xx/m7`` or ``stm32h745i_disco/stm32h745xx/m4`` as the targ…
118 …Check if the on-board ST-LINK V3 has the latest firmware version. It can be done with either `STM3…
|
| /Zephyr-4.1.0/doc/develop/west/ |
| D | troubleshooting.rst | 47 On Windows, this means that either west is not installed, or your :envvar:`PATH`
103 reports of this issue on other Linux distributions, like Arch Linux, either.
|
| D | built-in.rst | 99 ``PROJECT`` is either a project name as given in the manifest file, or a
123 even if the revisions appear to be available locally, either use ``-f always``
168 never fails either but does not treat all projects the same:
|
| /Zephyr-4.1.0/doc/security/ |
| D | sensor-threat.rst | 58 image is run, the flash shall contain either the update image in
72 key, usually either an RSA key or an EC private key. When
74 this secret either as part of the TLS establishment, or to sign a
276 these random numbers. It shall use either a Non-Deterministic
372 The system must log security-related events, and either store them
|
| /Zephyr-4.1.0/doc/develop/test/ |
| D | ztest.rst | 10 The framework can be used in two ways, either as a generic framework for
185 state that the tests depend on and that state either cannot be replicated or is difficult to
280 either can be testing functionality or APIs. Functions implementing a test case
328 it needs to report either a pass or fail. For example:
567 Zephyr provides several FFF-based fake drivers which can be used as either stubs or mocks. Fake
|
| /Zephyr-4.1.0/drivers/serial/ |
| D | Kconfig.native_pty | 12 to either connect to the terminal from which the executable was run, or into
|
| /Zephyr-4.1.0/samples/drivers/led/led_strip/ |
| D | README.rst | 50 #. Connect the LED strip control pin (either I2S SDOUT, SPI MOSI or GPIO) from
|
| /Zephyr-4.1.0/cmake/linker_script/common/ |
| D | common-ram.cmake | 33 # All kernel objects within are assumed to be either completely
|
| /Zephyr-4.1.0/doc/connectivity/networking/ |
| D | networking_with_host.rst | 75 * If you have multiple Zephyr instances, either QEMU or native_sim ones,
|
| D | net_pkt_processing_stats.rst | 14 processing takes either in sending or receiving path. There are two Kconfig
|
| /Zephyr-4.1.0/doc/project/ |
| D | documentation.rst | 12 generates either an on-line documentation browser (in HTML) and/or provides
|
| /Zephyr-4.1.0/modules/ |
| D | Kconfig.mcuboot | 86 This option should either be an absolute path or a path relative to
220 In this mode MCUboot can boot from either partition and will
236 from either slot, as long as it has been marked to be boot
|
| /Zephyr-4.1.0/samples/modules/tflite-micro/hello_world/ |
| D | README.rst | 57 can be downloaded either as a FPGA bitfile for the
|
| /Zephyr-4.1.0/samples/boards/espressif/flash_encryption/ |
| D | README.rst | 51 When enabling the Flash Encryption, user can encrypt the content either using a device
|
| /Zephyr-4.1.0/subsys/logging/backends/ |
| D | Kconfig.net | 84 This can be either IPv4 or IPv6 address.
|
| /Zephyr-4.1.0/boards/wiznet/w5500_evb_pico2/doc/ |
| D | index.rst | 111 either use SEGGER JLink or OpenOCD.
|
| /Zephyr-4.1.0/boards/beagle/beagley_ai/doc/ |
| D | index.rst | 35 module supports 512 interrupt inputs per R5F core. Each interrupt can be either
|
| /Zephyr-4.1.0/tests/kernel/timer/timer_behavior/ |
| D | README | 6 2. Periodic timers do not drift in either direction from expected total time.
|
| /Zephyr-4.1.0/boards/beagle/beaglebone_ai64/doc/ |
| D | index.rst | 35 module supports 512 interrupt inputs per R5F core. Each interrupt can be either
|
| /Zephyr-4.1.0/doc/connectivity/networking/api/ |
| D | capture.rst | 15 external system for analysis. The monitoring can be setup either manually
|
| /Zephyr-4.1.0/doc/hardware/peripherals/ |
| D | bc12.rst | 48 either a disconnected, portable-device, or charging port mode.
|
| /Zephyr-4.1.0/boards/nxp/lpcxpresso11u68/doc/ |
| D | index.rst | 101 probe (based on a NXP LPC43xx MCU). This MCU provides either a CMSIS-DAP or
|
| /Zephyr-4.1.0/boards/st/stm32l4r9i_disco/ |
| D | stm32l4r9i_disco.dts | 106 * Disable PLLP completely since it only feeds SAI, which is not active either.
|
| /Zephyr-4.1.0/lib/cpp/ |
| D | Kconfig | 84 Indicates that a full C++ standard library is required, either by
|
12345678910>>...15
