| /Zephyr-latest/samples/fuel_gauge/max17048/ |
| D | README.rst | 1 .. zephyr:code-sample:: max17048
2 :name: MAX17048 Li-Ion battery fuel gauge
11 .. _MAX17048: https://www.maximintegrated.com/en/products/power/battery-management/MAX17048.html
33 if you plug/unplug a charger it will take some time until it is actually detected by the chip. Don'…
34 to see in real time the charging status change because it will not work. If you really need to know…
|
| /Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/ |
| D | README.rst | 1 .. zephyr:code-sample:: stm32_pm_serial_wakeup
3 :relevant-api: subsys_pm_device
11 in low power context.
13 .. _stm32-pm-serial-wakeup-sample-requirements:
20 in core sleep states, as LPTIM (:dtcompatible:`st,stm32-lptim`).
25 - Clocked by an oscillator available in Stop mode (LSE, LSI) or an oscillator capable
27 - Matching oscillator sources should be enabled
28 - If LSE is selected as clock source and shell serial port is a LPUART current speed
30 - Port should be set as "wakeup-source"
40 .. zephyr-app-commands::
[all …]
|
| /Zephyr-latest/samples/subsys/usb/audio/headset/ |
| D | README.rst | 1 .. zephyr:code-sample:: usb-audio-headset
3 :relevant-api: _usb_device_core_api
5 Implement a USB Audio headset device with audio IN/OUT loopback.
11 project. This very simple sample that performs loopback over IN/OUT
17 In order to build the sample an overlay file with required options
22 After you have built and flashed the sample app image to your board, plug the
30 - Build and flash the sample as described above.
31 - Connect to the HOST.
32 - Chose default Audio IN/OUT.
33 - Start streaming audio (for example by playing an audio file on the HOST).
[all …]
|
| /Zephyr-latest/samples/subsys/usb/audio/headphones_microphone/ |
| D | README.rst | 1 .. zephyr:code-sample:: usb-audio-headphones-microphone
3 :relevant-api: _usb_device_core_api
5 Implement a USB Audio microphone + headphones device with audio IN/OUT loopback.
11 project. This very simple sample that performs loopback over IN/OUT
18 In order to build the sample an overlay file with required options
23 After you have built and flashed the sample app image to your board, plug the
31 - Build and flash the sample as described above.
32 - Connect to the HOST.
33 - Chose default Audio IN/OUT.
34 - Start streaming audio (for example by playing an audio file on the HOST).
[all …]
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | ti,boosterpack-header.yaml | 2 # SPDX-License-Identifier: Apache-2.0
9 BoosterPack plug-in modules are available in 20 and 40 pin variants. The
29 http://processors.wiki.ti.com/index.php/BYOB or in the documentation for
32 compatible: "ti,boosterpack-header"
34 include: [gpio-nexus.yaml, base.yaml]
|
| /Zephyr-latest/samples/subsys/usb/console/ |
| D | README.rst | 1 .. zephyr:code-sample:: usb-cdc-acm-console
3 :relevant-api: _usb_device_core_api usbd_api
21 This sample can be built for multiple boards, in this example we will build it
24 .. zephyr-app-commands::
25 :zephyr-app: samples/subsys/usb/console
30 Plug the board into a host device, for sample, a PC running Linux OS.
32 from the sample, use a command similar to :command:`minicom -D /dev/ttyACM0`.
34 .. code-block:: console
45 trying to access the device in the background.
|
| /Zephyr-latest/boards/shields/boostxl_ulpsense/doc/ |
| D | index.rst | 1 .. _boostxl-ulpsense:
3 BOOSTXL-ULPSENSE: Ultra-low Power Sensor BoosterPack
9 The Ultra-low Power Sensor BoosterPack (BOOSTXL-ULPSENSE) adds analog and
10 digital sensors to a TI LaunchPad |trade| development kit. The plug-in module
12 buttons, a light sensor, a reed switch, and an ultra-low power accelerometer.
26 Set ``--shield boostxl_ulpsense`` when you invoke ``west build``. For example:
28 .. zephyr-app-commands::
29 :zephyr-app: samples/sensor/accel_polling/
37 .. target-notes::
40 http://www.ti.com/tool/BOOSTXL-ULPSENSE
|
| /Zephyr-latest/tests/kernel/workq/work_queue/src/ |
| D | start_stop.c | 4 * SPDX-License-Identifier: Apache-2.0
11 /* In fact, each work item could take up to this value */
35 zassert_equal(k_work_queue_stop(&work_q, K_FOREVER), -EALREADY, in ZTEST()
36 "Succeeded to stop work queue on non-initialized work queue"); in ZTEST()
49 zassert_equal(k_work_queue_stop(&work_q, K_FOREVER), -EBUSY, in ZTEST()
51 zassert_true(k_work_queue_drain(&work_q, true) >= 0, "Failed to drain & plug work queue"); in ZTEST()
55 zassert_equal(k_work_submit_to_queue(&work_q, &work), -ENODEV, in ZTEST()
56 "Succeeded to submit work item to non-initialized work queue"); in ZTEST()
|
| /Zephyr-latest/include/zephyr/drivers/usb_c/ |
| D | usbc_tc.h | 3 * SPDX-License-Identifier: Apache-2.0
8 * @brief USB Type-C Cable and Connector API used for USB-C drivers
10 * The information in this file was taken from the USB Type-C
18 * @brief USB Type-C
19 * @defgroup usb_type_c USB Type-C
32 * See Table 4-3 VBUS Sink Characteristics
38 * See Table 4-3 VBUS Sink Characteristics
45 * See Table 4-29 VBUS and VCONN Timing Parameters
52 * See Table 4-29 VBUS and VCONN Timing Parameters
57 * @brief From the time the Source supplied VBUS in the Attached.SRC state.
[all …]
|
| /Zephyr-latest/samples/subsys/usb/cdc_acm/ |
| D | README.rst | 1 .. zephyr:code-sample:: usb-cdc-acm
2 :name: USB CDC-ACM
3 :relevant-api: usbd_api _usb_device_core_api uart_interface
5 Use USB CDC-ACM driver to implement a serial port echo.
14 This sample can be found under :zephyr_file:`samples/subsys/usb/cdc_acm` in the
21 boards supported in Zephyr.
32 .. zephyr-app-commands::
33 :zephyr-app: samples/subsys/usb/cdc_acm
41 Plug the board into a host device, for example, a PC running Linux.
44 .. code-block:: console
[all …]
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 11 This section is a quick hands-on reference to start debugging your
12 application with QEMU. Most content in this section is already covered in
19 In this quick reference, you'll find shortcuts, specific environmental
23 The simplest way to debug an application running in QEMU is using the GNU
24 Debugger and setting a local GDB server in your development system through QEMU.
27 debugging purposes. The build system generates the image in the build
46 .. code-block:: bash
48 qemu -s -S <image>
54 * ``-S`` Do not start CPU at startup; rather, you must type 'c' in the
56 * ``-s`` Shorthand for :literal:`-gdb tcp::1234`: open a GDB server on
[all …]
|
| /Zephyr-latest/tests/drivers/usb/bc12/src/ |
| D | charging_mode.c | 4 * SPDX-License-Identifier: Apache-2.0
12 * @brief TestPurpose: Verify BC1.2 devices configured in charging mode.
37 if (state->bc12_role == BC12_PORTABLE_DEVICE) { in bc12_test_result_cb()
38 LOG_INF("charging partner: type %d, voltage %d, current %d", state->type, in bc12_test_result_cb()
39 state->voltage_uv, state->current_ua); in bc12_test_result_cb()
40 } else if (state->bc12_role == BC12_CHARGING_PORT) { in bc12_test_result_cb()
42 state->pd_partner_connected); in bc12_test_result_cb()
44 fixture->partner_state = *state; in bc12_test_result_cb()
47 fixture->partner_state.type = BC12_TYPE_NONE; in bc12_test_result_cb()
48 fixture->partner_state.current_ua = 0; in bc12_test_result_cb()
[all …]
|
| /Zephyr-latest/boards/st/stm32g071b_disco/doc/ |
| D | index.rst | 5 The STM32G071B-DISCO Discovery board is a demonstration and development platform
6 for the STMicroelectronics Arm® Cortex® -M0+ core-based STM32G071RB USB Type-C™
7 and Power Delivery microcontroller. The STM32G071B-DISCO Discovery board is
9 interoperability with other USB Type-C™ devices. The STM32G071B-DISCO Discovery
10 board is intended for discovery and display of USB Type-C™ port characteristics
13 as a USB Type-C™ and Power Delivery analyzer.
15 - STM32G071RBT6 microcontroller featuring 128 Kbytes of Flash memory and
16 32 Kbytes of RAM in LQFP64 package
17 - Plastic case
18 - 1” 128 x 64 pixels OLED LCD module with SPI interface
[all …]
|
| /Zephyr-latest/samples/net/telnet/ |
| D | README.rst | 1 .. zephyr:code-sample:: telnet-console
3 :relevant-api: shell_api net_core net_if net_mgmt
19 - :ref:`networking_with_qemu`
33 Run Zephyr samples/net/telnet application in QEMU:
35 .. zephyr-app-commands::
36 :zephyr-app: samples/net/telnet
37 :host-os: unix
44 .. code-block:: console
53 .. code-block:: console
65 Freedom-K64F Board
[all …]
|
| /Zephyr-latest/boards/others/serpente/doc/ |
| D | index.rst | 6 The Serpente is a very small low-cost development and prototyping
8 The board comes with 3 different USB connector options: USB Type-C plug,
9 USB Type-C socket and USB Type-A plug.
14 - ATSAMD21E18A ARM Cortex-M0+ processor at 48 MHz
15 - 256 KiB flash memory and 32 KiB of RAM
16 - Extra 4MiB SPI flash memory
17 - RGB User LED
18 - Reset button
19 - Native USB port
27 +-----------+------------+------------------------------------------+
[all …]
|
| /Zephyr-latest/samples/subsys/usb/hid-mouse/ |
| D | README.rst | 1 .. zephyr:code-sample:: usb-hid-mouse
3 :relevant-api: _usb_device_core_api usb_hid_device_api input_interface
13 the number of buttons on the board) a right mouse button, X-axis movement,
14 and Y-axis movement.
16 will be performed on every button click if the bus is in suspended state.
17 This sample can be found under :zephyr_file:`samples/subsys/usb/hid-mouse` in the
24 There must be a :dtcompatible:`gpio-keys` group of buttons or keys defined at
28 The key mapping in the sample is as follows:
30 - ``INPUT_KEY_0``: left button
31 - ``INPUT_KEY_1``: right button
[all …]
|
| /Zephyr-latest/boards/ti/msp_exp432p401r_launchxl/doc/ |
| D | index.rst | 6 The SimpleLink MSP‐EXP432P401R LaunchPad development kit is an easy-to-use evaluation
8 developing on the SimpleLink MSP432 low-power + performance ARM |reg| 32-bit Cortex |reg|-M4F
14 * Low-power ARM Cortex-M4F MSP432P401R
15 * 40-pin LaunchPad development kit standard that leverages the BoosterPack plug-in module ecosystem
16 * XDS110-ET, an open-source onboard debug probe featuring EnergyTrace+ technology and application
21 Details on the MSP-EXP432P401R LaunchXL development board can be found in the
22 MSP-EXP432P401R LaunchXL User's Guide.
27 * The on-board 32-kHz crystal allows for lower LPM3 sleep currents and a higher-precision clock sou…
28 …default internal 32-kHz REFOCLK. Therefore, the presence of the crystal allows the full range of l…
30 * The on-board 48-MHz crystal allows the device to run at its maximum operating speed for MCLK and …
[all …]
|
| /Zephyr-latest/boards/phytec/phyboard_nash/doc/ |
| D | index.rst | 3 phyBOARD-Nash i.MX93
9 The phyBOARD-Nash is based on the phyCORE-i.MX93 SoM is based on the NXP i.MX93
11 development or in the final product. It is an entry-level development board,
13 amount of resources in more specific designs.
15 i.MX93 MPU is composed of one cluster of 2x Cortex-A55 cores and a single
16 Cortex-M33 core. Zephyr OS is ported to run on one of the Cortex-A55 core as
17 well as the Cortex-M33 core.
19 - Memory:
21 - RAM: 512 MB - 2GB LPDDR4
22 - EEPROM: 4 kB - 32 kB
[all …]
|
| /Zephyr-latest/boards/ct/ctcc/doc/ |
| D | index.rst | 10 using USB device with on-board nRF52840 SoC
12 * The Connectivity Card nRF9161 enables LTE-M/NB-IoT and DECT NR+ over mPCIe or M.2
13 using on-board USB-UART converter
23 * RADIO (LTE-M/NB-IoT and DECT NR+) (only nRF9161)
26 * :abbr:`UARTE (Universal asynchronous receiver-transmitter with EasyDMA)` (only nRF9161)
54 * The ``ctcc/nrf9161`` board target has one external SPI NOR 64Mbit memory and one on-board USB-UART
63 +-----------+------------+----------------------+
66 | CLOCK | on-chip | clock_control |
67 +-----------+------------+----------------------+
68 | FLASH | on-chip | flash |
[all …]
|
| /Zephyr-latest/boards/st/steval_fcu001v1/doc/ |
| D | index.rst | 6 The STEVAL-FCU001V1 is a Cortex M4 MCU-based flight controller unit for toy quad-copter drones.
13 - STM32F401CC in UFQFPN48 package
14 - ARM |reg| 32-bit Cortex |reg|-M4 MCU with FPU
15 - 84MHz max MCU frequency
16 - VDD from 1.7 V to 3.6 V
17 - 256 KB FLASH
18 - 64 KB SRAM
19 - General Purpose Timers
20 - Watchdog Timers (2)
21 - On board sensors:
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | bc12.rst | 15 should not be confused with the USB-C Power Delivery, which also uses the
19 charger capability on USB type C ports when the attached type-C partner does not
28 Charging Downstream Port Rated Current ICDP 1.5 - 5.0 A
30 Dedicated Charging Port Rated Current IDCP 1.5 - 5.0 A
36 limited by the IDEV_CHG parameter. So the BC1.2 support is capped at 1.5 A in
37 the Zephyr implementation when using portable-device mode.
39 …. _BC1.2 Specification: https://www.usb.org/document-library/battery-charging-v12-spec-and-adopter…
48 either a disconnected, portable-device, or charging port mode.
60 For portable-device mode, the BC1.2 driver powers up the detection chip and
76 specified by a devicetree property. If the driver supports detection of plug and
|
| /Zephyr-latest/include/zephyr/usb_c/ |
| D | tcpci.h | 3 * SPDX-License-Identifier: Apache-2.0
15 * Registers and fields are compliant to the Type-C Port Controller Interface
19 /** Register address - vendor id */
22 /** Register address - product id */
25 /** Register address - version of TCPC */
28 /** Register address - USB TypeC version */
30 /** Mask for major part of type-c release supported */
32 /** Macro to extract the major part of type-c release supported */
34 /** Mask for minor part of type-c release supported */
36 /** Macro to extract the minor part of type-c release supported */
[all …]
|
| /Zephyr-latest/boards/rakwireless/rak11720/doc/ |
| D | index.rst | 4 It is based on the powerful ultra-low power Apollo3 Blue SoC (AMA3B1KK-KBR-B0)
7 The AMA3B1KK-KBR-B0 has an integrated Bluetooth Low Energy transceiver
9 comes in the same size and footprint as our RAK3172 module which gives
18 supply and programming/debug interface is the base to plug a
19 RAK11722 (WisBlock Core module with the RAK11720) in.
21 - Apollo3 Blue SoC with up to 96 MHz operating frequency
22 - ARM® Cortex® M4F core
23 - 16 kB 2-way Associative/Direct-Mapped Cache per core
24 - Up to 1 MB of flash memory for code/data
25 - Up to 384 KB of low leakage / low power RAM for code/data
[all …]
|
| /Zephyr-latest/boards/ite/it8xxx2_evb/doc/ |
| D | index.rst | 9 The IT8XXX2 is a 32-bit RISC-V Micro-controller.
26 - RISC-V RV32IMAFC instruction set
27 - 4KB instruction cache size
28 - 60KB SDRAM in total
29 - Built-in 32.768 kHz clock generator
30 - PWM, eSPI, LPC, FLASH, UART, GPIO, Timer, Watchdog, ADC, JTAG
31 - 6 SMBus channels, with 3 DMA controllers, compatible with I2C
32 - SPI master/slave
33 - USB Type-c CC Logic
34 - USB Power Delivery
[all …]
|
| /Zephyr-latest/boards/openisa/rv32m1_vega/doc/ |
| D | index.rst | 8 The VEGAboard contains the RV32M1 SoC, featuring two RISC-V CPUs,
9 on-die XIP flash, and a full complement of peripherals, including a
10 2.4 GHz multi-protocol radio. It also has built-in sensors and
11 Arduino-style expansion connectors.
13 The two RISC-V CPUs are named RI5CY and ZERO-RISCY, and are
15 `RI5CY`_ and `ZERO-RISCY`_. RI5CY is the "main" core; it has more
16 flash and RAM as well as a more powerful CPU design. ZERO-RISCY is a
17 "secondary" core. The main ZERO-RISCY use-case is as a wireless
30 RV32M1 multi-core SoC:
32 - 1 MiB flash and 192 KiB SRAM (RI5CY core)
[all …]
|
