Home
last modified time | relevance | path

Searched refs:can (Results 351 – 375 of 2493) sorted by relevance

1...<<11121314151617181920>>...100

/Zephyr-latest/samples/net/openthread/coprocessor/
DREADME.rst12 The Co-Processor can act in two variants: Network Co-Processor (NCP) and Radio
16 Router can be obtained by following
21 The source code for this sample application can be found at:
69 product is based on NXP K64 and AT86RF233. This file can be used as an
/Zephyr-latest/tests/bsim/bluetooth/ll/edtt/
DREADME.txt7 Much more info about the tool can be found in https://github.com/EDTTool/EDTT
35 EDTT folder. You can do this by adding it to your `~/.bashrc`, `~/.zephyrrc`,
45 To compile both in an automated way you can just use the `compile.sh` (see
48 To run the tests you can either run one of the provided scripts, or run by
/Zephyr-latest/boards/nxp/rd_rw612_bga/
Dpre_dt_board.cmake4 # Suppress "spi_bus_bridge" as flexcomm node can be used as a SPI device.
/Zephyr-latest/boards/nxp/frdm_rw612/
Dpre_dt_board.cmake4 # Suppress "spi_bus_bridge" as flexcomm node can be used as a SPI device.
/Zephyr-latest/samples/basic/minimal/
DKconfig6 bool "Do print from the main thread which can be checked"
/Zephyr-latest/doc/services/pm/
Ddevice.rst8 save energy when they are not being used. This feature can be enabled by
26 devices, the decision to suspend or resume a device can also be
29 Each layer—device drivers, subsystems, and applications—can operate
42 and network, can also influence device power management.
49 - **Applications** running on Zephyr can impact device
59 the subsystem can use device runtime power management to ensure that
77 It can be enabled by setting :kconfig:option:`CONFIG_PM_DEVICE_SYSTEM_MANAGED`.
117 When using :ref:`pm-system`, device transitions can be run from the idle thread.
119 APIs **must** check whether they can do so with :c:func:`k_can_yield`.
121 This method of device power management can be useful in the following scenarios:
[all …]
/Zephyr-latest/doc/build/dts/api/
Dapi.rst7 based. Use of these macros has no impact on scheduling. They can be used from
11 macro named ``DT_DRV_COMPAT`` to be defined before they can be used; these are
13 :ref:`device drivers <device_model_api>`, though they can be used outside of
24 The APIs in this section can be used anywhere and do not require
31 time. While node identifiers are not C values, you can use them to access
35 The root node ``/`` has node identifier ``DT_ROOT``. You can create node
39 There are also :c:macro:`DT_PARENT` and :c:macro:`DT_CHILD` macros which can be
52 The following general-purpose macros can be used to access node properties.
56 Property values can be read using these macros even if the node is disabled,
68 devicetree specification, these macros can be used even for nodes without
[all …]
/Zephyr-latest/boards/shields/inventek_eswifi/doc/
Dindex.rst11 devices can run Cypress WICED or Inventek's IWIN (Inventek Systems Wireless
17 user can reprogram the modules to switch from one interface type to another
28 can use 5V from Arduino header, if board provide it, J17 position 1-2.
29 Otherwise, J17 2-3 will select USB-5V. More information can be found at
47 shield. These signals marked as optional can help on development. The current
48 driver do not handle that signals and are simple suggestions and can be left
117 To keep simple, you can keep only the WIFI interface enabled at
144 shell to scan local Wireless networks. With the password you can pick,
/Zephyr-latest/boards/seeed/xiao_esp32c6/doc/
Dindex.rst7 It consists of a high-performance (HP) 32-bit RISC-V processor, which can be clocked up to 160 MHz,
8 and a low-power (LP) 32-bit RISC-V processor, which can be clocked up to 20 MHz.
77 User can select the MCUboot bootloader by adding the following line
101 images. But it can be configured to create other kind of images.
130 For that reason, images can be built one at a time using traditional build.
176 the project. The custom OpenOCD can be obtained at `OpenOCD ESP32`_.
178 The Zephyr SDK uses a bundled version of OpenOCD by default. You can overwrite that behavior by add…
190 You can debug an application in the usual way. Here is an example for the :zephyr:code-sample:`hell…
/Zephyr-latest/doc/connectivity/networking/api/
Dmqtt_sn.rst17 but others like Bluetooth, UDP or even a UART can be used just as well.
20 library can be enabled with :kconfig:option:`CONFIG_MQTT_SN_LIB` Kconfig option
22 1.2. The Zephyr MQTT-SN implementation can be used with any message-based transport,
30 The MQTT-SN spec v1.2 can be found here:
48 Multiple MQTT-SN client instances can be created in the application and managed
72 The client context structure needs to be initialized and set up before it can be
106 After the Gateway address has been defined or found, the MQTT-SN client can
139 The connection can be closed by calling the :c:func:`mqtt_sn_disconnect` function. This
/Zephyr-latest/boards/weact/mini_stm32h7b0/doc/
Dindex.rst29 More information about the board can be found on the `Mini_STM32H7B0 website`_.
66 More information about STM32H7BO can be found here:
101 The STM32H7B0VB System Clock can be driven by an internal or external oscillator,
117 pins for the Serial Wire Debug (SWD) interface, which can be used to connect
130 bootloader mode and present itself as a USB DFU Mode device. You can program
162 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
181 You can build and flash the examples to make sure Zephyr is running correctly on
182 your board. The LED definitions can be found in
/Zephyr-latest/boards/weact/stm32h5_core/doc/
Dindex.rst24 More information about the board can be found on the `WeAct GitHub`_.
64 More information about STM32H562RG can be found here:
91 The STM32H562RG System Clock can be driven by an internal or external oscillator,
107 pins for the Serial Wire Debug (SWD) interface, which can be used to connect
120 bootloader mode and present itself as a USB DFU Mode device. You can program
151 Replace :code:`<tty_device>` with the port where the board can be found.
171 You can build and flash the examples to make sure Zephyr is running correctly on
172 your board. The LED definitions can be found in
/Zephyr-latest/doc/kernel/services/data_passing/
Dfifos.rst17 Any number of FIFOs can be defined (limited only by available RAM). Each FIFO is
25 A FIFO must be initialized before it can be used. This sets its queue to empty.
56 If desired, **multiple data items** can be added to a FIFO in a single operation
57 if they are chained together into a singly-linked list. This capability can be
61 them one at a time, and can be used to guarantee that anyone who removes
82 Alternatively, an empty FIFO can be defined and initialized at compile time
121 Additionally, a singly-linked list of data items can be added to a FIFO
124 Finally, a data item can be added to a FIFO with :c:func:`k_fifo_alloc_put`.
/Zephyr-latest/doc/kernel/services/other/
Dfloat.rst25 The kernel can be configured to provide only the floating point services
28 registers can be included or omitted, as desired.
45 On x86 platforms, the kernel initializes the floating point registers so they can
64 * FPU user: A thread that can use the standard floating point registers
66 * SSE user: A thread that can use both the standard floating point registers
70 so they can be used
91 * A statically-created ARM thread can be pretagged by passing the
94 * A dynamically-created ARM thread can be pretagged by passing the
112 an extra 72 bytes of stack space where the callee-saved FP context can
133 more, it can call :c:func:`k_float_disable`. This instructs the kernel
[all …]
/Zephyr-latest/boards/shields/ssd1306/doc/
Dindex.rst11 usually only four pins: GND, VCC, SCL and SDA. Display pins can be
34 This shield can only be used with a board which provides a configuration
/Zephyr-latest/samples/net/sockets/packet/
DREADME.rst21 packet every 5 seconds. You can use Wireshark to observe these
26 This sample can be built and executed on QEMU or native_sim board as
/Zephyr-latest/soc/nxp/imx/
DKconfig.defconfig7 # can override the defaults given here
/Zephyr-latest/tests/drivers/adc/adc_api/boards/
Dw5500_evb_pico2_rp2350a_m33.overlay7 /* W5500 EVB Pico2 can work the same configuration as W5500 EVB Pico */
/Zephyr-latest/boards/qorvo/decawave_dwm1001_dev/doc/
Dindex.rst18 Applications for the ``decawave_dwm1001_dev`` board configuration can be built,
26 and configure all the necessary software. Further information can be
40 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
/Zephyr-latest/boards/qorvo/decawave_dwm3001cdk/doc/
Dindex.rst18 Applications for the ``decawave_dwm3001cdk`` board target can be built, flashed,
26 and configure all the necessary software. Further information can be
40 Replace :code:`<tty_device>` with the port where the DWM3001CDK board can be
/Zephyr-latest/boards/bbc/microbit_v2/doc/
Dindex.rst12 25 LEDs, a microphone, two programmable buttons, and can be powered by either
16 More information about the board can be found at the `microbit website`_.
56 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
/Zephyr-latest/doc/services/tfm/
Drequirements.rst4 The following are some of the boards that can be used with TF-M:
51 You can install them via:
64 This can be installed on Linux via:
/Zephyr-latest/doc/develop/west/
Dindex.rst11 "pluggable": you can write your own west extension commands which add
21 Since west v0.8, you can also run west like this::
25 You can run ``west --help`` (or ``west -h`` for short) to get top-level help
/Zephyr-latest/tests/drivers/disk/disk_access/
DREADME.txt5 It is designed to test the NXP USDHC disk driver, but can be used for other
14 * Read test: Verifies that the driver can consistently read sectors. This test
22 * Write test: Verifies that the driver can consistently write sectors. This test
/Zephyr-latest/subsys/usb/device_next/class/
DKconfig.dfu30 attributes and means that the device can communicate over USB after the
34 int "Maximum number of bytes the device can accept per transfer"
56 Enable the built-in flash backend, which can serve up to two image

1...<<11121314151617181920>>...100