| /Zephyr-Core-3.7.0/cmake/modules/ |
| D | boards.cmake | 5 # Validate board and setup boards target.
7 # This CMake module will validate the BOARD argument as well as splitting the
8 # BOARD argument into <BOARD> and <BOARD_REVISION>. When BOARD_EXTENSIONS option
9 # is enabled (default) this module will also take care of finding board
12 # If a board implementation is not found for the specified board an error will
15 # If user provided board is a board alias, the board will be adjusted to real
16 # board name.
18 # If board name is deprecated, then board will be adjusted to new board name and
24 # - BOARD: Board, without revision field.
25 # - BOARD_REVISION: Board revision
[all …]
|
| /Zephyr-Core-3.7.0/scripts/utils/ |
| D | board_v1_to_v2.py | 3 Utility script to assist in the migration of a board from hardware model v1
12 - ``-b|--board``: The name of the board to migrate.
13 - ``-g|--group``: The group the board belongs to. This is used to group a set of
19 In some cases, the new board name will differ from the old board name. For
20 example, the old board name may have the SoC name as a suffix, while in HWMv2,
21 this is no longer needed. In such cases, ``-n|--new-board`` needs to be
26 For out-of-tree boards, provide ``--board-root`` pointing to the custom board
44 def board_v1_to_v2(board_root, board, new_board, group, vendor, soc, variants): argument
46 board_path = next(board_root.glob(f"boards/*/{board}"))
48 sys.exit(f"Board not found: {board}")
[all …]
|
| /Zephyr-Core-3.7.0/share/sysbuild/ |
| D | Kconfig.v2 | 5 config BOARD config
7 default "$(BOARD)"
9 This option holds the name of the board and is used to locate the files
10 related to the board in the source tree (under boards/).
11 The Board is the first location where we search for a linker.ld file,
18 If the BOARD has a revision field set, this is the revision.
19 Otherwise, it is the empty string. For example, if BOARD is
20 "plank@foo", this option will be "foo". If BOARD is "plank",
26 This hidden option is set in the board configuration and indicates
27 the Zephyr release that the board configuration will be removed.
[all …]
|
| /Zephyr-Core-3.7.0/scripts/west_commands/ |
| D | boards.py | 51 - name: board name
52 - qualifiers: board qualifiers (will be empty for legacy boards)
53 - arch: board architecture (deprecated)
55 - dir: directory that contains the board definition
56 - vendor: board vendor
62 help='''Format string to use to list each board;
93 for board in list_boards.find_boards(args):
94 if name_re is not None and not name_re.search(board.name):
96 log.inf(args.format.format(name=board.name, arch=board.arch,
97 dir=board.dir, hwm=board.hwm, qualifiers=''))
[all …]
|
| /Zephyr-Core-3.7.0/samples/drivers/mbox/ |
| D | Kconfig.sysbuild | 10 default "nrf5340dk/nrf5340/cpunet" if $(BOARD) = "nrf5340dk"
12 default "adp_xc7k/ae350" if $(BOARD) = "adp_xc7k"
13 default "mimxrt1170_evkb/mimxrt1176/cm4" if $(BOARD) = "mimxrt1170_evkb"
14 default "mimxrt1170_evk/mimxrt1176/cm4" if $(BOARD) = "mimxrt1170_evk"
15 default "mimxrt1160_evk/mimxrt1166/cm4" if $(BOARD) = "mimxrt1160_evk"
16 default "lpcxpresso55s69/lpc55s69/cpu1" if $(BOARD) = "lpcxpresso55s69"
17 …default "nrf54h20dk/nrf54h20/cpuppr" if "$(BOARD)${BOARD_QUALIFIERS}" = "nrf54h20dk/nrf54h20/cpuap…
18 …default "nrf54h20dk/nrf54h20/cpuapp" if "$(BOARD)${BOARD_QUALIFIERS}" = "nrf54h20dk/nrf54h20/cpura…
19 default "nrf54l15pdk/nrf54l15/cpuflpr" if $(BOARD) = "nrf54l15pdk"
20 default "stm32h747i_disco/stm32h747xx/m4" if $(BOARD) = "stm32h747i_disco"
|
| /Zephyr-Core-3.7.0/doc/hardware/porting/ |
| D | board_porting.rst | 3 Board Porting Guide
6 To add Zephyr support for a new :term:`board`, you at least need a *board
7 directory* with various files in it. Files in the board directory inherit
23 - Support for reusing the SoC and board Kconfig trees outside of the Zephyr
43 referred to as "hardware model v2") requires modifications to all existing board
47 with two options if they have an out-of-tree board (or SoC):
49 #. Convert the out-of-tree board to the current hardware model (recommended)
52 :ref:`zephyr module <modules>` or ``SOC_ROOT``). This will allow your board,
55 When converting your board from the previous to the current hardware model, we
58 how to port a simple board. Additionally, a `conversion script`_ is available
[all …]
|
| /Zephyr-Core-3.7.0/scripts/ |
| D | list_boards.py | 23 BOARD_SCHEMA_PATH = str(Path(__file__).parent / 'schemas' / 'board-schema.yml')
27 BOARD_YML = 'board.yml'
92 class Board: class
106 def board_key(board): argument
107 return board.name
127 if args.board is not None:
128 ret[arch] |= {b for b in boards if b.name == args.board}
177 ret[arch].add(Board(board_name, maybe_board, 'v1', arch=arch))
194 mutual_exclusive = {'board', 'boards'}
199 board_array = b.get('boards', [b.get('board', None)])
[all …]
|
| /Zephyr-Core-3.7.0/tests/cmake/overlays/soc_folder_kconfig/src/ |
| D | main.c | 65 zassert_false(INCLUDED_BOARD_SUFFIX, "Did not expect board suffix config to be present"); in ZTEST()
68 zassert_false(INCLUDED_BOARD, "Did not expect board config to be present"); in ZTEST()
69 zassert_true(INCLUDED_BOARD_QUALIFIERS, "Expected board qualifier config to be present"); in ZTEST()
72 zassert_true(INCLUDED_BOARD, "Expected board config to be present"); in ZTEST()
74 "Did not expect board qualifier config to be present"); in ZTEST()
78 zassert_false(INCLUDED_BOARD_OTHER, "Did not expect board other config to be present"); in ZTEST()
87 zassert_true(INCLUDED_BOARD_SUFFIX, "Expected board suffix config to be present"); in ZTEST()
89 zassert_false(INCLUDED_BOARD, "Did not expect board config to be present"); in ZTEST()
91 "Did not expect board qualifier config to be present"); in ZTEST()
93 zassert_false(INCLUDED_BOARD_OTHER, "Did not expect board other config to be present"); in ZTEST()
[all …]
|
| /Zephyr-Core-3.7.0/scripts/schemas/ |
| D | board-schema.yml | 6 ## board metadata YAML file.
8 # The board.yml file is a simple list of key value pairs containing board
26 schema;board-schema:
32 desc: Name of the board
36 desc: SoC family of the SoC on the board.
75 board:
76 include: board-schema
80 - include: board-schema
88 grouping of board targets. This is to allow for future image program cycles to not
95 of west flash for a given set of flash runners and board targets.
[all …]
|
| /Zephyr-Core-3.7.0/samples/subsys/ipc/openamp/ |
| D | Kconfig.sysbuild | 9 default "lpcxpresso54114/lpc54114/m0" if $(BOARD) = "lpcxpresso54114"
10 default "lpcxpresso55s69/lpc55s69/cpu1" if $(BOARD) = "lpcxpresso55s69"
11 default "mps2/an521/cpu1" if $(BOARD) = "mps2"
12 default "v2m_musca_b1/musca_b1/ns" if $(BOARD) = "v2m_musca_b1"
13 default "mimxrt1170_evk/mimxrt1176/cm4" if $(BOARD) = "mimxrt1170_evk"
14 default "mimxrt1160_evk/mimxrt1166/cm4" if $(BOARD) = "mimxrt1160_evk"
15 default "mimxrt1170_evkb/mimxrt1176/cm4" if $(BOARD) = "mimxrt1170_evkb"
|
| /Zephyr-Core-3.7.0/boards/ |
| D | Kconfig | 3 config BOARD config
5 # When using hw model v2, then the board is inherited from CMake.
6 default "$(BOARD)" if "$(HWM_SCHEME)" = "v2"
8 This option holds the name of the board and is used to locate the files
9 related to the board in the source tree (under boards/).
10 The Board is the first location where we search for a linker.ld file,
17 If the BOARD has a revision field set, this is the revision.
18 Otherwise, it is the empty string. For example, if BOARD is
19 "plank@foo", this option will be "foo". If BOARD is "plank",
24 default "$(BOARD)@$(BOARD_REVISION)$(BOARD_QUALIFIERS)" if "$(BOARD_REVISION)" != ""
[all …]
|
| D | Kconfig.v2 | 5 BOARD_STRING := $(normalize_upper,$(BOARD))
6 BOARD_TARGET_STRING := $(normalize_upper,$(BOARD)$(BOARD_QUALIFIERS))
12 Kconfig symbol identifying the board.
17 Kconfig symbol identifying the board target.
23 Contains the qualifiers of the board being used without the name of the board itself.
28 osource "$(BOARD_DIR)/Kconfig.$(BOARD)"
|
| /Zephyr-Core-3.7.0/boards/quicklogic/qomu/doc/ |
| D | index.rst | 9 The Qomu board is a platform with an on-board QuickLogic EOS S3 Sensor Processing Platform.
12 .. figure:: img/qomu-board.png
22 - 16 Mbit of on-board flash memory
27 Detailed information about the board can be found in a `Qomu repository`_ and `Qomu User Guide`_.
45 :board: qomu
48 #. Remove Qomu board from USB port.
49 #. Insert Qomu board to USB port.
68 https://github.com/QuickLogic-Corp/qomu-dev-board
71 https://github.com/QuickLogic-Corp/qomu-dev-board/blob/master/doc/Qomu_UserGuide.pdf
74 https://github.com/QuickLogic-Corp/qomu-dev-board/blob/master/doc/qomu-board.pdf
|
| /Zephyr-Core-3.7.0/boards/seeed/xiao_ble/ |
| D | board.cmake | 6 board_runner_args(uf2 "--board-id=Seeed_XIAO_nRF52840_Sense")
7 include(${ZEPHYR_BASE}/boards/common/nrfjprog.board.cmake)
8 include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
9 include(${ZEPHYR_BASE}/boards/common/pyocd.board.cmake)
10 include(${ZEPHYR_BASE}/boards/common/openocd.board.cmake)
11 include(${ZEPHYR_BASE}/boards/common/uf2.board.cmake)
12 include(${ZEPHYR_BASE}/boards/common/blackmagicprobe.board.cmake)
|
| /Zephyr-Core-3.7.0/samples/drivers/misc/ft800/ |
| D | README.rst | 18 * A board with SPI support
19 * Display with `FT800 EVE`_ like `VM800C board`_
24 You will need to connect the `FT800 EVE`_ SPI interface onto a board that
30 This sample should work on any board that has SPI enabled and has an Arduino
31 shield interface. For example, it can be run on the nRF52840-DK board as
36 :board: nrf52840dk/nrf52840
40 To build the sample for `VM800C board`_ the shield must be defined as described
45 :board: nrf52840dk/nrf52840
50 .. _VM800C board: https://www.ftdichip.com/old2020/Products/Modules/VM800C.html
|
| /Zephyr-Core-3.7.0/boards/nordic/nrf9160dk/ |
| D | board.cmake | 13 include(${ZEPHYR_BASE}/boards/common/nrfjprog.board.cmake)
14 include(${ZEPHYR_BASE}/boards/common/nrfutil.board.cmake)
15 include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
18 include(${ZEPHYR_BASE}/boards/common/nrfjprog.board.cmake)
19 include(${ZEPHYR_BASE}/boards/common/nrfutil.board.cmake)
20 include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
21 include(${ZEPHYR_BASE}/boards/common/openocd-nrf5.board.cmake)
|
| /Zephyr-Core-3.7.0/doc/build/flashing/ |
| D | configuration.rst | 1 .. _flashing-soc-board-config:
9 configuring when commands are ran for groups of board targets. As an example: a multi-core SoC
21 * ``board.yml`` (in board folder)
32 Groups of board targets can be specified using the ``groups`` key which has a list of board
33 target sets. Board targets are regular expression matches, for ``soc.yml`` files each set of
34 board targets must be in a ``qualifiers`` key (only regular expression matches for board
35 qualifiers are allowed, board names must be omitted from these entries). For ``board.yml``
36 files each set of board targets must be in a ``boards`` key, these are lists containing the
38 means that the command will be ran once with the first image flashing process per set of board
39 targets, or to ``last`` which will be ran once for the final image flash per set of board targets.
[all …]
|
| /Zephyr-Core-3.7.0/tests/cmake/overlays/soc_folder_overlay/src/ |
| D | main.c | 54 zassert_false(INCLUDED_BOARD_SUFFIX, "Did not expect board suffix overlay to be present"); in ZTEST()
57 zassert_false(INCLUDED_BOARD, "Did not expect board overlay to be present"); in ZTEST()
58 zassert_true(INCLUDED_BOARD_QUALIFIERS, "Expected board qualifier overlay to be present"); in ZTEST()
60 zassert_true(INCLUDED_BOARD, "Expected board overlay to be present"); in ZTEST()
62 "Did not expect board qualifier overlay to be present"); in ZTEST()
73 zassert_true(INCLUDED_BOARD_SUFFIX, "Expected board suffix overlay to be present"); in ZTEST()
74 zassert_false(INCLUDED_BOARD, "Did not expect board overlay to be present"); in ZTEST()
76 "Did not expect board qualifier overlay to be present"); in ZTEST()
85 zassert_false(INCLUDED_BOARD_SUFFIX, "Did not expect board suffix overlay to be present"); in ZTEST()
86 zassert_false(INCLUDED_BOARD, "Did not expect board overlay to be present"); in ZTEST()
[all …]
|
| /Zephyr-Core-3.7.0/boards/shields/x_nucleo_53l0a1/doc/ |
| D | index.rst | 3 X-NUCLEO-53L0A1 ranging and gesture detection sensor expansion board
9 The X-NUCLEO-53L0A1 expansion board features the VL53L0X ranging and gesture
11 an evaluation board that provides an introduction to the ranging and gesture
14 One VL53L0X is soldered on the expansion board itself. A set of spacers and
15 a cover glass are provided with the board, and can be fitted onto this center
19 The expansion board is compatible with the STM32 Nucleo board family,
26 More information about the board can be found at the
32 This shield can only be used with a development board that provides a
54 - `X-NUCLEO-53L0A1 ranging and gesture detection sensor expansion board User Manual`_
74 :board: nucleo_f429zi
[all …]
|
| /Zephyr-Core-3.7.0/boards/sifive/hifive1/doc/ |
| D | index.rst | 9 The HiFive1 is an Arduino-compatible development board with
10 an FE310 RISC-V SoC. Two revisions of this board are supported in Zephyr:
16 :alt: SiFive HiFive1 board
18 SiFive HiFive1 board (image courtesy of SiFive)
22 :alt: SiFive HiFive1 Rev B board
24 SiFive HiFive1 Rev B board (image courtesy of SiFive)
32 Applications for the HiFive1 board configuration can be built as usual (see
33 :ref:`build_an_application`) using the corresponding board name:
40 :board: hifive1
46 :board: hifive1@B
[all …]
|
| /Zephyr-Core-3.7.0/doc/ |
| D | glossary.rst | 17 to build an application image for a specified board configuration.
21 to create a custom kernel that makes efficient use of the board's
23 An application can sometimes be built for more than one type of board
25 if it does not require any board-specific capabilities.
28 A binary file that is loaded and executed by the board for which
33 Once an application image is loaded onto a board, the image takes control
41 board
44 hardware system or a simulated system running under QEMU. A board can
48 board configuration
50 present on a board are used by the kernel.
[all …]
|
| /Zephyr-Core-3.7.0/samples/drivers/eeprom/ |
| D | README.rst | 16 In case the target board has defined an EEPROM with alias ``eeprom-0`` the
18 :ref:`native_sim` board:
23 :board: native_sim
27 Otherwise either a board specific overlay needs to be defined, or a shield must
28 be activated. Any board with Arduino headers can for example build the sample
33 :board: nrf52840dk/nrf52840
38 For :ref:`gd32f450i_eval` board. First bridge the JP5 to USART with the jumper cap,
43 :board: gd32f450i_eval
|
| /Zephyr-Core-3.7.0/samples/subsys/ipc/ipc_service/static_vrings/ |
| D | Kconfig.sysbuild | 10 default "nrf5340dk/nrf5340/cpunet" if $(BOARD) = "nrf5340dk"
11 default "lpcxpresso55s69/lpc55s69/cpu1" if $(BOARD) = "lpcxpresso55s69"
12 default "mimxrt1160_evk/mimxrt1166/cm4" if $(BOARD) = "mimxrt1160_evk"
13 default "mimxrt1170_evk/mimxrt1176/cm4" if $(BOARD) = "mimxrt1170_evk"
14 default "mimxrt1170_evkb/mimxrt1176/cm4" if $(BOARD) = "mimxrt1170_evkb"
|
| /Zephyr-Core-3.7.0/samples/basic/rgb_led/ |
| D | README.rst | 23 The board must have red, green, and blue LEDs connected via PWM output channels.
26 <dt-guide>` aliases, usually in the :ref:`BOARD.dts file
34 an unsupported board:
38 Unsupported board: red-pwm-led devicetree alias is not defined
39 Unsupported board: green-pwm-led devicetree alias is not defined
40 Unsupported board: blue-pwm-led devicetree alias is not defined
43 :file:`BOARD.dts` file which supports this sample.
49 hardware that is already connected to LEDs on the board.
56 For example, to build and flash this board for :ref:`hexiwear`:
60 :board: hexiwear/mk64f12
|
| /Zephyr-Core-3.7.0/doc/templates/ |
| D | board.tmpl | 3 [Board Name]
8 [A short description about the board, its main features and availability]
14 :alt: Board Name
16 Board Name (Credit: <owner>)
29 [Tables describing the board PINs and how they are configured and can be used
37 [How to use this board with Zephyr and how to flash a Zephyr binary on this
43 [ How to debug this board]
|
