Searched refs:and (Results 651 – 675 of 3855) sorted by relevance
1...<<21222324252627282930>>...155
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.4.rst | 12 * Input subsystem: handles input events from various types of input devices and
17 * USB device controller API (UDC API) and nRF USBD controller driver.
27 * Various improvements to the testing framework and twister:
30 GoogleTest and Robot Framework.
31 - Transitioning to new Ztest API was completed and legacy Ztest was deprecated.
58 :kconfig:option:`CONFIG_FLASH_MAP` and :kconfig:option:`CONFIG_STREAM_FLASH`,
142 rather than a copy, and passed back to the handler. This enables the handler
144 is embedded in a larger struct and requires that the trigger is not allocated
154 options from ``CONFIG_KSCAN_FT5336``, ``CONFIG_KSCAN_FT5336_PERIOD`` and
156 :kconfig:option:`CONFIG_INPUT_FT5336_PERIOD` and
[all …]
|
| D | release-notes-1.7.rst | 8 kernel release, simplifying the overall Zephyr architecture and programming
10 nano- and micro-kernel APIs found in the 1.5.0 release and earlier.
13 maintaining the legacy functionality, adding additional capabilities, and allowing
16 We have introduced support for the RISC V and Xtensa architectures and now
20 device tree support includes flash/sram base address and UART devices. Board
21 support includes NXP Kinetis based SoCs, ARM Beetle, TI CC3200 LaunchXL, and
22 STML32L476 based SoCs. Plan is to add support for other architectures and
35 * Remove usage of micro/nano kernel terminology from kernel code and introduced
53 * Added ST Nucleo-F334R8, Nucleo-L476G, STM3210C-EVAL, and STM32373C-EVAL boards
54 * Added Panther and tinyTILE boards, based on Quark SE C1000 and Intel Curie
[all …]
|
| /Zephyr-latest/samples/bluetooth/peripheral/ |
| D | README.rst | 5 …Implement basic Bluetooth LE Peripheral role functionality (advertising and exposing GATT services…
10 Application demonstrating the Bluetooth LE Peripheral role. It has several well-known and
20 Building and Running
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | smp_protocol.rst | 7 MCUmgr to pass requests to devices and receive responses from them.
20 Each frame consists of a header and data. The ``Data Length`` field in the
24 one byte long, and takes the following form:
46 both the "Little-endian" and "Big-endian" frames but in reality the
51 Data is optional and is not present when ``Data Length`` is zero.
54 A description of the various fields and their meaning:
62 | ``Res`` | This is reserved, not-used field and must be |
68 | | and returned in the map, otherwise left as 0b00 |
69 | | to use the legacy SMP protocol. Versions 0b10 and |
70 | | 0b11 are reserved for future use and should not |
[all …]
|
| /Zephyr-latest/boards/adi/max32672fthr/doc/ |
| D | index.rst | 7 battery and power management. The form factor is a small, 0.9in by 2.6in, dual row header footprint
9 an OLED display, a RGB indicator LED, and a user pushbutton. The MAX32672FTHR provides
10 a power-optimized flexible platform for quick proof-ofconcepts and early software development
35 - Resource Protection Unit (RPU) and MemoryProtection Unit (MPU)
42 - Internal Low-Power 7.3728MHz and Ultra-Low-Power 80kHz Oscillators
65 - Security and Integrity
71 - Benefits and Features of MAX32672FTHR:
74 - On-Board DAPLink Debug and Programming Interface for Arm Cortex-M4
95 | CLOCK | on-chip | clock and reset control |
121 Connections and IOs
[all …]
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 3 Intel ADSP cAVS and ACE
6 Intel's Audio and Digital Signal Processing (ADSP) hardware offerings
7 include the Converged Audio Voice Speech (cAVS) series and its successor,
8 the Audio and Context Engine (ACE). These Xtensa-based ADSPs can be integrated
26 Xtensa OS (XTOS) and run on a variety of Intel and non-Intel platforms.
31 However, the instructions are generic and will work on other boards unless
42 host running on the board's main CPU. It is possible (and recommended) for users
43 to build the binary locally on their development machine and flash remotely,
45 the binary sent over the network by West and flashes it. You should install a
50 Note that if you plan to use SOF on your board, you will need to build and
[all …]
|
| /Zephyr-latest/doc/develop/ |
| D | beyond-GSG.rst | 9 issues and alternatives.
13 Python and pip
16 Python 3 and its package manager, pip\ [#pip]_, are used extensively by Zephyr
17 to install and run scripts required to compile and run Zephyr
18 applications, set up and maintain the Zephyr development environment,
19 and build project documentation.
30 and the system package manager, and is the default on Debian-based
62 Zephyr binaries are compiled and linked by a *toolchain* comprised of
63 a cross-compiler and related tools which are different from the compiler
64 and tools used for developing software that runs natively on your host
[all …]
|
| /Zephyr-latest/samples/sensor/apds9960/ |
| D | README.rst | 2 :name: APDS9960 RGB, ambient light, and gesture sensor
5 Get ambient light, RGB, and proximity/gesture data from an APDS9960 sensor.
11 ambient light, RGB, and proximity (or gesture) data. This sample checks the
14 Building and Running
|
| /Zephyr-latest/samples/bluetooth/periodic_sync_conn/ |
| D | README.rst | 5 Respond to periodic advertising and establish a connection.
14 subevent data. Once the connection is established, it will disconnect and wait
23 Building and Running
30 another board that will start periodic advertising and connect to this sample
|
| /Zephyr-latest/samples/bluetooth/peripheral_hids/ |
| D | README.rst | 15 code on the peripheral and requires that to be entered on the host during
16 pairing) and requires an authenticated link to access the GATT characteristics.
17 To disable authentication and just use encrypted channels instead, build the
26 Building and Running
|
| /Zephyr-latest/boards/infineon/cy8cproto_062_4343w/doc/ |
| D | index.rst | 7 platform that enables design and debug of PSOC 6 MCUs. It comes with a Murata
9 for touch buttons and slider, on-board debugger/programmer with KitProg3, microSD
10 card interface, 512-Mb Quad-SPI NOR flash, PDM-PCM microphone, and a thermistor.
13 the different components and features that come with this kit and use independently.
19 For more information about the PSOC 62 MCU SoC and CY8CPROTO-062-4343W board:
32 - Support of up to 2MB Flash and 1MB SRAM
35 application processor and a 100-MHz Arm Cortex-M0+ as the secondary
39 blocks, 7 programmable analog blocks, and 56 programmable digital blocks.
85 Programming and Debugging
88 … provide debugging, flash programming, and serial communication over USB. Flash and debug commands…
[all …]
|
| /Zephyr-latest/boards/espressif/esp8684_devkitm/doc/ |
| D | index.rst | 7 module with 1 MB/2 MB/4 MB SPI flash. This board integrates complete Wi-Fi and Bluetooth LE functio…
14 makes the chip smaller and yet more powerful than ESP8266. ESP32-C2 is built around a RISC-V
15 32-bit, single-core processor, with 272 KB of SRAM (16 KB dedicated to cache) and 576 KB of ROM.
16 ESP32-C2 has been designed to target simple, high-volume, and low-data-rate IoT applications,
17 such as smart plugs and smart light bulbs. ESP32-C2 offers easy and robust wireless connectivity,
18 which makes it the go-to solution for developing simple, user-friendly and reliable
27 - A Bluetooth LE subsystem that supports features of Bluetooth 5 and Bluetooth Mesh
59 Espressif HAL requires WiFi and Bluetooth binary blobs in order work. Run the command
87 must be built (and flashed) at least once.
106 The sysbuild makes possible to build and flash all necessary images needed to
[all …]
|
| /Zephyr-latest/boards/nxp/frdm_mcxa156/doc/ |
| D | index.rst | 6 FRDM-MCXA156 are compact and scalable development boards for rapid prototyping of
9 memory and an on-board MCU-Link debugger. Additional tools like our Expansion
10 Board Hub for add-on boards and the Application Code Hub for software examples
24 For more information about the MCX-A156 SoC and FRDM-MCXA156 board, see:
95 Connections and IOs
98 The MCX-A156 SoC has 5 gpio controllers and has pinmux registers which
121 Programming and Debugging
124 Build and flash applications as usual (see :ref:`build_an_application` and
130 A debug probe is used for both flashing and debugging the board. This board is
136 Linkserver is the default runner for this board, and supports the factory
[all …]
|
| /Zephyr-latest/boards/nxp/frdm_mcxc242/doc/ |
| D | index.rst | 6 FRDM-MCXC242 is a compact and scalable development board for rapid
9 interfaces and on-board MCU-Link debugger.
11 providing additional memory, communications and analog peripheral.
28 For more information about the MCXC242 SoC and FRDM-MCXC242 board, see
83 Connections and IOs
87 PORTB/GPIOB, PORTC/GPIOC, PORTD/GPIOD, and PORTE/GPIOE) for the FRDM-MCXC242 board.
129 Programming and Debugging
132 Build and flash applications as usual (see :ref:`build_an_application` and
138 A debug probe is used for both flashing and debugging the board. This board is
144 Linkserver is the default runner for this board, and supports the factory
[all …]
|
| /Zephyr-latest/boards/nxp/frdm_mcxc444/doc/ |
| D | index.rst | 6 FRDM-MCXC444 is a compact and scalable development board for rapid
9 interfaces and on-board MCU-Link debugger.
11 providing additional memory, communications and analog peripheral.
27 For more information about the MCXC444 SoC and FRDM-MCXC444 board, see
82 Connections and IOs
86 PORTB/GPIOB, PORTC/GPIOC, PORTD/GPIOD, and PORTE/GPIOE) for the FRDM-MCXC444 board.
124 Programming and Debugging
127 Build and flash applications as usual (see :ref:`build_an_application` and
133 A debug probe is used for both flashing and debugging the board. This board is
139 Linkserver is the default runner for this board, and supports the factory
[all …]
|
| /Zephyr-latest/boards/st/nucleo_g431rb/doc/ |
| D | index.rst | 7 with a wide range of connectivity support and configurations. Here are
19 - Two push-buttons: RESET and USER
28 - Ultra-low-power with FlexPowerControl (down to 28 nA Standby mode and 84
39 - RTC with HW calendar, alarms and calibration
42 …- 1x 32-bit timer and 2x 16-bit timers with up to four IC/OC/PWM or pulse counter and quadrature (…
43 … advanced motor control timers, with up to 8x PWM channels, dead time generation and emergency stop
44 - 1x 16-bit timer with 2x IC/OCs, one OCN/PWM, dead time generation and emergency stop
45 - 2x 16-bit timers with IC/OC/OCN/PWM, dead time generation and emergency stop
61 - 4x 12-bit DAC, low-power sample and hold
73 - USB 2.0 full-speed interface with LPM and BCD support
[all …]
|
| /Zephyr-latest/soc/espressif/esp32s3/ |
| D | Kconfig.mac | 14 Bluetooth and Ethernet) receive a universally administered MAC address. These are generated
15 sequentially by adding 0, 1, 2 and 3 (respectively) to the final octet of the base MAC address.
16 If the number of universal MAC addresses is two, only two interfaces (WiFi station and Bluetooth)
18 …and 1 (respectively) to the base MAC address. The remaining two interfaces (WiFi softap and Ethern…
19 receive local MAC addresses. These are derived from the universal WiFi station and Bluetooth MAC
|
| /Zephyr-latest/soc/intel/apollo_lake/doc/ |
| D | supported_features.txt | 4 In addition to the standard architecture devices (HPET, local and I/O APICs,
32 Typically, the master clock is 100MHz, and the firmware by default sets
34 results in the de-facto standard 1.8432MHz master clock and a max baud rate
35 of 115.2k. Higher baud rates are enabled by changing the PCP and telling
56 and ``clock-frequency`` (the resulting baud master clock). The meaning of
57 ``current-speed`` is unchanged, and as usual indicates the initial baud rate.
|
| /Zephyr-latest/boards/intel/adl/doc/ |
| D | index.rst | 12 the Processor Die and Alder Lake N Platform Controller Hub (ADL-N PCH) Die on
15 Proposed branding for Adler Lake N is Intel Processor (N100,N200) and
18 Alder Lake N Customer Reference Board (ADL-N CRB) and Alder Lake Reference
29 Connections and IOs
34 Programming and Debugging
65 .. _INTEL_ADL: https://edc.intel.com/content/www/us/en/design/products/platforms/processor-and-core…
|
| /Zephyr-latest/boards/kincony/kincony_kc868_a32/doc/ |
| D | index.rst | 19 - USB Type-B connector for programming and filling firmware
20 - RESET and DOWNLOAD buttons
29 Espressif HAL requires WiFi and Bluetooth binary blobs in order work. Run the command
43 Build and flash applications as usual (see :ref:`build_an_application` and
66 After the board has automatically reset and booted, you should see the following
|
| /Zephyr-latest/boards/nuvoton/npcx9m6f_evb/doc/ |
| D | index.rst | 14 - 256 KB RAM and 64 KB boot ROM
16 - UART0 and UART1
26 Connections and IOs
44 Programming and Debugging
47 This board comes with a Cortex ETM port which facilitates tracing and debugging
54 If the correct IDC headers are installed, this board supports both J-TAG and
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | l2cap.rst | 3 Logical Link Control and Adaptation Protocol (L2CAP)
8 support segmentation and reassembly transparently, they also support credit
25 it may block if no credits are available, and resuming as soon as more credits
30 listen to, the required security level ``sec_level``, and the callback
31 ``accept`` which is called to authorize incoming connection requests and
35 API and can be disconnected with the :c:func:`bt_l2cap_chan_disconnect` API.
|
| /Zephyr-latest/boards/nuvoton/npcx7m6fb_evb/doc/ |
| D | index.rst | 14 - 256 KB RAM and 64 KB boot ROM
16 - UART0 and UART1
26 Connections and IOs
44 Programming and Debugging
47 This board comes with a Cortex ETM port which facilitates tracing and debugging
54 If the correct IDC headers are installed, this board supports both J-TAG and
|
| /Zephyr-latest/samples/net/ptp/ |
| D | README.rst | 5 Enable PTP support and monitor messages and events via logging.
21 Building and Running
28 boards that have an Ethernet port and which has support for collecting
29 timestamps for sent and received Ethernet frames.
52 Compile the ``ptp4l`` daemon and start it like this:
|
| /Zephyr-latest/samples/drivers/led/lp50xx/ |
| D | README.rst | 13 and printed in the log messages. Next, from an infinite loop, a test pattern
15 :c:func:`led_write_channels` syscall) and then to each LED one by one (using the
16 :c:func:`led_set_brightness` and :c:func:`led_set_color` syscalls).
21 For all the LEDs first (using channel API) and then for each LED one by one:
31 Building and Running
34 This sample can be built and executed on boards with an I2C LP5009, LP5012,
|
1...<<21222324252627282930>>...155
