Searched refs:succeeds (Results 1 – 15 of 15) sorted by relevance
| /Zephyr-latest/tests/ctest/base/ |
| D | CMakeLists.txt | 21 # A test that always succeeds
|
| /Zephyr-latest/soc/arm/fvp_aemv8r/ |
| D | Kconfig.soc | 25 core through pm_cpu_on(), it always succeeds because
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | main.rst | 250 If association succeeds, the connectivity implementation will mark the iface as operational-up (see…
304 The connection attempt continues indefinitely until it succeeds, unless a timeout has been specifie…
306 In that case, the connection attempt will be abandoned if the timeout elapses before it succeeds.
328 …not a specified timeout, the iface will try to connect forever until it succeeds, even if it is no…
|
| /Zephyr-latest/samples/net/telnet/ |
| D | README.rst | 108 And if the DHCPv4 client succeeds, you will soon see something like:
|
| /Zephyr-latest/samples/bluetooth/mtu_update/ |
| D | README.rst | 82 and send his MTU to the other device. If the MTU exchange succeeds, the central
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-intro.rst | 14 each node in the devicetree to a binding file. When this succeeds, the build
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-dev.rst | 167 function. The caller should ensure that function succeeds by checking
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 55 register. If this load succeeds, then the word is treated as a PTE
96 restarted, which retries the refill process, which succeeds in
|
| /Zephyr-latest/boards/ti/cc3220sf_launchxl/doc/ |
| D | index.rst | 222 Once the connection succeeds, the network co-processor keeps the AP identity in
|
| /Zephyr-latest/boards/ti/cc3235sf_launchxl/doc/ |
| D | index.rst | 225 Once the connection succeeds, the network co-processor keeps the AP identity in
|
| /Zephyr-latest/cmake/modules/ |
| D | kconfig.cmake | 370 # succeeds, to avoid marking zephyr/.config as up-to-date when it hasn't been
|
| D | extensions.cmake | 2468 # flag and only set the linker property if the check succeeds
2536 # flag and only set the compiler or compiler-cpp property if the check succeeds
|
| /Zephyr-latest/doc/develop/west/ |
| D | workspaces.rst | 52 commit. It's up to your environment to make sure the fetch succeeds.
|
| D | manifest.rst | 2215 The ``--validate`` action either succeeds if the current manifest file is valid,
|
| /Zephyr-latest/doc/develop/tools/ |
| D | coccinelle.rst | 98 - ``chain`` tries the previous modes in the order above until one succeeds.
|
