Searched refs:what (Results 26 – 50 of 252) sorted by relevance
1234567891011
7 # the build target, but since the OSD32MP15x SiP is what a user can actually
44 # what the ztest_thread_stack defaults to.
110 /* This code memory region must match what the TF-M123 * Its available address space must be compatible with what
111 * compatible with what TF-M has defined for a single boot image,125 * Its available address space must be compatible with what
26 you know what you are doing. Beware cc2520 requires gpio and spi to83 you know what you are doing. It should be initialized after CC2520
28 you know what you are doing. Beware rf2xx requires gpio and spi to
34 you know what you are doing. Beware DW1000 requires gpio and spi to
100 string("TServerFramework " + name + " close failed: ") + ttx.what(); in releaseOneDescriptor()180 string errStr = string("TServerTransport died: ") + ttx.what(); in serve()
7 # what we want to get to invoke ECLAIR with the compiler call which is used in the zephyr
39 see what is supported by ``net iface`` net-shell command. It will print
25 Brief description of what the blob(s) do. It is especially important to describe
8 what goes in here to Zephyr-specific features.
47 Do not touch it unless you know what you are doing.
122 printf("caught exception: %s\n", e.what()); in main()
17 The driver uses one TIMER instance and, depending on what is set in
40 /* The broadcaster_output terminal defines what we are sending over Bluetooth */
5 # Determines what argument to give to --fpu= based on the
128 printf("caught exception: %s\n", e.what()); in main()
9 * Warning: This overlay clears clocks back to a state equivalent to what could
34 # but since the nRF9161 is what a user can actually see on a board, using
25 you don't know what board name to use:
18 Do not mess with it unless you know what you are doing.
3 # Determines what argument to give to -mfpu= based on the
8 * Warning: This overlay clears clocks back to a state equivalent to what could
9 # not what we want.
