Searched refs:will (Results 51 – 75 of 1633) sorted by relevance
12345678910>>...66
| /Zephyr-latest/subsys/mgmt/mcumgr/transport/ |
| D | Kconfig.lorawan | 28 this port will be treated as SMP packets.
34 Will use confirmed uplink packets for responses if enabled, otherwise will use
43 single message to be received, otherwise will support messages up to a single packet in
52 server, this will allow the next packet to be received without waiting for next
63 Stack size of the thread that will poll for empty additional packets when a partial
87 single uplink message. If disabled then uplinks that are too large will not be sent.
|
| /Zephyr-latest/lib/libc/newlib/ |
| D | Kconfig | 20 will be used for the newlib malloc() heap. The actual amount of
21 memory used will be the minimum of this value and the amount of
30 newlib heap. An assertion failure message will be displayed during
45 If this is left at 0, then remaining system RAM will be used for this
51 Build with floating point printf enabled. This will increase the size of
57 Build with floating point scanf enabled. This will increase the size of
|
| /Zephyr-latest/include/zephyr/linker/common-rom/ |
| D | common-rom-kernel-devices.ld | 10 * sorted in the order they will be initialized (i.e. ordered
30 * zephyr_pre0.elf is built, the linker will end up dropping it.
32 * built), the symbol will be added to the text section since it's
35 * the linking stages will end up shifting the addresses of the
36 * functions, which, in turn, will end up messing the ISR table
37 * (as the entries from _sw_isr_table will end up pointing to
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu_srv.rst | 48 :c:enum:`bt_mesh_dfu_effect`. The DFU effect return parameter will be communicated back to the
49 Distributor, and should indicate what effect the firmware update will have on the mesh state of the
57 If the transfer will cause the device to change its Composition Data or become
60 When the transfer will cause the Composition Data to change, and the
62 will be represented by Composition Data Pages 128, 129, and 130. The Models Metadata of the new
63 firmware image will be represented by Models Metadata Page 128. Composition Data Pages 0, 1 and 2,
64 and Models Metadata Page 0, will represent the Composition Data and the Models Metadata of the old
71 Metadata. The old Composition Data will then be loaded into Composition Data Pages 0, 1 and 2,
72 while the Composition Data in the new firmware will be loaded into Composition Data Pages 128, 129
73 and 130. The Models Metadata for the old image will be loaded into Models Metadata Page 0, and the
[all …]
|
| /Zephyr-latest/subsys/demand_paging/eviction/ |
| D | Kconfig | 16 This option is chosen when the eviction algorithm will be implemented
23 A periodic timer will clear the accessed state of all virtual pages.
24 When a page frame needs to be evicted, the algorithm will prefer to
50 A periodic timer will fire that clears the accessed state of all virtual
52 still has the accessed property, it will be considered as recently used.
|
| /Zephyr-latest/subsys/mgmt/mcumgr/mgmt/ |
| D | Kconfig | 16 notifications which will result in callbacks when a registered event occurs. Note that
22 registered and will all be called when registered events occur.
25 or decline the current operation, by returning false this will signal to the calling
32 This will add an extra field to the struct mgmt_handler that will allow a user
|
| /Zephyr-latest/soc/altr/zephyr_nios2f/cpu/ |
| D | README | 7 You will need the Quartus SDK in order to modify this CPU or flash it onto
17 The 'make flash' target will also package up the kernel and CPU into a single
18 .pof file which will then put the image onto the device using quartus_pgm tool.
|
| /Zephyr-latest/samples/tfm_integration/psa_crypto/ |
| D | Kconfig | 20 Enabling this option will make the 'psa' shell command available.
37 A static key value will be used for the elliptic curve 'secp256r1'
44 A randomly generated value will be used for the elliptic curve
|
| /Zephyr-latest/samples/bluetooth/periodic_sync_conn/ |
| D | README.rst | 13 This sample will send its address in response to the advertiser when receiving
14 subevent data. Once the connection is established, it will disconnect and wait
30 another board that will start periodic advertising and connect to this sample
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | tls_credentials_shell.rst | 53 Credential contents can be provided in-line with the call to ``cred add``, or will otherwise be sou…
82 …"``<DATA>``", "If provided, this argument will be used as the credential data, instead of any data…
200 …tents (so different storage formats for essentially identical credentials will have different dige…
201 …ific to the storage backend otherwise. Lines for which status is not zero will be printed with err…
203 After the list is printed, a final summary of the found credentials will be printed in the form:
243 …a entered into shell will be decoded from base64 into raw binary before storage. No terminator wil…
244 …red into shell will be decoded from base64 into raw binary and a NULL terminator will be appended …
245 …o shell will be passed into storage as-written, without a NULL terminator.", "Stored data will be …
246 …will be passed into storage as-written, with a NULL terminator.", "NULL terminator will be truncat…
|
| /Zephyr-latest/subsys/net/conn_mgr/ |
| D | Kconfig | 12 When enabled, this will start the connection manager that will
14 whether an interface is connected or not. It will then raise
29 Sets the stack size which will be used by the connection manager for connectivity monitoring.
|
| /Zephyr-latest/soc/nxp/lpc/lpc55xxx/ |
| D | Kconfig.defconfig | 14 # Indicates the second core will be enabled, and the part will run
23 # core, so that JLink flash will load it correctly.
29 # By default, CMSIS SystemInit will enable the clock to these RAM banks.
|
| /Zephyr-latest/doc/build/flashing/ |
| D | configuration.rst | 17 Flashing configuration is singular, it will only be read from a single location, this
38 means that the command will be ran once with the first image flashing process per set of board
39 targets, or to ``last`` which will be ran once for the final image flash per set of board targets.
42 command will only be used once for any board targets which used the nRF5340 SoC application or
43 network CPU cores, and will only reset the network or application core after all images for the
86 applications, the run once configuration will not be used. When flashing a sysbuild project with
87 multiple images, the flash runner run once configuration will be applied.
89 For example, building the :zephyr:code-sample:`smp-svr` sample for the nrf5340dk which will
98 both applications and will only perform a single device recovery operation when programming the
|
| /Zephyr-latest/samples/bluetooth/periodic_adv_conn/ |
| D | README.rst | 14 is application specific. This sample will connect to any synced device
15 responding with its address. Once the connection is established, it will
31 Zephyr tree that will synchronize and respond to this sample.
|
| /Zephyr-latest/samples/drivers/i2s/output/ |
| D | README.rst | 14 The sample will send a short burst of audio data, consisting of a sine wave.
15 The I2S TX queue will then be drained, and audio output will stop.
|
| /Zephyr-latest/drivers/pcie/host/ |
| D | Kconfig | 44 enabled, PCI(e) devices which support MSI will be configured (at
53 MSI can support up to 32 different messages. This will enable the
55 assigned to it. This will require for the selected architecture
64 If a device exposes support for both MSI-X and MSI, MSI-X will be
73 This will enable support both PTM root and PTM requester features.
80 This will enable retrieve interrupt routing information for PCI legacy
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_user_setup.rst | 22 this gateway, which will filter out packets based on the QEMU command line
40 Once this configuration option is enabled, all QEMU launches will use SLIRP.
42 not pass any arguments to it. This means that the Guest will only be able to
44 will be dropped by QEMU.
57 offloads this to the user, and expects that they will provide arguments
66 this command line will be reported by QEMU only. Here's what this particular
67 example will do,
87 Therefore, IPv6 will not work with User Networking.
|
| D | network_tracing.rst | 14 are enabled. The system will start to collect the receiving and sending call
16 It will also collect packet sending or receiving timings i.e., how long
22 API support are enabled. The system will start to collect what BSD socket
|
| /Zephyr-latest/cmake/modules/ |
| D | shields.cmake | 7 # This module will validate the SHIELD argument.
10 # error will be raised and a list of valid shields will be printed.
13 # The following variables will be defined when this module completes:
19 # The following targets will be defined when this CMake module completes:
20 # - shields: when invoked, a list of valid shields will be printed
23 # a warning will be printed.
46 # After processing all shields, only invalid shields will be left in this list.
|
| /Zephyr-latest/doc/services/pm/ |
| D | device_runtime.rst | 17 When device runtime power management is enabled on a device, its state will be
19 not used. On the first device request, it will be resumed and so put into the
20 :c:enumerator:`PM_DEVICE_STATE_ACTIVE` state. The device will remain in this
21 state until it is no longer used. At this point, the device will be suspended
23 device will be immediately put into the
25 asynchronously, it will be put into the
69 When runtime PM is enabled on a device it will no longer be resumed or suspended
83 devices to operate (e.g. a sensor may depend on a bus device), the bus will
91 indicate it *needs* the device to be active or operational. This function will
94 is no longer needed. This function will decrease the device usage count and
[all …]
|
| /Zephyr-latest/soc/nordic/nrf52/ |
| D | CMakeLists.txt | 7 …_SPIM_DESPITE_PAN_58 and an NRF SPIM driver are enabled, therefore PAN 58 will apply if RXD.MAXCNT…
13 …NOMALY_109_WORKAROUND disabled with SPIS, SPIM, TWIM or PWM enabled. This will occasionally cause …
|
| /Zephyr-latest/tests/boards/espressif/ethernet/ |
| D | Kconfig | 13 If no address is assigned within this time, test will fail.
20 If no reply is received within this time, test will fail.
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 7 given API will not change in future releases. At the same time, developers
71 Changes will not be announced.
91 minor changes. Backwards-compatibility will be maintained if reasonable.
110 will be merged
162 The RFC will then receive feedback through issue comments and will also be
164 community at large will have a chance to discuss it in detail.
170 proceed with confidence that it will be accepted.
192 Once the steps above have been completed, the outcome of the proposal will
207 Breaking API changes will be listed and described in the migration guide.
215 Deprecation and removal of APIs will be announced in the "API Changes"
[all …]
|
| /Zephyr-latest/tests/subsys/logging/log_blocking/ |
| D | Kconfig | 14 Specify the maximum rate at which messages will be logged from the
21 Specify the maximum rate at which log messages will be handled by
|
| /Zephyr-latest/subsys/testsuite/ztest/ |
| D | Kconfig | 124 This rule will call z_test_1cpu_start before each unit test and
133 This rule will fail the project if not all tests have been run.
140 This rule will reset gcov counters before running tests. This ensures
149 This rule will shuffle the order of tests and test suites.
153 int "[DEPRECATED] Number of iterations the test suite will run"
160 int "[DEPRECATED] Number of iterations the test will run"
171 This rule will repeat the tests and the test suites.
175 int "Number of iterations the test suite will run"
178 This rule will execute a test suite N number of times.
181 int "Number of iterations the test will run"
[all …]
|
12345678910>>...66
