Home
last modified time | relevance | path

Searched refs:simply (Results 76 – 100 of 127) sorted by relevance

123456

/Zephyr-latest/cmake/bintools/
Dbintools_template.cmake32 # To disable the message, simply silence the command with:
/Zephyr-latest/doc/connectivity/networking/
Doverview.rst117 support multiple network technologies at the same time simply by enabling
/Zephyr-latest/doc/services/debugging/
Dgdbstub.rst266 a breakpoint can be set for :c:func:`test`, or simply using
Dcoredump.rst397 #. Implement :c:func:`arch_coredump_tgt_code_get` simply to return
/Zephyr-latest/boards/native/nrf_bsim/doc/
Dnrf52_bsim.rst179 The UART console is disabled by default for BabbleSim boards, to enable it simply add the snippet :…
/Zephyr-latest/doc/develop/flash_debug/
Dnordic_segger.rst138 To avoid this, you can simply disable the Mass Storage Device by opening:
/Zephyr-latest/boards/ti/cc3220sf_launchxl/doc/
Dindex.rst123 If you had previously installed TI OpenOCD, you can simply switch to use
/Zephyr-latest/boards/adi/max32672evkit/doc/
Dindex.rst329 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/doc/kernel/services/other/
Dfatal.rst196 as the thread will simply not have permission to write to adjacent memory
/Zephyr-latest/boards/ti/cc3235sf_launchxl/doc/
Dindex.rst126 If you had previously installed TI OpenOCD, you can simply switch to use
/Zephyr-latest/doc/develop/test/
Dbsim.rst146 The build scripts ``compile.sh`` simply build all the required test and sample applications
/Zephyr-latest/boards/native/doc/
Darch_soc.rst250 addresses your binary will simply segfault.
271 QEMU cannot provide any emulation of execution speed. It simply
/Zephyr-latest/arch/arm/core/
DKconfig163 The kernel provides a simple NMI handler that simply hangs in a tight
/Zephyr-latest/doc/services/rtio/
Dindex.rst161 When a read is needed, the caller simply needs to replace the call
/Zephyr-latest/doc/kernel/
Dtimeutil.rst53 Keep in mind that these are simply time representations that must be
/Zephyr-latest/boards/adi/max32675evkit/doc/
Dindex.rst381 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/doc/kernel/memory_management/
Dheap.rst115 applications that want to destroy a multi heap should simply ensure
/Zephyr-latest/boards/toradex/verdin_imx8mp/doc/
Dindex.rst242 X56 debug connector and to the PC, or simply connecting a USB-C to X66 on the Verdin Development
/Zephyr-latest/doc/kernel/services/threads/
Dindex.rst191 Because of this, portable code can't simply pass an arbitrary character buffer
303 used only with great care from application code. These are not simply
/Zephyr-latest/doc/connectivity/usb/device/
Dusb_device.rst220 HID support abuses :ref:`device_model_api` simply to allow applications to use
361 The ``disk-property`` "NAND" may be confusing, but it is simply how some file
/Zephyr-latest/boards/adi/max78002evkit/doc/
Dindex.rst452 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/boards/acrn/acrn/doc/
Dindex.rst181 assignments with other guests. But for testing Zephyr simply using
/Zephyr-latest/doc/contribute/
Dexternal.rst80 The first way to integrate external source code into the project is to simply
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-le-host.rst86 simply utilize the advertising data of found devices, combining it
/Zephyr-latest/doc/develop/west/
Dbuilt-in.rst164 because it does not try to hold on to your commits and simply

123456