Searched refs:done (Results 351 – 375 of 469) sorted by relevance
1...<<111213141516171819
/Zephyr-latest/boards/st/nucleo_h755zi_q/doc/ |
D | index.rst | 145 two cores. This is done in 3 ways:
|
/Zephyr-latest/boards/st/nucleo_u083rc/doc/ |
D | index.rst | 243 This can be done by executing the following commands.
|
/Zephyr-latest/boards/st/nucleo_u575zi_q/doc/ |
D | index.rst | 260 This can be done by executing the following commands.
|
/Zephyr-latest/arch/arm64/core/ |
D | Kconfig | 197 the bounds of the current process stack are overflowed. This is done
|
/Zephyr-latest/boards/96boards/meerkat96/doc/ |
D | index.rst | 181 configuration is done in the file :zephyr_file:`boards/96boards/meerkat96/96b_meerkat96_mcimx7d_m4.…
|
/Zephyr-latest/tests/net/lib/lwm2m/interop/ |
D | README.md | 7 These tests require setup that is not done in Twister run, so follow this documentation to set
|
/Zephyr-latest/doc/releases/ |
D | migration-guide-3.5.rst | 31 error and have to be done correctly using 203 ``clocks`` node as it is done for other peripherals, for example, to select
|
/Zephyr-latest/boards/native/doc/ |
D | bsim_boards_design.rst | 368 targets. In the case of the bsim targets this is done by explicitly targeting 369 x86 (ILP32 ABI) instead of x86_64. This is done purposefully to provide more
|
/Zephyr-latest/subsys/bluetooth/host/shell/ |
D | bt.c | 753 goto done; in connected() 761 goto done; in connected() 776 done: in connected() 3499 goto done; in cmd_info() 3545 done: in cmd_info()
|
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/ |
D | ull_llcp_internal.h | 166 uint8_t done; member
|
/Zephyr-latest/scripts/west_commands/completion/ |
D | west-completion.zsh | 111 done
|
/Zephyr-latest/doc/kernel/services/other/ |
D | fatal.rst | 216 no protection against data corruption. Since the checks are typically done at
|
/Zephyr-latest/doc/contribute/documentation/ |
D | generation.rst | 221 collect and generate the HTML content. When done, you can view the HTML
|
/Zephyr-latest/doc/hardware/porting/ |
D | soc_porting.rst | 112 Detailed configurations, such as hardware description and configuration are done
|
/Zephyr-latest/doc/kernel/memory_management/ |
D | demand_paging.rst | 20 written back into the backing store. If no modifications is done or
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | blob.rst | 114 called repeatedly to move data to or from the BLOB. When the model is done processing the block, it
|
/Zephyr-latest/boards/st/nucleo_h745zi_q/doc/ |
D | index.rst | 157 two cores. This is done in 3 ways:
|
/Zephyr-latest/boards/st/nucleo_l552ze_q/doc/ |
D | nucleol552ze_q.rst | 199 Once done, before flashing, you need to first run a generated script that
|
/Zephyr-latest/boards/96boards/carbon/doc/ |
D | stm32f401xe.rst | 343 into DFU mode if you haven't done this before:
|
/Zephyr-latest/boards/nordic/nrf5340dk/doc/ |
D | index.rst | 203 Kconfig option ``BUILD_WITH_TFM`` to be enabled, which is done by
|
/Zephyr-latest/boards/nxp/imx8mp_evk/doc/ |
D | index.rst | 189 configuration is done based on board name (imx8mp_evk/mimx8ml8/m7 for ITCM and
|
/Zephyr-latest/boards/nxp/mimxrt595_evk/doc/ |
D | index.rst | 206 if not already done (these jumpers are installed by default).
|
/Zephyr-latest/boards/nxp/mimxrt685_evk/doc/ |
D | index.rst | 241 if not already done (these jumpers are installed by default).
|
/Zephyr-latest/boards/element14/warp7/doc/ |
D | index.rst | 174 configuration is done in the file :zephyr_file:`boards/element14/warp7/warp7_mcimx7d_m4.dts` with
|
/Zephyr-latest/subsys/net/ip/ |
D | Kconfig | 114 from inside qemu to host system. This can be done either via 1023 The RX calculation is done only for UDP, TCP or RAW packets, 1025 done for all network protocol packets.
|
1...<<111213141516171819