Searched refs:named (Results 76 – 100 of 157) sorted by relevance
1234567
/Zephyr-latest/boards/espressif/esp32c3_devkitm/doc/ |
D | index.rst | 7 a module named for its small size. This board integrates complete Wi-Fi and Bluetooth® Low Energy f…
|
/Zephyr-latest/boards/mediatek/ |
D | index.rst | 66 my mt8186 device named "steelix":
|
/Zephyr-latest/dts/arm/microchip/mec152x/ |
D | mec152xhsz-pinctrl.dtsi | 532 /* MEC152x QMSPI Port 2 can be external pins named gpspi_xxx or 533 * for the MEC1727 variant internal pins named int_spi_xxx. 587 * controller, named EEPROM controller in the data sheet.
|
/Zephyr-latest/share/sysbuild/cmake/modules/ |
D | sysbuild_extensions.cmake | 286 # Check for overlay named <ZBUILD_APPLICATION>.overlay. 705 # flashing order. Each image named "<image-dependency>" will be ordered before 706 # the image named "<image>".
|
/Zephyr-latest/boards/u-blox/ubx_evkninab3/doc/ |
D | index.rst | 309 The file has to be named ``<board>.overlay`` and placed in the app main directory to be
|
/Zephyr-latest/doc/develop/ |
D | env_vars.rst | 91 Create a file named :file:`~/.zephyrrc` if it doesn't exist, then add this
|
D | modules.rst | 80 may be named as their external project counterparts. 454 A module can be described using a file named :file:`zephyr/module.yml`. 637 To read these variables for a Zephyr module named ``foo``: 861 integration files for Zephyr modules via specifically named CMake variables. 1088 - If the project contains a file named :file:`zephyr/module.yml`, then the 1187 in a special branch named ``zephyr``.
|
/Zephyr-latest/arch/riscv/ |
D | Kconfig | 144 platform-specific versions named z_soc_irq_lock(), z_soc_irq_unlock() 155 platform-specific versions named z_soc_sys_read*() and z_soc_sys_write*().
|
/Zephyr-latest/doc/develop/west/ |
D | build-flash-debug.rst | 33 - If there is a Zephyr build directory named :file:`build` in your current 59 A build directory named :file:`build` will be created, and the application will 297 create a file named :file:`~/my-cache.cmake` with the following contents: 824 system. These will be named something like ``zephyr/zephyr.elf``,
|
D | troubleshooting.rst | 69 #. Look for a file named ``west.exe`` in the ``scripts`` directory
|
/Zephyr-latest/doc/build/dts/ |
D | bindings-syntax.rst | 138 a property named ``current-speed``. The property's value must be a single 393 property named ``foos`` with type ``phandle-array`` implicitly has specifier 687 If any file named :file:`foo.yaml` is found (see
|
D | macros.bnf | 144 ; The corresponding index number of a named pinctrl property. 149 ; The node identifier for the phandle in a named pinctrl property.
|
/Zephyr-latest/doc/build/dts/api/ |
D | api.rst | 11 macro named ``DT_DRV_COMPAT`` to be defined before they can be used; these are 309 from 0. These may also be named using the ``pinctrl-names`` property.
|
/Zephyr-latest/drivers/flash/ |
D | Kconfig | 38 in size, depending how they are named by vendor.
|
/Zephyr-latest/boards/espressif/esp32s3_devkitm/doc/ |
D | index.rst | 7 or ESP32-S3-MINI-1U, a module named for its small size. This board integrates complete Wi-Fi
|
/Zephyr-latest/boards/espressif/esp32s3_devkitc/doc/ |
D | index.rst | 7 or ESP32-S3-WROOM-1U, a module named for its small size. This board integrates complete Wi-Fi
|
/Zephyr-latest/boards/u-blox/ubx_bmd380eval/doc/ |
D | index.rst | 495 The file has to be named ``<board>.overlay`` and placed in the app
|
/Zephyr-latest/samples/net/sockets/http_server/ |
D | README.rst | 239 After generating a file named ``perf.data`` which contains the profiling data,
|
/Zephyr-latest/subsys/shell/ |
D | Kconfig | 324 When enabled, a custom application provided header, named
|
/Zephyr-latest/boards/u-blox/ubx_bmd340eval/doc/ |
D | index.rst | 498 The file has to be named ``<board>.overlay`` and placed in the app
|
/Zephyr-latest/boards/u-blox/ubx_bmd345eval/doc/ |
D | index.rst | 510 The file has to be named ``<board>.overlay`` and placed in the app
|
/Zephyr-latest/doc/releases/ |
D | migration-guide-3.7.rst | 63 of a stack frame. This new struct replaces the named struct ``z_arch_esf_t``. (:github:`73593`) 65 * The named struct ``z_arch_esf_t`` is now deprecated. Use ``struct arch_esf`` instead. (:github:`7… 100 * The Kconfig options previously named ``CONFIG_MBEDTLS_MAC_*_ENABLED`` have been renamed. 106 of other Kconfig options which are now named ``CONFIG_MBEDTLS_SHA*``. (:github:`73267`)
|
/Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
D | implementation.rst | 92 /* Define the implementation (named MY_CONNECTIVITY_IMPL) */ 149 …In the previous example, the context type is named ``MY_CONNECTIVITY_IMPL_CTX_TYPE``, because ``MY…
|
/Zephyr-latest/cmake/modules/ |
D | boards.cmake | 221 message("No board named '${BOARD}' found.\n\n"
|
/Zephyr-latest/doc/connectivity/bluetooth/autopts/ |
D | autopts-linux.rst | 345 If the error "ImportError: No module named pywintypes" appeared after the fresh setup,
|
1234567