Searched refs:will (Results 251 – 275 of 1633) sorted by relevance
1...<<11121314151617181920>>...66
| /Zephyr-latest/doc/services/storage/disk/ |
| D | nvme.rst | 20 Where the NVMe controller is the root of the device driver. This is the one that will get device dr…
26 If a controller exposes more than 1 namespace (disk), it will be possible to raise the amount of bu…
29 Each exposed disk, via it's related disk_info structure, will be distinguished by its name which is…
31 …mber. Most of the time, if only one NVMe disk is plugged into the system, one will see 'nvme0n0' as
|
| /Zephyr-latest/lib/libc/common/ |
| D | Kconfig | 69 If set to zero, then no malloc() heap will be available.
71 If set to -1, then all remaining system RAM will be used for this
77 will result.
81 16kB and all other systems will default to using all remaining
|
| /Zephyr-latest/subsys/bindesc/ |
| D | Kconfig.build_time | 14 If enabled, the build time used for the descriptors will express
21 If enabled, the file containing the build time definitions will
83 example, setting the format to "2023-02-05T00:07:04+0000" will set it as the build time,
97 example, setting the format to "2023-02-05" will set it as the build time,
109 example, setting the format to "T00:07:04+0000" will set it as the build time,
|
| /Zephyr-latest/tests/kernel/timer/timer_behavior/ |
| D | README | 15 collect samples. The "kernel.timer.timer_behavior_external" test will toggle a
16 GPIO pin on every cycle - first cycle will be a rising edge. This test expects
17 a Python module to interface with the external tool, which will provide the
18 necessary statistics that the test will use to assert the test status.
24 GPIO pin that will be toggled each period.
|
| /Zephyr-latest/tests/bsim/bluetooth/ |
| D | tests.nrf54l15bsim_nrf54l15_cpuapp.txt | 1 # Search paths(s) for tests which will be run in the nrf54l15 app core
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | rtc.rst | 123 To run the test suite, flash and run the application on your board, the output will
135 The emulated RTC device fully implements the RTC API, and will behave like a real
140 * RTC time will drift over time.
143 the time using :c:func:`rtc_get_time` will return ``-ENODATA``, until the time is
144 set using :c:func:`rtc_set_time`. The RTC will then behave as a real RTC, until the
148 :dtcompatible:`zephyr,rtc-emul` and will be included if :kconfig:option:`CONFIG_RTC`
|
| /Zephyr-latest/samples/subsys/shell/fs/ |
| D | README.rst | 31 Which by default will use the flash simulator. The flash simulator will use a file,
46 you will also have the flash filesystem mounted and accessible from your Linux host filesystem.
96 Once the board has booted, you will be presented with a shell prompt.
116 otherwise it will cause an error and nothing will be loaded.
|
| /Zephyr-latest/tests/subsys/logging/log_blocking/ |
| D | REAME.md | 11 In the last configuration, the log processing thread will block until space
57 so configured, we minimize the liklihood that the log processing thread will
58 stall. We can also be sure that the output will be able to relieve
59 backpressure (i.e. the core log buffer usage will tend to zero over time).
76 the core log buffer will approach 100% capacity and, eventually, stall the
85 unable to allocate new log messages and it will be stalled.
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.ipv4 | 20 This tells how many network interfaces there will be in the system
21 that will have IPv4 enabled.
51 packet will decrement the value and will drop the packet if the TTL
61 packet will decrement the value and will drop the packet if the TTL
161 will timeout. This value is in seconds.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | mqtt_sn.rst | 57 The MQTT-SN library will inform clients about certain events using a callback.
107 connect to the gateway. Call the :c:func:`mqtt_sn_connect` function, which will send a
113 If the connection was successful, :c:enumerator:`MQTT_SN_EVT_CONNECTED` will be notified to the
130 If the connection fails at the MQTT level or a timeout occurs, the connection will be aborted and
136 If a MQTT message is received, an MQTT callback function will be called and an
141 the socket), call :c:func:`mqtt_sn_client_deinit`, which will deinit the transport as well.
153 * Setting the will topic and message after the initial connect
|
| /Zephyr-latest/cmake/linker/ |
| D | target_template.cmake | 7 # This file will define optional linker macros for toolchains that are not
|
| /Zephyr-latest/subsys/fs/ |
| D | Kconfig.fatfs | 43 If formatting is not needed, disabling this flag will slightly
45 Note: This option is destructive to data and will automatically
50 prior to connecting to a device, otherwise it will not be
60 Sets how many root directory entries will be allocated when
207 Value set here will be used as maximum supported read/write
209 Option affects write/read granularity and will increase
214 This will affect your compile time RAM allocation, when
217 When this value is set to 512, all mount points will use
218 512 as sector size, all other values will cause FAT driver
278 will be mounted.
|
| /Zephyr-latest/doc/project/ |
| D | tsc.rst | 114 declines a new term or if the TSC fails to reconfirm the term, the seat will
117 will be open for new members outside of the quarterly nomination limit. The
118 elected member will serve a 2 year term.
134 A representative’s suspension will end and voting rights be restored at the start
143 Notice of suspension will be sent to representatives who miss three consecutive
144 meetings, noting that rights will be restored upon next attendance of a TSC
152 Members who opt out and then wish to reclaim their seat later will have their
164 refinements. Until then, additional clarifications (if/where needed) will be
169 met, the default voting mechanism will be a verbal motion to determine if
173 - Should there be any objections raised, the vote will move to email, and be
|
| /Zephyr-latest/subsys/shell/ |
| D | Kconfig | 24 and memory requirements of the shell. Enabling it will choose Kconfig
61 this option is set shell will expect 0x7F for backspace key.
68 Enabling this will allocate additional RAM memory where
69 the string of the prompt will be stored.
135 Shell will not collect characters that are not in
136 ASCII range: <0, 127>. As a result filtered characters will not be
198 Meta keys will not be active when shell echo is set to off.
213 finds the string, it will automatically print a help message
278 When enabled, backend will use the shell for logging.
303 If enabled, shell will be automatically started.
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 46 Peripheral role. This will be described in more detail in a later
52 Most Zephyr-based BLE devices will most likely be peripheral-role
55 :c:func:`bt_gatt_service_register` API the application will typically
67 role device will scan for available peripheral device and choose one to
68 connect to. Once connected, a central will typically act as a GATT
72 To initially discover a device to connect to the application will likely
84 An observer role device will use the :c:func:`bt_le_scan_start` API to
85 scan for device, but it will not connect to any of them. Instead it will
92 A broadcaster role device will use the :c:func:`bt_le_adv_start` API to
93 advertise specific advertising data, but the type of advertising will be
[all …]
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_1.rst | 41 In case of Zephyr this gets a little bit confusing because DTS will use
43 to single application, but will name them as "image-0" and "image-1" respectively.
105 A response will only contain information for valid images, if an image can not
168 | "hash" | SHA256 hash of the image header and body. Note that this will not be |
243 If "confirm" is false or not provided, an image with the "hash" will be set for
244 test, which means that it will not be marked as permanent and upon hard reset
245 the previous application will be restored to the primary slot.
247 application will be assumed as target for confirmation.
306 | | continuation and image verification functionality will be unavailable). Should |
313 | | upload will be rejected. Zephyr compares major, minor and revision (x.y.z) by |
[all …]
|
| /Zephyr-latest/samples/subsys/usb/console/ |
| D | README.rst | 21 This sample can be built for multiple boards, in this example we will build it
31 The board will be detected as a CDC_ACM serial device. To see the console output
|
| /Zephyr-latest/samples/sensor/tmp108/ |
| D | Kconfig | 27 although this will work with one shot enabled,
38 although this will work with one shot enabled,
|
| /Zephyr-latest/samples/drivers/uart/passthrough/ |
| D | README.rst | 10 This sample will virtually connect two UART interfaces together, as if Zephyr
23 the chosen ``uart,passthrough`` device - the pins and baudrate will need to
|
| /Zephyr-latest/samples/boards/bbc/microbit/pong/ |
| D | README.rst | 18 When multi-player mode has been selected the game will try to look for
22 If the board has a piezo buzzer connected to pin 0, this will be used to
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.e1000 | 26 Enabling this will turn on the hexdump of the received and sent
44 If the value is set properly, the timer will be accurate.
|
| /Zephyr-latest/samples/boards/st/backup_sram/ |
| D | README.rst | 14 VBAT is preserved, the incremented value will be shown on the next power-cycle.
19 To exercise this sample with an independent VBAT source, you will need to
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 132 After that, it checks that the sector after this one is empty, or it will erase it.
188 This operation is time consuming and it will cause some applications to not meet their real time
192 almost full and of course it will trigger the garbage collection on the next sector.
193 This will guarantee the application that the next write won't trigger the garbage collection.
225 will make all existing data invalid.
234 So, if we suppose that 4 sectors exist in a partition, ZMS will only use 3 sectors to store
236 The empty sector will rotate between the 4 sectors in the partition.
244 Values smaller than 8 bytes will be stored within the entry (ATE) itself, without writing data
287 Using storage systems that rely on an erase-value (NVS as an example) will need to emulate the
288 erase with write operations. This will cause a significant decrease in the life expectancy of
[all …]
|
| /Zephyr-latest/samples/sensor/sensor_shell/ |
| D | Kconfig | 7 On boards that do not have a sensor, enabling this will build a fake
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | shell.rst | 35 This is done to ensure that all available log will be printed to the shell output.
41 time the device boots up, as the device will remember its provisioning data between reboots.
94 The message will be sent to the current destination address, using the current network and
96 the device will only send packets to itself. To change the destination address to the All Nodes
102 configured network and application keys will receive and process the messages we send.
169 Reset the local mesh node to its initial unprovisioned state. This command will also clear
216 Enable or disable Low Power operation. Once enabled, the device will turn off its radio and
279 …* ``FaultID``: If present, the given fault ID will be deleted. If omitted, all registered faults w…
317 beacons with the given UUID. Once found, the unprovisioned device will be added to the mesh
321 …* ``UUID``: UUID of the unprovisioned device. Providing a hex-string shorter than 16 bytes will po…
[all …]
|
1...<<11121314151617181920>>...66
