Searched refs:some (Results 201 – 225 of 591) sorted by relevance
12345678910>>...24
| /Zephyr-latest/doc/connectivity/bluetooth/autopts/ |
| D | autopts-win10.rst | 242 …e.g. PuTTy with proper COM and baud rate. After board reset you should see some strings in console.
250 …e to Raw, IP to 127.0.0.1, port to 65123. After board reset you should see some strings in console.
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-syntax.rst | 180 Here are some more examples.
311 ``foo = "/path/to/some/node";``
576 /* ... some compatible with 'bus: spi', etc. ... */
586 /* ... some compatible with 'bus: i2c', etc. ... */
717 good idea to check if :file:`base.yaml` already defines some of the needed
746 In some cases, you may want to include some property definitions from a file,
|
| /Zephyr-latest/subsys/dfu/ |
| D | Kconfig | 76 on some hardware that has long erase times, to prevent long wait
|
| /Zephyr-latest/subsys/mgmt/osdp/ |
| D | Kconfig | 67 packet structure definition, some commercial CPs and PDs do not
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-shell.rst | 70 that is compiled in. To configure, use the :code:`log` command. Here are some examples:
|
| /Zephyr-latest/doc/_extensions/zephyr/domain/static/js/ |
| D | board-catalog.js | 186 (selectedSocs.length === 0 || selectedSocs.some((soc) => boardSocs.includes(soc)));
|
| /Zephyr-latest/samples/arch/smp/pktqueue/ |
| D | README.rst | 17 of packet headers is initialized. Each header contains some random data of size
|
| /Zephyr-latest/doc/develop/sca/ |
| D | codechecker.rst | 81 When running CodeChecker as part of ``twister`` some default options are set as following:
|
| /Zephyr-latest/samples/net/sockets/coap_download/ |
| D | README.rst | 47 echo "some test data" > file_root/test.txt
|
| /Zephyr-latest/dts/arm/nxp/ |
| D | nxp_lpc11u6x.dtsi | 47 * For some reasons, the IAP commands don't allow to
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 35 and check that it's not already in use. In some cases someone else may have
206 needs to provide some Kconfig settings before you can compile a Zephyr
227 other SoC related Kconfig settings. In some cases a SOC_PART_NUMBER.
|
| /Zephyr-latest/boards/native/native_sim/doc/ |
| D | index.rst | 50 Note that some drivers may have limitations, or may not support their whole driver API optional
98 If you want your application to gracefully finish when it reaches some point,
164 and is therefore normally best to test and debug your code, as some bugs are
182 If you select some feature which are not compatible with the host C library,
198 while being a HW agnostic test platform which in some cases utilizes the host
249 If, for some reason, native_sim runs slower than real time, all this
604 Apart from its own peripherals, the native_sim board also has some dedicated
605 backends for some of Zephyr's subsystems. These backends are designed to ease
694 Today, some native_sim peripherals and backends are, so far, only available when compiling with the
|
| /Zephyr-latest/doc/kernel/ |
| D | code-relocation.rst | 38 section will have some info regarding vector tables and other debug related
147 Take care if relocating kernel/arch files, some contain early initialization
|
| /Zephyr-latest/subsys/net/lib/http/ |
| D | Kconfig | 9 This parser requires some string-related routines commonly
16 This parser requires some string-related routines commonly
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 222 and minimal. But some notes are important to detail:
225 not illegal (though probably undesirable in some circumstances) to
249 a timeout), but may be a performance problem in some cases. The
303 timeout and loop, waiting for it to finish while doing some processing
360 But some care is still required for subsystems that use those. Note that
|
| /Zephyr-latest/doc/develop/test/ |
| D | ztest.rst | 69 the same suite will require some initial setup followed by some form of reset between each test.
155 where you might want to reset some state for every test in the binary (regardless of which suite is
183 While the Ztest framework provides a default :c:func:`test_main` function, it's possible that some
184 applications will want to provide custom behavior. This is particularly true if there's some global
379 some helpers for mocking functions, as demonstrated below.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | mpu_stack_objects.rst | 63 some added complexity when implementing stack guards.
|
| /Zephyr-latest/cmake/modules/ |
| D | west.cmake | 8 # Python interpreter as everything else, though, so we play some extra
|
| /Zephyr-latest/doc/services/storage/fcb/ |
| D | fcb.rst | 29 block of data, thereby freeing up some space, or stop writing new data
|
| /Zephyr-latest/boards/shields/x_nucleo_bnrg2a1/doc/ |
| D | index.rst | 43 Additionally, depending on your host board, some modifications of the BLE
|
| /Zephyr-latest/samples/boards/espressif/deep_sleep/ |
| D | README.rst | 23 3. ``GPIO``: Only supported by some Espressif SoCs, in the case of ESP32-C3
|
| /Zephyr-latest/soc/cdns/dc233c/include/ |
| D | xtensa-dc233c.ld | 62 * some linker issues which would balloon the size of
134 /* There is quite some space between .DoubleExceptionVector
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 66 Backporting a fix means that some or all of the fix commits, as they exist in the current version,
75 Even if some of the commits require changes, keep the commit messages of all the ported commits
|
| /Zephyr-latest/boards/st/nucleo_f767zi/doc/ |
| D | index.rst | 42 - Arm* Mbed Enabled* compliant (only for some Nucleo part numbers)
122 (*) nucleo_f767zi with soc cut-A (Device marking A) has some ethernet
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_WINDOWS.rst | 4 Zephyr plays some tricks here that require understanding the base
83 some extent enforces a fairly complicated stack layout to make that
|
12345678910>>...24
