Searched refs:revisions (Results 26 – 45 of 45) sorted by relevance
12
| /Zephyr-latest/boards/arduino/portenta_h7/doc/ |
| D | index.rst | 35 information on how to build for specific revisions of the board).
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-4.2.rst | 67 of a new ``arduino_uno_r4`` board with revisions (``arduino_uno_r4@minima`` and
|
| /Zephyr-latest/cmake/modules/ |
| D | boards.cmake | 259 "revision.cmake is not used, revisions must be defined in '${BOARD_DIR}/board.yml'"
264 "Board '${BOARD}' does not define any revisions."
|
| D | extensions.cmake | 933 # requested revision against available board revisions.
953 # EXACT: Revision is required to be an exact match. As example, available revisions are:
967 # revisions 0.x.0-0.99.99 and 1.0.0-1.99.99, and it is expected
974 # VALID_REVISIONS: A list of valid revisions for this board.
|
| /Zephyr-latest/boards/st/nucleo_f030r8/doc/ |
| D | index.rst | 168 Using revision **2** adapted for C-02(or higher) as default when not explicitly selecting revisions.
|
| /Zephyr-latest/doc/develop/west/ |
| D | release-notes.rst | 365 fetches for project revisions which are `lightweight tags`_ (it already
376 and check out such revisions manually after running ``west init``.
383 - ``west.manifest.Project.sha()`` now works correctly for tag revisions.
400 the ``git fetch`` command used to fetch remote revisions when updating each
716 - Commands and options which operate on git revisions now accept abbreviated
|
| D | config.rst | 234 from project remotes when those projects' revisions in the manifest file
|
| D | built-in.rst | 123 even if the revisions appear to be available locally, either use ``-f always``
|
| D | manifest.rst | 66 - In the above diagram, no project repository has two revisions "at
162 what revisions to track, and where the project should be stored on the local
1490 - locally check out the ``v2.0.0`` revisions for all zephyr projects except
2091 from Git at the latest ``manifest-rev`` revisions in their projects. These
2092 revisions can be updated to the values ``rev-1`` through ``rev-N`` by running
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | shields.rst | 128 Some shields may support several variants or revisions. In that case, it is
|
| /Zephyr-latest/boards/nordic/nrf9160dk/doc/ |
| D | index.rst | 387 In nRF9160 DK revisions earlier than v0.14.0, nRF9160 signals routed to
468 build for specific revisions of the board):
|
| /Zephyr-latest/boards/st/stm32h747i_disco/doc/ |
| D | index.rst | 132 The shield comes in different hardware revisions, the MB1166-A09
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 970 The Zephyr build system has support for specifying multiple hardware revisions
971 of a single board with small variations. Using revisions allows the board
987 revisions, and what revisions are supported.
|
| /Zephyr-latest/ |
| D | LICENSE | 42 editorial revisions, annotations, elaborations, or other modifications
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 211 C++20. Other standard revisions may vary. In doubt, do not rely on
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 213 of the Zephyr Project release team, module revisions referencing blobs may be
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 156 #. Otherwise, if board revisions are used and
|
| /Zephyr-latest/doc/build/dts/ |
| D | howtos.rst | 243 #. If the current board has :ref:`multiple revisions <porting_board_revisions>`
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 1153 main tree this is done using revisions. For code that is already merged and part
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 77 This option also supports different revisions of one same board,
|
12
