/Zephyr-latest/boards/native/nrf_bsim/common/ |
D | README.txt | 1 This folder contains components that could be 4 in tree, this folder is kept inside it.
|
/Zephyr-latest/samples/modules/tflite-micro/magic_wand/train/ |
D | data_prepare.py | 46 def prepare_original_data(folder, name, data, file_to_read): argument 48 if folder != "negative": 52 data_new[LABEL_NAME] = folder 60 data_new[LABEL_NAME] = folder 70 data_new[LABEL_NAME] = folder 78 data_new[LABEL_NAME] = folder 153 for idx1, folder in enumerate(folders): 155 prepare_original_data(folder, name, data, 156 … "./%s/output_%s_%s.txt" % (folder, folder, name))
|
/Zephyr-latest/scripts/ |
D | list_hardware.py | 34 def __init__(self, folder='', soc_yaml=None): argument 51 family = Family(f['name'], [folder], [], []) 53 series = Series(s['name'], [folder], f['name'], []) 56 [folder], s['name'], f['name'])) 65 [folder], None, f['name'])) 71 series = Series(s['name'], [folder], '', []) 74 [folder], s['name'], '')) 87 [folder], '', '')) 91 [folder], '', '')) 176 folder: List[str] [all …]
|
/Zephyr-latest/doc/_scripts/ |
D | gen_boards_catalog.py | 84 # containing folder. There are a few exceptions, like the "native" and "others" folders 86 for folder in board.dir.parents: 87 if folder.name in ["native", "others"]: 90 elif vnd_lookup.vnd2vendor.get(folder.name): 91 vendor = folder.name
|
/Zephyr-latest/doc/develop/getting_started/ |
D | installation_mac.rst | 18 * Run ``xattr -r -d com.apple.quarantine /path/to/folder`` where 19 ``path/to/folder`` is the path to the enclosing folder where the executables
|
/Zephyr-latest/tests/bsim/bluetooth/ll/edtt/ |
D | README.txt | 8 and in its `doc/` folder. 10 In very short, there is 2 applications in this folder: 35 EDTT folder. You can do this by adding it to your `~/.bashrc`, `~/.zephyrrc`,
|
/Zephyr-latest/tests/bsim/bluetooth/mesh/ |
D | README.rst | 8 Tests are organized into bash scripts under the test_scripts folder. Each 10 mesh subsystem, and each folder has a corresponding test_<subfolder>.c under the 22 procedure described in the parent folder. 24 To only run the mesh tests, set ``SEARCH_PATH`` to point to this folder before
|
/Zephyr-latest/cmake/modules/ |
D | FindBabbleSim.cmake | 9 # Path to the BabbleSim components source folder 54 `components/` folder, *and* BSIM_OUT_PATH to point to the folder where the simulator\n\
|
D | configuration_files.cmake | 18 # - APPLICATION_CONFIG_DIR: Root folder for application configuration 59 …ATION_CONFIG_DIR ${APPLICATION_CONFIG_DIR} CACHE PATH "The application configuration folder" FORCE)
|
/Zephyr-latest/scripts/west_commands/ |
D | build_helpers.py | 57 # Guess the build folder by iterating through all sub-folders from the 59 # proceed to iterate over subfolders only if there is a single folder 92 the default build folder is a build directory, it is returned. 149 top-level build folder is created and returned.
|
/Zephyr-latest/tests/bsim/ |
D | sh_common.source | 58 # For a caller running from a tests_script/ folder, get the path of its parent 65 # For a caller running from a tests_script/ folder, get the path of its parent
|
/Zephyr-latest/share/sysbuild/template/ |
D | CMakeLists.txt | 8 # file to the folder `<app-dir>/sysbuild` and use as a template and extend as needed.
|
/Zephyr-latest/tests/bsim/bluetooth/host/gatt/sc_indicate/ |
D | CMakeLists.txt | 8 components folder. More information can be found in \
|
/Zephyr-latest/tests/bsim/bluetooth/ll/cis/ |
D | CMakeLists.txt | 8 folder. More information can be found in\
|
/Zephyr-latest/tests/bsim/bluetooth/host/gatt/ccc_store/ |
D | CMakeLists.txt | 8 components folder. More information can be found in \
|
/Zephyr-latest/tests/bsim/bluetooth/host/security/ccc_update/ |
D | CMakeLists.txt | 8 components folder. More information can be found in \
|
/Zephyr-latest/doc/develop/west/ |
D | build-flash-debug.rst | 45 directory (i.e. the folder containing the application's :file:`CMakeLists.txt`) 90 ``west build`` will build all domains through the top-level build folder of the 394 - String, default ``build``. The build folder format string, used by 395 west whenever it needs to create or locate a build folder. The currently 408 - String, instructs west whether to try to guess what build folder to use 410 to resolve the build folder name. Can take these values: 413 require the user to provide a build folder with ``-d``. 414 - ``runners``: Try to guess the folder when using any of the 'runner' 419 folder before building. Can take the following values: 421 - ``never`` (default): Never automatically make the build folder [all …]
|
/Zephyr-latest/doc/contribute/documentation/ |
D | generation.rst | 162 the ``Scripts`` folder of your Python installation path. 164 add this folder to your ``PATH`` environment variable. Follow 185 Assuming the local Zephyr project copy is in a folder ``zephyr`` in your home 186 folder, here are the commands to generate the html content locally: 226 of the build folder and run ``cmake`` and then ``ninja`` again.
|
/Zephyr-latest/doc/develop/ |
D | beyond-GSG.rst | 123 :file:`zephyrproject` folder in sync with the code in the local zephyr 215 The other sample applications in the :zephyr_file:`samples` folder are 253 folder: 261 * or copy the rules file from the Zephyr SDK folder:: 284 add path to QEMU installation folder to PATH environment variable. 287 ``QEMU_BIN_PATH`` to the path of QEMU installation folder.
|
/Zephyr-latest/cmake/ |
D | pristine.cmake | 32 message(FATAL_ERROR "Refusing to run pristine in in-source build folder.")
|
/Zephyr-latest/samples/application_development/external_lib/ |
D | README.rst | 36 ``Binaries`` and ``Dependencies`` and extracting them to the same folder, or
|
/Zephyr-latest/scripts/pylib/pytest-twister-harness/tests/ |
D | conftest.py | 19 """Return path to `resources` folder"""
|
/Zephyr-latest/samples/net/cellular_modem/ |
D | README.rst | 13 script found in the server folder. DNS is used to look
|
/Zephyr-latest/samples/boards/st/mco/ |
D | README.rst | 17 To support another board, add a dts overlay file in boards folder.
|
/Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/ |
D | README.rst | 23 To support another board, add an overlay in boards folder.
|