Searched refs:with (Results 2151 – 2175 of 2945) sorted by relevance
1...<<81828384858687888990>>...118
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | ec_host_cmd.rst | 9 communicate with a target embedded controller (EC). The EC Host command subsystem implements the
32 SHI (Serial Host Interface) is different to this because it is used only for communication with a
127 with the data buffers
|
| D | smp_transport.rst | 38 prefixing each frame with two byte marker and terminating it with newline.
74 entire body with preceding length and following it CRC in a single
|
| /Zephyr-latest/doc/services/storage/secure_storage/ |
| D | index.rst | 14 The secure storage subsystem makes the PSA Secure Storage API available on all board targets with
18 Board targets with :ref:`tfm` enabled (ending in ``/ns``), for instance,
32 * does not aim at full compliance with the specification.
|
| /Zephyr-latest/boards/norik/octopus_io_board/doc/ |
| D | index.rst | 25 * :abbr:`UARTE (Universal asynchronous receiver-transmitter with EasyDMA)`
95 Some examples don't require non secure mode and can be built with ``octopus_io_board/nrf9160`` boar…
110 Replace <tty_device> with the port where the Octopus IO-Board can be found. For example, under Linu…
|
| /Zephyr-latest/boards/ti/cc26x2r1_launchxl/doc/ |
| D | index.rst | 15 The board is equipped with two LEDs, two push buttons and BoosterPack connectors
33 aligns with the LaunchPad standard.
148 Replace :code:`<tty_device>` with the port where the XDS110 application
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | socket_service.rst | 32 Define a network socket service. This socket service is created with extern
37 Define a network socket service with static scope. This socket service can only
86 /* Do something with the received data. The pev variable contains
|
| /Zephyr-latest/boards/lilygo/ttgo_t7v1_5/doc/ |
| D | index.rst | 18 This board is based on the ESP32-WROVER-E module with 4MB of flash (there
103 bootstrap the board with the ESP32 SoC.
162 The usual ``flash`` target will work with the ``ttgo_t7v1_5`` board
|
| /Zephyr-latest/boards/cdns/xt-sim/doc/ |
| D | index.rst | 33 releases (with multilib support).
160 The Xtensa executable can be run in the simulator either with a standalone core,
161 or with a core connected to simulated peripherals.
|
| /Zephyr-latest/boards/adi/eval_adin1110ebz/doc/ |
| D | index.rst | 8 with devices across 1.7km of cable.
20 A small prototyping area and test points are provided for experimentation with alternative cable
132 program to connect with your ADI board. For example:
|
| /Zephyr-latest/boards/ti/cc1352r1_launchxl/doc/ |
| D | index.rst | 15 The board is equipped with two LEDs, two push buttons and BoosterPack connectors
33 aligns with the LaunchPad standard.
142 Replace :code:`<tty_device>` with the port where the XDS110 application
|
| /Zephyr-latest/doc/develop/api/ |
| D | design_guidelines.rst | 18 associated with the callback. In the case of device drivers this
48 The assumption here, as with :c:struct:`gpio_callback`, is that the
76 developer in coordination with the community must determine whether
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 37 * A specific configuration context can be provided along with the ``can`` fixture separated by a
40 (i.e. run ``twister`` with the ``--pytest-args=--can-context=zcan0`` argument to use the ``zcan0``
91 Make sure the CAN bus is terminated with 120 ohm resistors at both ends. The termination resistor
|
| /Zephyr-latest/boards/adi/max32655evkit/doc/ |
| D | index.rst | 28 - Flexible Low-Power Modes with 7.3728MHz System Clock Option
55 - RTC with Wake-Up Timer
178 a Segger J-Link with Segger's native tooling by overriding the runner,
|
| /Zephyr-latest/samples/drivers/counter/maxim_ds3231/ |
| D | README.rst | 5 Interact with a DS3231 real-time clock using the counter API and dedicated driver API.
45 and the clock will be set to align that time with the time of the boot,
112 with a similar accuracy.
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 18 should comply with these principles.
33 We begin with an overview of secure design as it relates to
166 - least privilege (processes should operate with the least privilege
179 - input validation with allowlists (inputs should typically be checked
187 A "primary developer" in a project is anyone who is familiar with the
244 shall request the developer with vulnerability knowledge, or the
266 duration, with a default being a project-decided value. However,
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 13 mechanisms, with some important caveats, described in the following sections. It
161 Precompiled library blobs must be in a data format which is compatible with and
172 example, a target with a zephyr kernel clock driver that is just a porting layer
173 around a library blob would not be bootable with open source software.
186 for any target with upstream Zephyr support.
237 A request for integration with binary blobs must be made by creating a new
238 issue in the Zephyr project issue tracking system on GitHub with details
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 12 * x86_32 ISA with System V ABI
13 * ARMv7-M ISA with Thumb2 instruction set and ARM Embedded ABI (aeabi)
360 in the table has nothing to do with priority of an IRQ: priorities are
371 architectures with regards to interrupt controllers.
398 The kernel depends on a few functions that can be implemented with very few
424 The kernel provides support for CPU power management with two functions:
428 instruction for the architecture with interrupts unlocked, for example
497 is defined in architecture headers with :c:macro:`ARCH_STACK_PTR_ALIGN` and
502 - "kernel" stacks defined with :c:macro:`K_KERNEL_STACK_DEFINE()` and related
531 Stack objects all have the following layout, with some regions potentially
[all …]
|
| D | soc_porting.rst | 12 It is expected that you are familiar with the board concept in Zephyr.
20 - SoC family: a wider group of SoCs with similar characteristics.
36 contributed a SoC with identical name. If the SoC name is already in use, then
71 Replace ``<soc-name>`` with your SoC's name.
291 a given ``soc1`` with two clusters ``clusterA`` and ``clusterB``, then this
|
| /Zephyr-latest/samples/net/mqtt_publisher/ |
| D | README.rst | 29 was tested with mosquitto 1.3.4.
144 create the certificates and to set them up with the server.
148 try this sample with TLS enabled, by following these steps:
189 Use the following command to run it on your host with the default port:
230 This is the output from the FRDM UART console, with:
379 The IPv4 Wi-Fi support can be enabled in the sample with
|
| /Zephyr-latest/boards/acrn/acrn/doc/ |
| D | index.rst | 73 Zephyr image is ID zero. This allows you to launch ACRN with just one
107 ``zephyr.elf`` file. You can find this with binutils, for example:
154 If you plan to run Zephyr with one CPU only, you can skip it.
181 assignments with other guests. But for testing Zephyr simply using
264 with GRUB plugins or menus or timeouts:
290 You can see the Zephyr (vm 0) console output with the "vm_console"
|
| /Zephyr-latest/boards/snps/emsdp/doc/ |
| D | index.rst | 85 MISO with MOSI, DW SPI register is configured to internally connect them. This test
86 use two different speed to verify data transfer with asynchronous functionality.
91 result with buffer to check functionality.
113 Note that since the controllers that are mapped to the MikroBUS are shared with the Arduino
133 * Terminal emulator software for use with the USB-UART. Suggestion:
|
| /Zephyr-latest/cmake/modules/ |
| D | boards.cmake | 28 # replaced with underscores
30 # replaced with underscores
31 # - BOARD_DIR: Board directory with the implementation for selected board
33 # - BOARD_ROOT: BOARD_ROOT with ZEPHYR_BASE appended
269 # Allow users to omit the SoC when building for a board with a single SoC.
|
| /Zephyr-latest/boards/nxp/imx8mp_evk/doc/ |
| D | index.rst | 100 This board configuration uses a single serial communication channel with the
134 for example, with the :zephyr:code-sample:`synchronization` sample:
142 This will build an image with the synchronization sample app, boot it and
230 The device tree must inlcude CM7 dts node with compatible string "fsl,imx8mn-cm7",
291 2. Boot Linux kernel with specified dtb and then boot Zephyr by using remoteproc:
|
| /Zephyr-latest/tests/benchmarks/thread_metric/ |
| D | thread_metric_readme.txt | 16 from testing with different RTOS products should be scaled
126 2.5. Test execution with Twister tool
136 to collect measurements 3 times with 30 sec. intervals on most of the
194 This function creates a queue with a capacity to hold at least
231 is returned along with the pointer to the allocated memory
|
| /Zephyr-latest/boards/st/nucleo_f207zg/ |
| D | nucleo_f207zg.dts | 208 * nvs subsystem requires 2 sectors with a max total of 32K
210 * partition, which is compatible with mcuboot usage.
|
1...<<81828384858687888990>>...118
