Home
last modified time | relevance | path

Searched refs:with (Results 1 – 25 of 2676) sorted by relevance

12345678910>>...108

/Zephyr-latest/samples/boards/nordic/coresight_stm/
DREADME.rst61 [00:00:00.227,264] <inf> app/app: test with one argument 100
62 [00:00:00.227,265] <inf> app/app: test with one argument 100
64 [00:00:00.585,558] <inf> rad/app: test with one argument 100
65 [00:00:00.585,569] <inf> rad/app: test with one argument 100
67 [00:00:00.624,408] <inf> ppr/app: test with one argument 100
68 [00:00:00.624,433] <inf> ppr/app: test with one argument 100
70 [00:00:00.625,249] <inf> flpr/app: test with one argument 100
71 [00:00:00.625,251] <inf> flpr/app: test with one argument 100
73 rad: Timing for log message with 0 arguments: 5.10us
74 rad: Timing for log message with 1 argument: 6.10us
[all …]
/Zephyr-latest/tests/lib/cbprintf_fp/
DKconfig9 bool "Emit with printk"
12 bool "Emit with printf"
15 bool "Emit with printfcb"
18 bool "Emit with fprintf"
21 bool "Emit with fprintfcb"
DREADME.txt4 This ensures that formatted output to the console works as expected with
5 minimal libc and newlib versions with printk, printf, and cbprintf.
7 Footprint data can be obtained with:
/Zephyr-latest/tests/drivers/spi/spi_controller_peripheral/
DREADME.txt6 1. spi22-SPIM_SCK connected with spi21-SPIS_SCK,
7 2. spi22-SPIM_MISO connected with spi21-SPIS_MISO,
8 3. spi22-SPIM_MOSI connected with spi21-SPIS_MOSI,
9 4. spi22-cs-gpios connected with spi21-SPIS_CSN.
/Zephyr-latest/boards/adafruit/feather_m0_lora/doc/
Dindex.rst7 boards with an onboard battery connector and charger for 3.7 V lithium
35 | Flash | on-chip | Can be used with LittleFS to store files |
62 The `Adafruit Feather M0 with LoRa radio module Learn site`_ has detailed
69 with the on-chip PLL generating the 48 MHz system clock.
75 with LoRa, SERCOM0 is the Zephyr console and is available on pins 0
82 with LoRa, SERCOM3 is available on pin 20 (SDA) and pin 21 (SCL).
88 with LoRa, SERCOM4 is available on pin 22 (MISO), pin 23 (MOSI), and
95 with a host PC. See the :zephyr:code-sample-category:`usb` sample applications for
101 The Semtech SX127x radio chip on the Adafruit Feather M0 with LoRa
108 The Adafruit Feather M0 with LoRa ships with a BOSSA compatible
[all …]
/Zephyr-latest/boards/st/stm32h7s78_dk/doc/
Dindex.rst8 STM32H7S7L8H6H microcontroller with TrustZone |reg|. Here are some highlights of
13 - USB Type-C |trade| Host and device with USB power-delivery controller
14 - SAI Audio DAC stereo with one audio jacks for input/output,
15 - ST MEMS digital microphone with PDM interface
21 …- STMod+ expansion connector with fan-out expansion board for Wi‑Fi |reg|, Grove and mikroBUS |tra…
32 - On-board STLINK-V3E debugger/programmer with USB re-enumeration capability:
50 - Core: ARM |reg| 32-bit Cortex |reg| -M7 CPU with TrustZone |reg| and FPU.
57 - Arm |reg| TrustZone |reg| with ARMv8-M mainline security extension
60 - Flexible lifecycle scheme with secure debug authentication
63 - Secure data storage with hardware unique key (HUK)
[all …]
/Zephyr-latest/boards/native/native_posix/doc/
Dindex.rst24 Just like with :ref:`native_sim<native_sim>` you can build your Zephyr application
25 with the Zephyr kernel, creating a normal Linux executable with your host tooling,
28 But unlike with :ref:`native_sim<native_sim>` you are limited to only using the host C library.
53 Moreover, being limited to build only with the host C library, it is not possible to build
54 applications with the :ref:`Zephyr POSIX OS abstraction<posix_support>`, as there would be symbol
74 You can run, debug, build it with sanitizers or with coverage just like with
83 Just like :ref:`native_sim<native_sim>`, ``native_posix`` comes with two targets:
91 This target requires either a 64 bit system with multilib support installed or
92 one with a 32bit userspace.
/Zephyr-latest/samples/bluetooth/periodic_sync_rsp/
DREADME.rst2 :name: Periodic Advertising with Responses (PAwR) Synchronization
5 Implement Bluetooth LE Periodic Advertising with Responses Synchronization.
10 A simple application demonstrating the Bluetooth LE Periodic Advertising with
22 subevents and response slots, to that they can communicate with the
28 * A board with Bluetooth LE support
29 * A controller that supports the Periodic Advertising with Responses (PAwR) - Scanner feature
/Zephyr-latest/scripts/ci/es_upload/
DREADME.md9 with explicit scheme having all required Twister JSON report objects associated
14 by other tools, or rely on default data mapping with potential type misalignments.
16 The command examples below are simplified with parameters essential for data transformations.
17 For other command line options and more details run the upload script with `--help`,
18 or read its source code with inline comments there.
24 It is recommended to try the upload script with `--dry-run` option first
28 to connect with your server running the upload script.
31 ## Index creation with a map file
34 server with the appropriate map file, for example:
58 are renamed with the parent object's name as a prefix:
[all …]
/Zephyr-latest/boards/sensry/ganymed_bob/doc/
Dindex.rst15 RISC-V SoC with optional sensor level.
33 * :abbr:`4x TWIM (I2C-compatible two-wire interface with MicroDMA)`
35 * :abbr:`7x SPI (Serial Peripheral Interface with MicroDMA)`
36 * :abbr:`3x UART (Universal receiver-transmitter with MicroDMA)`
37 * :abbr:`1x TSN (Time sensitive networking ethernet MAC with MicroDMA)`
43 :alt: Ganymed Break-Out-Board (BOB) equipped with SY120 GBM
45 Ganymed Break-Out-Board (BOB) equipped with SY120 GBM (Credit: Sensry)
49 :alt: Ganymed Break-Out-Board (BOB) equipped with SY120 GEN1
51 Ganymed Break-Out-Board (BOB) equipped with SY120 GEN1 (Credit: Sensry)
61 …* SY120-GEN1 - Generic Module type 1 with top level sensors (Bosch BME680 - SPI1 , Bosch BMA456 - …
[all …]
/Zephyr-latest/snippets/nordic-flpr/
DREADME.rst3 Nordic FLPR snippet with execution from SRAM (nordic-flpr)
9 This snippet allows users to build Zephyr with the capability to boot Nordic FLPR
12 without the ``xip`` board variant, or with :kconfig:option:`CONFIG_XIP` disabled.
/Zephyr-latest/modules/hal_ethos_u/
DKconfig18 bool "using Ethos-U55 with 64 macs"
20 bool "using Ethos-U55 with 128 macs"
22 bool "using Ethos-U55 with 256 macs"
24 bool "using Ethos-U65 with 128 macs"
26 bool "using Ethos-U65 with 256 macs"
28 bool "using Ethos-U65 with 512 macs"
/Zephyr-latest/snippets/nordic-flpr-xip/
DREADME.rst3 Nordic FLPR snippet with execution in place (nordic-flpr-xip)
9 This snippet allows users to build Zephyr with the capability to boot Nordic FLPR
12 for the ``xip`` board variant, or with :kconfig:option:`CONFIG_XIP` enabled.
/Zephyr-latest/snippets/nordic-ppr-xip/
DREADME.rst3 Nordic boot PPR snippet with execution in place (nordic-ppr-xip)
9 This snippet allows users to build Zephyr with the capability to boot Nordic PPR
11 so the PPR image must be built for the ``xip`` board variant, or with
/Zephyr-latest/tests/subsys/debug/coredump_backends/
DKconfig10 Set if the test expects coredump backend with storage.
16 Test expects coredump backend storage with the size given.
17 If zero, then it is ignored and not compared with the actual size.
/Zephyr-latest/doc/services/portability/posix/option_groups/
Dindex.rst14 Enable this option group with :kconfig:option:`CONFIG_POSIX_BARRIERS`.
80 Enable this option group with :kconfig:option:`CONFIG_POSIX_C_LIB_EXT`.
107 Enable this option group with :kconfig:option:`CONFIG_POSIX_CLOCK_SELECTION`.
122 Enable this option group with :kconfig:option:`CONFIG_POSIX_DEVICE_IO`.
187 Enable this option group with :kconfig:option:`CONFIG_POSIX_FD_MGMT`.
228 Enable this option group with :kconfig:option:`CONFIG_POSIX_FILE_SYSTEM`.
266 Enable this option with :kconfig:option:`CONFIG_POSIX_FILE_SYSTEM_R`.
279 Enable this option group with :kconfig:option:`CONFIG_POSIX_MAPPED_FILES`.
294 Enable this option group with :kconfig:option:`CONFIG_POSIX_MEMORY_PROTECTION`.
307 Enable this option group with :kconfig:option:`CONFIG_POSIX_MULTI_PROCESS`.
[all …]
/Zephyr-latest/drivers/sensor/ti/tmp112/
DKconfig15 The TMP102 is compatible with the TMP112 but is less accurate and has
16 been successfully tested with this driver.
25 with SENSOR_ATTR_FULL_SCALE and value to set either 128 or 150
32 with SENSOR_ATTR_SAMPLING_FREQUENCY
/Zephyr-latest/tests/lib/sprintf/
DREADME.txt35 Testing sprintf() with integers ....
39 Testing sprintf() with strings ....
40 Testing sprintf() with misc options ....
41 Testing sprintf() with doubles ....
/Zephyr-latest/samples/sysbuild/with_mcuboot/
DREADME.rst2 :name: MCUboot with sysbuild
19 This is achieved with a sysbuild specific Kconfig configuration,
23 enables the bootloader when building with sysbuild.
26 is merged together with the default configuration files used by MCUboot.
31 To build both the sample and MCUboot with ``west`` for the ``reel_board``, run:
48 Hello sysbuild with mcuboot! nrf52840dk
/Zephyr-latest/samples/shields/x_nucleo_iks01a1/
DREADME.rst5 Interact with all the sensors of an X-NUCLEO-IKS01A1 shield.
20 This sample communicates over I2C with the X-NUCLEO-IKS01A1 shield
21 stacked on a board with an Arduino connector. The board's I2C must be
24 Please note that this sample can't be used with boards already supporting
36 This sample runs with X-NUCLEO-IKS01A1 stacked on any board with a matching
/Zephyr-latest/samples/bluetooth/broadcaster_multiple/
DREADME.rst13 This sample advertises two non-connectable non-scannable advertising sets with
17 When building this sample combined with a Bluetooth LE Controller, the
25 * A board with Bluetooth Low Energy with Extended Advertising support.
33 To test this sample use the Observer sample with Extended Scanning enabled,
/Zephyr-latest/samples/bluetooth/periodic_adv_rsp/
DREADME.rst2 :name: Periodic Advertising with Responses (PAwR) Advertiser
5 Use Bluetooth LE Periodic Advertising with Responses (PAwR) Advertiser functionality.
10 A simple application demonstrating the Bluetooth LE Periodic Advertising with
27 * A board with Bluetooth LE support
28 * A controller that supports the Periodic Advertising with Responses (PAwR) - Advertiser feature
/Zephyr-latest/arch/common/
Dfill_with_zeros.ld9 * counter) in executable segments with TrapInstr pattern, e.g. for ARM the
10 * TrapInstr pattern is 0xd4d4d4d4. GNU LD fills empty spaces with 0x00
13 * We may want to have some section (e.g. rom_start) filled with 0x00,
/Zephyr-latest/doc/services/device_mgmt/
Ddfu.rst16 The DFU subsystem deals with image management, but not with the transport
57 Zephyr is directly compatible with the open source, cross-RTOS
58 `MCUboot boot loader`_. It interfaces with MCUboot and is aware of the image
60 is the boot loader used with Zephyr. The source code itself is hosted in the
63 In order to use MCUboot with Zephyr you need to take the following into account:
85 More detailed information regarding the use of MCUboot with Zephyr can be found
86 in the `MCUboot with Zephyr`_ documentation page on the MCUboot website.
89 .. _MCUboot with Zephyr: https://docs.mcuboot.com/readme-zephyr
/Zephyr-latest/boards/nxp/mimxrt1010_evk/
Dmimxrt1010_evk.dts62 <4 0 &gpio1 15 0>, /* A4 (shared with D6) */
63 <5 0 &gpio1 16 0>, /* A5 (shared with D7) */
66 <8 0 &gpio1 19 0>, /* D2 (shared with D10) */
67 <9 0 &gpio1 20 0>, /* D3 (shared with D13) */
69 /* R793 not populated, D5 (shared with D14) */
70 <12 0 &gpio1 15 0>, /* D6 (shared with A4) */
71 <13 0 &gpio1 16 0>, /* D7 (shared with A5) */
74 <16 0 &gpio1 19 0>, /* D10 (shared with D2) */
77 <19 0 &gpio1 20 0>, /* D13 (shared with D3) */

12345678910>>...108