Searched refs:simply (Results 51 – 75 of 127) sorted by relevance
123456
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | smp_transport.rst | 26 introduced when a request or response is fragmented; the payload is simply
|
| /Zephyr-latest/boards/adi/max32655evkit/doc/ |
| D | index.rst | 171 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/cmake/linker/armlink/ |
| D | scatter_script.cmake | 255 # Currently we simply uses offset +0, but we must support offset defined
261 # Currently we simply uses offset +0, but we must support offset defined
|
| /Zephyr-latest/boards/96boards/nitrogen/doc/ |
| D | index.rst | 254 To fix the permission issue, simply add the following udev rule for the
|
| /Zephyr-latest/boards/adi/max32662evkit/doc/ |
| D | index.rst | 214 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/boards/adi/max32672fthr/doc/ |
| D | index.rst | 206 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/boards/adi/max32655fthr/doc/ |
| D | index.rst | 193 Once the USB cable is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.pthread | 139 hardware) but for now it simply increases the size of thread stacks.
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 137 Otherwise, it is sufficient to simply declare the context pointer type immediately before the call …
151 If your connectivity implementation does not need a context pointer, simply declare the type as voi…
374 …Therefore, it is recommended to simply always lock the binding, whether or not the resource being …
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | coap_server.rst | 235 following example simply prints when an event occurs.
|
| /Zephyr-latest/boards/mediatek/ |
| D | index.rst | 97 the ``mt8195//adsp`` board should work out of the box simply following
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 60 simply expands to 'static inline'. However to the post-build
259 implementation is simply called and there is no software trap.
563 simply invoke :c:macro:`K_OOPS()` which kills the calling thread. The current
596 be registered from user mode. APIs which simply install callbacks shall not
|
| /Zephyr-latest/boards/adi/max32666fthr/doc/ |
| D | index.rst | 220 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/boards/adi/apard32690/doc/ |
| D | index.rst | 192 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/boards/adi/max78000evkit/doc/ |
| D | index.rst | 285 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/boards/adi/max78000fthr/doc/ |
| D | index.rst | 187 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | virtual_memory.rst | 109 * ``K_MEM_VIRT_RAM_END`` is simply (``K_MEM_VIRT_RAM_START`` + ``K_MEM_VIRT_RAM_SIZE``).
|
| /Zephyr-latest/doc/develop/test/ |
| D | coverage.rst | 110 To build your application with ``gcc``'s `gcov`_, simply set
|
| /Zephyr-latest/boards/adi/max32690evkit/doc/ |
| D | index.rst | 286 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | zephyr_sdk.rst | 81 .. note:: If you want to uninstall the SDK, you may simply remove the directory
|
| /Zephyr-latest/boards/adi/max32666evkit/doc/ |
| D | index.rst | 298 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | rbtree.rst | 96 Typical implementations effect this by simply swapping the nodes
|
| /Zephyr-latest/boards/snps/nsim/arc_classic/doc/ |
| D | index.rst | 231 can simply :ref:`debug with MDB debugger <board_arc_nsim_debugging_mwdt>`.
243 avoid intermixing their output. For the MDB debugger simply use GUI mode.
|
| /Zephyr-latest/boards/adi/max32680evkit/doc/ |
| D | index.rst | 329 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 287 of course, but as it is (and has always been) simply a numerical zero,
299 :c:macro:`K_FOREVER` can simply use the :c:macro:`K_TIMEOUT_EQ()`
|
123456
