| /Zephyr-Core-3.4.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>.
10 # If a board implementation is not found for the specified board an error will
13 # If user provided board is a board alias, the board will be adjusted to real
14 # board name.
16 # If board name is deprecated, then board will be adjusted to new board name and
22 # - BOARD: Board, without revision field.
23 # - BOARD_REVISION: Board revision
24 # - BOARD_DIR: Board directory with the implementation for selected board
[all …]
|
| /Zephyr-Core-3.4.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
17 - Board: a particular CPU instance and its peripherals in a concrete hardware
19 - SoC: the exact system on a chip the board's CPU is part of
27 .. figure:: board/hierarchy.png
40 * - Board
75 :ref:`create-your-board-directory`. If you don't know, try:
78 board documentation to find out for sure.
113 .. _create-your-board-directory:
[all …]
|
| D | shields.rst | 6 Shields, also known as "add-on" or "daughter boards", attach to a board
14 Shield configuration files are available in the board directory
27 format that is merged with the board's :ref:`devicetree <dt-guide>`
41 board level, it is advised, specifically for shields devicetree descriptions,
52 Board compatibility
55 Hardware shield-to-board compatibility depends on the use of well-known
64 * Devicetree: A board :ref:`devicetree <dt-guide>` file,
65 :file:`BOARD.dts` should define an alternate nodelabel for each connector interface.
72 Board specific shield configuration
75 If modifications are needed to fit a shield to a particular board or board
[all …]
|
| /Zephyr-Core-3.4.0/samples/subsys/ipc/rpmsg_service/remote/ |
| D | CMakeLists.txt | 8 if("${BOARD}" STREQUAL "nrf5340dk_nrf5340_cpunet"
9 OR "${BOARD}" STREQUAL "bl5340_dvk_cpunet"
10 OR "${BOARD}" STREQUAL "lpcxpresso54114_m0"
11 OR "${BOARD}" STREQUAL "mps2_an521_remote"
12 OR "${BOARD}" STREQUAL "v2m_musca_b1_ns"
13 OR "${BOARD}" STREQUAL "esp32_net")
14 message(STATUS "${BOARD} compile as slave in this sample")
16 message(FATAL_ERROR "${BOARD} was not supported for this sample")
|
| /Zephyr-Core-3.4.0/samples/subsys/ipc/rpmsg_service/ |
| D | CMakeLists.txt | 10 if("${BOARD}" STREQUAL "nrf5340dk_nrf5340_cpuapp")
12 elseif("${BOARD}" STREQUAL "bl5340_dvk_cpuapp")
14 elseif("${BOARD}" STREQUAL "lpcxpresso54114_m4")
16 elseif("${BOARD}" STREQUAL "mps2_an521")
19 elseif("${BOARD}" STREQUAL "v2m_musca_b1")
21 elseif("${BOARD}" STREQUAL "esp32")
24 message(FATAL_ERROR "${BOARD} was not supported for this sample")
27 message(STATUS "${BOARD} compile as Master in this sample")
36 if("${BOARD}" STREQUAL "esp32")
53 if(("${BOARD}" STREQUAL "lpcxpresso54114_m4"))
[all …]
|
| /Zephyr-Core-3.4.0/samples/drivers/led_apa102/ |
| D | README.rst | 22 - Zephyr board with SPI master driver. SPI communications must use 5V
31 #. Ensure your Zephyr board, the 5V power supply, and the LED strip
33 #. Connect the MOSI pin of your board's SPI master to the data input
35 #. Connect the SCLK pin of your board's SPI master to the clock input
45 Configure For Your Board
48 Now check if your board is already supported, by looking for a file
51 If your board isn't supported yet, you'll need to configure the
54 #. Configure your board's SPI master in a configuration file under
57 To provide additional configuration for some particular board,
65 #. Configure your board's dts overlay. See ``nucleo_l432kc.overlay``
[all …]
|
| /Zephyr-Core-3.4.0/boards/arm/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.4.0/samples/subsys/ipc/openamp/ |
| D | Kconfig.sysbuild | 9 default "lpcxpresso54114_m0" if $(BOARD) = "lpcxpresso54114_m4"
10 default "lpcxpresso55s69_cpu1" if $(BOARD) = "lpcxpresso55s69_cpu0"
11 default "mps2_an521_remote" if $(BOARD) = "mps2_an521"
12 default "v2m_musca_b1_ns" if $(BOARD) = "v2m_musca_b1"
13 default "mimxrt1170_evk_cm4" if $(BOARD) = "mimxrt1170_evk_cm7"
14 default "mimxrt1160_evk_cm4" if $(BOARD) = "mimxrt1160_evk_cm7"
|
| /Zephyr-Core-3.4.0/boards/ |
| D | Kconfig | 3 config BOARD config
6 This option holds the name of the board and is used to locate the files
7 related to the board in the source tree (under boards/).
8 The Board is the first location where we search for a linker.ld file,
15 If the BOARD has a revision field set, this is the revision.
16 Otherwise, it is the empty string. For example, if BOARD is
17 "plank@foo", this option will be "foo". If BOARD is "plank",
23 This hidden option is set in the board configuration and indicates
24 the Zephyr release that the board configuration will be removed.
25 When set, any build for that board will generate a clearly visible
[all …]
|
| /Zephyr-Core-3.4.0/boards/arm/efr32_radio/doc/ |
| D | brd4255a.rst | 9 The EFR32FG13P Flex Gecko 2.4 GHz and 915 MHz Radio Board is delivered as a
10 `standalone Proprietary Wireless radio board`_. It contains a EFR32FG13P Wireless
15 :alt: SLWRB4255A Flex Gecko 2.4 GHz and 915 MHz Radio Board
19 The BRD4255A a.k.a. SLWRB4255A radio board plugs into the Wireless Starter Kit
33 For more information about the EFR32FG13 SoC and BRD4255A board, refer to these
45 :ref:`EFR32 Radio Board Supported Features <efr32_radio_supported_features>`
47 efr32_radio_brd4255a board.
57 board.
63 USART0 is connected to the board controller and is used for the console.
69 :ref:`Programming and Debugging EFR32 Radio Board <efr32_radio_programming>`
[all …]
|
| /Zephyr-Core-3.4.0/samples/drivers/misc/ft800/ |
| D | README.rst | 17 * A board with SPI support
18 * Display with `FT800 EVE`_ like `VM800C board`_
23 You will need to connect the `FT800 EVE`_ SPI interface onto a board that
29 This sample should work on any board that has SPI enabled and has an Arduino
30 shield interface. For example, it can be run on the nRF52840-DK board as
35 :board: nrf52840dk_nrf52840
39 To build the sample for `VM800C board`_ the shield must be defined as described
44 :board: nrf52840dk_nrf52840
49 .. _VM800C board: https://www.ftdichip.com/old2020/Products/Modules/VM800C.html
|
| /Zephyr-Core-3.4.0/tests/bsim/bluetooth/ll/cis/tests_scripts/ |
| D | connected_iso.sh | 15 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
18 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
21 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
24 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
27 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
30 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
33 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
36 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
39 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
42 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay_conf \
|
| D | connected_iso_acl_first.sh | 15 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
18 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
21 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
24 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
27 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
30 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
33 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
36 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
39 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
42 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-acl_first_conf \
|
| D | connected_iso_legacy_adv.sh | 15 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
18 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
21 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
24 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
27 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
30 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
33 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
36 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
39 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
42 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_conf \
|
| D | connected_iso_legacy_adv_acl_first.sh | 15 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
18 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
21 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
24 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
27 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
30 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
33 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
36 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
39 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
42 Execute ./bs_${BOARD}_tests_bsim_bluetooth_ll_cis_prj_conf_overlay-legacy_adv_acl_first_conf \
|
| /Zephyr-Core-3.4.0/boards/arm/efr32_radio/ |
| D | Kconfig.board | 2 # EFR32FG1P BRD4250B / EFR32FG13P BRD4255A board
9 bool "Silicon Labs BRD4104A (Blue Gecko Radio Board)"
15 bool "Silicon Labs BRD4250B (Flex Gecko Radio Board)"
21 bool "Silicon Labs BRD4180A (Mighty Gecko Radio Board)"
27 bool "Silicon Labs BRD4187C (Mighty Gecko Radio Board)"
33 bool "Silicon Labs BRD4255A (Flex Gecko Radio Board)"
|
| /Zephyr-Core-3.4.0/samples/basic/rgb_led/ |
| D | README.rst | 22 The board must have red, green, and blue LEDs connected via PWM output channels.
25 <dt-guide>` aliases, usually in the :ref:`BOARD.dts file
33 an unsupported board:
37 Unsupported board: red-pwm-led devicetree alias is not defined
38 Unsupported board: green-pwm-led devicetree alias is not defined
39 Unsupported board: blue-pwm-led devicetree alias is not defined
42 :file:`BOARD.dts` file which supports this sample.
48 hardware that is already connected to LEDs on the board.
55 For example, to build and flash this board for :ref:`hexiwear_k64`:
59 :board: hexiwear_k64
|
| /Zephyr-Core-3.4.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.4.0/boards/arm/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)
|
| /Zephyr-Core-3.4.0/tests/bsim/bluetooth/host/l2cap/split/scripts/ |
| D | _compile.sh | 8 BOARD="${BOARD:-nrf52_bsim}"
9 dut_exe="bs_${BOARD}_tests_bsim_bluetooth_host_l2cap_split_dut_prj_conf"
10 tester_exe="bs_${BOARD}_tests_bsim_bluetooth_host_l2cap_split_tester_prj_conf"
15 west build -b ${BOARD} -d build_dut dut && \
17 west build -b ${BOARD} -d build_tester tester && \
|
| /Zephyr-Core-3.4.0/samples/drivers/eeprom/ |
| D | README.rst | 15 In case the target board has defined an EEPROM with alias ``eeprom-0`` the
17 :ref:`native_posix` board:
22 :board: native_posix
26 Otherwise either a board specific overlay needs to be defined, or a shield must
27 be activated. Any board with Arduino headers can for example build the sample
32 :board: nrf52840dk_nrf52840
37 For :ref:`gd32f450i_eval` board. First bridge the JP5 to USART with the jumper cap,
42 :board: gd32f450i_eval
|
| /Zephyr-Core-3.4.0/boards/x86/rpl_crb/doc/ |
| D | index.rst | 8 Raptor Lake Reference Board (RPL CRB) is an example implementation of a
9 compact single board computer with high performance for IoT edge devices.
11 This board configuration enables kernel support for the `RPL`_ board.
14 This board configuration works on the variant of `RPL`_
20 General information about the board can be found at the `RPL`_ website.
32 Use the following procedures for booting an image on a RPL CRB board.
47 :board: rpl_crb
59 an Raptor Lake CRB board.
83 Booting the Raptor Lake CRB Board
86 Boot the Raptor Lake CRB board to the EFI shell with USB flash drive connected.
[all …]
|
| /Zephyr-Core-3.4.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]
|
| /Zephyr-Core-3.4.0/samples/drivers/led_lpd8806/ |
| D | README.rst | 21 - Zephyr board with SPI master driver. SPI communications must use 5V
30 #. Ensure your Zephyr board, the 5V power supply, and the LED strip
32 #. Connect the MOSI pin of your board's SPI master to the data input
34 #. Connect the SCLK pin of your board's SPI master to the clock input
46 #. Configure your board's SPI master in a configuration file under
49 To provide additional configuration for some particular board,
56 board's configuration options to set up your desired SPI master.
67 :board: <board>
71 Refer to your :ref:`board's documentation <boards>` for alternative
72 flash instructions if your board doesn't support the ``flash`` target.
[all …]
|
| /Zephyr-Core-3.4.0/samples/shields/lmp90100_evb/rtd/ |
| D | README.rst | 3 LMP90100 Sensor AFE Evaluation Board: RTD Sample
11 Sensor AFE Evaluation Board shield. The sample is designed for use
21 connected to the development board according to Example #3 ("3-wire
22 RTD Application") in the `LMP90100 Sensor AFE Evaluation Board User's
29 board with a matching Arduino connector. For this example, we use a
30 :ref:`frdm_k64f` board.
34 :board: frdm_k64f
52 .. _LMP90100 Sensor AFE Evaluation Board User's Guide:
|
