Searched refs:like (Results 226 – 250 of 517) sorted by relevance
12345678910>>...21
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 186 This is due to how Zephyr allocated threads' stacks are not *actually* being used like they are
257 development tools just like any other Linux application.
343 This final executable is typically called ``zephyr.exe`` and can be run or debugged just like any
351 When targeting native_sim, the native simulator is also built with some basic HW models like a
357 like the :ref:`simulated nRF5340 (nrf5340bsim)<nrf5340bsim>` are multi MCU targets. Where one
449 For more complex simulated boards, like :ref:`bsim ones<bsim boards>`, the board layer also provides
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.x86 | 34 older or idiosyncratic hardware (or environments like qemu
|
| /Zephyr-latest/doc/services/storage/fcb/ |
| D | fcb.rst | 7 flash like a FIFO. You append entries to the end, and read data from the
|
| /Zephyr-latest/boards/others/stm32f103_mini/doc/ |
| D | index.rst | 8 multiple version of this board like ``stm32f103_mini``.
|
| /Zephyr-latest/doc/services/portability/posix/implementation/ |
| D | index.rst | 6 In many ways, Zephyr provides support like any POSIX OS; API bindings are provided in the C
|
| /Zephyr-latest/cmake/ |
| D | package_helper.cmake | 34 # you just add the same argument to the helper like:
|
| /Zephyr-latest/boards/vcc-gnd/yd_stm32h750vb/doc/ |
| D | index.rst | 57 right USB drivers with a tool like `Zadig`_.
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | custom_cmake.rst | 31 variables when generating a build system for a Zephyr application, like so:
|
| /Zephyr-latest/subsys/net/lib/capture/ |
| D | Kconfig | 17 User can use network packet analyzer like Wireshark to
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 80 for running things like menuconfig with the prefix, for example (if using
329 To build a sample like ``hello_world`` with MCUboot,
443 when sysbuild is used, for example build targets like ``ram_report``,
465 used like so:
482 used like so:
499 used like so:
567 For an application, this would look like this:
793 If you want to add flashing dependencies instead, then do it like this:
|
| /Zephyr-latest/subsys/net/lib/config/ |
| D | Kconfig | 19 some link-layer dedicated settings like the channel.
213 functions like time(), gettimeofday(), etc. returned the
|
| /Zephyr-latest/boards/gd/gd32e507z_eval/doc/ |
| D | index.rst | 82 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/boards/gd/gd32f407v_start/doc/ |
| D | index.rst | 76 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/boards/others/stm32f401_mini/doc/ |
| D | index.rst | 80 right USB drivers with a tool like `Zadig`_.
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf54l15bsim.rst | 24 Just like for the nrf54l15dk target,
|
| /Zephyr-latest/doc/kernel/services/ |
| D | index.rst | 20 devices (like Wi-Fi and Bluetooth Low Energy), and complex multi-threading,
|
| /Zephyr-latest/samples/net/sockets/http_get/ |
| D | README.rst | 30 Build the Zephyr version of the application like this:
|
| /Zephyr-latest/samples/subsys/tracing/ |
| D | README.rst | 63 After the serial console has stable output like this:
|
| /Zephyr-latest/boards/phytec/phyboard_pollux/doc/ |
| D | index.rst | 11 Coretex-M7 core for real time applications like Zephyr. The phyBOARD-Pollux
12 can be used for various applications like SmartHomes, Industry 4.0, IoT etc.
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net-stack-architecture.rst | 45 * Application-level network protocols like CoAP, LWM2M, and MQTT.
48 * Core network protocols like IPv6, IPv4, UDP, TCP, ICMPv4, and ICMPv6.
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | menuconfig.rst | 68 something like ``python3-tk``/``python3-tkinter``.
92 things would look like in the ``menuconfig`` interface.
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | rbtree.rst | 53 environments that forbid the use of unbounded stack techniques like
56 There is also a :c:macro:`RB_FOR_EACH` iterator provided, which, like the
|
| /Zephyr-latest/doc/develop/tools/ |
| D | coccinelle.rst | 89 diff-like style.Lines of interest are indicated with ``-``.
206 is redirected to /dev/null, if you'd like to capture stderr you
481 in a diff-like style.
484 The diff-like output generated is NOT an applicable patch. The
|
| /Zephyr-latest/boards/nordic/nrf52840dongle/doc/ |
| D | index.rst | 165 something like ``COMx`` on Windows, and something else on macOS.
215 something like ``COMx`` on Windows, and something else on macOS.
234 ``COMx`` device). On Linux, something like
|
| /Zephyr-latest/boards/acrn/acrn/doc/ |
| D | index.rst | 65 elements like kconfig defconfig files or devicetree includes. You
88 Find the "<vm id="0">...<os_config>" tag that will look something like this:
224 can type them yourself if you like:
|
12345678910>>...21
