Searched full:variables (Results 1 – 25 of 422) sorted by relevance
12345678910>>...17
2 :name: Environment Variables4 Manipulate environment variables from a Zephyr application.10 variables in C. Then, all environment variables are then printed.38 Setting Environment Variables55 Getting Environment Variables65 The shell command below may be used to display all environment variables and their associated75 Unsetting Environment Variables78 The shell command below may be used to unset environment variables.
176 /* Pdelay Request state machine variables. */222 * @brief Pdelay Response state machine variables.229 /* SyncReceive state machine variables. */256 /* SyncSend state machine variables. */274 /* PortSyncSyncReceive state machine variables. */298 /* PortSyncSyncSend state machine variables. */355 /* SiteSyncSync state machine variables. */371 /* ClockSlaveSync state machine variables. */386 /* ClockMasterSyncOffset state machine variables. */395 /* ClockMasterSyncSend state machine variables. */[all …]
64 - **Use Uppercase for Cache Variables or variables shared across CMake files**:65 When defining cache variables using ``option`` or ``set(... CACHE ...)``, use73 - **Use Lowercase for Local Variables**: For local variables within CMake80 - **Consistent Prefixing**: Use consistent prefixes for variables to avoid name90 - **Quote Strings and Variables**: Always quote string literals and variables112 - Use CMake variables (``CMAKE_SOURCE_DIR``, ``CMAKE_BINARY_DIR``,
17 Any number of atomic variables can be defined (limited only by available RAM).24 in an array of atomic variables.66 Manipulating an Array of Atomic Variables69 An array of 32-bit atomic variables can be defined in the conventional manner.70 However, you can also define an N-bit array of atomic variables using73 A single bit in array of atomic variables can be manipulated using77 using an array of atomic variables.108 Use multiple atomic variables to implement critical section processing112 Using atomic variables is typically far more efficient than using
6 Thread Local Storage (TLS) allows variables to be allocated on a per-thread7 basis. These variables are stored in the thread stack which means every8 thread has its own copy of these variables.29 Declaring and Using Thread Local Variables32 The macro ``Z_THREAD_LOCAL`` can be used to declare thread local variables.
13 # Required variables:16 # Optional variables:19 # Optional environment variables:
6 # The module defines the following variables:14 # We first try to find it via the environment variables BSIM_OUT_PATH and BSIM_COMPONENTS_PATH.17 # Note that what we find through the environment variables is meant to have precedence.60 #Many apps cmake files (in and out of tree) expect these environment variables. Lets provide them:68 # Do NOT use it outside of this module. It uses variables internal to it79 # Do NOT use it outside of this module. It uses variables internal to it
7 # This CMake module will set the following variables in the build system based11 # The following variables will be defined when this CMake module completes:17 # Variables set by this module and not mentioned above are considered internal
12 # The following variables will be defined when this CMake module completes:21 # Required variables:24 # Optional variables:84 # Set output variables.
16 # dedicated build variables.17 # This CMake modules loads the sysbuild cache variables as target properties on36 … set_property(TARGET sysbuild_cache APPEND PROPERTY "SYSBUILD_CACHE:VARIABLES" "${CMAKE_MATCH_1}")
8 # This CMake module will set the following variables in the build system based14 # The following variables will be defined when this CMake module completes:23 # Variables set by this module and not mentioned above are considered internal
11 # The following variables will be defined when this CMake module completes:20 # If any of the above variables are already set when this CMake module is23 # Variables set by this module and not mentioned above are considered internal30 # Merge in variables from other sources (e.g. sysbuild)
16 # The following variables will be defined when this module completes:23 # The following variables may be updated when this module completes:30 # Optional variables:43 # parent scope. We'll set our outcome variables in the parent scope of
266 * @param ... Optional message and variables to print if the assertion fails273 * @param ... Optional message and variables to print if the assertion fails280 * @param ... Optional message and variables to print if the assertion fails287 * @param ... Optional message and variables to print if the assertion fails294 * @param ... Optional message and variables to print if the assertion fails301 * @param ... Optional message and variables to print if the assertion fails308 * @param ... Optional message and variables to print if the assertion fails319 * @param ... Optional message and variables to print if the assertion fails330 * @param ... Optional message and variables to print if the assertion fails341 * @param ... Optional message and variables to print if the assertion fails[all …]
3 Environment Variables7 environment variables. This page describes how.9 Setting Variables73 environment variables. Make sure to use the "User" environment variables area165 Important Environment Variables169 is a description of some of these important environment variables. This is not200 The following additional environment variables are significant when configuring217 You might need to update some of these variables when you222 CMake or environment variables to do so. Please consult your emulator's or223 board's documentation for more information. The following environment variables
4 Place and use variables in the Core Coupled Memory (CCM).14 or __ccm_noinit_section those variables are placed in the CCM.16 The __ccm_data_section prefix should be used for variables that20 The __ccm_bss_section prefix should be used for variables that24 The __ccm_noinit_section prefix should be used for variables92 examples are shown. Note that the ``noinit`` section holds variables with93 uninitialized data. After writing to the variables, they all should hold the
2 :name: Condition Variables5 Manipulate condition variables in a multithreaded application.10 This sample demonstrates the usage of :ref:`condition variables <condvar>` in a11 multithreaded application. Condition variables are used with a mutex
22 #. :ref:`Set these environment variables <env_vars>`:28 #. To check that you have set these variables correctly in your current49 Run ``brew install gcc-arm-embedded`` and configure the variables
52 the following environment variables specific to the board in addition to the56 Cadence and set the license variables as per the instruction from Cadence.57 Next, set the following environment variables:59 The bottom three variables are specific to acp_6_0.
10 # Optional variables:28 # Merge in variables from other sources44 # Sysbuild must ensure any locally defined variables in sysbuild/CMakeLists.txt
13 * The structure below gathers variables that may be used by the simulated API calls14 * to mock behavior of a flash device; the variables may be used however it is desired,15 * because it is up to the mocked functions and checks afterwards to relate these variables
20 the following environment variables specific to the board in addition to the21 Xtensa toolchain environment variables listed in :ref:`intel_adsp_generic`.
3 Condition Variables16 Any number of condition variables can be defined (limited only by available RAM). Each119 Use condition variables with a mutex to signal changing states (conditions) from121 Condition variables are not the condition itself and they are not events.
57 /* Variables names generation. */62 /* Variables entries generation. */114 /* Variables names generation. */121 /* Variables entries generation. */
