Searched refs:named (Results 51 – 75 of 157) sorted by relevance
1234567
| /Zephyr-latest/samples/drivers/soc_flash_nrf/ |
| D | README.rst | 24 there is a fixed-partition named ``storage_partition`` defined
|
| /Zephyr-latest/tests/kernel/timer/timer_behavior/ |
| D | README | 29 named on testcase.yaml, with the following interface:
|
| /Zephyr-latest/boards/u-blox/ubx_evkannab1/doc/ |
| D | index.rst | 156 are named sw0 and sw1 in the dts file.
|
| /Zephyr-latest/boards/adafruit/feather_nrf52840/doc/ |
| D | index.rst | 145 A mass storage device named ``FTHR840BOOT`` for (Express) or
|
| /Zephyr-latest/doc/develop/tools/ |
| D | stm32cubeide.rst | 129 ModuleNotFoundError: No module named 'pykwalify'
|
| /Zephyr-latest/doc/develop/west/ |
| D | zephyr-cmds.rst | 236 This will create a tags file named ``GTAGS`` in the workspace :ref:`topdir
238 named ``GPATH`` and ``GRTAGS`` in the same place).
|
| D | manifest.rst | 210 default. It will be cloned into a directory named ``proj2``. The commit
286 file is named :file:`west-commands.yml` by convention. See
610 - ``project-1``: one group, named ``groupA``
611 - ``project-2``: two groups, named ``groupB`` and ``groupC``
1128 along with another project named ``bar`` in the same workspace.
1160 in sync, along with another project named ``bar`` in the same workspace.
1253 other files. For example, a project named ``foo`` in your :file:`west.yml`
1254 makes west ignore other projects named ``foo`` imported from your ``projects``
1470 With this manifest file, the project named ``hal_nordic``:
1657 projects named ``a-vendor-hal`` and ``an-application``, even if those same
[all …]
|
| D | why.rst | 109 them. West itself is a Python package named ``west``; its libraries
|
| D | config.rst | 200 Then a project named ``hal_bar`` is inactive, but a project named
|
| /Zephyr-latest/boards/u-blox/ubx_evkninab1/doc/ |
| D | index.rst | 164 are named sw0 and sw1 in the dts file.
|
| /Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/ |
| D | debug-with-arm-ds.rst | 94 A new configuration named ``New_configuration`` will be created.
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-intro.rst | 109 above example binding would be named :file:`foo-company,bar-device.yaml` by
|
| D | intro-input-output.rst | 108 file named :file:`pre_dt_board.cmake` which configures these extra flags, like
|
| D | phandles.rst | 235 ``phandle-array-prop``\ 's specifier space is named ``baz``. Then we would need
316 In general, a ``phandle-array`` property named ``foos`` implicitly has
|
| /Zephyr-latest/doc/build/version/ |
| D | index.rst | 24 Application version information is set on a per-application basis in a file named :file:`VERSION`,
|
| /Zephyr-latest/boards/seeed/xiao_ble/doc/ |
| D | index.rst | 53 device named ``XIAO BLE`` should appear on the host. Using the command line, or
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | x86.rst | 85 the script, populate a CMake list named ``X86_EXTRA_GEN_MMU_ARGUMENTS``
|
| /Zephyr-latest/boards/pjrc/teensy4/doc/ |
| D | index.rst | 320 #. After application startup a serial device named like
|
| /Zephyr-latest/boards/nxp/ucans32k1sic/doc/ |
| D | index.rst | 58 This board has 5 GPIO ports named from ``gpioa`` to ``gpioe``.
|
| /Zephyr-latest/boards/cdns/xt-sim/doc/ |
| D | index.rst | 126 The linker script should be named ``linker.ld`` and placed in the directory
|
| /Zephyr-latest/doc/connectivity/bluetooth/autopts/ |
| D | autopts-win10.rst | 194 If the error "ImportError: No module named pywintypes" appeared after the fresh setup,
|
| /Zephyr-latest/doc/kernel/object_cores/ |
| D | index.rst | 16 Each instance of an object embeds an object core field named ``obj_core``.
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | slist.rst | 89 fields from arbitrary structures and emits an arbitrarily named set of
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 89 them in a subdirectory of :file:`<app>` named :file:`src`.
326 named :file:`src`. This makes it easier to distinguish between project
337 this example, we'll assume you created a file named :file:`src/main.c`.
339 #. Create a file named :file:`CMakeLists.txt` in the ``app`` directory with the
359 CMake target named ``app`` (see :ref:`cmake_pkg`). Adding sources to this
373 #. Create at least one Kconfig fragment for your application (usually named
379 file named :file:`app.overlay`. See :ref:`set-devicetree-overlays`.
|
| /Zephyr-latest/boards/we/orthosie1ev/doc/ |
| D | index.rst | 7 a module named for its small size. This board integrates complete Wi-Fi and Bluetooth® Low Energy f…
|
1234567
