Home
last modified time | relevance | path

Searched refs:revisions (Results 1 – 25 of 43) sorted by relevance

12

/Zephyr-latest/boards/adafruit/qt_py_esp32s3/
Drevision.cmake2 …message(FATAL_ERROR "Invalid board revision, ${BOARD_REVISION}, valid revisions are: <none> (for n…
/Zephyr-latest/boards/seagate/legend/
Drevision.cmake6 …message(FATAL_ERROR "${BOARD_REVISION} is not a valid revision for Legend. Accepted revisions: ${L…
/Zephyr-latest/boards/others/stm32_min_dev/
Drevision.cmake6 … "${BOARD_REVISION} is not a valid revision for stm32_min_dev. Accepted revisions: ${BOARD_REVISIO…
/Zephyr-latest/scripts/
Dlist_boards.py46 revisions = []
48 revisions.append(Revision.from_dict(r))
49 return Revision(revision['name'], revisions)
103 revisions: List[str] = field(default_factory=list, compare=False) variable in Board
286 revisions=[Revision.from_dict(v) for v in
432 [x.name for x in b.revisions]),
/Zephyr-latest/soc/espressif/common/
DKconfig13 ESP32 SoC has multiple revisions, some of which are not supported by the current
14 implementation, as such as REV0 and REV1. In case those revisions are required,
/Zephyr-latest/samples/boards/nordic/dynamic_pinctrl/
DREADME.rst13 Slightly different board revisions that implement just small changes (like
16 able to boot onto multiple board revisions.
19 revisions, the firmware needs to select the appropriate routing when the
/Zephyr-latest/soc/nordic/nrf52/
DKconfig101 This anomaly applies to IC revisions "Engineering B" up to "3", the most
113 This anomaly applies to IC revisions up to "3", the most recent one.
/Zephyr-latest/doc/hardware/porting/
Dboard_porting.rst318 This includes the SoC, board variants, and board revisions.
334 revisions:
754 Multiple board revisions
760 Board revisions are described in the ``revision`` entry of the
770 revisions:
777 - ``number``: matches integer revisions
778 - ``letter``: matches single letter revisions from ``A`` to ``Z`` only
789 board ``plank`` defines revisions ``0.5.0``, and ``1.5.0`` and the user builds
863 Some boards may not use board revisions supported natively by Zephyr.
864 For example string revisions.
[all …]
/Zephyr-latest/boards/shields/st_b_lcd40_dsi1_mb1166/doc/
Dindex.rst13 The shield comes in different hardware revisions, the MB1166-A09
/Zephyr-latest/doc/hardware/peripherals/
Di2c.rst13 from previous revisions as of its release October 1, 2021.
/Zephyr-latest/doc/develop/west/
Dwithout-west.rst43 # and check out the specified revisions as well.
47 and keeping existing ones up to date at the latest revisions.
Dworkspaces.rst20 as project revisions.
33 since west does not manage the manifest repository's branches or revisions.
255 The main advantage to using ``import`` is not having to track the revisions of
Dbasics.rst182 revisions should be checked out locally. Project repositories which already
184 revisions in the manifest file.
Drelease-notes.rst365 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
/Zephyr-latest/boards/silabs/dev_kits/sltb010a/doc/
Dindex.rst3 SLTB010A is a development kit based on the EFR32BG22 SoC. Early revisions of
5 revisions (BRD4184B).
/Zephyr-latest/boards/shields/nrf7002eb/doc/
Dindex.rst50 edge-connector on some boards, like earlier revisions of the Thingy53 than v1.0.0.
/Zephyr-latest/boards/sifive/hifive1/doc/
Dindex.rst7 an FE310 RISC-V SoC. Two revisions of this board are supported in Zephyr:
/Zephyr-latest/boards/st/stm32f3_disco/doc/
Dindex.rst33 Recent PCB revisions (E and newer) are shipped with I3G4250D and LSM303AGR.
269 Again you have to use the adapted command for newer PCB revisions (E and newer):
/Zephyr-latest/boards/nxp/mimxrt1050_evk/doc/
Dindex.rst316 Newer revisions of this board use :ref:`lpc-link2-onboard-debug-probe`,
317 while older revisions use the :ref:`opensda-onboard-debug-probe`.
318 Schematic revisions A/A1 use the K20 OpenSDA probe, and B/B1 use the
/Zephyr-latest/doc/services/device_mgmt/
Dota.rst29 configured to observe your available firmware revisions on the Golioth Cloud.
/Zephyr-latest/boards/seagate/legend/doc/
Dindex.rst8 The Legend board family contains three revisions: 25hdd, 25ssd, and 35.
/Zephyr-latest/boards/olimex/lora_stm32wl_devkit/doc/
Dolimex_lora_stm32wl_devkit.rst138 On board revisions C or newer:
/Zephyr-latest/boards/arduino/portenta_h7/doc/
Dindex.rst75 information on how to build for specific revisions of the board).
/Zephyr-latest/cmake/modules/
Dboards.cmake277 "revision.cmake is not used, revisions must be defined in '${BOARD_DIR}/board.yml'"
282 "Board '${BOARD}' does not define any revisions."
/Zephyr-latest/boards/nxp/mimxrt1060_evk/doc/
Dindex.rst329 * This board also has two revisions, the EVKA and EVKB. EVKA is the default target for this board.
350 Two revisions of the RT1060 EVK exist. For the RT1060 EVK, J47/J48 are the SWD

12