Searched refs:what (Results 76 – 100 of 252) sorted by relevance
1234567891011
| /Zephyr-latest/boards/sparkfun/pro_micro_rp2040/ |
| D | board.cmake | 3 # This configuration allows selecting what debug adapter debugging to use
|
| /Zephyr-latest/boards/arm/mps3/ |
| D | mps3_corstone300_an547_ns.dts | 78 /* The memory regions defined below must match what the TF-M
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | l2cap.rst | 29 the :c:struct:`bt_l2cap_server` struct which informs what ``psm`` it should
|
| /Zephyr-latest/cmake/compiler/iar/ |
| D | iccarm-cpu.cmake | 5 # Determines what argument to give to --cpu= based on the
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | tcpc.rst | 20 resistors. It also provides a way to sense and report what resistors are
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 10 and what the Zephyr Project and the Zephyr Safety Working Group / Committee try to achieve.
19 In this section we give the reader an overview of what the general goal of the safety certification
20 is, what standard we aim to achieve and what quality standards and processes need to be implemented
133 pre-condition and what needs to be done to achieve an auditable code base from the safety
195 technical level what the software should do, and on the other hand, it is an important and
207 A high test coverage, in turn, is evidence of safety that the code conforms precisely to what it
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | fatal.rst | 39 The policy for what to do when encountering a failed assertion is controlled
107 The first parameter tells ``__ASSERT_EVAL()`` what to do if ``__ASSERT()`` is
108 disabled. The second parameter tells ``__ASSERT_EVAL()`` what to do if
239 The policy for what to do when encountering a fatal error is determined by the
|
| /Zephyr-latest/soc/nxp/imxrt/ |
| D | Kconfig.defconfig | 83 # what the ztest_thread_stack defaults to.
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | semihost.rst | 24 of code across datasets that are larger than what can fit into ROM of an
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 109 of what may or may not be a valid kernel object, the address can be validated
113 it is important to know what subsystem a driver belongs to so that
116 determine what subsystem the driver belongs to.
127 * A type field indicating what kind of object this is, which is some
254 what API struct they are set to.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | heartbeat.rst | 19 what features the node supports.
|
| D | health_srv.rst | 19 are close to the limits of what the node is designed to withstand, but not
|
| /Zephyr-latest/modules/thrift/src/thrift/transport/ |
| D | TSSLServerSocket.cpp | 105 GlobalOutput.printf("getaddrinfo() -> %d; %s", e.code().value(), e.what()); in listen()
|
| D | TSSLSocket.h | 369 const char *what() const noexcept override in what() function
|
| /Zephyr-latest/doc/build/dts/ |
| D | troubleshooting.rst | 134 There is currently no documentation for what device drivers exist and which
140 - Look inside that directory for relevant files until you figure out what the
190 If your driver's Kconfig is not set to ``y``, you need to figure out what you
273 You can then search for the file in the build directory to see what your
333 Some hints for what to check next if you don't see the "whoops" error message:
|
| /Zephyr-latest/arch/nios2/ |
| D | Kconfig | 60 describing what that cause code means.
|
| /Zephyr-latest/cmake/ |
| D | target_toolchain_flags.cmake | 40 # Configure the toolchain flags based on what toolchain technology is used
|
| D | gcc-m-cpu.cmake | 3 # Determines what argument to give to -mcpu= based on the
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 007_ext-source.md | 17 Brief description of what this software does
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.quectel-bg9x | 70 Do not mess with it unless you know what you are doing.
|
| /Zephyr-latest/samples/basic/blinky_pwm/ |
| D | README.rst | 19 frequency of 1 Hz. This sample calibrates itself to what the hardware supports
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | gmap.rst | 7 the remote device's GMAS to see what GMAP roles and features they support.
|
| /Zephyr-latest/samples/boards/nordic/nrfx_prs/ |
| D | README.rst | 31 for the UARTE), it can be checked that what is sent by a given peripheral
|
| /Zephyr-latest/samples/basic/blinky/ |
| D | README.rst | 89 - If you're not sure what to do, check the devicetrees for supported boards which
|
| /Zephyr-latest/doc/develop/west/ |
| D | extensions.rst | 96 'one-line help for what my-command-name does', # self.help
151 help: one-line help for what my-command-name does
185 help: one-line help for what my-command-name does
|
1234567891011
