Home
last modified time | relevance | path

Searched refs:will (Results 951 – 975 of 1633) sorted by relevance

1...<<31323334353637383940>>...66

/Zephyr-latest/arch/xtensa/core/
DREADME_WINDOWS.rst17 and WINDOWBASE is 15, quads 15, 0, 1, and 2 will be visible as
53 will be set by the ENTRY instruction, and remain set after rotations
56 each call frame that is live in hardware registers, and it will be
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dcap.rst9 The Acceptor will typically be a resource-constrained device, such as a headset, earbud or hearing
17 calling :code:`cap_acceptor init`, which will register the CAS and CSIS services, as well as
43 If :code:`CONFIG_BT_CSIP_SET_MEMBER_NOTIFIABLE` is enabled, this will also notify connected
66 The Initiator will typically be a resource-rich device, such as a phone or PC. The Initiator can
200 The following commands will setup a CAP broadcast source using the 16_2_1 preset (defined by BAP):
242 The Commander will typically be a either co-located with a CAP Initiator or be on a separate
/Zephyr-latest/doc/services/device_mgmt/smp_groups/
Dsmp_group_8.rst33 already downloaded and where their position in the file is (MCUmgr will cache
38 Note that file handles will remain open for consecutive requests (as long as
162 Allows to upload a file to a specified location. Command will automatically overwrite
167 Note that file handles will remain open for consecutive requests (as long as
170 even be removed. Note that file handles will remain open for consecutive
471 Note that the default type will be crc32 if it is enabled, or sha256 if crc32 is
/Zephyr-latest/boards/intel/adsp/doc/
Dintel_adsp_generic.rst31 However, the instructions are generic and will work on other boards unless
32 otherwise stated. You will be referred to the documentation for your specific
50 Note that if you plan to use SOF on your board, you will need to build and
61 you will also need to set up the SOF rimage signing tool and key.
159 this point onward, we will refer to the board as the "remote host" and your
163 :zephyr_file:`soc/intel/intel_adsp/tools/remote-fw-service.py` will receive
/Zephyr-latest/subsys/mgmt/hawkbit/
DKconfig34 Set the interval that the hawkbit update server will be polled.
35 This time interval is zero and 43200 minutes(30 days). This will be overridden
/Zephyr-latest/drivers/ethernet/nxp_enet/
DKconfig134 Setting this option will configure MCUX clock block to feed RMII
179 If the value is set properly, the timer will be accurate.
/Zephyr-latest/drivers/sensor/
DKconfig46 support streaming (usually hardware FIFO backed), the shell will continue
72 interrupt handler will collect data.
/Zephyr-latest/doc/kernel/services/data_passing/
Dstacks.rst37 If :kconfig:option:`CONFIG_NO_RUNTIME_CHECKS` is enabled, the kernel will *not* detect
40 already full will result in array overflow, and lead to unpredictable behavior.
/Zephyr-latest/samples/boards/nordic/mesh/onoff-app/
DREADME.rst22 the secondary elements will appear at 0x101, 0x102 and 0x103.
27 If a LED server is provided with a publish address, it will
/Zephyr-latest/samples/boards/st/ccm/
DREADME.rst26 buffers that will receive data). Compared to bss or data the
49 The first time the example is run after power on, the output will
/Zephyr-latest/boards/ruuvi/ruuvitag/doc/
Dindex.rst90 * 13 = P0.19 = LED2 (green) / GPIO (can be used as a GPIO pin but the LED will blink)
91 * 14 = P0.17 = LED1 (red) / GPIO (can be used as a GPIO pin but the LED will blink)
/Zephyr-latest/doc/services/input/
Dindex.rst35 subscribers with no device filter will receive the event.
43 callback will receive all the events in the system. This is the only type of
/Zephyr-latest/samples/boards/96boards/argonkey/microphone/
DREADME.rst70 case the oversampling/decimation factor will be 64.
72 At the end of the acquisition the PCM data will be printed on the terminal
/Zephyr-latest/drivers/ethernet/
DKconfig.stm32_hal131 If the value is set properly, the timer will be accurate.
165 hash set in the multicast table will be received and all
/Zephyr-latest/include/zephyr/arch/x86/intel64/
Dlinker.ld31 * ... there is no 16-bit code yet, but there will be when we add SMP.
154 /* This should be put here before BSS section, otherwise the .bss.__gcov will
/Zephyr-latest/boards/m5stack/m5stack_stamps3/doc/
Dindex.rst107 supply. If this pin is pulled low this main 3.3V power supply for the MCU will be
145 The usual ``flash`` target will work with the ``m5stack_stamps3`` board
/Zephyr-latest/lib/heap/
DKconfig41 Setting this to a high level will cause the heap to return
46 properties ("most" allocations that fit will succeed) but
/Zephyr-latest/boards/nxp/frdm_rw612/doc/
Dindex.rst157 ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_ble_a2.bin`` will be linked
167 ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_wifi_a2.bin`` will be linked
/Zephyr-latest/boards/olimex/stm32_h103/doc/
Dindex.rst185 will have to use an external probe connected to the available 20-pin JTAG
188 By default when using ``west debug`` ST-Link will be used with OpenOCD's
/Zephyr-latest/tests/benchmarks/app_kernel/
DREADME.txt9 benchmark will execute with four configurations (kernel/kernel, kernel/user,
11 will omit both the memory slabs and mailbox tests.
/Zephyr-latest/doc/releases/
Drelease-notes-3.4.rst57 (:kconfig:option:`CONFIG_MCUBOOT_IMG_MANAGER`) will now need to also select
141 the user-allocated sensor trigger will be stored by the driver as a pointer,
176 using picolibc, only applications using picolibc will be affected by this
203 addition, if the file access state is not lost, it will now only be called
236 been dropped. This function will now just reboot the device without changing
680 folder/s by using ``--alt-config-root``. When a test is found, Twister will
683 ``$test_root/tests/foo/testcase.yaml``, Twister will use
718 * When MCUboot image signing is enabled, a warning will now be emitted by cmake
721 the user that the generated image will not be bootable by MCUboot as-is.
728 If you have been using custom partition layout for MCUboot, you will have to label
[all …]
/Zephyr-latest/boards/snps/emsdp/doc/
Dindex.rst260 Software Development Platform, but it will load the application and immediately run.
261 If power is removed, the application will be lost since it wasn't written to flash.
263 Most of the time you will not be flashing your program but will instead debug
/Zephyr-latest/boards/nxp/imx8mp_evk/doc/
Dindex.rst138 This will build an image with the synchronization sample app, boot it and
188 At compilation time you have to choose which RAM will be used. This
264 M7 Core will get the first instruction from zero address of ITCM, but romstart relocation
265 will make the storage size of zephyr.bin too large, so we don't enable it by default in
/Zephyr-latest/boards/nxp/mimxrt1160_evk/doc/
Dindex.rst225 running at 600MHz. When targeting the M4 core, SysTick will also be used,
229 oscillator on the board will be used as a source for the GPT timer to
252 sample will do this automatically by setting the image order.
292 Regardless of your choice in debug probe, we will use the OpenSDA
/Zephyr-latest/boards/element14/warp7/doc/
Dindex.rst8 Zephyr was ported to run on the M4 core. In a later release, it will also
173 At compilation time you have to choose which RAM will be used. This
197 Below you will find the instructions to load and run Zephyr on M4 from A7 using
200 Connect both micro USB interfaces into the PC. In one USB interface you will

1...<<31323334353637383940>>...66