Searched refs:will (Results 1151 – 1175 of 1633) sorted by relevance
1...<<41424344454647484950>>...66
| /Zephyr-latest/samples/shields/x_nucleo_iks01a3/standard/ |
| D | README.rst | 49 not present, it will just be skipped.
|
| /Zephyr-latest/cmake/compiler/clang/ |
| D | compiler_flags.cmake | 48 # C implicit promotion rules will want to make floats into doubles very easily
|
| /Zephyr-latest/samples/subsys/shell/shell_module/ |
| D | README.rst | 102 Example usage: [ dynamic add test ] will add a dynamic command
|
| /Zephyr-latest/boards/sparkfun/micromod/ |
| D | micromod_nrf52840.dts | 187 * Storage partition will be used by FCB/LittleFS/NVS
|
| /Zephyr-latest/boards/others/stm32f030_demo/doc/ |
| D | index.rst | 90 You will see the LED blinking every second.
|
| /Zephyr-latest/boards/snps/hsdk/support/ |
| D | openocd.cfg | 38 # CHIPNAME will be used to choose core family (600, 700 or EM). As far as
|
| /Zephyr-latest/boards/snps/hsdk4xd/support/ |
| D | openocd.cfg | 38 # CHIPNAME will be used to choose core family (600, 700 or EM). As far as
|
| /Zephyr-latest/samples/arch/smp/pktqueue/ |
| D | README.rst | 40 is created, which will control "sender" queue processing.
|
| /Zephyr-latest/samples/basic/blinky/ |
| D | README.rst | 50 You will see a build error at the source code line defining the ``struct
|
| /Zephyr-latest/boards/m5stack/m5stack_atoms3/doc/ |
| D | index.rst | 89 The usual ``flash`` target will work with the ``m5stack_atoms3`` board
|
| /Zephyr-latest/boards/st/nucleo_f746zg/ |
| D | nucleo_f746zg.dts | 14 * WARNING: The pin PA7 will conflict on selection of SPI_1 and ETH_STM32_HAL.
|
| /Zephyr-latest/include/zephyr/arch/sparc/ |
| D | linker.ld | 151 * will not be cleared during the boot process.
|
| /Zephyr-latest/boards/m5stack/m5stack_atom_lite/doc/ |
| D | index.rst | 87 The usual ``flash`` target will work with the ``m5stack_atom_lite`` board
|
| /Zephyr-latest/boards/m5stack/m5stack_atoms3_lite/doc/ |
| D | index.rst | 87 The usual ``flash`` target will work with the ``m5stack_atoms3_lite`` board
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.timer | 9 Select 'y' here and Zephyr will provide implementations of clock_getres(), clock_gettime(),
|
| /Zephyr-latest/samples/net/prometheus/ |
| D | README.rst | 87 Once restarted, Prometheus will start scraping metrics from your server according
|
| /Zephyr-latest/samples/net/sockets/coap_download/ |
| D | README.rst | 12 a blockwise transfer will be used to receive the data.
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server/ |
| D | README.rst | 64 Linux. (Note: if you look at the source, you will see that the code is
|
| /Zephyr-latest/subsys/net/l2/ppp/ |
| D | Kconfig | 106 TCP stack will consume all net_bufs before transferring
|
| /Zephyr-latest/boards/nxp/mimxrt1010_evk/ |
| D | mimxrt1010_evk.dts | 174 * timer will be used instead of systick, as allows the core clock to
|
| /Zephyr-latest/boards/nxp/mimxrt1170_evk/ |
| D | mimxrt1170_evk_mimxrt1176_cm7.dts | 131 * timer will be used instead of systick, as allows the core clock to
|
| /Zephyr-latest/tests/arch/arm/arm_thread_swap/ |
| D | README.txt | 17 - the swap return value can be set and will be return, properly,
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 97 save energy independently of the system power state. Devices will keep
98 reference of their usage and will automatically be suspended or resumed.
178 repository that will be cloned and managed by west when working with the
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | shell.rst | 153 ``can start`` subcommand as shown below. This will enable reception and transmission of CAN frames.
230 If :kconfig:option:`CONFIG_CAN_RX_TIMESTAMP` is enabled, each line will be prepended with a
268 the command will wait indefinitely for the bus recovery to succeed.
|
| /Zephyr-latest/include/zephyr/arch/x86/ia32/ |
| D | linker.ld | 33 * the Zephyr Kernel image. If a symbol is used but not defined the linker will
330 * will be removed with "--gc-sections" by LLVM lld, so add keep
389 /* ROM ends here, position counter will now be in RAM areas */
|
1...<<41424344454647484950>>...66
