Searched refs:using (Results 51 – 75 of 1710) sorted by relevance
12345678910>>...69
| /Zephyr-latest/doc/services/profiling/ |
| D | perf.rst | 16 using the return address and frame pointer.
19 in the stack trace to function names using symbols from the ELF file, and to prints them in the
25 You can configure this module using the following options:
|
| /Zephyr-latest/boards/nxp/mimxrt1020_evk/ |
| D | CMakeLists.txt | 11 message(WARNING "It appears you are using the board definition for "
34 message(WARNING "You are using SDRAM as RAM but no device "
41 message(WARNING "You appear to be using the GPT hardware timer. "
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | power_management.rst | 10 channel states are mutable using :ref:`sensor-attribute`. While total device suspending and resume
11 can be done using the power management ref counting APIs if the device implements the necessary
15 :ref:`pm-device-runtime` using explicit calls at an application level to :c:func:`pm_device_runtime…
|
| /Zephyr-latest/samples/drivers/i2c/rtio_loopback/ |
| D | README.rst | 5 Perform I2C transfers between I2C controller and custom I2C target using RTIO.
11 using RTIO. It uses up to two I2C controllers, acting as I2C controller and
34 that this could be the same controller. This is done using the devicetree
|
| /Zephyr-latest/drivers/gpio/ |
| D | Kconfig.emul | 14 using the regular GPIO callback API and the additional API
16 GPIO instance is accomplished using device tree and an example of
|
| /Zephyr-latest/samples/net/openthread/shell/ |
| D | README.rst | 5 Test Thread and IEEE 802.15.4 using the OpenThread shell.
11 boards using the OpenThread shell.
|
| /Zephyr-latest/samples/basic/hash_map/ |
| D | Kconfig | 15 Of course, using realloc(), we are limited by the amount of available
16 heap memory. For test scenarios using the Minimal C library, the heap
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_9.rst | 123 | | appears if an error is returned when using SMP version 2. |
126 | | non-zero (error condition) when using SMP version 2. |
129 | | using SMP version 1 or for SMP errors when using SMP version 2. |
|
| /Zephyr-latest/boards/nordic/nrf9131ek/doc/ |
| D | index.rst | 120 image. The Secure image can be built using either Zephyr or
122 using Zephyr. The two alternatives are described below.
126 By default the Secure image for nRF9131 is built using TF-M.
128 Building the Secure firmware using Zephyr
133 1. Build the Secure Zephyr application using ``-DBOARD=nrf9131ek/nrf9131`` and
135 2. Build the Non-Secure Zephyr application using ``-DBOARD=nrf9131ek/nrf9131/ns``.
141 The process to build the Secure firmware image using TF-M and the Non-Secure
142 firmware image using Zephyr requires the following action:
145 using ``-DBOARD=nrf9131ek/nrf9131/ns``.
171 and :ref:`application_run`), using ``-DBOARD=nrf9131ek/nrf9131``.
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-qual.rst | 12 The Zephyr Bluetooth host can be qualified using Bluetooth's PTS (Profile Tuning
13 Suite) software. It is originally a manual process, but is automated by using
|
| /Zephyr-latest/drivers/i2c/ |
| D | Kconfig.dw | 24 data transfers. All Tx operations are done using dma channel 0 and
25 all Rx operations are done using dma channel 1.
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | spsc_pbuf.rst | 14 Packets are added to the buffer using :c:func:`spsc_pbuf_write` which copies a
17 Packets are copied out of the buffer using :c:func:`spsc_pbuf_read`.
|
| /Zephyr-latest/tests/lib/hash_map/ |
| D | Kconfig | 15 Of course, using realloc(), we are limited by the amount of available
16 heap memory. For test scenarios using the Minimal C library, the heap
|
| /Zephyr-latest/samples/drivers/lcd_hd44780/ |
| D | README.rst | 5 Control an HD44780-based LCD display using GPIO pins.
10 generic LCD controller using GPIO pins to interface with
|
| /Zephyr-latest/tests/subsys/debug/cs_trace_defmt/ |
| D | README | 1 Test for decoder of frames encoded using Coresight Trace Formatter.
|
| /Zephyr-latest/boards/nxp/mimxrt1160_evk/ |
| D | CMakeLists.txt | 11 message(WARNING "It appears you are using the board definition for "
34 message(WARNING "You are using SDRAM as RAM but no device "
41 message(WARNING "You appear to be using the GPT hardware timer. "
|
| /Zephyr-latest/samples/sensor/sx9500/ |
| D | README.txt | 5 A simple example using the sx9500 SAR proximity sensor.
|
| /Zephyr-latest/samples/subsys/mgmt/mcumgr/smp_svr/ |
| D | README.rst | 53 If you want to try out Device Firmware Upgrade (DFU) over the air using
162 when using image management commands for updating firmware). This issue can be
169 Now that the SMP server is running on your board and you are able to communicate with it using a
175 * Build an MCUboot enabled application using sysbuild, see :ref:`smp_svr_sample_build`
176 * Upload the signed image using an MCUmgr client
177 * Listing the images on the device using an MCUmgr client
178 * Mark the uploaded image for testing using an MCUmgr client
179 * Reset the device remotely using an MCUmgr client
180 * Confirm the uploaded image using an MCUmgr client (optional)
223 device using the tool of your choice, which should print the status and hash values of each of
[all …]
|
| /Zephyr-latest/drivers/sensor/ti/tmp112/ |
| D | Kconfig | 24 When set extended mode can be selected using tmp112_attr_set
31 When set conversion rate can be set at runtime using sensor_attr_set
|
| /Zephyr-latest/boards/nxp/common/ |
| D | segger-ecc-systemview.rst | 8 Note that when using SEGGER SystemView or RTT with this SOC, the RTT control
11 symbol, which can be found using a debugger or by examining the ``zephyr.map``
|
| /Zephyr-latest/samples/modules/nanopb/ |
| D | README.rst | 4 Serialize and deserialize structured data using the nanopb module.
9 A simple protocol buffer sample using :ref:`nanopb_reference` for serializing structured data
|
| /Zephyr-latest/samples/net/sockets/echo/ |
| D | README.rst | 5 Implements a simple IPv4/IPv6 TCP echo server using BSD sockets.
11 server supporting both IPv4 and IPv6 and using a BSD Sockets compatible API.
44 to it. The application implements a single-threaded server using blocking
81 After having connected to an Access Point using the sample Wi-Fi shell,
|
| /Zephyr-latest/boards/nordic/nrf5340dk/doc/ |
| D | index.rst | 184 image for the application core. The Secure image can be built using either
186 images are always built using Zephyr. The two alternatives are described below.
191 using TF-M.
197 The process to build the Secure firmware image using TF-M and the Non-Secure
198 firmware image using Zephyr requires the following steps:
201 for the application core using ``-DBOARD=nrf5340dk/nrf5340/cpuapp/ns``.
218 2. Build the application firmware for the network core using
222 Building the Secure firmware using Zephyr
226 using Zephyr requires the following steps:
229 using ``-DBOARD=nrf5340dk/nrf5340/cpuapp`` and
[all …]
|
| /Zephyr-latest/samples/sysbuild/with_mcuboot/ |
| D | README.rst | 4 Build a Zephyr application + MCUboot using sysbuild.
8 A simple example that demonstrates how building a sample using sysbuild can
16 This sample automatically includes MCUboot as bootloader when built using
|
| /Zephyr-latest/boards/nxp/mimxrt1040_evk/ |
| D | CMakeLists.txt | 16 message(WARNING "It appears you are using the board definition for "
39 message(WARNING "You are using SDRAM as RAM but no device "
46 message(WARNING "You appear to be using the GPT hardware timer. "
|
12345678910>>...69
