Home
last modified time | relevance | path

Searched +full:board +full:- +full:level (Results 1 – 25 of 251) sorted by relevance

1234567891011

/Zephyr-Core-3.5.0/dts/bindings/pinctrl/
Dnuvoton,npcx-pinctrl.yaml2 # SPDX-License-Identifier: Apache-2.0
10 - bias-pull-down: Enable pull-down resistor.
11 - bias-pull-up: Enable pull-up resistor.
12 - drive-open-drain: Output driver is open-drain.
15 - pinmux-locked: Lock pinmux configuration for peripheral device
16 - pinmux-gpio: Inverse pinmux back to gpio
17 - psl-in-mode: Select the assertion detection mode of PSL input
18 - psl-in-pol: Select the assertion detection polarity of PSL input
20 An example for NPCX7 family, include the chip level pinctrl DTSI file in the
21 board level DTS:
[all …]
Dnuvoton,npcx-leakage-io.yaml2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "nuvoton,npcx-leakage-io"
11 leak-gpios:
12 type: phandle-array
15 property at the board level DT file to save more power consumption.
/Zephyr-Core-3.5.0/soc/arm/ti_simplelink/cc13x2_cc26x2/
DKconfig.soc4 # SPDX-License-Identifier: Apache-2.0
33 bool "Board defines custom RFCC26XX hwAttrs structure"
35 The board defines its own RFCC26XX_hwAttrs structure (e.g., for
49 associated pin is at the correct logic level on reset.
57 Set the pin that is level checked if the bootloader backdoor is
61 int "ROM bootloader backdoor level"
66 Set the active level of the pin selected for the bootloader backdoor.
/Zephyr-Core-3.5.0/soc/arm/ti_simplelink/cc13x2x7_cc26x2x7/
DKconfig.soc4 # SPDX-License-Identifier: Apache-2.0
33 bool "Board defines custom RFCC26XX hwAttrs structure"
35 The board defines its own RFCC26XX_hwAttrs structure (e.g., for
49 associated pin is at the correct logic level on reset.
57 Set the pin that is level checked if the bootloader backdoor is
61 int "ROM bootloader backdoor level"
66 Set the active level of the pin selected for the bootloader backdoor.
/Zephyr-Core-3.5.0/samples/boards/nrf/mesh/onoff_level_lighting_vnd_app/
DREADME.rst1 .. _bluetooth-mesh-onoff-level-lighting-vnd-sample:
3 Bluetooth: Mesh Generic OnOff, Generic Level, Lighting & Vendor Models
10 - Generic OnOff Server
11 - Generic OnOff Client
12 - Generic Level Server
13 - Generic Level Client
14 - Generic Default Transition Time Server
15 - Generic Default Transition Time Client
16 - Generic Power OnOff Server
17 - Generic Power OnOff Setup Server
[all …]
/Zephyr-Core-3.5.0/samples/basic/custom_dts_binding/
DREADME.rst1 .. zephyr:code-sample:: gpio-custom-dts-binding
3 :relevant-api: gpio_interface devicetree-generic-id devicetree-generic-exist
10 In Zephyr, all hardware-specific configuration is described in the devicetree.
18 For typical use cases like LEDs or buttons, the existing :dtcompatible:`gpio-leds` or
19 :dtcompatible:`gpio-keys` compatibles can be used.
25 :zephyr_file:`samples/basic/custom_dts_binding/dts/bindings/power-switch.yaml`. The gate driver for
32 For each board that should be supported, a ``.overlay`` file has to be defined
35 Afterwards, the sample can be built and executed for the ``<board>`` as follows:
37 .. zephyr-app-commands::
38 :zephyr-app: samples/basic/custom_dts_binding
[all …]
/Zephyr-Core-3.5.0/doc/build/dts/
Ddesign.rst1 .. _dt-design:
14 Zephyr's built-in device drivers and sample applications shall obtain
20 - New device drivers shall use devicetree APIs to determine which :ref:`devices
21 to create <dt-create-devices>`.
23 - In-tree sample applications shall use :ref:`aliases <dt-alias-chosen>` to
25 used in the current build. For example, the :zephyr:code-sample:`blinky` sample uses this to
28 - Boot-time pin muxing and pin control for new SoCs shall be accomplished via a
29 devicetree-based pinctrl driver
34 - Zephyr's :ref:`twister_script` currently use :file:`board.yaml` files to
35 determine the hardware supported by a board. This should be obtained from
[all …]
/Zephyr-Core-3.5.0/samples/drivers/led_ws2812/
DREADME.rst1 .. zephyr:code-sample:: led-ws2812
3 :relevant-api: led_strip_interface
18 .. _74AHCT125: https://cdn-shop.adafruit.com/datasheets/74AHC125.pdf
20 - LED strip using WS2812 or compatible, such as the `NeoPixel Ring 12
23 - Note that 5V communications may require a level translator, such as the
26 - LED power strip supply. It's fine to power the LED strip off of your board's
27 IO voltage level even if that's below 5V; the LEDs will simply be dimmer in
33 #. Ensure your Zephyr board, and the LED strip share a common ground.
35 your board to the data input pin of the first WS2812 IC in the strip.
36 #. Power the LED strip at an I/O level compatible with the control pin signals.
[all …]
/Zephyr-Core-3.5.0/doc/develop/test/
Dtwister.rst8 case on boards marked as default in the board definition file.
21 When using (at least) one ``-v`` option, twister's console output
26 - The test is marked as ``build_only: true`` in its ``.yaml``
28 - The test configuration has defined a ``harness`` but you don't have
30 - The target device is not connected and not available for flashing
31 - You or some higher level automation invoked twister with
32 ``--build-only``.
38 .. group-tab:: Linux
40 .. code-block:: bash
42 $ source zephyr-env.sh
[all …]
/Zephyr-Core-3.5.0/scripts/west_commands/
Dbuild.py3 # SPDX-License-Identifier: Apache-2.0
20 _ARG_SEPARATOR = '--'
26 west build [-h] [-b BOARD[@REV]]] [-d BUILD_DIR]
27 [-t TARGET] [-p {auto, always, never}] [-c] [--cmake-only]
28 [-n] [-o BUILD_OPT] [-f]
29 [--sysbuild | --no-sysbuild] [--domain DOMAIN]
30 [source_dir] -- [cmake_opt [cmake_opt ...]]
40 cmake_opt extra options to pass to cmake; implies -c
41 (these must come after "--" as shown above)
45 A "pristine" build directory is empty. The -p option controls
[all …]
/Zephyr-Core-3.5.0/soc/arm/cypress/psoc6/
Dsoc.h3 * Copyright (c) 2020-2021, ATL Electronics
5 * SPDX-License-Identifier: Apache-2.0
10 * @brief Board configuration macros
12 * This header file is used to specify and describe board-level aspects
/Zephyr-Core-3.5.0/boards/arm/adafruit_itsybitsy_nrf52840/
DKconfig.defconfig1 # Adafruit ItsyBitsy nRF52840 Express board configuration
4 # SPDX-License-Identifier: Apache-2.0
8 config BOARD config
44 # Set USB log level to error only
/Zephyr-Core-3.5.0/boards/arm/mimxrt595_evk/
DKconfig.defconfig1 # MIMXRT595-EVK board
3 # Copyright 2022-2023, NXP
4 # SPDX-License-Identifier: Apache-2.0
8 config BOARD config
32 # Turn on Device Level Power Management as we wish
/Zephyr-Core-3.5.0/doc/services/tfm/
Dbuild.rst3 TF-M Build System
6 When building a valid ``_ns`` board target, TF-M will be built in the
7 background, and linked with the Zephyr non-secure application. No knowledge
8 of TF-M's build system is required in most cases, and the following will
9 build a TF-M and Zephyr image pair, and run it in qemu with no additional
12 .. code-block:: bash
14 $ west build -p auto -b mps2_an521_ns samples/tfm_integration/psa_protected_storage/ -t run
18 deal with signing the secure and non-secure images before deploying them.
20 Images Created by the TF-M Build
23 The TF-M build system creates the following executable files:
[all …]
/Zephyr-Core-3.5.0/tests/kernel/sched/deadline/
Dprj.conf9 # specific instead of using the board-level default.
/Zephyr-Core-3.5.0/soc/arm/nxp_kinetis/k6x/
Dsoc.h2 * Copyright (c) 2014-2015 Wind River Systems, Inc.
5 * SPDX-License-Identifier: Apache-2.0
10 * @brief Board configuration macros for the fsl_frdm_k64f platform
12 * This header file is used to specify and describe board-level aspects for the
/Zephyr-Core-3.5.0/samples/subsys/sensing/simple/
DREADME.rst1 .. zephyr:code-sample:: sensing
3 :relevant-api: sensing_api
5 Get high-level sensor data in defined intervals.
31 .. zephyr-app-commands::
32 :zephyr-app: samples/subsys/sensing/simple
33 :host-os: unix
34 :board: native_posix
38 To build for another board, change "native_posix" above to that board's name.
/Zephyr-Core-3.5.0/boards/arm/bl654_usb/
DKconfig.defconfig1 # BL654 USB adapter board configuration
3 # Copyright (c) 2021-2022 Laird Connectivity
4 # SPDX-License-Identifier: Apache-2.0
8 config BOARD config
12 # must be linked after Nordic MBR, that is factory-programmed on the board.
53 # Set USB log level to error only
/Zephyr-Core-3.5.0/scripts/utils/
Dpinctrl_nrf_migrate.py4 # SPDX-License-Identifier: Apache-2.0
11 nRF-based boards using the old <signal>-pin properties to select peripheral
12 pins. The script will parse a board Devicetree file and will first adjust that
13 file by removing old pin-related properties replacing them with pinctrl states.
14 A board-pinctrl.dtsi file will be generated containing the configuration for
28 -i path/to/board.dts
29 [--no-backup]
30 [--skip-nrf-check]
31 [--header ""]
35 .. code-block:: devicetree
[all …]
/Zephyr-Core-3.5.0/samples/subsys/logging/logger/
DREADME.rst1 .. zephyr:code-sample:: logging
3 :relevant-api: log_api log_ctrl
10 main features: severity levels, timestamping, module level filtering and
11 instance level filtering. It also showcases logging capabilities in terms of
20 .. zephyr-app-commands::
21 :zephyr-app: samples/subsys/logging/logger
22 :host-os: unix
23 :board: qemu_x86
31 .. code-block:: console
38 Instance level logging showcase.
[all …]
/Zephyr-Core-3.5.0/boards/shields/mikroe_mcp2518fd_click/doc/
Dindex.rst3 MikroElektronika MCP2518FD Click shield (CAN-FD)
7 --------
9 MCP2518FD Click shield has a MCP2518FD CAN-FD controller via a SPI
10 interface and a high-speed ATA6563 CAN transceiver.
18 The shield uses a mikroBUS interface. The target board must define
20 (see :ref:`shields` for more details). The target board must also
21 support level triggered interrupts.
26 Set ``-DSHIELD=mikroe_mcp2518fd_click`` when you invoke ``west build``,
29 .. zephyr-app-commands::
30 :zephyr-app: samples/drivers/can/counter
[all …]
/Zephyr-Core-3.5.0/soc/arm/nxp_lpc/lpc54xxx/
Dsoc.h4 * SPDX-License-Identifier: Apache-2.0
9 * @brief Board configuration macros for the nxp_lpc54114 platform
11 * This header file is used to specify and describe board-level aspects for the
/Zephyr-Core-3.5.0/dts/xtensa/espressif/esp32/
Desp32_d0wd_v3.dtsi4 * SPDX-License-Identifier: Apache-2.0
11 gpio-reserved-ranges = <20>,<24>,<28 31>; // NC
14 /* Add flash or psram on board or application level */
/Zephyr-Core-3.5.0/boards/arm/degu_evk/
DKconfig.defconfig4 # SPDX-License-Identifier: Apache-2.0
8 config BOARD config
30 # Set USB log level to error only
/Zephyr-Core-3.5.0/boards/arm/twr_ke18f/dts/bindings/
Dnxp,flexio.yaml2 # SPDX-License-Identifier: Apache-2.0
6 declares pinctrl properties, so that the user can MUX pins at the board level
11 include: [base.yaml, pinctrl-device.yaml]
14 pinctrl-0:
16 pinctrl-names:

1234567891011