Searched refs:simply (Results 26 – 50 of 127) sorted by relevance
123456
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.mode | 38 colors, or asynchronous logging, and all messages are simply
|
| /Zephyr-latest/doc/develop/sca/ |
| D | codechecker.rst | 63 - Skip parsing the analysis, useful if you simply want to store the results.
|
| /Zephyr-latest/samples/bluetooth/hci_uart_3wire/ |
| D | README.rst | 63 need to attach it to the Linux Host first. To do so simply build the sample and
96 to the Linux Host first. To do so simply build the sample and connect the
|
| /Zephyr-latest/samples/bluetooth/hci_uart/ |
| D | README.rst | 63 to attach it to the Linux Host first. To do so simply build the sample and
96 to the Linux Host first. To do so simply build the sample and connect the
|
| /Zephyr-latest/boards/seagate/legend/doc/ |
| D | index.rst | 97 computer, then you can simply run the ``west flash`` command to write a firmware
|
| /Zephyr-latest/boards/adi/max32650evkit/doc/ |
| D | index.rst | 97 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/boards/adi/max32650fthr/doc/ |
| D | index.rst | 96 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/boards/adi/max32660evsys/doc/ |
| D | index.rst | 100 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/boards/adi/ad_swiot1l_sl/doc/ |
| D | index.rst | 101 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/samples/drivers/spi_flash_at45/ |
| D | README.rst | 27 simply disabling the :kconfig:option:`CONFIG_SPI_FLASH_AT45_USE_READ_MODIFY_WRITE` option.
|
| /Zephyr-latest/boards/nxp/lpcxpresso11u68/doc/ |
| D | index.rst | 126 #. Next, simply run the ``west flash`` command
|
| /Zephyr-latest/boards/ti/msp_exp432p401r_launchxl/doc/ |
| D | index.rst | 64 If you had previously installed TI OpenOCD, you can simply switch to use
|
| /Zephyr-latest/drivers/display/ |
| D | Kconfig.mcux_elcdif | 76 production applications should simply disable the PXP.
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | timers.rst | 9 or it can simply record the expiration and wait for the application
213 If the thread had no other work to do it could simply sleep
|
| /Zephyr-latest/samples/userspace/prod_consumer/ |
| D | README.rst | 30 Application B simply processes the data. Let's pretend this data is
|
| /Zephyr-latest/doc/services/portability/posix/conformance/ |
| D | index.rst | 27 However, we may add implementations that simply fail with ENOSYS as long as the functional
|
| /Zephyr-latest/samples/net/sockets/echo_server/ |
| D | README.rst | 12 for incoming IPv4 or IPv6 packets (sent by the echo client) and simply sends
|
| /Zephyr-latest/samples/subsys/llext/edk/ |
| D | README.rst | 21 semaphores, spawning threads to listen for events or simply publishing or
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 17 When developing a Zephyr-based application, then a developer simply needs to write
301 If a Zephyr is specified in the list, but not found in the system, it is simply ignored and
306 Zephyr. When testing is done, the ``zephyr-test`` folder can simply be removed.
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 91 :c:func:`irq_lock` are not simply invoking a very short (often ~1
208 reasonable fallback when IPI is not available: we can simply spin,
298 Similarly, where on a uniprocessor system Zephyr could simply create a
302 complicated than simply testing the thread pointer for equality with a
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | ZephyrConfig.cmake | 136 # As this code is processed inside registered packages, we simply test if another package has a
|
| D | ZephyrConfigVersion.cmake | 128 # As this code is processed inside registered packages, we simply test if
|
| /Zephyr-latest/boards/adi/max32670evkit/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 | slabs.rst | 41 A thread that needs to use a memory block simply allocates it from a memory
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 83 The job of that exception handler is simply to ensure that the TLB has
89 fault, and simply indicates unmapped memory. The result is TLB miss
214 context switch time, you can simply change RADID and the page table
|
123456
