Searched refs:and (Results 626 – 650 of 3855) sorted by relevance
1...<<21222324252627282930>>...155
| /Zephyr-latest/samples/net/sockets/can/ |
| D | README.rst | 5 Send and receive raw CAN frames using BSD sockets API.
10 The socket CAN sample is a server/client application that sends and receives
16 interface, and then installs a CAN filter to the socket so that the
18 * Receive function which starts to listen the CAN socket and prints
31 Building and Running
|
| /Zephyr-latest/samples/posix/uname/ |
| D | README.rst | 4 Use ``uname()`` to acquire system information and output it to the console.
9 In this sample application, the POSIX `uname()`_ function is used to acquire system information and
10 it is output to the console. Additionally, uname is added as a shell command and system information
13 Building and Running
16 This project outputs to the console. It can be built and executed on QEMU as follows:
|
| /Zephyr-latest/samples/subsys/dap/ |
| D | README.rst | 9 This sample app demonstrates use of a SWDP interface driver and CMSIS DAP
18 and optionally ``nRESET`` to ``reset``. The optional ``noe`` pin is used to enable the port,
21 Building and Running
24 The following commands build and flash DAP sample.
32 Connect HIC to the target and try some pyOCD commands, for example:
|
| /Zephyr-latest/tests/lib/mem_alloc/ |
| D | README.txt | 8 NEWLIB and MINIMAL_LIB.
10 or non-functional, and is NOT intended to be a comprehensive test suite
15 Building and Running Project:
17 This project outputs to the console. It can be built and executed
33 # and restore pre-defined configuration info
|
| /Zephyr-latest/samples/arch/smp/pi/ |
| D | README.rst | 8 This sample application calculates Pi independently in many threads, and
18 number of digits calculated (``DIGITS_NUM``), and the
21 Building and Running
24 This project outputs Pi values calculated by each thread and in the end total time
25 required for all the calculation to be done. It can be built and executed
|
| /Zephyr-latest/samples/subsys/usb/audio/headphones_microphone/ |
| D | README.rst | 13 Input (Microphone) and one Output (Headphones) device.
15 Building and Running
20 software and hardware specific information which allow to fully
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.
|
| /Zephyr-latest/samples/sensor/vcnl4040/ |
| D | README.rst | 2 :name: VCNL4040 Proximity and Ambient Light Sensor
5 Get proximity and ambient light data from a VCNL4040 sensor (polling & trigger mode).
10 This sample periodically measures proximity and light for
12 is enabled with the high threshold value of 127 and data is fetched based
26 Building and Running
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 12 The :dfn:`Zephyr bus - zbus` is a lightweight and flexible software bus enabling a simple way for
22 communication possible. The bus implements message-passing and publish/subscribe communication
26 messages. Additionally, besides other actions, threads can publish and observe channels. When a
33 from each other because they only use zbus channels and do not need to know each other to talk.
44 * Set of channels that consists of the control metadata information, and the message itself;
49 * Threads (subscribers and message subscribers) and callbacks (listeners) publishing, reading, and
58 The bus makes the publish, read, claim, finish, notify, and subscribe actions available over
59 channels. Publishing, reading, claiming, and finishing are available in all RTOS thread contexts,
60 including ISRs. The publish and read operations are simple and fast; the procedure is channel
61 locking followed by a memory copy to and from a shared memory region and then a channel unlocking.
[all …]
|
| /Zephyr-latest/boards/nxp/mimxrt1062_fmurt6/doc/ |
| D | index.rst | 7 processor series and expands the i.MX RT series to three scalable families.
11 ideal for real-time applications such as High-Speed GPIO, CAN FD, and
39 - Left and right speaker out connectors
60 For more information about the MIMXRT1062 SoC and MIMXRT1062-FMURT6 board, see
122 Connections and I/Os
242 ``LPUART8 and 2`` for GPS/MAG, ``LPUART3 and 4`` for Telemetry and the remaining are not used.
244 Programming and Debugging
247 Build and flash applications as usual (see :ref:`build_an_application` and
253 A debug probe is used for both flashing and debugging the board. This board is
264 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search
[all …]
|
| /Zephyr-latest/boards/antmicro/myra_sip_baseboard/doc/ |
| D | index.rst | 7 128kB FRAM, and FTDI FT231XQ USB to UART converter. The board is equipped with temperature,
8 humidity, and pressure sensors, designed to help monitor conditions in server rooms.
10 The sensors are placed on a separate island that is detachable from the main PCB and can be
11 installed directly in the required place. It provides local storage for data logging and a battery
21 - USB-C Connector for data and power
44 - RTC: Real-time clock with hardware calendar, alarms, and calibration
47 - 1x 32-bit timer and 2x 16-bit timers with up to 4x IC/OC/PWM or pulse counter and quadrature
59 - 512 KB Flash memory with ECC and PCROP protection
63 - 3x 16-bit ADCs with up to 36 channels, hardware oversampling, and resolution up to 16-bit
67 - Internal temperature sensor and voltage reference with support for three output voltages
[all …]
|
| /Zephyr-latest/boards/beagle/beaglev_fire/doc/ |
| D | index.rst | 8 horizons for developers, tinkerers, and the open-source community to explore the vast potential of
9 RISC-V architecture and FPGA technology. It has the same P8 & P9 cape header pins as BeagleBone
11 Built around the powerful and energy-efficient RISC-V instruction set architecture (ISA) along with
13 hobbyists, and researchers to explore and experiment with RISC-V technology.
34 In order to upload the application to the device, you'll need OpenOCD and GDB
37 Download and installation instructions can be found on
39 <https://www.microchip.com/en-us/products/fpgas-and-plds/fpga-and-soc-design-tools/programming-and-…
63 Leave it running, and in a different terminal, use GDB to upload the binary to
74 and load the binary:
106 …rd that's connected over USB and UART, interrupting the HSS boot process with a key press, and the…
|
| /Zephyr-latest/boards/nxp/ucans32k1sic/doc/ |
| D | index.rst | 7 board designed for both automotive and industrial applications. The UCANS32K1SIC
8 provides two CAN SIC interfaces and is based on the 32-bit Arm Cortex-M4F
20 - eDMA, 12-bit ADC, MPU, ECC and more.
25 - JST-GH DroneCode compliant standard connectors and I/O headers
26 - user RGB LED and button.
28 More information about the hardware and design resources can be found at
55 Connections and IOs
124 Programming and Debugging
130 This board configuration supports `Lauterbach TRACE32`_ and `SEGGER J-Link`_
131 West runners for flashing and debugging applications. Follow the steps described
[all …]
|
| /Zephyr-latest/boards/nxp/lpcxpresso55s06/doc/ |
| D | index.rst | 10 with a PMod/host interface port and MikroElektronika Click module
17 - 256 KB flash and 96 KB SRAM on-chip
22 - Reset, ISP, wake, and user buttons for easy testing of software functionality
28 For more information about the LPC55S06 SoC and LPCXPresso55S06 board, see:
74 Connections and IOs
112 and the remaining are not used.
114 Programming and Debugging
117 Build and flash applications as usual (see :ref:`build_an_application`
118 and :ref:`application_run` for more details).
123 A debug probe is used for both flashing and debugging the board. This
[all …]
|
| /Zephyr-latest/doc/develop/languages/c/ |
| D | picolibc.rst | 7 embedded systems, targeting `C17 (ISO/IEC 9899:2018)`_ and `POSIX 2018
9 source project which is provided for Zephyr as a module, and included
19 implemented in :file:`lib/libc/picolibc/libc-hooks.c` and translate
60 For every release of Zephyr, the toolchain-bundled Picolibc and the
90 Picolibc supports all standard C formatted input and output functions,
91 including :c:func:`printf`, :c:func:`fprintf`, :c:func:`sprintf` and
94 Picolibc formatted input and output function implementation supports
95 all format specifiers defined by the C17 and POSIX 2018 standards with
105 Printk, cbprintf and friends
111 * printk, snprintk and vsnprintk
[all …]
|
| /Zephyr-latest/boards/st/nucleo_h7a3zi_q/doc/ |
| D | index.rst | 6 The STM32 Nucleo-144 boards offer combinations of performance and power that
7 provide an affordable and flexible way for users to build prototypes and try
19 libraries and examples available with the STM32Cube MCU Package.
26 - 2 user and reset push-buttons
37 - capability: mass storage, virtual COM port and debug port.
38 - Comprehensive free software libraries and examples available with the
64 - USB OTG Full Speed and High Speed(1)
89 and a ST morpho connector. Board is configured as follows:
108 Nucleo H7A3ZI-Q board has 4 UARTs and 4 USARTs. The Zephyr console output is
111 Programming and Debugging
[all …]
|
| /Zephyr-latest/boards/arm/v2m_musca_b1/doc/ |
| D | index.rst | 11 CPU and the following devices:
68 - nSRST: Cortex-M33 system reset and CoreSight debug reset.
106 Musca B1 is a Cortex-M33 based SoC and has 15 fixed exceptions and 77 IRQs.
111 Zephyr provides handlers for exceptions 1-7, 11, 12, 14, and 15, as listed
146 | | | | and IRQ offloading |
225 V2M Musca B1 has a 32.768kHz crystal clock. The clock goes to a PLL and is
226 multiplied to drive the Cortex-M33 processors and SSE-200 subsystem. The
235 for RX/TX and no flow control (CTS/RTS) or FIFO. The Zephyr console output,
242 secure and non-secure memory maps. By default, all of the memory space is
244 - Secure and Non-secure peripherals via the Peripheral Protection Controller
[all …]
|
| /Zephyr-latest/doc/develop/test/ |
| D | ztest.rst | 7 to be used during development. It provides basic assertion macros and a generic
22 :c:func:`ztest_run_all` and should return a boolean to decide if the suite should run.
24 will be called and run once per test suite run.
54 the ``suite_name`` and ``test_name``. You can then access the passed parameter within
115 accessible. This is because the fixture memory is owned and initialized by kernel space. The Ztest
116 framework provides the :c:macro:`ZTEST_DMEM` and :c:macro:`ZTEST_BMEM` macros for use of such
148 In this example, the above tests should be marked as failed and skipped respectively. Instead,
154 Test rules are a way to run the same logic for every test and every suite. There are a lot of cases
185 state that the tests depend on and that state either cannot be replicated or is difficult to
223 sample folder to ``tests/foo/bar`` and edit files there adjusting for your test
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | access.rst | 8 into elements and models, which are implemented by the application.
16 assigned its own unicast address, and may only contain one of each type of
18 node behavior. For instance, a node that contains a sensor, two lights and a
23 The node's element and model structure is specified in the node composition
26 :ref:`bluetooth_mesh_models`) and a set of models for implementing common
29 not specified by the Bluetooth SIG are vendor models, and must be tied to a
40 the minimum acceptable payload length and the callback to pass them to. Models
45 data, and cannot be changed at runtime. The end of the opcode list is
83 and calling :c:func:`bt_mesh_model_send`.
84 * By setting up a :c:struct:`bt_mesh_model_pub` structure and calling
[all …]
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.7.rst | 10 This release is the last non-maintenance 3.x release and, as such, will be the next
16 It changes the way both SoCs and boards are named, defined and constructed in Zephyr.
18 * A long-awaited :ref:`HTTP Server <http_server_interface>` library, and associated service API,
19 allow to easily implement HTTP/1.1 and HTTP/2 servers in Zephyr. Resources can be registered
20 statically or dynamically, and WebSocket support is included.
23 Options and Option groups required for :ref:`PSE51 <posix_aep_pse51>`,
24 :ref:`PSE52 <posix_aep_pse52>`, and :ref:`PSE53 <posix_aep_pse53>`.
26 Gateway (AG), Advanced Audio Distribution Profile (A2DP), and Audio/Video Distribution Transport
29 :ref:`read-then-decode approach <sensor-read-and-decode>` that enables more types of sensors and
31 * A new :ref:`LLEXT Extension Developer Kit (EDK) <llext_build_edk>` makes it easier to develop and
[all …]
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 10 your application and allows :ref:`tools` running on a host to visualize the inner-working of
11 the kernel and various subsystems.
19 4. Deciding on and writing the I/O transport mechanics,
21 6. Writing custom ad-hoc tools for filtering and presentation.
26 Different formats, transports and host tools are available and supported in
31 interface between payload/format (Top Layer) and the transport mechanics
32 (bottom Layer) is generic and efficient enough to model these. See the
56 Common Trace Format, CTF, is an open format and language to describe trace
57 formats. This enables tool reuse, of which line-textual (babeltrace) and
65 CTF allows us to formally describe application specific payload and the
[all …]
|
| /Zephyr-latest/boards/rakwireless/rak4631/doc/ |
| D | index.rst | 9 (Bluetooth Low Energy) and the newest LoRa transceiver
21 supply for the RAK4631 module and has the
28 - iPEX connectors for the LORA antenna and BLE antenna.
38 Connections and IOs
47 Programming and Debugging
59 "J-Link Software and Documentation Pack" and install the "J-Link Software
60 and Documentation pack for Linux". The application JLinkExe needs to be
79 Then build and flash the :zephyr:code-sample:`hello_world` application.
|
| /Zephyr-latest/boards/waveshare/esp32s3_touch_lcd_1_28/doc/ |
| D | index.rst | 7 suitable to build watches or similar projects. This board integrates complete Wi-Fi and Bluetooth
8 Low Energy functions, an accelerometer and gyroscope, a battery charger and GPIO extension port.
14 and Bluetooth® Low Energy (Bluetooth LE). It consists of high-performance dual-core microprocessor
16 RF module, and numerous peripherals.
25 - Bluetooth LE 5.0 with long-range support and up to 2Mbps data rate
38 - Ultra-Low-Power (ULP) coprocessors: ULP-RISC-V and ULP-FSM
52 and/or exchanging data over OpenAMP framework. See :zephyr:code-sample-category:`ipc` folder as cod…
65 Espressif HAL requires WiFi and Bluetooth binary blobs in order work. Run the command
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_pkt_filter.rst | 14 construct custom rules for accepting and/or denying packet transmission
15 and reception. This can be used to create a basic firewall, control
21 Both the transmission and reception paths may have a list of filter rules.
22 Each rule is made of a set of conditions and a packet outcome. Every packet
25 as specified by the current rule and no more rules are considered. If one
34 :c:func:`npf_append_rule()`, and :c:func:`npf_remove_rule()`.
36 and ``npf_recv_rules`` for incoming packets.
49 to statically define condition instances for various conditions, and
70 The above would accept IP packets that are 200 bytes or smaller, and drop
|
| /Zephyr-latest/arch/common/ |
| D | Kconfig | 7 bool "Semihosting support for ARM and RISC-V targets"
11 RISC-V target to communicate and use the Input/Output facilities on
16 This option is compatible with hardware and with QEMU, through the
44 The ARMv6-M, ARMv7-M, and ARMv8-R MPU MPU architecture requires a power-of-two
45 alignment of MPU region base address and size.
48 to have power-of-two alignment for base address and region size.
50 The ARMv8-M and ARMv8-R MPU requires the active MPU regions be non-overlapping.
53 guard, user thread stack, and application memory domains), if the
67 of full partitioning the default behavior for the ARMv8-M and ARMv8-R MPU
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 1 .. _sensor-fetch-and-get:
3 Fetch and Get
6 The stable and long existing APIs for reading sensor data and handling triggers
16 has been obtained and stored into the driver instance's private data.
23 It should be noted that calling fetch and get from multiple contexts without
24 a locking mechanism is undefined and most sensor drivers do not attempt to
31 Using fetch and get sensor can be read in a polling manner from software threads.
47 Triggers may not be set from user mode threads, and the callback is not
|
1...<<21222324252627282930>>...155
