Searched refs:and (Results 201 – 225 of 3855) sorted by relevance
12345678910>>...155
| /Zephyr-latest/samples/sensor/lps22hb/ |
| D | README.rst | 2 :name: LPS22HB Temperature and Pressure Sensor
5 Get pressure and temperature data from an LPS22HB sensor (polling mode).
10 sensor and displays it on the console.
21 - LPS22HB: https://www.st.com/en/mems-and-sensors/lps22hb.html
23 Building and Running
|
| /Zephyr-latest/boards/raytac/mdbt53v_db_40/doc/ |
| D | index.rst | 14 * a full-featured Arm Cortex-M33F core with DSP instructions, FPU, and
35 * RADIO (Bluetooth Low Energy and 802.15.4)
62 - Interfaces: SPI, UART, I2C, I2S, PWM, ADC, and NFC
75 See `MDBT53V-DB-40 website`_ and `MDBT53V-DB-40 Specification`_
78 Connections and IOs
114 The IDAU is implemented with the System Protection Unit and is used to
115 define secure and non-secure memory maps. By default, all of the memory
116 space (Flash, SRAM, and peripheral address space) is defined to be secure
120 Programming and Debugging
129 to have Secure attribute set; the latter allows to build and run
[all …]
|
| /Zephyr-latest/boards/nordic/nrf52840dk/doc/ |
| D | index.rst | 10 Nordic Semiconductor nRF52840 ARM Cortex-M4F CPU and the following devices:
20 * RADIO (Bluetooth Low Energy and 802.15.4)
36 and the datasheet.
87 See `nRF52840 DK website`_ and `nRF52840 DK Hardware guide`_
90 Connections and IOs
110 Programming and Debugging
114 built, flashed, and debugged in the usual way. See
115 :ref:`build_an_application` and :ref:`application_run` for more details on
116 building and running.
122 and configure all the necessary software. Further information can be
[all …]
|
| /Zephyr-latest/boards/nordic/nrf52833dk/doc/ |
| D | index.rst | 10 support for the Nordic Semiconductor nRF52833 ARM Cortex-M4F CPU and
21 * RADIO (Bluetooth Low Energy and 802.15.4)
31 contains the processor's information and the datasheet.
83 See `nRF52833 DK website`_ and `nRF52833 DK Hardware guide`_
86 Connections and IOs
106 Programming and Debugging
110 flashed, and debugged in the usual way. See :ref:`build_an_application` and
111 :ref:`application_run` for more details on building and running.
117 and configure all the necessary software. Further information can be
118 found in :ref:`nordic_segger_flashing`. Then build and flash
[all …]
|
| /Zephyr-latest/doc/project/ |
| D | dev_env_and_tools.rst | 1 .. _dev-environment-and-tools:
3 Development Environment and Tools
12 been reviewed, passed a series of checks (CI), and are approved by maintainers.
18 and linked to any relevant :ref:`bug or feature tracking issues<bug_reporting>`
21 The Zephyr project uses GitHub for code reviews and Git tree management. When
35 or timezone. We have developers and contributors from across the globe. When
37 time to give developers and contributors the opportunity to review and comment
38 on changes. There are different categories of changes and we know that some
39 changes do require reviews by subject matter experts and owners of the subsystem
41 addressed with general reviews and do not need to be queued for a maintainer or
[all …]
|
| /Zephyr-latest/boards/adi/max32675evkit/doc/ |
| D | index.rst | 7 microcontroller designed for industrial and medical sensors. It contains an integrated, low-power
9 industrial sensors for configuration and diagnostics.
33 - Flexible Resolution and Sample Rates (24 Bits at 0.4ksps, 16 Bits at 4ksps)
45 - Robust Security and Reliability
48 - Secure Nonvolatile Key Storage and AES-128/192/256
53 - Benefits and Features of MAX32675EVKIT:
55 …condary Master with the Ability to Connect to Existing 4-20mA Current Loop and Communicate with HA…
62 - 10-Pin SWD and Connector
64 - On-Board 1.0V, 1.8V, and 3.3V LDO Regulators
66 - Two General-Purpose LEDs and Two General-Purpose Pushbutton Switches
[all …]
|
| /Zephyr-latest/boards/wch/linkw/doc/ |
| D | index.rst | 7 processor and the following devices:
13 The board is equipped with two LEDs and two Buttons.
21 32 MHz crystal or the internal 8 MHz oscillator and runs up to 144 MHz.
23 CAN, 2 USB Device, USB Host, OPA, ETH with PHY, several timers, and BLE 5.3.
46 Connections and IOs
61 Programming and Debugging
64 Applications for the ``linkw`` board target can be built and flashed
65 in the usual way (see :ref:`build_an_application` and :ref:`application_run`
81 up, build and flash applications as usual (see :ref:`build_an_application` and
106 You can build and flash the examples to make sure Zephyr is running
[all …]
|
| /Zephyr-latest/boards/ebyte/e73_tbb/doc/ |
| D | index.rst | 7 support for the Nordic Semiconductor nRF52832 ARM Cortex-M4F CPU and
27 contains the processor's information and the datasheet.
37 and solder NFC antenna using NFC_ANT connector.
44 See `E73-TBB website`_ and `Nordic Semiconductor Infocenter`_
47 Connections and IOs
135 Programming and Debugging
142 and configure all the necessary software.
144 to corresponding pins on your J-Link device, then build and flash the application in the usual way.
158 Testing the LEDs and buttons in the E73-TBB
161 There are 2 samples that allow you to test that the buttons (switches) and LEDs on
[all …]
|
| /Zephyr-latest/boards/tdk/robokit1/doc/ |
| D | index.rst | 6 The TDK RoboKit1 is a development board for use primarily with ROS2 and provides a large
10 It pairs a 300MHz Cortex-M7 ATSAME70Q21 with an array of TDK sensors and pin headers useful for rob…
19 - Micro-AB USB debug (Microchip EDBG) interface supporting CMSIS-DAP, Virtual COM Port and Data
37 Connections and IOs
51 The ATSAME70Q21 MCU has five UARTs and three USARTs. One of the UARTs is
52 configured for the console and is available as a Virtual COM Port via the USB2 connector.
54 Programming and Debugging
58 Both west flash and west debug commands should correctly work with both USB0 and USB1
59 connected and the board powered.
80 USB debug port (USB1), USB2 for a serial console, and remaining micro USB for
[all …]
|
| /Zephyr-latest/samples/bluetooth/tmap_central/ |
| D | README.rst | 2 :name: Telephone and Media Audio Profile (TMAP) Central
5 Implement the TMAP Call Gateway (CG) and Unicast Media Sender (UMS) roles.
10 Application demonstrating the TMAP central functionality. Implements the CG and UMS roles.
18 Building and Running
|
| /Zephyr-latest/samples/bluetooth/tmap_peripheral/ |
| D | README.rst | 2 :name: Telephone and Media Audio Profile (TMAP) Peripheral
5 Implement the TMAP Call Terminal (CT) and Unicast Media Receiver (UMR) roles.
10 Application demonstrating the TMAP peripheral functionality. Implements the CT and UMR roles.
18 Building and Running
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 6 The Bluetooth Host implements all the higher-level protocols and
7 profiles, and most importantly, provides a high-level API for
20 host, and vice-versa.
41 connection-oriented roles central implicitly enables observer role, and
43 when creating an application is to decide which roles are needed and go
45 least the observer and broadcaster roles, and possibly also the
53 devices. This means that they perform connectable advertising and expose
65 role, but it is still a plausible one and equally well supported in
67 role device will scan for available peripheral device and choose one to
69 client, first performing discovery of available services and then
[all …]
|
| /Zephyr-latest/boards/silabs/starter_kits/efm32wg_stk3800/doc/ |
| D | index.rst | 17 - 2 user buttons, 2 LEDs and a touch slider
18 - Ambient Light Sensor and Inductive-capacitive metal sensor
21 For more information about the EFM32WG SoC and EFM32WG-STK3800 board:
35 Connections and IOs
39 currently enabled (PORTB, PORTE and PORTF) for the EFM32WG-STK3800 board.
42 means Pin number 2 on PORTE, as used in the board's datasheets and manuals.
72 The EFM32WG SoC has three USARTs, two UARTs and two Low Energy UARTs (LEUART).
73 UART0 is connected to the board controller and is used for the console.
75 Programming and Debugging
85 The EFM32WG-STK3800 includes an `J-Link`_ serial and debug adaptor built into the
[all …]
|
| /Zephyr-latest/boards/silabs/starter_kits/slstk3400a/doc/ |
| D | index.rst | 14 - Real-time energy and power profiling
15 - ARM Cortex M0+ with 64 kB Flash and 8 kB RAM
17 - 2 user buttons, 2 user LEDs and 2 touch buttons
38 Connections and IOs
42 currently enabled (PORTB, PORTE and PORTF) for the SLSTK3400A board.
45 means Pin number 4 on PORTF, as used in the board's datasheets and manuals.
75 The EFM32HG SoC has two USARTs, two UARTs and two Low Energy UARTs (LEUART).
76 USART1 is connected to the board controller and is used for the console.
78 Programming and Debugging
88 The SLSTK3400 includes an `J-Link`_ serial and debug adaptor built into the
[all …]
|
| /Zephyr-latest/boards/atmel/sam/sam4l_ek/doc/ |
| D | index.rst | 9 user the ability to balance between the lowest possible power consumption and
10 the feature set selected for the application. The WAIT and RETENTION modes
11 provide full logic and RAM retention, associated with fast wake-up capability
12 (<1.5μs) and a very low consumption of, respectively, 3 μA and 1.5 μA. In
14 peripherals and RAM are powered off consuming less than 0.9μA with external
42 - 1 user touch button and One user pushbutton
54 Connections and IOs
70 the embedded debug unit and can works as a console. The USART0 is shared
71 between all others headers and RS-485 port.
73 Programming and Debugging
[all …]
|
| /Zephyr-latest/doc/services/resource_management/ |
| D | index.rst | 8 clocks, other peripherals, and binary device power management. The
28 and binary device power management.
32 * The stable states are off, on, and error. The service always begins
35 * The core operations are request (add a dependency) and release (remove
37 state) and cancel (to reclaim client data from an in-progress
45 transition from off to on, from on to off, and optionally from an
47 and interrupt context.
48 * The request and reset operations are asynchronous using
53 immediately turned on again (where context allows) and waiting clients
57 responsible for recording whether their requests were accepted, and for
[all …]
|
| /Zephyr-latest/boards/renesas/fpb_ra6e2/doc/ |
| D | index.rst | 8 seamlessly evaluate the features of the RA6E2 MCU group and develop
10 and e2 studio IDE. The users can use rich on-board features along with
21 - Multiple clock sources - RA6E2 MCU oscillator and sub-clock oscillator crystals,
22 providing precision 24.000 MHz and 32,768 Hz reference clock.
25 **System Control and Ecosystem Access**
27 - USB Full Speed Host and Device (micro-AB connector)
35 - User LEDs and buttons
39 - Debug/power LED (yellow) indicating power and the debug connection
45 - Two Digilent PmodTM (SPI, UART and I3C) connectors
68 Programming and Debugging
[all …]
|
| /Zephyr-latest/boards/ezurio/bl654_dvk/doc/ |
| D | bl654_dvk.rst | 24 * RADIO (Bluetooth Low Energy and 802.15.4)
52 Connections and IOs
72 Programming and Debugging
76 and debugged in the usual way. See :ref:`build_an_application` and
77 :ref:`application_run` for more details on building and running.
83 and configure all the necessary software. Further information can be
84 found in :ref:`nordic_segger_flashing`. Then build and flash
85 applications as usual (see :ref:`build_an_application` and
101 Then build and flash the application in the usual way.
124 Testing the LEDs and buttons on the BL654 DVK
[all …]
|
| /Zephyr-latest/boards/circuitdojo/feather/doc/ |
| D | index.rst | 16 for bringing your LTE-M and NB-IoT applications to life. The circuitdojo_feather_nrf9160
46 Connections and IOs
49 The nRF9160 Feather has everything you know and love about
57 Push buttons and Switches
66 Contains a USB/UART connection for both debugging and loading new
82 Programming and Debugging
100 Trusted Firmware-M (TF-M) and building the ``ns`` target is not supported for this board.
109 and configure all the necessary software. Further information can be
110 found in :ref:`nordic_segger_flashing`. Then build and flash
111 applications as usual (see :ref:`build_an_application` and
[all …]
|
| /Zephyr-latest/samples/modules/tflite-micro/hello_world/ |
| D | README.rst | 9 This sample TensorFlow application replicates a sine wave and
13 sine function and generates x values to print alongside the
18 a model and converting it for use with TensorFlow Lite Micro for
22 reference kernels and one with CMSIS-NN optimized kernels.
25 This README and sample have been modified from
31 Building and Running
37 Add the tflite-micro module to your West manifest and pull it:
44 The reference kernel application can be built and executed on QEMU as follows:
55 The CMSIS-NN kernel application can be built and executed on any Arm(R) Cortex(R)-M core based plat…
58 [MPS3 FPGA prototyping board](https://developer.arm.com/tools-and-software/development-boards/fpga-…
[all …]
|
| /Zephyr-latest/drivers/sensor/renesas/hs300x/ |
| D | Kconfig | 1 # Renesas HS300x temperature and humidity sensor configuration options
7 bool "HS300x Temperature and Humidity Sensor"
12 Enable driver for HS300x temperature and humidity sensors.
|
| /Zephyr-latest/drivers/sensor/sensirion/sht4x/ |
| D | Kconfig | 1 # SHT4x temperature and humidity sensor configuration options
7 bool "SHT4x Temperature and Humidity Sensor"
13 Enable driver for SHT4x temperature and humidity sensors.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | sar_cfg_cli.rst | 11 version 1.1, and it supports the configuration of the lower transport layer behavior of a node that
15 (SAR Transmitter and SAR Receiver) using SAR Configuration messages.
17 The SAR Transmitter procedure is used to determine and configure the SAR Transmitter state of a SAR
18 Configuration Server. Function calls :c:func:`bt_mesh_sar_cfg_cli_transmitter_get` and
19 :c:func:`bt_mesh_sar_cfg_cli_transmitter_set` are used to get and set the SAR Transmitter state
22 The SAR Receiver procedure is used to determine and configure the SAR Receiver state of a SAR
23 Configuration Server. Function calls :c:func:`bt_mesh_sar_cfg_cli_receiver_get` and
24 :c:func:`bt_mesh_sar_cfg_cli_receiver_set` are used to get and set the SAR Receiver state of the
|
| /Zephyr-latest/samples/net/ipv4_autoconf/ |
| D | README.rst | 5 Perform IPv4 autoconfiguration and self-assign a random IPv4 address
10 This sample application starts a IPv4 autoconf and self-assigns
12 the IPv4 address and resolves IPv4 conflicts if multiple
20 Building and Running
24 on a :zephyr:board:`frdm_k64f` board to configure a link local IPv4 address and
28 host machine and check for new interfaces.
53 Once IPv4 LL has completed probing and announcement, details are shown like this:
66 To verify the Zephyr application is running and has configured an IP address
|
| /Zephyr-latest/doc/develop/manifest/ |
| D | index.rst | 9 this contributing and review process for imported components.
14 The projects below are enabled by default and will be downloaded when you
16 essential for building generic Zephyr application and include among others
28 Inactive and Optional Projects/Modules
32 The projects below are optional and will not be downloaded when you
34 and use them to write application code and extend your workspace with the added
49 The projects listed below are external and are not directly imported into the
|
12345678910>>...155
