| /Zephyr-latest/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-latest/doc/_extensions/zephyr/domain/templates/ |
| D | board-card.html | 7 class="board-card"
8 {% if board.doc_page -%}
9 href="../{{ board.doc_page | replace(".rst", ".html") }}"
13 aria-label="Open the documentation page for {{ board.full_name }}"
14 data-name="{{ board.full_name}}"
15 data-arch="{{ board.archs | join(" ") }}"
16 data-vendor="{{ board.vendor }}"
17 data-socs="{{ board.socs | join(" ") }}"
19 <div class="vendor">{{ vendors[board.vendor] }}</div>
20 {% if board.image -%}
[all …]
|
| /Zephyr-latest/samples/drivers/mbox/ |
| D | Kconfig.sysbuild | 9 string "Remote board"
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/cpuapp" if "$(BOARD)${BOARD_QUALIFIERS}" = "nrf54h20dk/nrf54h20/cpura…
18 default "nrf54l15dk/nrf54l15/cpuflpr" if $(BOARD) = "nrf54l15dk"
19 default "stm32h747i_disco/stm32h747xx/m4" if $(BOARD) = "stm32h747i_disco"
[all …]
|
| /Zephyr-latest/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-latest/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-latest/samples/sensor/mcux_acmp/ |
| D | README.rst | 11 sample supports the :zephyr:board:`twr_ke18f`, :zephyr:board:`mimxrt1170_evk`, :zephyr:board:`frdm_…
12 , :zephyr:board:`frdm_ke17z512` and :zephyr:board:`mimxrt1180_evk`.
16 the positive input can be adjusted by turning the on-board potentiometer for
17 :zephyr:board:`twr_ke18f` board, for :zephyr:board:`mimxrt1170_evk` the voltage signal is
18 captured on J25-13, the :zephyr:board:`frdm_ke17z` and :zephyr:board:`frdm_ke17z512` boards are
19 captured in J2-3, the :zephyr:board:`mimxrt1180_evk` board are captured in J45-13, need
29 Build the application for the :zephyr:board:`twr_ke18f` board, and adjust the
30 ACMP input voltage by turning the on-board potentiometer.
34 :board: twr_ke18f
40 Build the application for the MIMXRT1170-EVK board, and adjust the
[all …]
|
| /Zephyr-latest/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-latest/scripts/west_commands/ |
| D | boards.py | 50 - name: board name
51 - full_name: board full name (typically, its commercial 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 self.inf(args.format.format(name=board.name, arch=board.arch,
[all …]
|
| /Zephyr-latest/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
94 # HWMv1 only supports a single Path, and requires Board dataclass to be hashable.
109 # Get the main board directory.
145 sys.exit(f'ERROR: qualifiers {qualifiers} not found when extending board {self.name}')
150 def board_key(board): argument
151 return board.name
171 if args.board is not None:
172 ret[arch] |= {b for b in boards if b.name == args.board}
[all …]
|
| /Zephyr-latest/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-latest/boards/norik/octopus_io_board/doc/ |
| D | index.rst | 1 .. zephyr:board:: octopus_io_board
6 Octopus IO-Board is an expansion to the Octopus SoM, which is built around the nRF9160 SiP
7 offering NB-IoT and LTE-M connectivity, GPS and accelerometer. Octopus IO-Board expands
29 Octopus IO-Board offers the following features:
44 More information about the board can be found at the `Octopus IO-Board Product Page`_
45 and in the `Octopus IO-Board Documentation`_.
53 The Octopus IO-Board features multiple dedicated pin headers for peripherals:
69 The Octopus IO-Board can be powered from the following sources:
76 When powered from USB-C or solar cell, the board can charge the Li-Po battery. The battery voltage …
81 The board has a built-in LDO regulator that is used to power the Octopus SoM and peripherals. The E…
[all …]
|
| /Zephyr-latest/samples/basic/blinky_pwm/ |
| D | README.rst | 26 The board must have an LED connected to a PWM output channel. The PWM
28 <dt-guide>` alias, usually in the :ref:`BOARD.dts file
35 already connected to an LED on the board.
42 * - Board
44 * - :zephyr:board:`nucleo_f401re`
46 * - :zephyr:board:`nucleo_l476rg`
48 * - :zephyr:board:`stm32f4_disco`
50 * - :zephyr:board:`nucleo_f302r8`
52 * - :zephyr:board:`nucleo_f103rb`
54 * - :zephyr:board:`nucleo_wb55rg`
[all …]
|
| /Zephyr-latest/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 | index.rst | 6 If you are looking to add Zephyr support for a new board, please start with the
9 When adding support documentation for a board, remember to use the template
10 available under :zephyr_file:`doc/templates/board.tmpl`.
12 Shields are hardware add-ons that can be stacked on top of a board to add extra
22 * A board must meet **all** criteria selected across different fields. For example, if you select
27 * Can't find your exact board? Don't worry! If a similar board with the same or a closely related
28 MCU exists, you can use it as a :ref:`starting point <create-your-board-directory>` for adding
29 support for your own board.
38 .. zephyr:board-catalog::
|
| 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 "$(KCONFIG_BOARD_DIR)/Kconfig.$(BOARD)"
|
| /Zephyr-latest/tests/cmake/hwm/board_extend/src/ |
| D | main.c | 51 zassert_true(EXTENDED_BOARD_A, "Expected extended board to be set");
52 zassert_true(EXTENDED_BOARD_ONE_B, "Expected extended board to be set");
53 zassert_false(EXTENDED_BOARD_TWO_C, "Did not expect extended board two to be set");
54 zassert_true(EXTENDED_BOARD_D, "Expected extended board to be set");
55 zassert_false(BASE_BOARD_CONFIG, "Did not expect base board to be set");
60 zassert_true(EXTENDED_BOARD_A, "Expected extended board to be set");
61 zassert_false(EXTENDED_BOARD_ONE_B, "Did not expect extended board one to be set");
62 zassert_true(EXTENDED_BOARD_TWO_C, "Expected extended board to be set");
63 zassert_true(EXTENDED_BOARD_D, "Expected extended board to be set");
64 zassert_false(BASE_BOARD_CONFIG, "Did not expect base board to be set");
[all …]
|
| /Zephyr-latest/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-latest/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
39 schema;board-schema:
45 desc: Name of the board
49 desc: Full name of the board. Typically set to the commercial name of the board.
56 desc: SoC family of the SoC on the board.
97 board:
98 include: board-schema
102 - include: board-schema
115 grouping of board targets. This is to allow for future image program cycles to not
[all …]
|
| /Zephyr-latest/boards/quicklogic/qomu/doc/ |
| D | index.rst | 1 .. zephyr:board:: qomu
6 The Qomu board is a platform with an on-board QuickLogic EOS S3 Sensor Processing Platform.
12 - 16 Mbit of on-board flash memory
17 Detailed information about the board can be found in a `Qomu repository`_ and `Qomu User Guide`_.
35 :board: qomu
38 #. Remove Qomu board from USB port.
39 #. Insert Qomu board to USB port.
58 https://github.com/QuickLogic-Corp/qomu-dev-board
61 https://github.com/QuickLogic-Corp/qomu-dev-board/blob/master/doc/Qomu_UserGuide.pdf
64 https://github.com/QuickLogic-Corp/qomu-dev-board/blob/master/doc/qomu-board.pdf
|
| /Zephyr-latest/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-latest/samples/drivers/dac/ |
| D | README.rst | 15 The DAC output is defined in the board's devicetree and pinmux file.
17 The board's :ref:`/zephyr,user <dt-zephyr-user>` node must have ``dac``,
24 :zephyr:board:`nucleo_l073rz` as follows:
28 :board: nucleo_l073rz
35 :zephyr:board:`nucleo_l152re` as follows:
39 :board: nucleo_l152re
46 :zephyr:board:`nucleo_f767zi` as follows:
50 :board: nucleo_f767zi
57 :zephyr:board:`stm32f3_disco` as follows:
61 :board: stm32f3_disco
[all …]
|
| /Zephyr-latest/boards/panasonic/pan1770_evb/doc/ |
| D | index.rst | 1 .. zephyr:board:: pan1770_evb
6 The PAN1770 Evaluation Board is a development tool for the PAN1770 module
14 evaluation board on the `product website`_.
16 The PAN1770 evaluation board is closely linked to these other evaluation
19 * :zephyr:board:`pan1780_evb`
20 * :zephyr:board:`pan1781_evb`
21 * :zephyr:board:`pan1782_evb`
26 You can find the `user guide`_ for the PAN1770 Evaluation Board in the
39 The schematics for the PAN1770 Evaluation Board are available in the
45 Please use the ``pan1770_evb`` board configuration when
|
| /Zephyr-latest/samples/subsys/ipc/ipc_service/static_vrings/ |
| D | Kconfig.sysbuild | 10 default "nrf5340dk/nrf5340/cpunet" if $(BOARD) = "nrf5340dk"
11 default "nrf5340bsim/nrf5340/cpunet" if $(BOARD) = "nrf5340bsim"
12 default "lpcxpresso55s69/lpc55s69/cpu1" if $(BOARD) = "lpcxpresso55s69"
13 default "mimxrt1160_evk/mimxrt1166/cm4" if $(BOARD) = "mimxrt1160_evk"
14 default "mimxrt1170_evk/mimxrt1176/cm4" if $(BOARD) = "mimxrt1170_evk"
15 default "mimxrt1170_evkb/mimxrt1176/cm4" if $(BOARD) = "mimxrt1170_evkb"
|
| /Zephyr-latest/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 :zephyr:board:`gd32f450i_eval` board. First bridge the JP5 to USART with the jumper cap,
43 :board: gd32f450i_eval
|
| /Zephyr-latest/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
|
