Home
last modified time | relevance | path

Searched +full:built +full:- +full:in (Results 1 – 25 of 816) sorted by relevance

12345678910>>...33

/Zephyr-latest/drivers/serial/
DKconfig.esp321 # SPDX-License-Identifier: Apache-2.0
16 bool "ESP32 built-in USB serial driver"
22 Enable the built-in USB serial interface present in some Espressif
23 MCUs like ESP32-Cx.
26 (USB_SERIAL_JTAG), which acts as a CDC-ACM interface towards the
27 USB host. The USB stack is built into the chip and accessed
Duart_native_ptty_bottom.h4 * SPDX-License-Identifier: Apache-2.0
7 * When built with the native_simulator this will be built in the runner context,
/Zephyr-latest/doc/connectivity/networking/
Dnetworking_with_host.rst31 * QEMU using built-in Ethernet driver.
34 built-in Ethernet driver. Not all QEMU boards support built-in Ethernet so
35 in some cases, you might need to use the SLIP method for host connectivity.
42 this support is built into QEMU, it can be used with any model and requires no
49 * User mode networking emulates a built-in IP router and DHCP server, and
59 * The Zephyr instance can be executed as a user space process in the host
62 requires that there is an adaptation driver in Zephyr for interfacing
/Zephyr-latest/samples/subsys/llext/modules/
DKconfig1 # SPDX-License-Identifier: Apache-2.0
12 This enables building the hello_world function, implemented in
13 hello_world_ext.c, either as an llext module or as a built-in part of
16 If you select 'm', the hello_world function will be built as an llext
18 linked in the Zephyr image.
20 Note that additional architecture-specific configuration may be
Dprj.conf4 # CONFIG_MODULES must be enabled to allow setting any options to "m" in the
6 # as-is even if Zephyr has a completely different concept for "modules".
10 # LLEXT is only required when loading the extension at runtime. Since in this
11 # basic example there's only one llext, leaving it in when building the
12 # extension as a built-in is redundant; in a real application, however, there
29 # built-in by default.
31 # To build it as an llext, please follow the instructions in the documentation
32 # of this sample; there are architecture-specific settings that must be set in
/Zephyr-latest/samples/subsys/llext/edk/
DREADME.rst1 .. zephyr:code-sample:: llext-edk
3 :relevant-api: llext_apis
19 run in different contexts. Extensions ``ext1``, ``ext2`` and ``ext3`` run in
22 subscribing to events. Extension ``kext1`` runs in a kernel thread, albeit similar
26 providing some level of isolation - although the kernel one still has access
29 Note that the kernel extension is only available when the EDK is built with
33 The application is built using the Zephyr build system. The EDK is built using
34 the Zephyr build system as well, via ``llext-edk`` target. The EDK is then
35 extracted and the extensions are built using CMake.
40 One could build the extensions in different directories, not related to the
[all …]
/Zephyr-latest/doc/_templates/
Dsearchbox.html3 (ex. built-in search, Google Custom Search, ...)
5 {%- if ('singlehtml' not in builder) %}
6 <div class="search-container" role="search">
7 <form id="rtd-search-form" class="wy-form" action="{{ pathto('search') }}" method="get">
9 aria-label="{{ _('Search docs') }}" />
10 {%- if google_searchengine_id is defined %}
11 <span id="search-se-settings-icon" class="fa fa-gear" role="button" tabindex="0"
12 title="Search settings" aria-label="Search settings"
13 aria-haspopup="true" aria-controls="search-se-menu" aria-expanded="false"
16 <div id="search-se-menu" role="menu" aria-labelledby="search-se-settings-icon">
[all …]
/Zephyr-latest/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.
12 Consequently, also GPIO pins are configured in the devicetree and assigned to a specific purpose
15 This is in contrast to other embedded environments like Arduino, where e.g. the direction (input /
16 output) of a GPIO pin is configured in the application firmware.
18 For typical use cases like LEDs or buttons, the existing :dtcompatible:`gpio-leds` or
19 :dtcompatible:`gpio-keys` compatibles can be used.
24 custom devicetree binding for the power output controlled via a GPIO pin is specified in the file
25 :zephyr_file:`samples/basic/custom_dts_binding/dts/bindings/power-switch.yaml`. The gate driver for
[all …]
/Zephyr-latest/subsys/tracing/
Dtracing_backend_posix_bottom.h4 * SPDX-License-Identifier: Apache-2.0
7 * When built with the native_simulator this will be built in the runner context,
/Zephyr-latest/samples/application_development/external_lib/
DREADME.rst1 .. zephyr:code-sample:: external_library
12 system and how to include the built static library.
17 To use this sample on a Windows host operating system, GNU Make needs to be in
25 .. code-block:: bash
34 The pre-built make application can be downloaded from
37 getting the ``Complete package`` setup. Once installed and in the path, build
/Zephyr-latest/samples/drivers/eeprom/
DREADME.rst1 .. zephyr:code-sample:: eeprom
3 :relevant-api: eeprom_interface
5 Store a boot count value in EEPROM.
10 This sample demonstrates the :ref:`EEPROM driver API <eeprom_api>` in a simple boot counter
16 In case the target board has defined an EEPROM with alias ``eeprom-0`` the
17 sample can be built without further ado. This applies for example to the
20 .. zephyr-app-commands::
21 :zephyr-app: samples/drivers/eeprom
22 :host-os: unix
31 .. zephyr-app-commands::
[all …]
/Zephyr-latest/boards/seeed/xiao_esp32c6/support/
Dopenocd.cfg1 # ESP32C6 has built-in JTAG interface over USB port in pins GPIO13/GPIO12 (D-/D+).
4 source [find board/esp32c6-builtin.cfg]
/Zephyr-latest/boards/espressif/esp32c6_devkitc/support/
Dopenocd.cfg1 # ESP32C6 has built-in JTAG interface over USB port in pins GPIO13/GPIO12 (D-/D+).
4 source [find board/esp32c6-builtin.cfg]
/Zephyr-latest/snippets/
Dindex.rst1 .. _built-in-snippets:
3 Built-in snippets
/Zephyr-latest/boards/beagle/beagleplay/support/
Dopenocd.cfg1 # SPDX-License-Identifier: Apache-2.0
6 # Since BeaglePlay CC1352 does not have a built in debugger, we use XDS110 in launchpad
/Zephyr-latest/drivers/input/
Dinput_sdl_touch_bottom.h4 * SPDX-License-Identifier: Apache-2.0
7 * When built with the native_simulator this will be built in the runner context,
/Zephyr-latest/drivers/gpio/
Dgpio_emul_sdl_bottom.h5 * SPDX-License-Identifier: Apache-2.0
8 * When built with the native_simulator this will be built in the runner context,
/Zephyr-latest/samples/subsys/smf/smf_calculator/
DREADME.rst1 .. zephyr:code-sample:: smf_calculator
3 :relevant-api: smf
13 The 'business logic' of the calculator is based on the statechart given in
14 Fig 2.18 of *Practical UML Statecharts in C/C++* 2nd Edition by Miro Samek.
15 This uses a three-layer hierarchical statechart to handle situations such as
19 screen in the ``op_entered`` state depending on if a previous result is
25 :figclass: align-center
30 output, based on the sample in samples/drivers/display. The state machine updates
34 on RAM-constrained boards like the :zephyr:board:`disco_l475_iot1`.
40 must be passed to ``west build`` using the ``--shield`` option, e.g.
[all …]
/Zephyr-latest/samples/drivers/dac/
DREADME.rst1 .. zephyr:code-sample:: dac
2 :name: Digital-to-Analog Converter (DAC)
3 :relevant-api: dac_interface
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``,
18 ``dac-channel-id``, and ``dac-resolution`` properties set. See the predefined
19 overlays in :zephyr_file:`samples/drivers/dac/boards` for examples.
23 The sample can be built and executed for the
26 .. zephyr-app-commands::
27 :zephyr-app: samples/drivers/dac
[all …]
/Zephyr-latest/boards/norik/octopus_io_board/doc/
Dindex.rst6 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
9 development and prototyping of low-power IoT applications.
11 nRF9160 SiP contains ARM Cortex-M33 application processor and the
18 * :abbr:`I2C (Inter-Integrated Circuit)`
25 * :abbr:`UARTE (Universal asynchronous receiver-transmitter with EasyDMA)`
29 Octopus IO-Board offers the following features:
32 * USB-C for power
41 * Tag-Connect TC2030-IDC 6-pin connector for SWD programming and debugging
44 More information about the board can be found at the `Octopus IO-Board Product Page`_
[all …]
/Zephyr-latest/boards/we/orthosie1ev/support/
Dopenocd.cfg3 # ESP32C3 has built-in JTAG interface over USB port in pins GPIO18/GPIO19 (D-/D+).
7 # Otherwise, use external JTAG programmer as ESP-Prog
/Zephyr-latest/boards/espressif/esp32c3_devkitc/support/
Dopenocd.cfg3 # ESP32C3 has built-in JTAG interface over USB port in pins GPIO18/GPIO19 (D-/D+).
7 # Otherwise, use external JTAG programmer as ESP-Prog
/Zephyr-latest/boards/espressif/esp32c3_devkitm/support/
Dopenocd.cfg3 # ESP32C3 has built-in JTAG interface over USB port in pins GPIO18/GPIO19 (D-/D+).
7 # Otherwise, use external JTAG programmer as ESP-Prog
/Zephyr-latest/boards/espressif/esp32c3_rust/support/
Dopenocd.cfg3 # ESP32C3 has built-in JTAG interface over USB port in pins GPIO18/GPIO19 (D-/D+).
7 # Otherwise, use external JTAG programmer as ESP-Prog
/Zephyr-latest/doc/develop/west/
Dindex.rst3 West (Zephyr's meta-tool)
6 The Zephyr project includes a swiss-army knife command line tool named
7 ``west``\ [#west-name]_. West is developed in its own `repository`_.
9 West's built-in commands provide a multiple repository management system with
15 Like ``git`` and ``docker``, the top-level ``west`` command takes some common
16 options, a sub-command to run, and then options and arguments for that
17 sub-command::
19 west [common-opts] <command> [opts] <args>
23 python3 -m west [common-opts] <command> [opts] <args>
25 You can run ``west --help`` (or ``west -h`` for short) to get top-level help
[all …]

12345678910>>...33