Searched refs:and (Results 301 – 325 of 3855) sorted by relevance
1...<<11121314151617181920>>...155
/Zephyr-latest/samples/net/sockets/packet/ |
D | README.rst | 12 received, and sends a dummy packet every 5 seconds. 16 Building and Running 19 When the application is run, it opens a packet socket and prints 22 sent and received packets. 26 This sample can be built and executed on QEMU or native_sim board as
|
/Zephyr-latest/drivers/display/ |
D | Kconfig.nrf_led_matrix | 11 Enable driver for a LED matrix with rows and columns driven by 14 Assignment of GPIOs to rows and columns and the mapping of those 17 The driver uses one TIMER instance and, depending on what is set in 18 devicetree, one PWM instance or one or more GPIOTE and PPI channels
|
/Zephyr-latest/tests/drivers/regulator/voltage/boards/ |
D | rpi_pico.overlay | 8 * But the rpi_pico board and most boards that use the rp2040, VREG_OUT and 9 * DVDD are directly connected, and no available exposed trace on the board. 12 * thermal via connect to VREG_OUT. (Around between C and E of CE mark of silk print.) 13 * Scraping the resist on there and soldering wire to make it able to measure by ADC.
|
/Zephyr-latest/samples/sensor/lps22hh/ |
D | README.rst | 2 :name: LPSS22HH Temperature and Pressure Sensor 5 Get pressure and temperature data from an LPS22HH sensor (polling & trigger mode). 10 sensor and displays it on the console. 21 - LPS22HH: https://www.st.com/en/mems-and-sensors/lps22hh.html 23 Building and Running
|
/Zephyr-latest/boards/silabs/starter_kits/slstk3701a/doc/ |
D | index.rst | 16 - 2 user buttons, 2 LEDs and a touch slider 17 - Relative humidity, magnetic Hall Effect and inductive-capacitive metal sensor 25 For more information about the EFM32GG11 SoC and SLSTK3701A board: 39 Connections and IOs 46 means pin number 1 on PORTE, as used in the board's datasheets and manuals. 89 The EFM32GG11 SoC has six USARTs, two UARTs and two Low Energy UARTs (LEUART). 90 USART4 is connected to the board controller and is used for the console. 92 Programming and Debugging 102 The SLSTK3701A includes an `J-Link`_ serial and debug adaptor built into the 105 - A USB connection to the host computer, which exposes a mass storage device and a [all …]
|
/Zephyr-latest/boards/sparkfun/thing_plus/doc/ |
D | index.rst | 16 for bringing your LTE-M and NB-IoT applications to life. The sparkfun_thing_plus_nrf9160 42 Connections and IOs 45 The nRF9160 Thing Plus has everything you know and love about 53 Push buttons and Switches 62 Contains a USB/UART connection for both debugging and loading new 78 Programming and Debugging 101 and configure all the necessary software. Further information can be 102 found in :ref:`nordic_segger_flashing`. Then build and flash 103 applications as usual (see :ref:`build_an_application` and 117 Then build and flash the application in the usual way. [all …]
|
/Zephyr-latest/boards/st/stm32l1_disco/doc/ |
D | index.rst | 7 an integrated ST-LINK/V2 debugger and programmer. The boards have a 8 24-segment LCD and a touch slider, along with two user LEDs and a user button. 10 It also comes with a comprehensive STM32 software HAL library and various 20 stm32l1_disco configuration enables support for STM32LDISCOVERY board and 32 ST-LINK/V2 (with SWD connector for programming and debugging) 34 - External application power supply: 3 V and 5 V 41 - Two push buttons (user and reset) 43 and easy probing 52 Connections and IOs 84 Programming and Debugging [all …]
|
/Zephyr-latest/boards/others/stm32_min_dev/doc/ |
D | index.rst | 6 The STM32 Minimum Development Board, is a popular and inexpensive 18 and circuits using a breadboard, for example. 23 This port is a starting point for your own customizations and not a complete 28 external connectors and placement of components. Many vendors use port PC13/PB12 32 More information on hooking up peripherals and lengthy how to articles can be 66 and B1 (Boot 1). The pins B0 and B1 are present in between logic 0 and 1 lines. The 67 silk screen on the PCB reads BX- or BX+ to indicate 0 and 1 logic lines for B0 and B1 86 Connections and IOs 120 Programming and Debugging 124 built and flashed in the usual way (see :ref:`build_an_application` and
|
/Zephyr-latest/boards/fanke/fk750m1_vbt6/doc/ |
D | index.rst | 9 applications, leveraging its robust capabilities and support for sophisticated display 10 and image processing technologies. 14 Its wide range of hardware features, including advanced display and image processing capabilities, 15 allowing for comprehensive evaluation and testing of peripherals and functionalities. 26 … TCM RAM (64 Kbytes ITCM RAM + 128 Kbytes DTCM RAM), 864 Kbytes user SRAM, and 4 Kbytes SRAM in Ba… 32 - 1 reset button, and 1 BOOT button 35 - USB OTG Full Speed and High Speed(1) 39 - SWD and serial port accessibility through a pin header 80 Programming and Debugging 83 Applications for the ``fk750m1_vbt6`` board target can be built and flashed in the usual [all …]
|
/Zephyr-latest/boards/adafruit/feather_m0_lora/doc/ |
D | index.rst | 7 boards with an onboard battery connector and charger for 3.7 V lithium 8 polymer batteries, charging status indicator and user LEDs, native USB 9 connector, 20 I/O pins, and a LoRa radio module from Semtech. 16 - 256 KiB flash memory and 32 KiB of RAM 17 - Battery connector and charger for 3.7 V lithium polymer batteries 29 Connections and IOs 33 information about the board including `pinouts`_ and the `schematic`_. 45 with LoRa, SERCOM0 is the Zephyr console and is available on pins 0 46 (RX) and 1 (TX). 52 with LoRa, SERCOM3 is available on pin 20 (SDA) and pin 21 (SCL). [all …]
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 6 As an open-source project, we welcome and encourage the community to submit 8 standards and methods for submitting changes help reduce the chaos that can result 12 and enhancement requests, and submit patches to the project so your patch will 22 configure, install, and use it as explained in the `Zephyr Project website`_ 23 and how to set up your development environment as introduced in the Zephyr 26 You should be familiar with common developer tools such as Git and CMake, and 30 on https://github.com and have Git tools available on your development system. 34 (Linux, macOS, and Windows) but some of the tools used in the sections below 35 are only available on Linux and macOS. On Windows, instead of running these 58 contribution and allowing you to use the software however you would like [all …]
|
/Zephyr-latest/boards/cypress/cy8ckit_062_wifi_bt/doc/ |
D | index.rst | 7 platform that enables design and debug of the PSOC 62 MCU and the Murata 12 processor and a 100-MHz Arm Cortex-M0+ that supports low-power operations, 15 a PDM-PCM digital microphone interface, and industry-leading capacitive-sensing 20 The Cortex-M0+ is a primary core on the board's SoC. It starts first and 35 13. KitProg2 status LEDs (LED1, LED2, and LED3) 37 15. PSOC 6 I/O header (J18, J19 and J20) 39 17. PSOC 6 debug and trace header (J12) 40 18. Arduino Uno R3 compatible PSOC 6 I/O header (J2, J3 and J4) 41 19. PSOC 6 program and debug header (J11) 43 21. CapSense slider and buttons [all …]
|
/Zephyr-latest/boards/adi/max32666evkit/doc/ |
D | index.rst | 5 The MAX32666EVKIT provides a platform for evaluating the capabilities of the MAX32665 and MAX32666 6 high-efficiency Arm® microcontrollers and audio DSP for wearable and hearable device applications. 15 - High-Efficiency Microcontroller and Audio DSP for Wearable and Hearable Devices 22 - Optional Error Correction Code (ECC-SEC-DED)for Cache, SRAM, and Internal Flash 26 - 1Mbps and 2Mbps Data Throughput 27 - Long Range (125kbps and 500kbps) 59 - Trust Protection Unit (TPU) with MAA SupportsFast ECDSA and Modular Arithmetic 64 - Benefits and Features of MAX32666EVKIT: 70 - Stereo Audio Codec with Line-In and Line-Out 3.5mm Jacks 82 - On-Board 1.8V and 3.3V Regulators [all …]
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.6.rst | 7 release introduces the unified Kernel replacing the separate nano- and 8 micro-kernels and simplifying the overall Zephyr architecture and programming 10 Support for the ARM Cortex-M0/M0+ family was added and board support for 13 infrastructure, and testing. 17 * Introduced the Unified Kernel; the nano and micro kernel were removed. 19 * Legacy tests and samples were moved to tests/legacy and samples/legacy. 20 * Unified kernel documentation was added and legacy nanokernel/microkernel 23 * Added support for USB mass storage and access to the filesystem. 35 * SLIST: Added sys_slist_get() to fetch and remove the head, also Added 36 append_list and merge_slist. [all …]
|
/Zephyr-latest/boards/qemu/leon3/doc/ |
D | index.rst | 8 Programming and Debugging 11 Applications for the ``qemu_leon3`` board configuration can be built and run in 12 the usual way for emulated boards (see :ref:`build_an_application` and 18 While this board is emulated and you can't "flash" it, you can use this 19 configuration to run basic Zephyr applications and kernel tests in the QEMU 29 QEMU, and display the following console output:
|
/Zephyr-latest/boards/qemu/riscv32/doc/ |
D | index.rst | 8 Programming and Debugging 11 Applications for the ``qemu_riscv32`` board configuration can be built and run in 12 the usual way for emulated boards (see :ref:`build_an_application` and 18 While this board is emulated and you can't "flash" it, you can use this 19 configuration to run basic Zephyr applications and kernel tests in the QEMU 29 QEMU, and display the following console output:
|
/Zephyr-latest/boards/mikroe/stm32_m4_clicker/doc/ |
D | index.rst | 8 1 MB of Flash memory and 192 KB of SRAM. 14 buttons, and a reset button. It features a mikroBUS socket for interfacing 23 Programming and debugging 29 You can build and flash an application in the usual way (See 30 :ref:`build_an_application` and 33 Here is an example for building and flashing the :zephyr:code-sample:`blinky` application.
|
/Zephyr-latest/samples/sensor/bmi270/ |
D | README.rst | 5 Configure and read accelerometer and gyroscope data from a BMI270 sensor. 10 This sample application configures the accelerometer and gyroscope to 22 Connect Supply: **VDD**, **VDDIO**, **GND** and Interface: **SDA**, **SCL**. 24 Depending on the baseboard used, the **SDA** and **SCL** lines require Pull-Up 27 Building and Running
|
/Zephyr-latest/samples/bluetooth/periodic_sync_rsp/ |
D | README.rst | 16 Which subevent to listen to and in which response slot to respond is 19 the assigned subevent and response slot. 21 Flash this sample to multiple devices and they will be given different 22 subevents and response slots, to that they can communicate with the 31 Building and Running 39 sample and transfer the synchronization info.
|
/Zephyr-latest/drivers/sensor/ti/ti_hdc20xx/ |
D | Kconfig | 1 # TI_HDC20XX temperature and humidity sensor configuration options 7 bool "Texas Instruments HDC20XX Temperature and Humidity Sensor" 13 Enable driver for TI HDC20XX temperature and humidity sensors
|
/Zephyr-latest/boards/silabs/dev_kits/xg24_ek2703a/doc/ |
D | index.rst | 19 - Crystals for LFXO (32.768 kHz) and HFXO (39 MHz). 21 For more information about the EFR32MG24 SoC and BRD2703A board, refer to these 34 Connections and IOs 38 means Pin number 2 on PORTA, as used in the board's datasheets and manuals. 68 The EFR32MG24 SoC has one USART and two EUSARTs. 69 USART0 is connected to the board controller and is used for the console. 71 Programming and Debugging 82 Build the Zephyr kernel and application: 89 Connect the xg24_ek2703a to your host computer using the USB port and you 99 Reset the board and you'll see the following message on the corresponding serial port [all …]
|
/Zephyr-latest/boards/silabs/dev_kits/sltb009a/doc/ |
D | index.rst | 8 1024kB flash, and 192kB RAM. 16 - 2 user buttons and 2 LEDs 19 For more information about the WGM160P and SLTB009A board: 31 Connections and IOs 38 means pin number 1 on PORTE, as used in the board's datasheets and manuals. 73 The EFM32GG12 SoC has five USARTs, two UARTs and two Low Energy UARTs (LEUART). 74 USART0 is connected to the board controller and is used for the console. 76 Programming and Debugging 86 The SLTB009A includes an `J-Link`_ serial and debug adaptor built into the 97 Here is an example to build and flash the :zephyr:code-sample:`hello_world` application. [all …]
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | ieee802154.rst | 21 You need to create a free IEEE account and can then downloading it. 26 were accepted into the standard, namely IEEE 802.15.4g (SUN FSK) and IEEE 27 802.15.4e (TSCH) which are of relevance to industrial IoT and automation. For 32 to IEEE 802.15.4-2020 section, table and figure numbering - unless otherwise 35 Zephyr supports both, native IEEE 802.15.4 and Thread, with 6LoWPAN. Zephyr's 46 Gives an introduction and overview over the whole IEEE 802.15.4 subsystem and 47 all of its APIs, configuration and user interfaces for all audiences. 60 typical shell, socket, Kconfig and devicetree APIs that can be accessed through 84 network layers (L3+), its socket and network context abstractions. This API is 96 The OpenThread API is part of the :ref:`thread_protocol_interface` subsystem and
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | dfu_srv.rst | 19 :c:macro:`BT_MESH_DFU_SRV_INIT`, and must be populated before the Bluetooth Mesh subsystem is 20 started. Each firmware image in the image list must be independently updatable, and should have its 23 For instance, a device with an upgradable bootloader, an application and a peripheral chip with 31 the binary image. The interaction between the Firmware Update Server, BLOB Transfer Server and 47 The result of the transfer check is a pass/fail status return and the expected 49 Distributor, and should indicate what effect the firmware update will have on the mesh state of the 54 Composition Data and Models Metadata 60 When the transfer will cause the Composition Data to change, and the 62 will be represented by Composition Data Pages 128, 129, and 130. The Models Metadata of the new 63 firmware image will be represented by Models Metadata Page 128. Composition Data Pages 0, 1 and 2, [all …]
|
D | blob.rst | 7 Transfer Model specification version 1.0 and provide functionality for sending large binary objects 13 bytes). The BLOB transfer protocol has built-in recovery procedures for packet losses, and sets up 17 BLOB transfers are constrained by the transfer speed and reliability of the underlying mesh network. 19 BLOB to be transferred in 10-15 minutes. However, network conditions, transfer capabilities and 21 parameters of the transfer according to the application and network configuration, as well as 23 and reliability of the protocol. However, achieving transfer rates close to the ideal rate is 34 The BLOB Transfer Client is instantiated on the sender node, and the BLOB Transfer Server is 47 transfer through the mesh network. The BLOBs are continuous data objects, divided into blocks and 48 chunks to make the transfers reliable and easy to process. No limitations are put on the contents or 49 structure of the BLOB, and applications are free to define any encoding or compression they'd like [all …]
|
1...<<11121314151617181920>>...155