Searched refs:is (Results 1 – 25 of 2798) sorted by relevance
12345678910>>...112
| /Zephyr-latest/samples/sensor/dht_polling/ |
| D | README.rst | 30 It also requires a correct fixture setup when the sensor is present.
50 hs300x@44: temp is 25.31 °C humidity is 30.39 %RH
51 hs300x@44: temp is 25.51 °C humidity is 30.44 %RH
52 hs300x@44: temp is 25.51 °C humidity is 30.37 %RH
53 hs300x@44: temp is 25.51 °C humidity is 30.39 %RH
54 hs300x@44: temp is 25.31 °C humidity is 30.37 %RH
55 hs300x@44: temp is 25.31 °C humidity is 30.35 %RH
56 hs300x@44: temp is 25.51 °C humidity is 30.37 %RH
57 hs300x@44: temp is 25.51 °C humidity is 30.37 %RH
58 hs300x@44: temp is 25.51 °C humidity is 30.39 %RH
[all …]
|
| /Zephyr-latest/samples/kernel/condition_variables/simple/ |
| D | README.rst | 16 execution based on when the worker thread signals the main thread that is
80 [thread zephyr_app_main] done is 0 which is < 20 so waiting on cond
141 [thread 0] done is now 1. Signalling cond.
143 [thread zephyr_app_main] done is 1 which is < 20 so waiting on cond
144 [thread 1] done is now 2. Signalling cond.
146 [thread zephyr_app_main] done is 2 which is < 20 so waiting on cond
147 [thread 2] done is now 3. Signalling cond.
149 [thread zephyr_app_main] done is 3 which is < 20 so waiting on cond
150 [thread 3] done is now 4. Signalling cond.
152 [thread zephyr_app_main] done is 4 which is < 20 so waiting on cond
[all …]
|
| /Zephyr-latest/doc/services/portability/ |
| D | cmsis_rtos_v2.rst | 6 Cortex-M Software Interface Standard (CMSIS) RTOS is a vendor-independent
21 ``osMutexPrioInherit`` is supported by default and is not configurable,
24 ``osMutexRecursive`` is also supported by default. If this attribute is
25 not set, an error is thrown when the same thread tries to acquire
28 ``osMutexRobust`` is not supported in Zephyr.
34 ``osError`` (Unspecified error) is not supported.
38 semaphore_id is in an invalid semaphore state) is not supported.
42 is in an invalid mutex state) is not supported.
46 is in an invalid timer state) is not supported.
50 parameter msgq_id is in an invalid message queue state)
[all …]
|
| /Zephyr-latest/modules/ |
| D | Kconfig.mcux | 24 Set if the 12B1MSPS SAR ADC module is present in the SoC.
29 Set if the 12-bit ADC (ADC12) module is present in the SoC.
34 Set if the 16-bit ADC (ADC16) module is present in the SoC.
39 Set if the LPADC module is present in the SoC.
44 Set if the L1 or L2 cache is present in the SoC.
49 Set if the clock control module (CCM) module is present in the SoC.
54 Set if the revision 2 of clock control module (CCM) module is present in the SoC.
55 This is present in SoC's such as RT1170
60 Set if the syscon module is present in the SoC.
65 Set if the peripheral clock controller module (PCC) module is
[all …]
|
| /Zephyr-latest/tests/cmake/hwm/board_extend/oot_root/boards/native/native_sim_extend/ |
| D | Kconfig | 8 This kconfig is set when the extended variant board config fragment
9 is supposed to be sourced, that is when oot variant defines 'extends:'
15 This kconfig is promptless and is expected to be set through the
22 This kconfig is promptless and is expected to be set through the
29 This kconfig is set when the extended variant board defconfig fragment
30 is supposed to be sourced, that is when oot variant defines 'extends:'
|
| /Zephyr-latest/samples/subsys/sip_svc/ |
| D | README.rst | 39 Got response of transaction id 0x00 and voltage is 0.846878v
40 Got response of transaction id 0x01 and voltage is 0.858170v
41 Got response of transaction id 0x02 and voltage is 0.860168v
42 Got response of transaction id 0x03 and voltage is 0.846832v
43 Got response of transaction id 0x04 and voltage is 0.858337v
44 Got response of transaction id 0x05 and voltage is 0.871704v
45 Got response of transaction id 0x06 and voltage is 0.859421v
46 Got response of transaction id 0x07 and voltage is 0.857254v
47 Got response of transaction id 0x08 and voltage is 0.858429v
48 Got response of transaction id 0x09 and voltage is 0.859879v
[all …]
|
| /Zephyr-latest/doc/services/storage/nvs/ |
| D | nvs.rst | 7 FIFO-managed circular buffer. The flash area is divided into sectors. Elements
8 are appended to a sector until storage space in the sector is exhausted. Then a
9 new sector in the flash area is prepared for use (erased). Before erasing the
10 sector it is checked that identifier - data pairs exist in the sectors in use,
11 if not the id-data pair is copied.
13 The id is a 16-bit unsigned number. NVS ensures that for each used id there is
19 Each element is stored in flash as metadata (8 byte) and data. The metadata is
20 written in a table starting from the end of a nvs sector, the data is
22 of: id, data offset in sector, data length, part (unused), and a CRC. This CRC is
28 .. note:: The data CRC is checked only when the whole data of the element is read.
[all …]
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.deprecated | 5 # This file should be removed after Zephyr 4.0 is released
14 This option is deprecated.
23 This option is deprecated.
32 This option is deprecated.
41 This option is deprecated.
50 This option is deprecated.
59 This option is deprecated.
68 This option is deprecated.
81 This option is deprecated.
90 This option is deprecated.
[all …]
|
| /Zephyr-latest/doc/services/debugging/ |
| D | cs_trace_defmt.rst | 6 Formatter is a method of wrapping multiple trace streams (specified by 7 bit ID) into a
7 single output stream. Formatter is using 16 byte frames which wraps up to 15 bytes of
8 data. It is used, for example, by ETR (Embedded Trace Router) which is a circular RAM
9 buffer where data from various trace streams can be saved. Typically tracing data is
16 Deformatter is initialized with a user callback. Data is decoded using
17 :c:func:`cs_trace_defmt_process` in 16 bytes chunks. Callback is called whenever stream changes or
18 end of chunk is reached. Callback contains stream ID and the data.
|
| D | mipi_stp_decoder.rst | 9 trace sources. Stream consists of opcode (shortest is 4 bit long) followed by optional data and
14 One example where protocol is used is ARM Coresight STM (System Trace Macrocell) where data
17 This module can be used to perform on-chip decoding of the data stream. STP v2 is used.
22 Decoder is initialized with a callback. A callback is called on each decoded opcode.
24 relative). Decoder can be in synchronization or not. Initial state is configurable.
25 If decoder is not synchronized to the stream then it decodes each nibble in search for ASYNC opcode.
27 :c:func:`mipi_stp_decoder_sync_loss`. :c:func:`mipi_stp_decoder_decode` is used to decode the data.
35 * When decoding nibbles, it is more efficient when core supports unaligned memory access.
37 Optimized version is used for ARM Cortex-M (expect for M0).
38 * Limited set of the most common opcodes is implemented.
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | demand_paging.rst | 6 Demand paging provides a mechanism where data is only brought into physical
7 memory as required by current execution context. The physical memory is
16 there is a free page frame. If there is no more free page frames,
17 the eviction algorithm is invoked to select a data page to be paged out,
19 page has been modified after it is first paged in, the data will be
20 written back into the backing store. If no modifications is done or
21 after written back into backing store, the data page is now considered
22 paged out and the corresponding page frame is now free. The paging code
25 page into the free page frame. Now the data page is in physical memory
31 in anticipation that they are required in the near future. This is used to
[all …]
|
| /Zephyr-latest/boards/shields/semtech_sx1276mb1mas/ |
| D | semtech_sx1276mb1mas.overlay | 25 dio-gpios = <&arduino_header 8 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>, /* DIO0 is D2 */
26 <&arduino_header 9 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>, /* DIO1 is D3 */
27 <&arduino_header 10 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>, /* DIO2 is D4 */
28 <&arduino_header 11 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>, /* DIO3 is D5 */
29 <&arduino_header 14 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>, /* DIO4 is D8 */
30 <&arduino_header 15 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>; /* DIO5 is D9 */
32 rfo-enable-gpios = <&arduino_header 4 GPIO_ACTIVE_HIGH>; /* RXTX_EXT is A4 */
|
| /Zephyr-latest/cmake/app/ |
| D | boilerplate.cmake | 4 # The use of this file is deprecated #
12 # The `REQUIRED HINTS $ENV{ZEPHYR_BASE}` variant is required for any application
15 # Loading of this file directly is deprecated and only kept for backward compatibility.
18 # When `find_package(Zephyr)` is used then `Zephyr_DIR` is defined, else
19 # old style inclusion is used. Warning is only printed in first invocation.
20 message(WARNING "Loading of Zephyr boilerplate.cmake directly is deprecated, "
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | regulators.rst | 7 example is a GPIO that controls a transistor that supplies current to a device
8 that is not always needed. Another example is a PMIC, typically a much more
13 regulator API is used to issue requests for power when the device is to be
16 The simplest case where a regulator is needed is one where there is only one
18 infrastructure is not justified, and ``*-gpios`` devicetree properties should be
19 used. There is no device interface to these regulators as they are entirely
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 6 # All text after a double hash (##) is considered a comment and is placed in
7 # front of the TAG it is preceding.
9 # All text after a single hash (#) is considered a comment and will be ignored.
10 # The format is:
31 # file that follow. The default is UTF-8 which is also the encoding used for all
35 # The default value is: UTF-8.
39 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
41 # project for which the documentation is generated. This name is used in the
43 # The default value is: My Project.
49 # control system is used.
[all …]
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.nrf_xrtc | 14 System clock source is initiated but does not wait for clock readiness.
15 When this option is picked, system clock may not be ready when code relying
16 on kernel API is executed. Requested timeouts will be prolonged by the
22 System clock source initialization waits until clock is available. In some
25 it is ready. When this option is picked, system clock is available after
26 system clock driver initialization but it may be less accurate. Option is
33 System clock source initialization waits until clock is stable. When this
34 option is picked, system clock is available and stable after system clock
|
| /Zephyr-latest/drivers/watchdog/ |
| D | Kconfig.nxp_fs26 | 19 Device driver initialization priority. Device is connected to SPI bus,
28 watchdog error counter is decremented by 1 each time the watchdog is
38 watchdog is properly refreshed, this counter is incremented by 1. Each
39 time this counter reaches its maximum value and if the next refresh is
40 also good, the fault error counter is decremented by 1. Each time
41 there is a bad watchdog refresh, this counter is reset to 0.
53 watchdog configuration, value 0x0000 is not allowed.
58 If the device is started in DEBUG mode, the driver will exit this mode
59 so that the watchdog is enabled. Otherwise, if the device is in DEBUG
60 mode and this driver is enabled, it will fail to initialize.
[all …]
|
| /Zephyr-latest/doc/services/logging/ |
| D | cs_stm.rst | 6 The Arm CoreSight SoC-400 is a comprehensive library of components for the creation of debug and
7 trace functionality within a system. The STM (System Trace Macrocell) is a trace source that
8 is integrated into a CoreSight system, designed primarily for high-bandwidth trace of
9 instrumentation embedded into software. This instrumentation is made up of memory-mapped writes to
12 register sets) which can be independently accessed thus there is no need for locking when various
24 TPIU (Trace Port Interface Unit) or saved in the RAM Circular Buffer which is called ETR (Embedded
25 Trace Router). TPIU is a 5 pin interface (4 data pins and clock) and external tool is required to
27 When ETR is used then one core in the system is responsible for processing that data, for example
33 ETR is a circular RAM buffer to which tracing data is saved. Since it may contain data from
34 various sources additional wrapping protocol is used to multiplex them. ``Coresight Trace
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_if.rst | 13 The network interface is a nexus that ties the network device drivers
15 data is transferred via a network interface. The network interfaces cannot be
17 and that section is populated at linking time.
22 :kconfig:option:`CONFIG_NET_VLAN` is enabled. These macros are typically used in
26 by calling ``net_if_down()``. When the device is powered ON, the network
27 interface is also turned ON by default.
50 packet priority. This is typically done in Ethernet networks when virtual LANs
55 If the :kconfig:option:`CONFIG_NET_PROMISCUOUS_MODE` is enabled and if the underlying
56 network technology supports promiscuous mode, then it is possible to receive
57 all the network packets that the network device driver is able to receive.
[all …]
|
| /Zephyr-latest/samples/sensor/vl53l0x/ |
| D | README.rst | 11 and target. The result is displayed on the console.
28 sensor, which is present on the disco_l475_iot1 board.
40 prox is 0
41 distance is 1938
42 prox is 1
43 distance is 70
44 prox is 0
45 distance is 1995
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | mpsc_pbuf.rst | 6 A :dfn:`Multi Producer Single Consumer Packet Buffer (MPSC_PBUF)` is a circular
9 is a single context that consumes the data. However, it is possible that another
11 Packet is produced in two steps: first requested amount of data is allocated,
12 producer fills the data and commits it. Consuming a packet is also performed in
14 on packet is freed. This approach reduces memory copying.
20 * Allocator ensures that contiguous memory of requested length is allocated.
24 be allocated. For each dropped packet user callback is called.
33 Each packet in the buffer contains ``MPSC_PBUF`` specific header which is used
40 * busy - bit set when packet is being consumed (claimed but not free)
47 | 0 | 0 | space is free |
[all …]
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | ota.rst | 9 Over-the-Air (OTA) Update is a method for delivering firmware updates to remote
14 when an update is available. Security is a concern with OTA updates; firmware
18 same method can be used as part of OTA. The binary is first downloaded
28 `Golioth`_ is an IoT management platform that includes OTA updates. Devices are
30 When a new version is available, the device downloads and flashes the binary. In
31 this implementation, the connection between cloud and device is secured using
32 TLS/DTLS, and the signed firmware binary is confirmed by MCUboot before the
42 `Eclipse hawkBit`_ |trade| is an update server framework that uses polling on a
43 REST api to detect firmware updates. When a new update is detected, the binary
44 is downloaded and installed. MCUboot can be used to verify the signature before
[all …]
|
| /Zephyr-latest/samples/sensor/tmp108/ |
| D | README.rst | 11 macro definitions included for turning off and on alerts if that is set up, and
27 Temperature is 22.875C
28 Temperature is 22.875C
29 Temperature is 22.875C
30 Temperature is 22.875C
31 Temperature is 22.875C
32 Temperature is 22.875C
|
| /Zephyr-latest/subsys/shell/ |
| D | Kconfig.template.shell_log_queue_timeout | 8 If queue with pending log messages is full, oldest log message is
9 dropped if queue is still full after requested time (-1 is forever).
10 Logger thread is blocked for that period, thus long timeout impacts
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net_pkt_processing_stats.rst | 15 options that control this. For transmit (TX) path the option is called
16 :kconfig:option:`CONFIG_NET_PKT_TXTIME_STATS` and for receive (RX) path the options is
18 network packet statistics is collected. For RX, only UDP, TCP or raw packet
19 type network packet statistics is collected.
59 * Packet was created by application so the time is **0**.
60 * Packet is about to be placed to transmit queue. The time it took from network
61 packet creation to this state, is **22** microseconds in this example.
62 * The correct TX thread is invoked, and the packet is read from the transmit
64 * The network packet was just sent and the network stack is about to free the
67 sent. The value **63** tells also the same information, but is calculated
[all …]
|
12345678910>>...112
