Home
last modified time | relevance | path

Searched refs:will (Results 126 – 150 of 1633) sorted by relevance

12345678910>>...66

/Zephyr-latest/soc/nxp/imx/imx7d/
DKconfig.defconfig.mcimx7d_m417 #-Disable this option if you use the bin format as this choice will enlarge it.
20 # will be filled in the bin file.
/Zephyr-latest/samples/bluetooth/hci_uart/boards/
Dnrf52833dk_nrf52833_df.overlay20 /* This is an example switch pattern that will be used to set an
26 * Radio peripheral. The pins will be acquired by Radio to
Dnrf5340dk_nrf5340_cpunet_df.overlay20 /* This is an example switch pattern that will be used to set an
26 * Radio peripheral. The pins will be acquired by Radio to
Dnrf54l15dk_nrf54l15_cpuapp_df.overlay20 /* This is an example switch pattern that will be used to set an
26 * Radio peripheral. The pins will be acquired by Radio to
/Zephyr-latest/samples/bluetooth/hci_uart_3wire/boards/
Dnrf5340dk_nrf5340_cpunet_df.overlay19 /* This is an example switch pattern that will be used to set an
25 * Radio peripheral. The pins will be acquired by Radio to
Dnrf52833dk_nrf52833_df.overlay19 /* This is an example switch pattern that will be used to set an
25 * Radio peripheral. The pins will be acquired by Radio to
/Zephyr-latest/samples/bluetooth/broadcaster/
DREADME.rst11 The application will periodically send out advertising packets with
14 (the number will roll back to 0 after 255).
/Zephyr-latest/boards/others/neorv32/
DCMakeLists.txt17 …message(STATUS "neorv32 binary will be written to: ${PROJECT_BINARY_DIR}/${CONFIG_KERNEL_BIN_NAME}…
27 …message(STATUS "neorv32 VHDL will be written to: ${PROJECT_BINARY_DIR}/${CONFIG_KERNEL_BIN_NAME}.v…
/Zephyr-latest/boards/ezurio/bl5340_dvk/
DKconfig13 The board which will be used for CPUNET domain when creating a multi
26 The board which will be used for CPUAPP domain when creating a multi
/Zephyr-latest/scripts/ci/
Dtwister_ignore.txt3 # The patterns listed in this file will be compared with the list of files
5 # are matched, then twister will not do a full run and optionally will only
/Zephyr-latest/samples/boards/nxp/mimxrt1060_evk/system_off/
DREADME.rst17 A power monitor will be able to distinguish among these states.
37 3. Device will turn on and idle for 2 seconds
38 4. Device will turn itself off using deep sleep state 1. Press SW 5
/Zephyr-latest/samples/drivers/misc/grove_display/
DREADME.rst25 You will need to connect the Grove LCD via the Grove shield onto a board that
28 On some boards you will need to use 2 pull-up resistors (10k Ohm) between the
33 characters will not be displayed on the LCD (3.3V is enough to power just the
/Zephyr-latest/boards/
Dindex.rst19 * Use the form below to filter the list of supported boards. If a field is left empty, it will
23 both a vendor and an architecture, only boards that match both will be displayed. Within a
24 single field, selecting multiple options (such as two architectures) will show boards matching
/Zephyr-latest/tests/benchmarks/sched_queues/
DREADME.rst19 times will be displayed. The following will build this project with verbose
30 the summary statistics will be parsed as data records.
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_callbacks.rst25 :kconfig:option:`CONFIG_MCUMGR_MGMT_NOTIFICATION_HOOKS` which will compile the
26 registration and notification system into the code. This will not provide any
66 event, which will be called after a MCUmgr command has been processed and
82 As an example, the following registration is allowed, which will register for 3
93 The following code is not allowed, and will cause undefined operation, because
135 by a handler will be returned to the MCUmgr client.
169 * (which will have failed set to true)
189 :c:enumerator:`MGMT_EVT_OP_FS_MGMT_FILE_ACCESS` event, which will be called
281 or earlier, then it will need to be migrated to the new system. To migrate
282 code, the following callback registration functions will need to be migrated
[all …]
/Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt/
DKconfig33 Use heap to allocate flash image upload context, otherwise a static variable will
40 to allocate this context or it will not be possible to perform DFU; it may also not be
109 When enabled, the MCUmgr will compare base address of application,
110 encoded into .bin file header with use of imgtool, on upload and will
119 The status list send back from the device will only be filled with data that is non-zero,
135 This will enable the upload check hook which will send image upload requests to
143 This will enable DFU status hooks which can be checked by the application to monitor DFU
150 This will enable use of a mutex to lock the image group object access, preventing issues
165 Note: setting this to a non-disabled option will prevent uploading of padded and
208 This will enable the slot information function which will return information about all
[all …]
/Zephyr-latest/doc/build/sysbuild/
Dindex.rst73 :file:`runners.yaml` files that each Zephyr build system will contain. These
79 as part of sysbuild, it will be prefixed with ``mcuboot_``. This also allows
270 For example, the following commands will work in the same way:
345 The deprecated MCUBoot Kconfig option ``CONFIG_ZEPHYR_TRY_MASS_ERASE`` will
430 target to execute and it will run.
472 application's :file:`sysbuild.cmake` file, or any other CMake file you know will
558 This will include ``second_sample`` by default, while still allowing you to
577 As a result, ``my_sample`` will be built as part of the sysbuild build invocation,
578 but it will be excluded from the default image sequence used by ``west flash``.
597 configuration files from the application (MCUboot) itself will be used.
[all …]
/Zephyr-latest/
DKconfig.zephyr20 # $ARCH and $KCONFIG_BOARD_DIR will be glob patterns when building documentation.
94 When enabled, the application will be linked into the flash partition
109 the kernel should be loaded into. Changing this value from zero will
110 affect the Zephyr image's link, and will decrease the total amount of
122 area that the Zephyr image will be allowed to occupy. If zero, the
123 image will be able to occupy from the FLASH_LOAD_OFFSET to the end of
178 script will be generated by the toolchain specific linker generator.
179 For LD based linkers, this will be the ld generator, for ARMClang /
180 armlink based linkers it will be the scatter generator.
234 where the kernel begins. Changing this value from zero will affect
[all …]
/Zephyr-latest/soc/intel/intel_adsp/
DKconfig87 Bytes to reserve at the start of HP-SRAM. Zephyr will not
95 When true, the trace_out layer will also use a SIMCALL
97 of an enclosing simulator process. All window contents will
125 When true, FW will store its entire context into IMR before
144 When true, FW will run with enabled clock gating. This options change
147 does not mean that this will happen).
/Zephyr-latest/doc/kernel/usermode/
Dkernelobjects.rst19 dereference these addresses, doing so will cause a memory protection fault.
39 will be freed.
65 Kernel objects that are found but do not meet the above conditions will not be
71 information will be printed if the script is run with the ``--verbose`` flag,
87 permissions on it) the object will be automatically freed. User threads
106 the object placement criteria will have their memory addresses placed in a
126 option and the build system will generate an error if this value is too low.
144 thread will then run in user mode with any permissions it had been granted
148 :c:macro:`K_INHERIT_PERMS` option, the child thread will be granted the
154 By default, when a user thread is created, it will only have access permissions
[all …]
/Zephyr-latest/drivers/serial/
DKconfig.native_posix34 Note that other, non UART messages, will also be printed to the
48 When ``--wait_uart`` is used, writes to the UART will be held until a
64 command line option, this will be the default command which will be
70 The 2nd UART will not be affected by this option.
/Zephyr-latest/soc/intel/intel_adsp/ace/
DKconfig31 When this option is enabled, the SRAM retention mode will be
33 the retention mode will not be activated.
/Zephyr-latest/soc/native/inf_clock/
DKconfig.soc8 clock. That means the CPU will always run in zero time until completion after
10 infinite loop in the code which does not sleep the CPU will cause the process
/Zephyr-latest/cmake/compiler/
Dcompiler_features.cmake12 # - `compile_feature_c99` will contain `c_std_90;c_std_99`
13 # - `compile_feature_iso9899:2011` will contain `c_std_90;c_std_99;c_std_11`
/Zephyr-latest/soc/nxp/mcx/mcxn/
DKconfig38 Indicates the second core will be enabled, and the part will run

12345678910>>...66