Searched refs:and (Results 401 – 425 of 3855) sorted by relevance
1...<<11121314151617181920>>...155
| /Zephyr-latest/subsys/usb/device_next/app/ |
| D | Kconfig.cdc_acm_serial | 4 # This file contains Kconfig options and defaults for configuring the USB
5 # device stack and CDC ACM instance to be used as the default serial backend
10 bool "Initialize USB device and CDC ACM UART at boot"
15 required, configured, and enabled.
35 You must use your own VID for samples and applications outside of
42 You must use your own PID for samples and applications outside of
|
| /Zephyr-latest/samples/boards/nxp/mimxrt1060_evk/system_off/ |
| D | README.rst | 10 This sample can be used for basic power measurement and as an example of
14 * Turn the system off after enabling wakeup through a button press, and
24 Building, Flashing and Running
37 3. Device will turn on and idle for 2 seconds
39 to wake the device and restart the application as if it had been
41 alarm to fire and wake the device up automatically.
|
| /Zephyr-latest/samples/cpp/cpp_synchronization/ |
| D | README.rst | 13 and a cooperative thread take turns printing a greeting message to the console,
14 and use timers and semaphores to control the rate at which messages are
15 generated. This demonstrates that kernel scheduling, communication, and
18 Building and Running
21 This kernel project outputs to the console. It can be built and executed
|
| /Zephyr-latest/samples/sensor/sht3xd/ |
| D | README.rst | 5 Get temperature and humidity from a SHT3XD sensor (polling & trigger mode).
11 temperature and humidity. The result is written to the console.
23 Connect Supply: **VDD**, **GND** and Interface: **SDA**, **SCL**
24 and optionally connect the **ALERT** to a interrupt capable GPIO.
26 Depending on the baseboard used, the **SDA** and **SCL** lines require Pull-Up
29 Building and Running
|
| /Zephyr-latest/boards/shields/buydisplay_2_8_tft_touch_arduino/doc/ |
| D | index.rst | 10 pixels and is based on the ILI9341 controller. This shield comes with
14 More information about the shield and Arduino adapter can be found at
15 the `Buydisplay 2.8" TFT Touch Shield website`_ and
46 adjust driver configuration and its Device Tree entry to make use of
53 for Arduino connectors and defines node aliases for SPI and GPIO interfaces
77 …https://www.buydisplay.com/arduino-shield-for-tft-lcd-with-ili9341-controller-and-arduino-due-mega…
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | lcd_srv.rst | 7 specification. The model is optional, and is enabled through the
11 version 1.1, and is used to support the functionality of exposing pages of Composition Data that do
12 not fit in a Config Composition Data Status message and to expose metadata of the model instances.
14 The Large Composition Data Server does not have an API of its own and relies on a
28 :c:struct:`bt_mesh_models_metadata_entry` structure. Each entry contains the length and ID of the
29 metadata, and a pointer to the raw data. Entries can be created using the
31 marks the end of the metadata list and must always be present. If the model has no metadata, the
|
| /Zephyr-latest/doc/develop/west/ |
| D | index.rst | 10 features inspired by Google's Repo tool and Git submodules. West is also
13 building applications, flashing and debugging them, and more.
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
26 for available west commands, and ``west <command> -h`` for detailed help on
|
| /Zephyr-latest/tests/bluetooth/tester/ |
| D | README | 5 Tester application uses binary protocol to control Zephyr stack and is aimed at
8 stack. BTP commands and events are received and buffered for further processing
26 Building and running on QEMU:
37 To build tester application for QEMU use BOARD=qemu_cortex_m3 and
41 Note: Target board have to support enough UARTs for BTP and controller.
48 Next, build and flash tester application by employing the "flash" build
|
| /Zephyr-latest/samples/basic/threads/ |
| D | README.rst | 5 Spawn multiple threads that blink LEDs and print information to the console.
14 The first two each control an LED. These LEDs, ``led0`` and ``led1``, have
15 loop control and timing logic controlled by separate functions.
17 - ``blink0()`` controls ``led0`` and has a 100ms sleep cycle
18 - ``blink1()`` controls ``led1`` and has a 1000ms sleep cycle
21 :ref:`FIFO <fifos_v2>` identifying the thread/LED and how many times it has
32 ``led0`` and ``led1`` :ref:`devicetree <dt-guide>` aliases, usually in the
|
| /Zephyr-latest/samples/drivers/clock_control_xec/ |
| D | README.rst | 11 hardware configuration and exercises some clock control
14 Building and Running
17 The sample can be built and executed on boards using west.
18 No pins configurations, except GPIO014 is used as indicator for entry/exit and
20 GPIO221 alternate function 1 is 32KHZ_OUT and can be monitored on Assembly 6915 JP7 pin 5.
66 Prints MEC172x VBAT and PCR register pertaining to power on status and
|
| /Zephyr-latest/boards/sifive/hifive1/doc/ |
| D | index.rst | 9 and `HiFive1 Rev B <https://www.sifive.com/boards/hifive1-rev-b>`__.
23 Programming and debugging
59 <https://www.sifive.com/boards>`_ and extract it.
75 The HiFive 1 Rev B uses Segger J-Link OB for flashing and debugging. To flash and
77 `Segger J-Link Software and Documentation Pack
79 and choose version V6.46a or later (Downloads for Windows, Linux, and macOS are
82 Now you can flash the application as usual (see :ref:`build_an_application` and
|
| /Zephyr-latest/boards/intel/socfpga/agilex5_socdk/doc/ |
| D | index.rst | 10 environment that includes both hardware and software for developing
12 developing custom ARM* processor-based SoC designs and ideal for intelligent
13 applications at the edge, embedded and more.
21 multi-core ARM processors of Dual-core A55 and Dual-core A76
45 NOTE: TODO, more details on dev kit will be updated as and when available.
50 Programming and Debugging
56 ATF BL2 is the First Stage Boot Loader (FSBL) and ATF BL31 is the Run time resident firmware which
57 provides services like SMC (Secure monitor calls) and PSCI (Power state coordination interface).
80 `Intel® Agilex™ 5 FPGA and SoC FPGA <https://www.intel.in/content/www/in/en/products/details/fpga/a…
|
| /Zephyr-latest/samples/net/wifi/apsta_mode/ |
| D | README.rst | 5 Configure a Wi-Fi board to operate as both an Access Point (AP) and a Station (STA).
11 an Access Point (AP) and a Station (STA) simultaneously.
12 This sample demonstrates how to configure and utilize AP-STA mode.
14 Configuration and usage of following interfaces is shown in sample.
16 1. ``AP mode``: AP mode is configured and enabled. DHCPv4 server is also
18 2. ``STA mode``: Provide the SSID and PSK of you router
24 the board into AP-STA mode to support both modes and attempts to connect to the
25 AP specified by the provided SSID and PSK.
39 Building, Flashing and Running
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | host-tools.rst | 7 flash and debug Zephyr applications.
10 ``debug``, ``debugserver``, and ``attach`` commands, provided your board
11 hardware supports them and your Zephyr board directory's :file:`board.cmake`
22 allows users to develop and program boards with SAM-BA support using
24 bootloader and both extensions from Arduino and Adafruit. Full support was
53 1. Define flash partitions required to accommodate the bootloader and
59 3. Build and flash the SAM-BA bootloader on the device.
65 1. Define flash partitions required to accommodate the bootloader and
77 3. Build and flash the SAM-BA bootloader on the device.
85 Typical flash layout and configuration
[all …]
|
| /Zephyr-latest/boards/st/nucleo_c031c6/doc/ |
| D | index.rst | 5 The STM32 Nucleo-64 development board with STM32C031C6 MCU, supports Arduino and ST morpho connecti…
7 The STM32 Nucleo board provides an affordable, and flexible way for users to try out new concepts,
8 and build prototypes with the STM32 microcontroller, choosing from the various
9 combinations of performance, power consumption and features.
11 The STM32 Nucleo board integrates the ST-LINK/V2-1 debugger and programmer.
23 and 12 Kbytes of SRAM.
40 - Two push-button: USER and RESET
56 Connections and IOs
72 Programming and Debugging
77 Applications for the ``nucleo_c031c6`` board configuration can be built and
[all …]
|
| /Zephyr-latest/boards/renesas/da14695_dk_usb/doc/ |
| D | index.rst | 10 The development kit comes with an integrated debugger and an USB hub
11 to have both the on-chip USB and the J-Link connected via a single port.
63 Connections and IOs
66 The DA14695 Development Kit USB has one LED and one push button which can be used
67 by applications. The UART is connected to on-board serial converter and accessible
77 Programming and Debugging
81 built, flashed, and debugged in the usual way. See
82 :ref:`build_an_application` and :ref:`application_run` for more details on
83 building and running.
90 by using dedicated `eZFlashCLI`_ tool that takes care of writing header and can
[all …]
|
| /Zephyr-latest/doc/kernel/services/ |
| D | index.rst | 9 including device drivers, networking stack, and application-specific code,
15 requirements (such as a set of interrupt handlers and a single background task).
17 simple LED wearable, and store inventory tags.
20 devices (like Wi-Fi and Bluetooth Low Energy), and complex multi-threading,
22 include: fitness wearables, smart watches, and IoT wireless gateways.
24 Scheduling, Interrupts, and Synchronization
27 These pages cover basic kernel services related to thread scheduling and
52 threads and ISRs.
70 [2] Objects added with k_fifo_alloc_put() and k_lifo_alloc_put()
79 [5] ISRS can send and/or receive only when passing K_NO_WAIT as the
|
| /Zephyr-latest/samples/sensor/fdc2x1x/ |
| D | README.rst | 5 Get capacitance and frequency data from a FDC2X1X sensor (polling & trigger).
10 This sample application periodically reads frequency and capacitance data from the
12 to read the 12-Bit and 28-Bit, as well as the 2-Channel and 4-Channel versions
18 detection and gesture recognition to remote liquid level sensing. The sensor in
19 a capacitive sensing system is any metal or conductor, allowing for low cost and
30 Connect supply **VDD** and **GND**. The supply voltage can be in
35 Connect Interface: **SDA**, **SCL** and optionally connect **INTB** to a
42 Building and Running
45 This sample outputs sensor data to the console and can be read by any serial
101 FDC2X1X Datasheet and Product Info:
|
| /Zephyr-latest/boards/renesas/fpb_ra4e1/doc/ |
| D | index.rst | 7 with 512 KB code flash memory, 8 KB of data flash memory, and 128 KB of SRAM. RA4E1 MCUs
9 USB 2.0 Full-Speed, Quad SPI, and advanced analog.
23 RA MCU oscillator and sub-clock oscillator crystals, providing precision 24.000 MHz (not fitted)
24 and 32,768 Hz reference clocks are also available
26 **System Control and Ecosystem Access**
35 - User LEDs and buttons
39 - Debug/power LED (yellow) indicating power and the debug connection
63 Programming and Debugging
67 built, flashed, and debugged in the usual way. See
68 :ref:`build_an_application` and :ref:`application_run` for more details on
[all …]
|
| /Zephyr-latest/boards/renesas/fpb_ra6e1/doc/ |
| D | index.rst | 8 feature and connectivity integration including Ethernet, and unprecedented performance
19 the RA MCU. RA MCU oscillator and sub-clock oscillator crystals, providing
20 precision 24.000 MHz (not fitted) and 32,768 Hz reference clocks are also available
22 **System Control and Ecosystem Access**
31 - User LEDs and buttons
35 - Debug/power LED (yellow) indicating power and the debug connection
64 Programming and Debugging
68 built, flashed, and debugged in the usual way. See
69 :ref:`build_an_application` and :ref:`application_run` for more details on
70 building and running.
[all …]
|
| /Zephyr-latest/cmake/sca/eclair/ECL/ |
| D | toolchain.ecl | 1 # get the toolchain compiler and version from the environment
16 …__asm__: see \"6.48 Alternate Keywords\", and \"6.47 How to Use Inline Assembly Language in C Code…
20 __volatile__: see \"6.48 Alternate Keywords\" and \"6.47.2.1 Volatile\";
21 …__alignof: see \"6.48 Alternate Keywords\" and \"6.44 Determining the Alignment of Functions, Typ…
23 …__alignof__: see \"6.48 Alternate Keywords\" and \"6.44 Determining the Alignment of Functions, T…
28 …\"-Wc99-c11-compat\" and \"-Wc99-c2x-compat\" in \"3.8 Options to Request or Suppress Warnings\". …
36 -doc="See Chapter \"6.1 Statements and Declarations in Expressions\" of "GCC_MANUAL"."
38 -doc="See Chapter \"6.24 Arithmetic on void- and Function-Pointers\" of "GCC_MANUAL"."
72 -doc_begin="The maximum size of an object is defined in the MAX_SIZE macro, and for a 32 bit archit…
73 …The maximum size for an array is defined in the PTRDIFF_MAX and in a 32 bit architecture is 2^30-1…
[all …]
|
| /Zephyr-latest/tests/kernel/context/ |
| D | README.txt | 1 Title: Context and IRQ APIs
5 This test verifies that the kernel CPU and context APIs operate as expected.
44 - Continuation irq_lock: unlock interrupts, loop and verify the tick
52 - Use these routines to disable and enable timer interrupts so that they can
53 be tested in the same way as irq_lock() and irq_unlock().
57 Building and Running Project:
59 This project outputs to the console. It can be built and executed
75 # and restore pre-defined configuration info
81 tc_start() - Test kernel CPU and thread routines
84 Testing interrupt locking and unlocking
[all …]
|
| /Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/ |
| D | README.rst | 12 ivshmem-server needs to be available and running. The server is available in
29 #. Run ivshmem-server. For the ivshmem-server, both number of vectors and
31 For Zephyr, the number of vectors and shared memory size of ivshmem are
32 decided at compile-time and run-time, respectively. For Arm64 we use
41 #. Appropriately set ownership of ``/dev/shm/ivshmem`` and
51 Building and Running
55 and create them, these folders will receive the output of Zephyr west commands:
68 to test this sample, so append the option ``-d path/to/instance_1`` and
92 go to the other terminal window and check with ``ivshmem`` command:
100 IVshmem up and running:
[all …]
|
| /Zephyr-latest/tests/kernel/timer/timer_behavior/ |
| D | README | 1 # Test a timer implementations variance and long term drift
3 Records and calculates statistical values against a timer validating that.
5 1. Timer variance and standard deviation is below defined acceptable values.
8 Timers are meant to be precise and accurate. This test validates an implementation is both.
43 'total_time': Total time, between first and last period.
45 and an integer value of how many data values are collected for the statistics.
48 to account for expected drift in the test and between the DUT and the external
59 have parameters "tool", with the name of a loadable Python module and
67 the board under test and one at the external tool (Zephyr implementation of
68 the timer also plays a role, and it's the real target of the test, but it
[all …]
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | ec_host_cmd.rst | 22 The backend is a layer between a peripheral driver and the general handler. It is responsible for
23 sending and receiving commands via chosen peripheral.
26 is valid and the user has provided a handler for a received command id, the command handler is
33 host. SHI does not have API itself, thus the backend and peripheral driver layers are combined into
41 sends/receives specific number of bytes) and need to constant sending status byte (the SPI module
42 is enabled and disabled per transaction). It forces implementing the SPI driver within a backend,
67 The STM32 SPI host command backend driver supports the :dtcompatible:`st,stm32h7-spi` and
69 corresponding compatible string. For example, to enable FIFO support and support for the STM32H7
79 The chip that runs Zephyr is a SPI slave and the ``cs-gpios`` property is used to point our CS pin.
82 The supported backend and peripheral drivers:
[all …]
|
1...<<11121314151617181920>>...155
