Searched refs:and (Results 576 – 600 of 3855) sorted by relevance
1...<<21222324252627282930>>...155
| /Zephyr-latest/soc/espressif/esp32/ |
| D | Kconfig.mac | 13 all four interfaces (WiFi station, WiFi softap, Bluetooth and Ethernet) receive a universally
14 administered MAC address. These are generated sequentially by adding 0, 1, 2 and 3 (respectively)
16 only two interfaces (WiFi station and Bluetooth) receive a universally administered MAC address.
17 These are generated sequentially by adding 0 and 1 (respectively) to the base MAC address.
18 The remaining two interfaces (WiFi softap and Ethernet) receive local MAC addresses.
19 These are derived from the universal WiFi station and Bluetooth MAC addresses, respectively.
|
| /Zephyr-latest/boards/qemu/riscv32_xip/doc/ |
| D | index.rst | 8 Programming and Debugging
11 Applications for the ``qemu_riscv32_xip`` 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/riscv32e/doc/ |
| D | index.rst | 8 Programming and Debugging
11 Applications for the ``qemu_riscv32e`` 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/samples/drivers/video/tcpserversink/ |
| D | README.rst | 5 Capture video frames and send them over the network to a TCP client.
10 This sample application gets frames from a video capture device and sends
16 This samples requires a video capture device and network support.
29 Building and Running
50 Then from a peer on the same network you can connect and grab frames.
62 For video software generator, the default resolution should be width=320 and height=160.
|
| /Zephyr-latest/doc/contribute/style/ |
| D | code.rst | 3 C Code and General Style Guidelines
17 exceptions and clarifications:
19 * Use `snake case`_ for code and variables.
22 * Add braces to every ``if``, ``else``, ``do``, ``while``, ``for`` and
31 * Use proper capitalization of nouns in code comments (e.g. ``UART`` and not
32 ``uart``, ``CMake`` and not ``cmake``).
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.init | 7 menu "SoC and Board Hooks"
30 A custom SoC hook soc_early_init_hook() is executed before the kernel and
38 A custom SoC hook soc_late_init_hook() is executed after the kernel and
47 arch_kernel_init() for the primary core, and at the end of arch_secondary_cpu_init()
55 A custom board hook board_early_init_hook() is executed before the kernel and
63 A custom board hook board_late_init_hook() is executed after the kernel and
|
| /Zephyr-latest/samples/net/mdns_responder/ |
| D | README.rst | 5 Listen and respond to mDNS queries.
10 This application will wait mDNS queries for a pre-defined hostname and
11 respond to them. The default hostname is **zephyr** and it is set in the
22 Building and Running
25 Build and run the mdns-responder sample application like this:
37 Open a terminal window in your host and type:
|
| /Zephyr-latest/subsys/retention/ |
| D | Kconfig.blinfo | 21 Adds a bootloader information sharing system for MCUboot and
23 MCUboot and the running image. This can be used by applications so
24 that they know how to e.g. handle firmware updates and place them
27 In order to use this, a retention area must be created and set as
29 must be built with the same "zephyr,bootloader-info" DTS node and
30 have CONFIG_BOOT_SHARE_DATA, CONFIG_BOOT_SHARE_DATA_BOOTINFO and
|
| /Zephyr-latest/samples/sensor/lis2dh/ |
| D | README.rst | 11 LIS2DH sensor (or the compatible LS2DH12, LIS3DH, and LSM303DLHC
12 sensors), and displays the sensor data on the console.
24 https://www.st.com/en/mems-and-sensors/lis2dh.html.
26 Building and Running
30 and shields supported by Zephyr, including:
38 and get access to the console where acceleration data is displayed.
|
| /Zephyr-latest/samples/sensor/max17262/ |
| D | README.rst | 5 Get voltage, current and temperature data from a MAX17262 sensor (polling mode).
10 This sample application periodically reads voltage, current and temperature
12 SENSOR_CHAN_GAUGE_AVG_CURRENT, and SENSOR_CHAN_GAUGE_TEMP.
18 ModelGauge m5 algorithm. The IC monitors a single-cell battery pack and
23 connectors and defines node aliases for the I2C interface.
27 Building and Running
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_pkt.rst | 15 a means to hold the packet, write and read it, as well as necessary
19 The data structure and the whole API around it are defined in
26 transmission path, and **RX** for the reception one. In both paths,
27 each net_pkt is written and read from the beginning to the end, or
45 already two pools, one for the TX path and one for the RX path.
53 However, by its nature, a raw net_pkt is useless without a buffer and
63 A more complete allocator exists, where both the net_pkt and its buffer
80 awareness to buffer allocation and, as we will see later, its
93 As seen previously, the net_pkt and its buffer can be allocated at
97 The network interface, the family, and the protocol of the packet are
[all …]
|
| /Zephyr-latest/boards/st/b_l4s5i_iot01a/doc/ |
| D | index.rst | 7 with a wide range of connectivity support and configurations. Here are
19 - ARDUINO ® Uno V3 and Pmod TM expansion connector
21 - 2 push-buttons (user and reset)
25 - Capacitive digital sensor for relative humidity and temperature
26 - Time-of-flight and gesture-detection sensors
28 - 3D accelerometer and 3D gyroscope
32 - MCU current ammeter with 4 ranges and auto-calibration
47 - Ultra-low-power with FlexPowerControl (down to 130 nA Standby mode and 100 uA/MHz run mode)
57 - RTC with HW calendar, alarms and calibration
58 - Up to 21 capacitive sensing channels: support touchkey, linear and rotary touch sensors
[all …]
|
| /Zephyr-latest/boards/ezurio/bt510/doc/ |
| D | bt510.rst | 18 * RADIO (Bluetooth Low Energy and 802.15.4)
41 Connections and IOs
84 Programming and Debugging
87 Applications for the ``bt510`` board configuration can be built, flashed, and
88 debugged in the usual way. See :ref:`build_an_application` and
89 :ref:`application_run` for more details on building and running.
132 board, on the programming board set SW6 to the supply out position and SW5 to the 3V3
133 position, ensure there is a jumper on J35 and that SW1 is in the debug position, then
142 Then build and flash applications as usual (see :ref:`build_an_application` and
153 NOTE: On the BT510, the UART lines are at TTL levels and must be passed through
[all …]
|
| /Zephyr-latest/boards/st/stm32f3_disco/doc/ |
| D | index.rst | 7 MCU with everything required for beginners and experienced users to get
12 board and easy probing
14 C and newer, debugger/programmer with SWD connector
17 - External application power supply: 3 V and 5 V
24 and green (LD6/LD7)
26 - Two push-buttons: USER and RESET
30 acceleration sensor and a 3D digital magnetic sensor;
33 Recent PCB revisions (E and newer) are shipped with I3G4250D and LSM303AGR.
49 - Routine booster: 8 Kbytes of SRAM on instruction and data bus
136 STM32F3DISCOVERY has up to 2 I2Cs. I2C1 is connected to the LSM303DLHC and is
[all …]
|
| /Zephyr-latest/boards/others/icev_wireless/doc/ |
| D | index.rst | 6 The ICE-V Wireless is a combined ESP32C3 and iCE40 FPGA board.
14 Lattice iCE40UP5k-SG48 FPGA to allow WiFi and Bluetooth control of the FPGA. ESP32 and FPGA I/O is
15 mostly uncommitted except for the pins used for SPI communication between ESP32 and FPGA. Several
33 Connections and IOs
36 The ICE-V Wireless provides 1 row of reference, ESP32-C3, and iCE40 signals
48 GPIO21, FPGA_P34, and GND. Note that GPIO2 and GPIO3 may be configured for
51 For PMOD details, please refer to the `PMOD Specification`_ and the image
58 Programming and Debugging
61 Programming and debugging for the ICE-V Wireless ESP32-C3 target is
64 Building and Flashing
[all …]
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_ace15_mtpm.rst | 11 Refer to :ref:`intel_adsp_generic` for more details on Intel ADSP ACE and CAVS.
31 Programming and Debugging
34 Refer to :ref:`intel_adsp_generic` for generic instructions on programming and
35 debugging applicable to all CAVS and ACE platforms.
|
| D | intel_adsp_cavs25.rst | 11 Refer to :ref:`intel_adsp_generic` for more details on Intel ADSP ACE and CAVS.
28 Programming and Debugging
31 Refer to :ref:`intel_adsp_generic` for generic instructions on programming and
32 debugging applicable to all CAVS and ACE platforms.
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/os_mgmt_client/ |
| D | Kconfig | 5 # of MCUmgr client subsystem and provides Kconfig options to configure
6 # group commands behaviour and other aspects.
15 bool "MCUmgr client request and response handlers for OS management"
19 Enables MCUmgr client request and response handlers for OS management.
|
| /Zephyr-latest/soc/snps/emsdp/ |
| D | linker.ld | 14 * SRAM base address and size
24 /* Instruction Closely Coupled Memory (ICCM) base address and size */
32 * DCCM base address and size. DCCM is the data memory.
34 /* Data Closely Coupled Memory (DCCM) base address and size */
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | cfg_cli.rst | 8 mesh node, including encryption keys, model configuration and feature
17 and ``addr`` as their first parameters. These should be set to the network
18 index and primary unicast address that the target node was provisioned with.
20 The Configuration Client model is optional, and it must only be instantiated on the
|
| /Zephyr-latest/samples/sensor/magn_trig/ |
| D | README.rst | 4 Test and debug magnetometer with interrupts
10 the available device that implements SENSOR_TRIG_DATA_READY and SENSOR_CHAN_MAGN_*.
12 Building and Running
23 Make sure the aliases are in devicetree, then build and run with:
|
| /Zephyr-latest/samples/bluetooth/eddystone/ |
| D | README.rst | 12 it is connectable and allows configuration of the advertised data, the
13 broadcast power levels, and the advertising intervals. It also forms part of
14 the definition of how Eddystone-EID beacons are configured and registered with
24 Building and Running
|
| /Zephyr-latest/samples/subsys/sensing/simple/ |
| D | README.rst | 11 two sensors, with the underlying device bmi160 emulator, and gets the sensor
24 #. Run forever and get the sensor data.
26 Building and Running
29 This application can be built and executed on :ref:`native_sim <native_sim>` as follows:
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.sync_io | 10 Select 'y' here and Zephyr will provide an implementation of fsync().
20 Select 'y' here and Zephyr will provide an implementation of fdatasync(), fsync(),
21 and msync().
35 Select 'y' here and Zephyr will provide an alias for fsync() as _fsync().
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-4.0.rst | 38 * Nordic nRF53 and nRF91 based boards can use the common devicetree overlays in ``dts/common/nordic…
39 to define default flash and ram partitioning based on TF-M.
49 * The :c:macro:`DT_REG_ADDR` macro and its variants are now expanding into an
52 * The :c:macro:`DT_REG_SIZE` macro and its variants are also expanding into
69 * The Kconfig options ``CONFIG_MBEDTLS_TLS_VERSION_1_0`` and ``CONFIG_MBEDTLS_TLS_VERSION_1_1``
70 …have been removed because Mbed TLS doesn't support TLS 1.0 and 1.1 anymore since v3.0. (:github:`7…
76 corresponding build symbol was removed in Mbed TLS 3.1.0 and is now assumed to
107 ``zcbor_bool_*()``, ``zcbor_nil_*()``, and ``zcbor_undefined_*()``.
117 Device Drivers and Devicetree
127 ``microchip,mcp230xx`` and ``microchip,mcp23sxx`` should change their devicetree ``compatible``
[all …]
|
1...<<21222324252627282930>>...155
