Searched refs:and (Results 276 – 300 of 3855) sorted by relevance
1...<<11121314151617181920>>...155
| /Zephyr-latest/doc/ |
| D | glossary.rst | 12 (Application Program Interface) A defined set of routines and protocols for
19 and at least one CMakeLists.txt file.
28 A binary file that is loaded and executed by the board for which
30 Each application image contains both the application's code and the
34 of the system, initializes it, and runs as the system's sole application.
35 Both application code and kernel code execute as privileged code
42 A target system with a defined set of devices and capabilities,
43 which can load and execute an application image. It may be an actual
57 The human-readable name of a :term:`board`. Uniquely and descriptively
64 follow the :term:`board name` (and optionally :term:`board revision`) to
[all …]
|
| /Zephyr-latest/drivers/sensor/silabs/si7210/ |
| D | Kconfig | 1 # Si7210 Hall Effect Magnetic Position and Temperature Sensor configuration options
6 bool "Si7210 Hall Effect Magnetic Position and Temperature Sensor"
11 Enable driver for Si7210 Hall Effect Magnetic Position and Temperature Sensor.
|
| /Zephyr-latest/boards/silabs/radio_boards/ |
| D | index.rst | 17 development platform for application development and debugging of wireless
28 Wireless Starter Kits and Wireless Pro Kits are kits that bundle one or more
43 - On-board Segger J-Link debugger with USB and Ethernet interfaces
45 - 2 user buttons and 2 LEDs
47 - Si7021 Relative Humidity and Temperature Sensor
55 - On-board Segger J-Link debugger with USB and Ethernet interfaces
57 - 2 user buttons, joystick and 2 LEDs
59 - Si7021 Relative Humidity and Temperature Sensor
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-scope-purpose.rst | 3 Scope and purpose
7 hardware. The `Devicetree specification`_ defines its source and binary
17 As such, devicetree is both a hardware description language and a configuration
19 devicetree and Zephyr's other main configuration language, Kconfig.
21 There are two types of devicetree input files: *devicetree sources* and
24 <build_overview>` uses devicetree sources and bindings to produce a generated C
35 All Zephyr and application source code files can include and use
|
| /Zephyr-latest/boards/renesas/rcar_h3ulcb/doc/ |
| D | rcar_h3ulcb_a57.rst | 18 * 2 channels for HDMI1.4b output and 1channel for RGB888 output and 1channel for LVDS;
21 * USB3.0 x 2ch and USB2.0 x 3ch interfaces;
23 * two- and three-dimensional graphics engines;
28 * USB3.0 and USB2.0 interfaces;
33 Connections and IOs
61 | MMC | renesas_rcar_mmc | DMA and SCC |
69 Programming and Debugging
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 10 Bluetooth Mesh DFU implements a distribution mechanism for firmware images, and does not put any
12 to provide the qualifiable parts of the Bluetooth Mesh DFU specification, and leave the usage,
13 firmware validation and deployment to the application.
35 Target node is the receiver and user of the transferred firmware images. All its functionality is
37 Target nodes, and they will all be updated concurrently.
43 relies on an Initiator to give it a list of Target nodes and transfer parameters. The Distributor
44 functionality is implemented in two models, :ref:`bluetooth_mesh_dfd_srv` and
46 with the Initiator, and the :ref:`bluetooth_mesh_dfu_cli` is responsible for distributing the
51 :ref:`Provisioner <bluetooth_mesh_provisioning>` and :ref:`Configurator
53 Target nodes and their firmware, and will control (and initiate) all firmware updates. The
[all …]
|
| /Zephyr-latest/doc/develop/optimizations/ |
| D | tools.rst | 7 and :ref:`data_structure_tools` using different build system targets.
11 Footprint and Memory Usage
14 The build system offers 3 targets to view and analyse RAM, ROM and stack usage
15 in generated images. The tools run on the final image and give information
16 about size of symbols and code being used in both RAM and ROM. Additionally,
25 * Hidden - The RAM and ROM reports list all processing symbols with no matching
32 * No paths - The RAM and ROM reports list all processing symbols with relative paths
41 You can have multiple cases of the same function, and the No paths category
48 List all compiled objects and their RAM usage in a tabular form with bytes
49 per symbol and the percentage it uses. The data is grouped based on the file
[all …]
|
| /Zephyr-latest/boards/arduino/nano_33_iot/doc/ |
| D | index.rst | 7 Wifi, Bluetooth, a 6 axis IMU, and secure element.
13 - 256 KiB flash memory and 32 KiB of RAM
17 - Wifi and Bluetooth via a u-blox NINA-W102
19 - LSM6DS3 six axis accelerometer and gyro
26 Connections and IOs
37 APB and GCLK unit are set up in the same way as the upstream Arduino
43 The SAMD21 MCU has 6 SERCOM based USARTs. SERCOM5 is available on pins 1 and 2.
48 The SAMD21 MCU has 3 TCC based PWM units with up to 4 outputs each and a period
56 and 15.
66 Programming and Debugging
[all …]
|
| /Zephyr-latest/boards/renesas/rzn2l_rsk/doc/ |
| D | index.rst | 8 your PC. This product has rich functional ICs such as Gigabit Ethernet PHY and Octal Flash,
12 * Rich functional ICs such as Gigabit Ethernet PHY and Octal Flash are mounted,
16 * Emulator circuit is mounted, and program debugging can be started by simply connecting USB cable
17 to PC (two USB cables are included, one for emulator and the other for power supply)
57 Connections and IOs
64 * LEDs defined as ``led0``, ``led1``, ``led2`` and ``led3``,
68 Programming and Debugging
72 built, flashed, and debugged in the usual way. See :ref:`build_an_application`
73 and :ref:`application_run` for more details on building and running.
79 2. Connect the micro-USB type-B to J-Link OB USB connector (J10), and then the LED4 is lighted.
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | w1.rst | 10 ground for both data transmission and device power supply.
12 and is a single master multidrop bus. This means one master initiates all data
15 to 15.4 kbps in standard mode and up to 125 kbps in overdrive mode.
18 10 meters length are expected to work solid. Optimized timing parameters and
36 temperature sensors and serial memories.
41 presence detect and bit transfer operations.
45 In the future, a GPIO/Timer based driver and hardware specific drivers might
47 * The 1-Wire network layer handles all means for slave identification and bus
52 includes a 8-bit `1-Wire Family Code`_ and a 8-bit CRC.
57 * Transport layer and Presentation layer functions are not implemented in the
[all …]
|
| /Zephyr-latest/boards/nxp/lpcxpresso54114/doc/ |
| D | index.rst | 6 The LPCXpresso54114 board has been developed by NXP to enable evaluation of and
16 - LPC54114 dual-core (M4F and dual M0) MCU running at up to 100 MHz
17 - On-board high-speed USB based debug probe with CMSIS-DAP and J-Link protocol
22 - Expansion options based on Arduino UNO and Pmod™, plus additional expansion
24 - On-board 1.8 V and 3.3 V regulators plus external power supply option
26 - Built-in MCU power consumption and supply voltage measurement
27 - UART, I²C and SPI port bridging from LPC54114 target to USB via the on-board
31 For more information about the LPC54114 SoC and LPCXPRESSO54114 board:
75 Connections and IOs
118 configured as USART for the console and the remaining are not used.
[all …]
|
| /Zephyr-latest/boards/silabs/starter_kits/slstk3402a/doc/ |
| D | index.rst | 16 - 2 user buttons, 2 LEDs and a touch slider
17 - Humidity, temperature, and inductive-capacitive metal sensor
20 For more information about the EFM32PG SoC and SLSTK3402A board:
39 Gecko and the Jade Gecko is their core. The Pearl Gecko contains an ARM®
40 Cortex®-M4F core, and the Jade Gecko an ARM® Cortex®-M3 core. Other features
41 such as memory and peripherals are the same.
45 To build firmware for the Jade Gecko and run it on the EFM32 Pearl Gecko Starter
49 Connections and IOs
53 are currently enabled (PORTA, PORTB, PORTD and PORTF) for the SLSTK3402A
57 means pin number 2 on PORTE, as used in the board's datasheets and manuals.
[all …]
|
| /Zephyr-latest/boards/nordic/nrf54h20dk/doc/ |
| D | index.rst | 11 All software for the nRF54H20 SoC is experimental and hardware availability
14 The nRF54H20 DK is a single-board development kit for evaluation and development
19 * an Arm Cortex-M33 core with DSP instructions, FPU, and Armv8-M Security
21 * an Arm Cortex-M33 core with DSP instructions, FPU, and Armv8-M Security
45 * RADIO (Bluetooth Low Energy and 802.15.4)
106 Connections and IOs
126 Programming and Debugging
133 Applications for all targets can be built and flashed the usual way.
134 See :ref:`build_an_application` and :ref:`application_run` for more details on
135 building and running. Debugging is for now limited to the application and radio
[all …]
|
| /Zephyr-latest/doc/services/llext/ |
| D | load.rst | 4 Once an extension is built and the ELF file is available, it can be loaded into
6 extension into memory, access its symbols and call its functions.
19 passing in the extension name and the configured loader. Once that completes
20 successfully, the extension is loaded into memory and is ready to be used.
27 Initializing and cleaning up the extension
36 LLEXT supports calling the functions listed in the ``.preinit_array`` and
38 function, and the functions listed in the ``.fini_array`` section with the
40 :ref:`User Mode <usermode_api>`, and thus can be called from either kernel or
49 signature that is compatible with the :c:func:`k_thread_create` API, and will
51 context, and finally :c:func:`llext_teardown` before returning.
[all …]
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 8 device's EFI boot partition via whatever means you like and run it
16 relocatable, and cannot be placed at specific locations in memory.
22 binary into memory and copy it vs. a bootloader like grub that will
25 any platform top out at 200kb or so, and grub is at minimum about 5x
26 that size, and potentially MUCH more if you start enabling the default
32 The code and link environment here is non-obvious. The simple rules
38 And if you forget this and use a global by mistake, the build will
39 work fine and then fail inexplicably at runtime with a garbage
50 independent code. Non-static global variables and function addresses
51 in ELF get found via GOT and PLT tables that are populated at load
[all …]
|
| /Zephyr-latest/doc/develop/west/ |
| D | without-west.rst | 12 addition to the main zephyr repository, and keeping them up to date
15 - flashing and debugging without understanding detailed usage of the
20 If you have previously installed west and want to stop using it,
27 Otherwise, Zephyr's build system will find it and may try to use
43 # and check out the specified revisions as well.
47 and keeping existing ones up to date at the latest revisions.
52 You can build a Zephyr application using CMake and Ninja (or make) directly
65 If you don't have west installed and your application does not need any of
68 If you don't have west installed and your application *does* need one
74 Similarly, if your application requires binary blobs and you are not using
[all …]
|
| /Zephyr-latest/boards/adi/max32670evkit/doc/ |
| D | index.rst | 8 compromising battery life. It combines a flexible and versatile power management unit
10 The MAX32670 also offers legacy designs an easy and cost optimal upgradepath
38 - Internal Low-Power 7.3728MHz and Ultra-Low-Power 80kHz Oscillators
42 - External Clock Input for the LPUART and LPTMR
65 - Security and Integrity
71 - Benefits and Features of MAX32670EVKIT:
74 - UART0 and UART3 Interface is Selectable Through On-Board Jumpers
77 - SPI and I2C Signals Accessed Through 0.1in Headers
78 - GPIOs and Miscellaneous Signals Accessed Through 0.1in Headers
80 - On-Board SIMO Regulator and LDO for IC and Peripherals
[all …]
|
| /Zephyr-latest/samples/tfm_integration/tfm_secure_partition/ |
| D | README.rst | 10 "secure services" to other partitions and/or to the non-secure firmware. TF-M already contains
14 This sample creates a dummy secure partition and secure service for TF-M and instructs the TF-M
19 partition, and retrieve a hash of the secret.
22 build files and build configuration files. The partition is built by the TF-M build system, refer to
29 "dummy_partition", "DUMMY_PARTITION", "dp", and "DP" to your own partition name. Also, look through
30 both the secure and non-secure CMakeLists.txt file and make relevant changes, as well as the yaml
33 Building and Running
|
| /Zephyr-latest/boards/particle/nrf51_blenano/doc/ |
| D | index.rst | 20 Connections and IOs
38 More information about Nano and DAPLink can be found at the `RedBear Github`_.
40 Programming and Debugging
43 Applications for the ``nrf51_blenano`` board configuration can be built and
44 flashed in the usual way (see :ref:`build_an_application` and
56 with the VIN and GND pins should face **towards** the USB connector.
58 properly solder headers and assemble the DAPLink and BLE Nano boards.
60 Now build and flash applications as usual. Here is an example for the
|
| /Zephyr-latest/boards/shields/adafruit_data_logger/doc/ |
| D | index.rst | 10 Battery Backup`_, an SD card interface, two user LEDs, and a prototyping area.
46 .. [1] The user LEDs are not connected to ``D3`` and ``D4`` by default. Jumper or jumper wire
47 connections must be established between the ``L1`` and ``Digital I/O 3`` pins for ``LED1``
48 and ``L2`` and ``Digital I/O 4`` pins for ``LED2`` if they are to be used.
51 wire connection must be established between the ``SQ`` pin and the ``Digital I/O 7`` pin in
54 internal GPIO pull-up and thus no external pull-up resistor is needed.
59 This shield can only be used with a board which provides a configuration for Arduino connectors and
60 defines node aliases for SPI and GPIO interfaces (see :ref:`shields` for more details).
|
| /Zephyr-latest/boards/rakwireless/rak3172/doc/ |
| D | index.rst | 7 The breakout board has the RAK3172 as its core and with soldered to the
14 It is designed to easy access to the pins on the board and simplify the evaluation of the RAK3172
18 - 256-Kbyte Flash memory and 64-Kbyte SRAM
20 - Hardware encryption AES256-bit and a True random number generator
43 Programming and Debugging
46 The RAK3172 board can be debugged and flashed with an external debug probe connected
58 Connect the board to your host computer and build and flash an application.
60 Build the Zephyr kernel and application, then flash it to the device:
|
| /Zephyr-latest/samples/subsys/smf/hsm_psicc2/ |
| D | README.rst | 12 Building and Running
15 It should be possible to build and run this sample on almost any board or emulator.
17 Building and Running for ST Disco L475 IOT01 (B-L475E-IOT01A)
19 The sample can be built and executed for the :zephyr:board:`disco_l475_iot1` as follows:
34 topologies up to four levels of state nesting and is used with permission of the author.
36 For each state, the entry, run, and exit actions are logged to the console, as well as logging
37 when a state handles an event, or explicitly ignores it and passes it up to the parent state.
44 is no way to restart the state machine once terminated, and future events are ignored.
51 will support these transitions in the future and the list would become outdated.
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/ |
| D | response_big.html.bin | 27 …roject where silicon vendors, OEMs, ODMs, ISVs, and OSVs can contribute technology to reduce the c…
31 …and small IoT wireless gateways. Because the Zephyr OS is modular and supports multiple architectu…
35 …and control communications, radar, telecommunications and image processing. The most recent exampl…
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server/src/ |
| D | response_big.html.bin | 27 …roject where silicon vendors, OEMs, ODMs, ISVs, and OSVs can contribute technology to reduce the c…
31 …and small IoT wireless gateways. Because the Zephyr OS is modular and supports multiple architectu…
35 …and control communications, radar, telecommunications and image processing. The most recent exampl…
|
| /Zephyr-latest/samples/boards/st/sensortile_box/ |
| D | README.rst | 11 This sample enables all sensors of SensorTile.box board, and then
12 periodically reads and displays data on the console from the following
15 - HTS221: ambient temperature and relative humidity
16 - LPS22HH: ambient temperature and atmospheric pressure
18 - LSM6DSOX: 6-Axis acceleration and angular velocity
32 Building and Running
35 Build and flash the sample in the following way:
45 Then, power cycle the board by disconnecting and reconnecting the USB cable.
83 sensor, you will see the accelerometer, gyro, and temperature values change.
|
1...<<11121314151617181920>>...155
