Home
last modified time | relevance | path

Searched +full:time +full:- +full:of +full:- +full:flight (Results 1 – 25 of 29) sorted by relevance

12

/Zephyr-latest/drivers/sensor/st/vl53l1x/
DKconfig1 # VL53L0X time of flight sensor configuration options
4 # SPDX-License-Identifier: Apache-2.0
7 bool "VL53L1X time of flight sensor"
14 Enable driver for VL53L1X I2C-based time of flight sensor.
19 bool "Use interrupt mode for VL53L1X time of flight sensor"
23 Enable interrupt mode for VL53L1X time of flight sensor. Otherwise,
27 bool "Use xshut pin on VL53L1X time of flight sensor"
Dvl53l1.c1 /* vl53l1.c - Driver for ST VL53L1X time of flight sensor */
6 * SPDX-License-Identifier: Apache-2.0
53 ret = VL53L1_GetRangingMeasurementData(&drv_data->vl53l1x, &drv_data->data); in vl53l1x_read_sensor()
59 ret = VL53L1_ClearInterruptAndStartMeasurement(&drv_data->vl53l1x); in vl53l1x_read_sensor()
81 k_work_submit(&drv_data->work); in vl53l1x_gpio_callback()
86 struct vl53l1x_data *drv_data = dev->data; in vl53l1x_init_interrupt()
87 const struct vl53l1x_config *config = dev->config; in vl53l1x_init_interrupt()
90 drv_data->dev = dev; in vl53l1x_init_interrupt()
92 if (!gpio_is_ready_dt(&config->gpio1)) { in vl53l1x_init_interrupt()
93 LOG_ERR("%s: device %s is not ready", dev->name, config->gpio1.port->name); in vl53l1x_init_interrupt()
[all …]
/Zephyr-latest/drivers/sensor/st/vl53l0x/
DKconfig1 # VL53L0X time of flight sensor configuration options
4 # SPDX-License-Identifier: Apache-2.0
7 bool "VL53L0X time of flight sensor"
14 Enable driver for VL53L0X I2C-based time of flight sensor.
29 must have an xshut-gpio property.
Dvl53l0x.c1 /* vl53l0x.c - Driver for ST VL53L0X time of flight sensor */
8 * SPDX-License-Identifier: Apache-2.0
31 * https://www.st.com/en/embedded-software/stsw-img005.html
32 * There are also examples of use in the L4 cube FW:
33 * https://www.st.com/en/embedded-software/stm32cubel4.html
60 struct vl53l0x_data *drv_data = dev->data; in vl53l0x_setup_single_shot()
67 ret = VL53L0X_StaticInit(&drv_data->vl53l0x); in vl53l0x_setup_single_shot()
70 dev->name); in vl53l0x_setup_single_shot()
74 ret = VL53L0X_PerformRefCalibration(&drv_data->vl53l0x, in vl53l0x_setup_single_shot()
79 dev->name); in vl53l0x_setup_single_shot()
[all …]
/Zephyr-latest/boards/shields/x_nucleo_53l0a1/doc/
Dindex.rst3 X-NUCLEO-53L0A1 ranging and gesture detection sensor expansion board
9 The X-NUCLEO-53L0A1 expansion board features the VL53L0X ranging and gesture
10 detection sensor, based on ST’s FlightSense™, Time-of-Flight technology. It is
12 detection capabilities of the VL53L0X module.
14 One VL53L0X is soldered on the expansion board itself. A set of spacers and
24 :alt: X-NUCLEO-53L0A1
27 `X-NUCLEO-53L0A1 website`_.
45 The 7 segment display is connected to two GPIO expanders, each of one handles
54 - `X-NUCLEO-53L0A1 ranging and gesture detection sensor expansion board User Manual`_
55 - `VL53L0X Time-of-Flight ranging and gesture detection sensor Datasheet`_
[all …]
/Zephyr-latest/samples/shields/x_nucleo_53l0a1/
Dsample.yaml2 name: X-NUCLEO-53L0A1 time-of-flight distance sensor shield
8 filter: dt_enabled_alias_with_parent_compat("sw0", "gpio-keys")
/Zephyr-latest/dts/bindings/sensor/
Dst,vl53l0x.yaml2 # SPDX-License-Identifier: Apache-2.0
4 description: STMicroelectronics VL53L0X Time of Flight sensor
8 include: [sensor-device.yaml, i2c-device.yaml]
11 xshut-gpios:
12 type: phandle-array
Dst,vl53l1x.yaml2 # SPDX-License-Identifier: Apache-2.0
4 description: STMicroelectronics VL53L1X Time of Flight sensor
8 include: [sensor-device.yaml, i2c-device.yaml]
11 xshut-gpios:
12 type: phandle-array
20 int-gpios:
21 type: phandle-array
/Zephyr-latest/subsys/net/lib/mqtt_sn/
DKconfig1 # MQTT-SN Library for Zephyr
4 # SPDX-License-Identifier: Apache-2.0
7 bool "MQTT-SN Library Support [EXPERIMENTAL]"
15 int "Maximum payload size of an MQTT-SN message"
20 int "Number of preallocated messages"
25 int "Number of topics that can be managed"
35 int "Maximum number of gateways to store internally"
46 length in bytes of the address data structure for your implemented transport.
54 int "Number of publishes that can be in-flight at the same time"
59 int "Maximum number of clients Keep alive time for MQTT-SN (in seconds)"
[all …]
/Zephyr-latest/samples/sensor/vl53l0x/
DREADME.rst1 .. zephyr:code-sample:: vl53l0x
2 :name: VL53L0X Time Of Flight sensor
3 :relevant-api: sensor_interface
22 - VL53L0X: https://www.st.com/en/imaging-and-photonics-solutions/vl53l0x.html
30 .. zephyr-app-commands::
31 :zephyr-app: samples/sensor/vl53l0x/
38 .. code-block:: console
/Zephyr-latest/dts/bindings/i2c/
Dinfineon,cat1-i2c.yaml2 # an affiliate of Cypress Semiconductor Corporation
4 # SPDX-License-Identifier: Apache-2.0
11 Example devicetree configuration with vl53l0x Time-of-Flight (ToF)
15 compatible = "infineon,cat1-i2c";
18 #address-cells = <1>;
19 #size-cells = <0>;
21 pinctrl-0 = <&p6_0_scb3_i2c_scl &p6_1_scb3_i2c_sda>;
22 pinctrl-names = "default";
30 The pinctrl nodes need to be configured as open-drain and
31 input-enable:
[all …]
/Zephyr-latest/boards/tdk/robokit1/doc/
Dindex.rst7 number of small ground robotics useful sensors including chirp sensors for time of flight
10 It pairs a 300MHz Cortex-M7 ATSAME70Q21 with an array of TDK sensors and pin headers useful for rob…
15 - ATSAME70Q21 ARM Cortex-M7 Processor
16 - 12 MHz crystal oscillator (Pres)
17 - 32.768 kHz crystal oscillator
18 - Micro-AB USB device
19 - Micro-AB USB debug (Microchip EDBG) interface supporting CMSIS-DAP, Virtual COM Port and Data
20 - JTAG interface connector
21 - One reset pushbutton
22 - One red user LED
[all …]
/Zephyr-latest/doc/project/
Drelease_process.rst6 The Zephyr project releases on a time-based cycle, rather than a feature-driven
7 one. Zephyr releases represent an aggregation of the work of many contributors,
10 A time-based release process enables the Zephyr project to provide users with a
11 balance of the latest technologies and features and excellent overall quality. A
12 roughly 4-month release cycle allows the project to coordinate development of
14 maintain the quality of the overall release without delays because of one or two
19 - Release tagging procedure:
21 - linear mode on main branch,
22 - release branches for maintenance after release tagging.
23 - Each release period will consist of a development phase followed by a
[all …]
/Zephyr-latest/include/zephyr/bluetooth/
Dconn.h6 * Copyright (c) 2015-2016 Intel Corporation
8 * SPDX-License-Identifier: Apache-2.0
73 * Connection Interval: 30-50 ms
102 uint8_t pref_tx_phy; /**< Bitmask of preferred transmit PHYs */
103 uint8_t pref_rx_phy; /**< Bitmask of preferred receive PHYs */
108 * @param _pref_tx_phy Bitmask of preferred transmit PHYs.
109 * @param _pref_rx_phy Bitmask of preferred receive PHYs.
120 * @param _pref_tx_phy Bitmask of preferred transmit PHYs.
121 * @param _pref_rx_phy Bitmask of preferred receive PHYs.
152 /** Maximum Link Layer transmission payload time in us. */
[all …]
/Zephyr-latest/samples/net/mqtt_sn_publisher/compose/
Dmosquitto.conf36 # setting behaviour from previous versions of mosquitto.
50 # Defaults to 'auto-'
51 #auto_id_prefix auto-
55 # message to the topic had access at the time they published, but that access
57 # default, the source of a retained message will be checked for access rights
67 # The maximum number of QoS 1 and 2 messages currently inflight per
71 # maximum. Setting to 1 will guarantee in-order delivery of QoS 1
92 # specifies a keepalive time greater than max_keepalive they will be sent a
101 # set the maximum packet size to that number of bytes. If a client sends a
103 # to all clients regardless of the protocol version they are using, but v3.1.1
[all …]
/Zephyr-latest/kernel/
DKconfig3 # Copyright (c) 2014-2015 Wind River Systems, Inc.
4 # SPDX-License-Identifier: Apache-2.0
9 module-str = kernel
13 bool "Multi-threading" if ARCH_HAS_SINGLE_THREAD_SUPPORT
27 int "Number of coop priorities" if MULTITHREADING
32 Number of cooperative priorities configured in the system. Gives access
35 K_PRIO_COOP(0) to K_PRIO_COOP(CONFIG_NUM_COOP_PRIORITIES - 1)
39 -CONFIG_NUM_COOP_PRIORITIES to -1
44 The total number of priorities is
52 int "Number of preemptible priorities" if MULTITHREADING
[all …]
/Zephyr-latest/doc/services/rtio/
Dindex.rst3 Real Time I/O (RTIO)
18 RTIO takes a lot of inspiration from Linux's io_uring in its operations and API
26 in Zephyr requires direct knowledge of the hardware and how it works. There is
27 no understanding in the DMA API of other Zephyr devices and how they relate.
32 To enable asynchronous operations, especially with DMA, a description of what
34 DMA features such as channels with priority, and sequences of transfers requires
35 more than a simple list of descriptions.
45 lock-free ring buffers acting as queues shared between the kernel and a userland
49 io_uring_submit call. This call may block the caller when a number of
53 sequence of operations in an asynchronous way directly relates
[all …]
/Zephyr-latest/boards/st/stm32wb5mm_dk/doc/
Dstm32wb5mm_dk.rst6 The STM32WB5MM-DK Discovery kit is designed as a complete demonstration
8 on the Arm |reg| Cortex |reg|-M4 and Arm |reg| Cortex |reg|-M0+ cores.
9 The STM32 device is a multi-protocol wireless and ultra-low-power device
10 embedding a powerful and ultra-low-power radio compliant with the
12 IEEE 802.15.4-2011.
15 STM32WB5MM-DK supports the following features:
17 * STM32WB5MMG (1-Mbyte Flash memory, 256-Kbyte SRAM)
18 - Dual-core 32‑bit (Arm |reg| Cortex |reg|-M4 and M0+)
19 - 2.4 GHz RF transceiver
20 - 0.96-inch 128x64 OLED display
[all …]
/Zephyr-latest/boards/st/stm32u5a9j_dk/doc/
Dindex.rst6 The STM32U5A9J-DK Discovery kit is a complete demonstration and development
7 platform for the STM32U5A9NJH6Q microcontroller, featuring an Arm® Cortex®-M33
10 Leveraging the innovative ultra-low-power oriented features, 2.5 Mbytes of
11 embedded SRAM, 4 Mbytes of embedded flash memory, and rich graphics features,
12 the STM32U5A9J-DK Discovery kit enables users to easily prototype applications
13 with state-of-the-art energy efficiency, as well as providing stunning and
14 optimized graphics rendering with the support of the 2.5D NeoChrom Accelerator,
15 Chrom-ART Accelerator, and Chrom-GRC™ MMU.
17 The full range of hardware features available on the board helps users to
18 enhance their application development by an evaluation of all the peripherals
[all …]
/Zephyr-latest/boards/st/b_l4s5i_iot01a/doc/
Dindex.rst6 The B_L4S5I_IOT01A Discovery kit features an ARM Cortex-M4 based STM32L4S5VI MCU
7 with a wide range of connectivity support and configurations. Here are
8 some highlights of the B_L4S5I_IOT01A Discovery kit:
11 - STM32L4S5VIT6 microcontroller featuring 2 Mbyte of Flash memory, 640 Kbytes of RAM in LQFP100 pac…
12 - On-board ST-LINK/V2-1 supporting USB re-enumeration capability
13 - Three different interfaces supported on USB:
15 - Virtual com port
16 - Mass storage
17 - Debug port
19 - ARDUINO ® Uno V3 and Pmod TM expansion connector
[all …]
/Zephyr-latest/subsys/bluetooth/host/
DKconfig3 # Copyright (c) 2016-2020 Nordic Semiconductor ASA
4 # Copyright (c) 2015-2016 Intel Corporation
5 # SPDX-License-Identifier: Apache-2.0
8 bool "Dedicated workqueue for long-running tasks."
11 Adds an API for a workqueue dedicated to long-running tasks.
23 int "Long workqueue priority. Should be pre-emptible."
58 # the worst-case stack size if an out-of-tree controller is used.
70 # Hidden option for Co-Operative Tx thread priority
81 High priority events are always processed in the context of the caller of bt_recv()
90 High priority HCI packets will processed in the context of the caller of bt_recv().
[all …]
/Zephyr-latest/boards/st/b_u585i_iot02a/doc/
Dindex.rst6 The B_U585I_IOT02A Discovery kit features an ARM Cortex-M33 based STM32U585AI MCU
7 with a wide range of connectivity support and configurations. Here are
8 some highlights of the B_U585I_IOT02A Discovery kit:
11 - STM32U585AII6Q microcontroller featuring 2 Mbyte of Flash memory, 786 Kbytes of RAM in UFBGA169 p…
12 - 512-Mbit octal-SPI Flash memory, 64-Mbit octal-SPI PSRAM, 256-Kbit I2C EEPROM
13 - USB FS, Sink and Source power, 2.5 W power capability
14 - 802.11 b/g/n compliant Wi-Fi® module from MXCHIP
15 - Bluetooth Low Energy from STMicroelectronics
16 - MEMS sensors from STMicroelectronics
18 - 2 digital microphones
[all …]
/Zephyr-latest/boards/st/disco_l475_iot1/doc/
Dindex.rst6 The B-L475E-IOT01A Discovery kit for IoT node allows users to develop
8 The Discovery kit enables a wide diversity of applications by exploiting
9 low-power communication, multiway sensing and ARM |reg| Cortex |reg|-M4 core-based
14 - 64-Mbit Quad-SPI (Macronix) Flash memory
15 - Bluetooth |reg| V4.1 module (SPBTLE-RF)
16 - Sub-GHz (868 or 915 MHz) low-power-programmable RF module (SPSGRF-868 or SPSGRF-915)
17 - Wi-Fi |reg| module Inventek ISM43362-M3G-L44 (802.11 b/g/n compliant)
18 - Dynamic NFC tag based on M24SR with its printed NFC antenna
19 - 2 digital omni-directional microphones (MP34DT01)
20 - Capacitive digital sensor for relative humidity and temperature (HTS221)
[all …]
/Zephyr-latest/subsys/net/lib/lwm2m/
Dlwm2m_object.h3 * Copyright (c) 2018-2019 Foundries.io
5 * SPDX-License-Identifier: Apache-2.0
15 * 1. Redistributions of source code must retain the above copyright
16 * notice, this list of conditions and the following disclaimer.
18 * notice, this list of conditions and the following disclaimer in the
20 * 3. Neither the name of the copyright holder nor the names of its
26 * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
30 * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
31 * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
32 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
[all …]
/Zephyr-latest/include/zephyr/drivers/
Dspi.h4 * SPDX-License-Identifier: Apache-2.0
27 #include <zephyr/dt-bindings/spi/spi.h>
73 * Whatever data is transmitted is looped-back to the receiving buffer of
115 /** Requests - if possible - to keep CS asserted after the transaction */
139 * Default is single, which is the case most of the time.
155 * This can be used to control a CS line via a GPIO line, instead of
161 * GPIO devicetree specification of CS GPIO.
187 * cs-gpios = <&gpio1 10 GPIO_ACTIVE_LOW>,
190 * a: spi-dev-a@0 {
194 * b: spi-dev-b@1 {
[all …]

12