Searched +full:long +full:- +full:sample (Results 1 – 25 of 115) sorted by relevance
12345
| /Zephyr-latest/dts/bindings/adc/ |
| D | nxp,kinetis-adc16.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "nxp,kinetis-adc16"
8 include: ["adc-controller.yaml", "pinctrl-device.yaml"]
14 channel-mux-b:
22 periodic-trigger:
26 "#io-channel-cells":
29 clk-source:
33 long-sample:
36 - 0
37 - 1
[all …]
|
| /Zephyr-latest/samples/drivers/led/pwm/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
10 If set to 0, the short-cycle blinking demo will not be performed.
13 int "Blinking delay for long cycle demo"
16 Specifies the LED on/off delay in milliseconds for long cycle
18 If set to 0, the long-cycle blinking demo will not be performed.
25 PWM-LED sample.
|
| /Zephyr-latest/samples/posix/eventfd/src/ |
| D | main.c | 4 * SPDX-License-Identifier: Apache-2.0
6 * This sample application is roughly based on the sample code in Linux
18 /* As Zephyr doesn't provide command-line args, emulate them. */
55 (unsigned long long)u, (unsigned long long)u); in reader()
72 if (efd == -1) { in main()
|
| /Zephyr-latest/samples/net/sockets/txtime/ |
| D | Kconfig | 1 # Private config options for txtime sample app
4 # SPDX-License-Identifier: Apache-2.0
6 mainmenu "Networking TXTIME sample application"
39 how long it takes to send data so the actual data content is not
40 important for this sample application.
45 int "How long to wait between sent packets (in milliseconds)"
63 but for purpose of this sample application, we set the time in
82 Set VLAN (virtual LAN) tag (id) that is used in the sample
101 Set VLAN (virtual LAN) tag (id) that is used in the sample
|
| D | README.rst | 1 .. zephyr:code-sample:: so_txtime
3 :relevant-api: bsd_sockets ethernet
10 This sample is a simple UDP sender/receiver which will set the
17 User can control how long the application should wait between packets sent by
27 ``echo-server`` application from `net-tools`_ project to catch these and
30 to create an ``AF_PACKET`` type socket. In this case, the ``echo-server``
33 This sample can be built and executed on qemu_x86 board as
36 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
|
| /Zephyr-latest/samples/subsys/canbus/isotp/ |
| D | README.rst | 1 .. zephyr:code-sample:: isotp
2 :name: ISO-TP library
3 :relevant-api: can_isotp
5 Use ISO-TP library to exchange messages between two boards.
9 This sample demonstrates how to use the :ref:`ISO-TP library <can_isotp>`.
11 Messages are exchanged between two boards. A long message, that is sent with
12 a block-size (BS) of eight frames, and a short one that has a minimal
13 separation-time (STmin) of five milliseconds.
15 The send function call for the short message is non-blocking, and the send
16 function call for the long message is blocking.
[all …]
|
| /Zephyr-latest/samples/drivers/lora/ |
| D | index.rst | 1 .. zephyr:code-sample-category:: lora
3 :show-listing:
5 These samples demonstrate how to use :ref:`LoRa <lora_api>` for long-range wireless
|
| /Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/ |
| D | README.rst | 1 .. zephyr:code-sample:: uac2-explicit-feedback
2 :name: USB Audio asynchronous explicit feedback sample
3 :relevant-api: usbd_api uac2_device i2s_interface
5 USB Audio 2 explicit feedback sample playing audio on I2S.
10 This sample demonstrates how to implement USB asynchronous audio playback with
14 The device running this sample presents itself to the host as a Full-Speed
15 Asynchronous USB Audio 2 class device supporting 48 kHz 16-bit 2-channel
21 Asynchronous USB Audio is used when the actual sample clock is not controlled by
22 USB host. Because the sample clock is independent from USB SOF it is inevitable
24 shorter than 1 ms according to audio source (USB host). In the long run, this
[all …]
|
| /Zephyr-latest/samples/modules/cmsis_dsp/moving_average/ |
| D | README.rst | 1 .. zephyr:code-sample:: cmsis-dsp-moving-average
2 :name: CMSIS-DSP moving average
4 Use the CMSIS-DSP library to calculate the moving average of a signal.
9 This sample demonstrates how to use the CMSIS-DSP library to calculate the moving average of a
12 It can be run on any board supported in Zephyr, but note that CMSIS-DSP is specifically optimized
13 for ARM Cortex-A and Cortex-M processors.
19 The sample uses a very simple input signal of 32 samples, and computes the moving average using a
21 CMSIS-DSP function, and displayed on the console.
24 In order to allow an easy comparison of the efficiency of the CMSIS-DSP library when used on ARM
25 processors vs. other architectures, the sample outputs the time and number of cycles it took to
[all …]
|
| /Zephyr-latest/samples/sensor/sgp40_sht4x/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
7 mainmenu "SGP40/SHT4X sample application"
31 0 -> High power heater pulse -> ~200 mW @3.3V
32 1 -> Medium power heater pulse -> ~110 mW @3.3V
33 2 -> Low power heater pulse -> ~20 mW @3.3V
41 0 -> Long heater pulse -> 1.1s
42 1 -> Short heater pulse -> 0.11s
|
| /Zephyr-latest/samples/net/sockets/tcp/src/ |
| D | main.c | 4 * SPDX-License-Identifier: Apache-2.0
7 /* TCP Sample for TTCN-3 based Sanity Check */
27 * This application is used together with the TTCN-3 based sanity check
34 * to keep the sample running in order to execute TTCN-3 TCP sanity check.
83 printf("Received %ld bytes\n", (long)len); in udp()
|
| /Zephyr-latest/samples/drivers/soc_flash_nrf/ |
| D | README.rst | 1 .. zephyr:code-sample:: soc-flash-nrf
3 :relevant-api: flash_interface flash_area_api
10 This sample demonstrates using the :ref:`Flash API <flash_api>` on an SoC internal storage.
11 The sample uses :ref:`Flash map API <flash_map_api>` to obtain a device that has one
16 Within the sample, user may observe how read/write/erase operations
23 The sample will be built for any SoC with internal storage, as long as
24 there is a fixed-partition named ``storage_partition`` defined
27 .. zephyr-app-commands::
28 :zephyr-app: samples/drivers/soc_flash_nrf
33 Sample Output
[all …]
|
| /Zephyr-latest/dts/bindings/sensor/ |
| D | ti,bq274xx.yaml | 4 # SPDX-License-Identifier: Apache-2.0
11 include: [sensor-device.yaml, i2c-device.yaml]
14 design-voltage:
17 description: Battery Design Voltage in mV (3300 - 4400)
19 design-capacity:
24 taper-current:
31 terminate-voltage:
38 chemistry-id:
44 int-gpios:
45 type: phandle-array
[all …]
|
| /Zephyr-latest/tests/drivers/sensor/generic/src/ |
| D | main.c | 4 * SPDX-License-Identifier: Apache-2.0
73 * - get multiple channels values consistently in two operations:
74 * fetch sample and get the values of each channel individually.
75 * - check the results with sensor_value type avoids use of
79 * - function and block box testing,Interface testing,
83 * - N/A
86 * - N/A
89 * -# Define a device and bind to dummy sensor.
90 * -# Fetch the sample of dummy senor and check the result.
91 * -# Get SENSOR_CHAN_LIGHT/SENSOR_CHAN_RED/SENSOR_CHAN_GREEN/
[all …]
|
| /Zephyr-latest/samples/subsys/fs/zms/ |
| D | README.rst | 1 .. zephyr:code-sample:: zms
3 :relevant-api: zms_high_level_api
9 The sample shows how to use ZMS to store ID/VALUE pairs and reads them back.
10 Deleting an ID/VALUE pair is also shown in this sample.
12 The sample stores the following items:
18 #. A long set of data (128 bytes)
35 This sample can be found under :zephyr_file:`samples/subsys/fs/zms` in the Zephyr tree.
37 The sample can be built for several platforms, but for the moment it has been tested only
40 .. zephyr-app-commands::
41 :zephyr-app: samples/subsys/fs/zms
[all …]
|
| /Zephyr-latest/samples/subsys/rtio/sensor_batch_processing/src/ |
| D | main.c | 4 * SPDX-License-Identifier: Apache-2.0
21 #define PROCESS_TIME ((M - 1) * SAMPLE_PERIOD)
28 struct rtio_iodev *iodev = vnd_sensor->data; in main()
59 if (cqe->result < 0) { in main()
71 * Model as a long sleep that takes multiple sensor sample in main()
78 LOG_HEXDUMP_DBG(userdata[m], SAMPLE_SIZE, "Sample data:"); in main()
|
| /Zephyr-latest/tests/kernel/timer/timer_behavior/ |
| D | README | 1 # Test a timer implementations variance and long term drift
10 --------------------------------------------------------------------------------
16 GPIO pin on every cycle - first cycle will be a rising edge. This test expects
23 "test-kernel-timer-behavior-external", with property "timeout-gpios" being the
31 run(seconds: float, options: str) -> {}, int
33 The `seconds` parameter defines for how long the data collection is expected
51 One can check `pytest/saleae_logic2.py` file as a sample of external tool
60 "tool-options", a string with options passed to the Python module helper.
83 the saleae_logic2 module ones are listed at pytest/requirements-saleae.txt.
86 pip install -r pytest/requirements-saleae.txt
|
| /Zephyr-latest/subsys/net/lib/config/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
7 module-dep = NET_LOG
8 module-str = Log level for network config library
9 module-help = Enables net config library to output debug messages.
18 networking client/server sample applications, or
19 some link-layer dedicated settings like the channel.
67 int "How long to wait for networking to be ready and available"
132 The PAN ID to use by default in the sample.
138 The channel to use by default in the sample application.
144 The TX power to use by default in the sample application.
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | read_and_decode.rst | 1 .. _sensor-read-and-decode:
14 Benefits over :ref:`sensor-fetch-and-get`
19 that have been run into with :ref:`sensor-fetch-and-get`.
25 functions that work on vectors of data to be done (e.g. low-pass filters, FFT,
40 * Requesting multiple reads to the same device for Ping-Pong (double buffering)
45 * Potentially pre-programming DMAs to trigger on GPIO events, leaving the CPU
48 Additionally, other shortcomings of :ref:`sensor-fetch-and-get` related to memory
53 enabling pre-programmed DMA transfers on GPIO interrupts.
54 * Far less likely triggers are missed due to long held interrupt masks from
71 channels to poll. Requesting either blocking or non-blocking reads, then
[all …]
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.5.rst | 21 taking a ``void *mem`` pointer instead of a ``void **mem`` double-pointer.
37 * The default C library used on most targets has changed from the built-in
47 increase by 8-16 bytes.
68 * Picolibc removes the ``-ffreestanding`` compiler option. This allows
71 the Zephyr required type -- ``int main(void)``.
74 'double', 'long long', 'integer', and 'minimal. 'double' offers a
76 hexadecimal formats, full integer support including long long, C99
77 integer size specifiers (j, z, t) and POSIX positional arguments. 'long
78 long' mode removes float support, 'integer' removes long long support
100 * ``psa-arch-tests``
[all …]
|
| D | release-notes-1.6.rst | 7 release introduces the unified Kernel replacing the separate nano- and
8 micro-kernels and simplifying the overall Zephyr architecture and programming
10 Support for the ARM Cortex-M0/M0+ family was added and board support for
11 Cortex-M was expanded.
22 * Added support for several ARM Cortex-M boards
34 * Added DLIST to operate in all elements of a doubly-linked list.
52 * ARM: Added support for ARM Cortex-M0/M0+.
55 * x86: Changed IRQ controller to return -1 if cannot determine source vector.
99 * Added raw HCI API to enable physical HCI transport for a Controller-only build.
100 * Added sample raw HCI apps for USB and UART.
[all …]
|
| D | release-notes-1.7.rst | 10 nano- and micro-kernel APIs found in the 1.5.0 release and earlier.
52 * Added NXP FRDM-KW41Z board
53 * Added ST Nucleo-F334R8, Nucleo-L476G, STM3210C-EVAL, and STM32373C-EVAL boards
93 * Added sample application (wpanusb) for exporting IEEE 802.15.4 radio over
100 * Created IRC client sample application.
101 * Created HTTP server and client sample applications.
102 * Created net-shell module for interacting with network sub-system.
136 * Imported Segger J-Link RTT library
145 * New local-content generation theme (read-the-docs)
147 * Site-wide glossary added.
[all …]
|
| D | release-notes-1.5.rst | 7 1.5.0. This is the first release to follow the 3-month release cadence.
13 - TCP Support
14 - Integration of the Paho MQTT Library support with QoS
15 - Flash Filesystem Support
16 - Integration of the mbedTLS library for encryption
17 - Improved BR/EDR support (for L2CAP, in particular).
18 - Support for the Altera Nios II/f soft CPU architecture
25 - Added nano_fifo_put_list() APIs, which allows queuing a list of elements
27 - Removed unused memory pool structure field.
28 - Enhanced memory pool code.
[all …]
|
| /Zephyr-latest/tests/kernel/mem_protect/stackprot/ |
| D | README.txt | 7 --------------------------------------------------------------------------------
16 --------------------------------------------------------------------------------
20 Problems caused by out-dated project information can be addressed by
27 # and restore pre-defined configuration info
29 --------------------------------------------------------------------------------
31 Sample Output:
32 tc_start() - Test Stack Protection Canary
36 alternate_thread: Input string is too long and stack overflowed!
52 PASS - main.
|
| /Zephyr-latest/samples/subsys/zbus/benchmark/ |
| D | README.rst | 1 .. zephyr:code-sample:: zbus-benchmark
3 :relevant-api: zbus_apis
7 This sample implements an application to measure the time for sending 256KB from the producer to the
13 .. zephyr-app-commands::
14 :zephyr-app: samples/subsys/zbus/dyn_channel
15 :host-os: unix
17 :gen-args: -DCONFIG_BM_MESSAGE_SIZE=512 -DCONFIG_BM_ONE_TO=1 -DCONFIG_BM_LISTENERS=y
28 Sample Output
32 .. code-block:: console
34 *** Booting Zephyr OS build zephyr-vX.Y.Z ***
[all …]
|
12345
