Home
last modified time | relevance | path

Searched refs:will (Results 151 – 175 of 1633) sorted by relevance

12345678910>>...66

/Zephyr-latest/tests/kernel/common/
Dmultilib.txt8 (for example, ARM Cortex-M requires thumb2 multilib and will be broken with
11 will call support routine(s) in libgcc and checks for expected result.
/Zephyr-latest/samples/bluetooth/scan_adv/
DREADME.rst11 role functionality. The application will periodically send out
14 has received (the number will roll back to 0 after 255).
/Zephyr-latest/samples/drivers/led/pwm/
DKconfig10 If set to 0, the short-cycle blinking demo will not be performed.
18 If set to 0, the long-cycle blinking demo will not be performed.
/Zephyr-latest/boards/makerdiary/nrf52840_mdk_usb_dongle/
DKconfig.defconfig18 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION
19 # which will make it link into the correct partition specified in DTS file,
/Zephyr-latest/boards/nordic/thingy53/
DKconfig18 The board which will be used for CPUNET domain when creating a multi
31 The board which will be used for CPUAPP domain when creating a multi
/Zephyr-latest/drivers/flash/
DKconfig.nordic_qspi_nor29 When CONFIG_FLASH_PAGE_LAYOUT is used this driver will support
40 these restrictions. Such data will be copied into this buffer to
41 allow the write to proceed. Multiple transfers will be initiated
53 This will also disable power management for the QSPI NOR flash chip.
DKconfig.simulator45 …If selected, writing to a non-erased program unit will succeed, otherwise, it will return an error.
50 but only change from erase-value to opposite will be registered.
89 Only up to this number of beginning pages will be tracked
/Zephyr-latest/
D.gitlint7 # By default gitlint will ignore merge commits. Set to 'false' to disable.
15 # Set the extra-path where gitlint will search for user defined rules
34 # will not cause a violation, but "WIP: my title" will.
/Zephyr-latest/subsys/mgmt/mcumgr/grp/fs_mgmt/
DKconfig36 Maximum file size that will be allowed to be downloaded from
62 This value affects how much of data will fit into download buffer,
71 By default file chunk, that will be read off storage and fit into
74 Enabling this option allows to set MAXIMUM value that will be
85 Sets the MAXIMUM size of chunk which will be rounded down to
86 number of bytes that, with all the required headers, will fit
88 might be lower then selected, in which case compiler warning will
137 Enable the supported hash/checksum command which will return details on
177 then MGMT_ERR_EBUSY will be returned.
188 file handle cleaned up. Each access to the file will reset the idle
/Zephyr-latest/doc/services/storage/nvs/
Dnvs.rst33 data CRC will make all existing data invalid.
39 During initialization NVS will verify the data stored in flash, if it
40 encounters an error it will ignore any data with missing/incorrect metadata.
63 - ``NVS_FLASH_DEVICE`` is a reference to the flash device that will be used. The
90 first sector will be full after 1024/12 = 85.33 minutes. After another 85.33
92 only two sectors, the first sector will be used for storage and will be erased
115 The NVS in-flash image will stay compatible unless the
131 disabled, the NVS application will get an MPU fault if it references
134 and the NVS API will return an ``-ETIMEDOUT`` error.
/Zephyr-latest/cmake/modules/
Darch_v2.cmake8 # This CMake module will set the following variables in the build system based
11 # If no implementation is available for the current arch an error will be raised.
14 # The following variables will be defined when this CMake module completes:
Droot.cmake7 # This CMake module will convert all relative paths in existing ROOT lists to
17 # If a root is defined it will check the list of paths in the root and convert
19 # If a root is undefined it will still be undefined when this module has loaded.
/Zephyr-latest/samples/fuel_gauge/max17048/
DREADME.rst33 if you plug/unplug a charger it will take some time until it is actually detected by the chip. Don'…
34 to see in real time the charging status change because it will not work. If you really need to know…
35 when the battery is being charged you will need other method.
/Zephyr-latest/tests/subsys/sd/mmc/
DREADME.txt8 use. It requires an SD card be connected to the board to pass, and will
20 block reads. Ensure the subsystem will reject reads beyond the end of
24 block writes. Ensure the subsystem will reject writes beyond the end of
/Zephyr-latest/tests/subsys/sd/sdmmc/
DREADME.txt8 use. It requires an SD card be connected to the board to pass, and will
20 block reads. Ensure the subsystem will reject reads beyond the end of
24 block writes. Ensure the subsystem will reject writes beyond the end of
/Zephyr-latest/subsys/rtio/
DKconfig16 adds a small RAM overhead for a single semaphore. By default wait_for will
29 will use polling on the completion queue with a k_yield() in between
39 without a pre-allocated memory buffer. Instead the buffer will be taken
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob_cli.rst64 not :c:macro:`BT_MESH_ADDR_UNASSIGNED`, the messages in the transfer will be sent to the group
73 losing Target nodes. Using group addresses for BLOB transfers will generally only pay off if the
74 list of Target nodes is extensive, and the effectiveness of each addressing strategy will vary
92 Increasing the wait time will increase this delay.
100 to respond, or respond with incompatible transfer parameters, will be dropped.
104 non-overlapping block size range, it will be dropped. Lost Target nodes will be reported through the
122 <bt_mesh_blob_cli_cb.end>` callback. Lost Target nodes will be reported through the
/Zephyr-latest/drivers/serial/
DKconfig.altera23 Enabling this will cause the transmitter to wait for rising edge of CTS before sending.
24 …The receiver will deassert RTS as soon as a byte is received and reassert after the byte is fetche…
/Zephyr-latest/share/sysbuild/
DCMakeLists.txt11 # This will update the APP_DIR cache variable to PATH type and apply a comment.
12 # If APP_DIR is a relative path, then CMake will adjust to absolute path based
/Zephyr-latest/drivers/mipi_dsi/
DKconfig.mcux25 Use SMARTDMA. This accelerator will automatically
34 format, which will then be byte swapped.
/Zephyr-latest/boards/panasonic/pan1783/
DKconfig14 The board which will be used for CPUNET domain when creating a multi
27 The board which will be used for CPUAPP domain when creating a multi
/Zephyr-latest/boards/nordic/nrf52840dongle/
DKconfig.defconfig16 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION
17 # which will make it link into the correct partition specified in DTS file,
/Zephyr-latest/arch/arm64/core/xen/
DKconfig20 Built binary will be used as Xen privileged domain (Domain 0).
35 interface that Zephyr will use to communicate with the hypervisor.
/Zephyr-latest/tests/subsys/sd/sdio/
DREADME.txt5 devices. Note that this test will only perform basic reads from the SDIO card
6 after initialization, as most registers present on the card will be vendor
/Zephyr-latest/modules/mbedtls/
DKconfig78 twice this value will be allocated (on mbedTLS own heap, so the
89 mbedTLS/Zephyr integration (e.g. native TLS sockets), this will
92 If you use mbedTLS directly instead, you will need to perform
129 __FILE__ macro to files' basenames. This will reduce code footprint
138 Filename passed as argument to debug hook will be stripped from
144 Disable basename extraction from filenames in log mesasges. This will
179 is enabled otherwise the build will fail.
188 Zephyr will, during the device startup, initialize the heap automatically.
197 The mbedtls routines will use this heap if enabled.
220 By default mbed TLS will be initialized at Zephyr init. Disabling this option
[all …]

12345678910>>...66