Searched full:yml (Results 1 – 25 of 118) sorted by relevance
12345
| /Zephyr-latest/scripts/ci/ |
| D | twister_ignore.txt | 11 .codecov.yml
17 .github/workflows/issue_count.yml
18 .github/workflows/stats_merged_prs.yml
19 .github/workflows/assigner.yml
20 .github/workflows/daily_test_version.yml
21 .github/workflows/do_not_merge.yml
22 .github/workflows/stale_issue.yml
23 .github/workflows/stale-workflow-queue-cleanup.yml
24 .github/workflows/greet_first_time_contributor.yml
26 .github/workflows/backport_issue_check.yml
[all …]
|
| /Zephyr-latest/doc/build/snippets/ |
| D | writing.rst | 10 Snippets are defined using YAML files named :file:`snippet.yml`.
12 A :file:`snippet.yml` file contains the name of the snippet, along with
79 :file:`snippet.yml` files underneath a subdirectory named :file:`snippets/`,
83 system will look for :file:`snippet.yml` files underneath the following
89 The :file:`snippet.yml` files can be nested anywhere underneath these
92 #. In any :ref:`module <modules>` whose :file:`module.yml` file provides a
96 :file:`module.yml` file:
103 And then any :file:`snippet.yml` files in ``baz/snippets`` will
141 This :file:`snippet.yml` adds :file:`foo.overlay` to the build:
150 :file:`snippet.yml`.
[all …]
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | test_platform.py | 198 'm0/boards/zephyr/p1/board.yml': """\
218 'm0/boards/zephyr/p2/board.yml': """\
233 'm0/boards/arm/p3/board.yml': """\
259 'm0/soc/zephyr/soc.yml': """\
270 'm1/boards/zephyr/p1e1/board.yml': """\
285 'm1/boards/zephyr/p1e2/board.yml': """\
292 'm1/boards/zephyr/p2/board.yml': """\
302 'm2/boards/misc/board.yml': """\
320 'm2/soc/zephyr/soc.yml': """\
326 'm3/boards/zephyr/p1e1/board.yml': """\
[all …]
|
| /Zephyr-latest/scripts/west_commands/ |
| D | patch.py | 30 WEST_PATCH_SCHEMA_PATH = Path(__file__).parents[1] / "schemas" / "patch-schema.yml"
35 WEST_PATCH_YAML = Path("zephyr") / "patches.yml"
76 The patches.yml syntax is described in "scripts/schemas/patch-schema.yml".
114 "--patch-yml",
116 Path to patches.yml file (absolute or relative to module dir,
200 The meta data is generated and appended to the provided patches.yml file.
202 If no patches.yml file exists, it will be created.
282 self.die("patch-yml must not be an absolute path in combination with src-module")
316 yml = yaml.load(f, Loader=SafeLoader)
317 return pykwalify.core.Core(source_data=yml, schema_data=patches_schema).validate()
[all …]
|
| D | debug.py | 21 # Keep this in sync with the string in west-commands.yml.
42 # Keep this in sync with the string in west-commands.yml.
66 # Keep this in sync with the string in west-commands.yml.
84 # Keep this in sync with the string in west-commands.yml.
|
| D | robot.py | 18 # Keep this in sync with the string in west-commands.yml.
|
| D | simulate.py | 18 # Keep this in sync with the string in west-commands.yml.
|
| /Zephyr-latest/doc/develop/west/ |
| D | manifest.rst | 91 # i.e. the repository containing west.yml
286 file is named :file:`west-commands.yml` by convention. See
378 :file:`west.yml`:
386 west-commands: scripts/west-commands.yml
392 the location of the corresponding :file:`west-commands.yml` relative to the
445 The pykwalify schema :file:`manifest-schema.yml` in the `west source code
956 You are using this :file:`parent/west.yml` manifest:
960 # parent/west.yml:
971 And :file:`child/west.yml` contains:
975 # child/west.yml:
[all …]
|
| D | extensions.rst | 30 See :file:`zephyr/scripts/west-commands.yml` and the
60 #. Add information about it to a :file:`west-commands.yml` file.
61 #. Make sure the :file:`west-commands.yml` file is referenced in the
135 Step 2: Add or Update Your :file:`west-commands.yml`
138 You now need to add a :file:`west-commands.yml` file to your project which
172 :file:`west-commands.yml` file to get the basic information it needs to display
176 multiple files, your :file:`west-commands.yml` will look something like this:
203 See the file :file:`west-commands-schema.yml` in the `west repository`_ for a
204 schema describing the contents of a :file:`west-commands.yml`.
209 Finally, you need to specify the location of the :file:`west-commands.yml` you
[all …]
|
| D | workspaces.rst | 164 its :ref:`modules` in its :file:`west.yml`
178 and names other projects required to build it in its :file:`west.yml`. This
194 │ └── west.yml # main manifest with optional import(s) and override(s)
201 └── west.yml # This can be partially imported with lower precedence or ignored.
205 Here is an example :file:`application/west.yml` which uses
211 # Example T2 west.yml, using manifest imports.
227 Another way to do the same thing is to copy/paste :file:`zephyr/west.yml`
228 to :file:`application/west.yml`, adding an entry for the zephyr
243 west-commands: scripts/west-commands.yml
258 :file:`zephyr/west.yml` revision, instead of having to be copy/pasted (and
[all …]
|
| D | basics.rst | 32 │ ├── west.yml # manifest file
85 file is named :file:`west.yml` by default; this can be overridden using the
150 #. Set ``manifest.file`` to ``west.yml``
176 (e.g. ``zephyr``) and ``manifest.file`` (e.g. ``west.yml``) options.
178 :file:`zephyrproject/zephyr/west.yml`).
|
| /Zephyr-latest/doc/build/flashing/ |
| D | configuration.rst | 20 * ``soc.yml`` (in soc folder)
21 * ``board.yml`` (in board folder)
26 Configuration is applied in the yml file by using a ``runners`` map with a single ``run_once``
33 target sets. Board targets are regular expression matches, for ``soc.yml`` files each set of
35 qualifiers are allowed, board names must be omitted from these entries). For ``board.yml``
41 An example flashing configuration for a ``soc.yml`` is shown below in which the ``--recover``
|
| /Zephyr-latest/.github/workflows/ |
| D | west_cmds.yml | 13 - 'scripts/west-commands.yml'
15 - '.github/workflows/west_cmds.yml'
22 - 'scripts/west-commands.yml'
24 - '.github/workflows/west_cmds.yml'
|
| D | pylib_tests.yml | 13 - '.github/workflows/pylib_tests.yml'
20 - '.github/workflows/pylib_tests.yml'
|
| D | twister_tests.yml | 16 - '.github/workflows/twister_tests.yml'
26 - '.github/workflows/twister_tests.yml'
|
| D | scripts_tests.yml | 13 - '.github/workflows/scripts_tests.yml'
20 - '.github/workflows/scripts_tests.yml'
|
| D | devicetree_checks.yml | 14 - '.github/workflows/devicetree_checks.yml'
21 - '.github/workflows/devicetree_checks.yml'
|
| /Zephyr-latest/scripts/schemas/ |
| D | arch-schema.yml | 8 # The archs.yml file is a simple list of key value pairs containing architectures
25 desc: Location of the arch implementation relative to the archs.yml file.
|
| /Zephyr-latest/scripts/ |
| D | snippets.py | 52 '''Process the data in a snippet.yml file, after it is loaded into a
139 # The paths to all the snippet.yml files. One snippet
140 # can have multiple snippet.yml files.
184 # Name of the file containing the pykwalify schema for snippet.yml
186 SCHEMA_PATH = str(Path(__file__).parent / 'schemas' / 'snippet-schema.yml')
192 SNIPPET_YML = 'snippet.yml'
232 '''Process snippet.yml files under each *snippet_root*
248 '''Process snippet.yml files under each *snippet_root*
264 '''Process snippet.yml files in *root_dir*,
289 '''Load a snippet.yml file *snippet_yml*, validate the contents
|
| D | list_hardware.py | 21 SOC_SCHEMA_PATH = str(Path(__file__).parent / 'schemas' / 'soc-schema.yml')
25 ARCH_SCHEMA_PATH = str(Path(__file__).parent / 'schemas' / 'arch-schema.yml')
29 SOC_YML = 'soc.yml'
30 ARCHS_YML_PATH = PurePath('arch/archs.yml')
97 # soc.yml file
116 '''Load SoCs from a soc.yml file.
122 sys.exit(f'ERROR: socs.yml file not found: {socs_file.as_posix()}', e)
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 53 Modules are repositories that contain a :file:`zephyr/module.yml` file, so that
56 section in the :file:`west.yml` manifest file.
73 * The module repository codebase shall include a *module.yml* file in a
87 * Module repositories names should be explicitly set in the :file:`zephyr/module.yml` file.
332 * document (for example in the module README or .yml file) the default license
449 .. _module-yml:
454 A module can be described using a file named :file:`zephyr/module.yml`.
455 The format of :file:`zephyr/module.yml` is described in the following:
463 The name should be specified in the :file:`zephyr/module.yml` file. This will
494 :file:`zephyr/module.yml`.
[all …]
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 6 …zephyr repository itself and the MCUmgr :ref:`module <modules>` defined in :zephyr_file:`west.yml`.
86 #. Update ``west.yml`` within Zephyr, creating a pull-request to update the MCUmgr library referenc…
97 #. Update ``west.yml`` within Zephyr, creating a pull-request to update the MCUmgr library referenc…
113 #. Ensure that the author of the fix has also provided the ``west.yml`` update for Zephyr 2.7.
156 Merge west.yml
159 As an MCUmgr maintainer, you may not be able to merge the ``west.yml`` update, to introduce the fix…
|
| /Zephyr-latest/.github/ |
| D | license_config.yml | 9 - yml
|
| /Zephyr-latest/submanifests/ |
| D | README.txt | 2 in this directory will be included in the main west.yml file sorted by
|
| D | example.yaml.sample | 1 # Example manifest file you can include into the main west.yml file.
|
12345
