Searched refs:variables (Results 1 – 25 of 82) sorted by relevance
1234
7 Thread-local storage (TLS) is a mechanism by which variables are allocated such that there 9 of such variables:13 - :ref:`c11-std`: C11 standard introduces special keyword to declare variables as thread local.20 The ESP-IDF FreeRTOS provides the following API to manage thread local variables:26 In this case maximum number of variables that can be allocated is limited by30 Using that API user can allocate thread local variables of an arbitrary size and assign them to any…31 Different tasks can have different sets of TLS variables.42 … the following :doc:`pthread API </api-reference/system/pthread>` to manage thread local variables:49 This API has all benefits of the one above, but eliminates some its limits. The number of variables…58 The ESP-IDF FreeRTOS supports thread local variables according to C11 standard (ones specified with…[all …]
73 …ROJECT_NAME`` variable and (optionally) defines other project-wide make variables. It includes the…109 These variables all have default values that can be overridden for custom behaviour. Look in ``make…111 …. Defaults to the directory containing the Makefile. Many other project variables are based on thi…119 Any paths in these Makefile variables should be absolute paths. You can convert relative paths usin…121 These variables should all be set before the line ``include $(IDF_PATH)/make/project.mk`` in the Ma…137 Running the ``make list-components`` target dumps many of these variables and can help debug the di…159 .. component variables:164 The following component-specific variables are available for use inside ``component.mk``, but shoul…171 The following variables are set at the project level, but exported for use in the component build:180 …1`` and ``v4.0`` will all have the same values of ``ESP_IDF_VERSION_*`` variables, but different `…[all …]
90 The main program can access the global ULP-RISC-V program variables, the build system makes this po…98 Note that all symbols (variables, arrays, functions) are declared as ``uint32_t``. For functions an…104 …variables from the main program, the generated header file should be included using an ``include``…
152 …variables used by code which runs from RTC memory must be placed into RTC slow memory. For example…166 and word-aligned. We suggest to place DMA buffers in static variables rather than in the stack. Use…167 to declare global/local static variables like::206 …- Use macro ``WORD_ALIGNED_ATTR`` in functions before variables to place them in proper positions …
96 Note that all symbols (variables, arrays, functions) are declared as ``uint32_t``. For functions an…102 …variables from the main program, the generated header file should be included using an ``include``…113 …hich depends on the address of the store instruction, thus when reading variables written by the U…
12 …and what callstack of that task lead to the crash. It is also possible dumping variables content on17 …an examine memory, variables and tasks states manually. Note that since not all memory is saved in…121 Dumping variables on demand125 …ump supports retrieving variable data over GDB by attributing special notations declared variables.
95 Note that all symbols (variables, arrays, functions) are declared as ``uint32_t``. For functions an…101 …variables from the main program, the generated header file should be included using an ``include``…112 …hich depends on the address of the store instruction, thus when reading variables written by the U…
94 .. note:: The environment variables ``ESPPORT`` and ``ESPBAUD`` can be used to set default values f…103 …ding/removing files from the source tree, or when modifying CMake cache variables. For example, ``…174 …ORT`` and ``ESPBAUD`` environment variables to specify the serial port and baud rate. You can set …178 .. note:: Providing environment variables at the start of the command like this is Bash shell Synta…184 .. note:: Providing variables at the end of the command line is ``make`` syntax, and works for ``ma…255 … uses to learn how to build the project; and may set project-wide CMake variables. It includes the…301 These variables all have default values that can be overridden for custom behaviour. Look in :idf_f…309 Any paths in these variables can be absolute paths, or set relative to the project directory.311 To set these variables, use the `cmake set command <cmake set_>`_ ie ``set(VARIABLE "VALUE")``. The…407 .. _component variables:[all …]
15 def get_make_variables(path, makefile='Makefile', expected_failure=False, variables={}): argument23 variable_setters = [('%s=%s' % (k,v)) for (k,v) in variables.items()]64 variables={
29 …file:`tools/idf_tools.py` script when installing the tools or setting up the environment variables.68 …variables which need to be set to use the installed tools. For most of the tools, setting ``PATH``…70 …The environment variables can be listed in either of ``shell`` or ``key-value`` formats, set by ``…88 …Exporting environment variables in Powershell format is not supported at the moment. ``key-value``…90 …The output of this command may be used to update the environment variables, if the shell supports …122 … them in the command line. The following scripts modify the environment variables in the current s…
159 .. _preset-component-variables:191 .. _optional-project-wide-component-variables:248 - ``IDF_VER`` — ESP-IDF 的版本，请参阅 `预设的组件变量 <#preset-component-variables>`_。261 - 每个组件都可以设置一些 `可选的项目通用组件变量 <#optional-project-wide-component-variables>`_ ，他们会通过 ``component_proje…312 .. _warn-undefined-variables-legacy:335 …``component.mk`` 文件来自定义这些值。有关详细信息，请参阅 `可选的项目通用组件变量 <#optional-project-wide-component-variables>`_ 。
2 # ESPBAUD environment variables from within ninja or make or another25 # Main purpose of this script: we can't expand these environment variables in the main IDF CMake bu…
25 # Generate flasher_args.json for tools that need it. The variables below are used27 …# Some of the variables (flash mode, size, frequency, chip) are already set in project_include.cma…
1 # Note: we can't expand these environment variables in the main IDF CMake build,
27 * Public names (non-static variables and functions) should be namespaced with a per-component or pe…28 * Static variables should be prefixed with ``s_`` for easy identification. For example, ``static bo…326 … be written in ``CamelCase`` with a capital letter as beginning. Member variables and methods shal…336 * First put constructors/destructors, then member functions, then member variables.352 // then public member variables359 // then private member variables451 - For locally scoped variables, use lowercase (``with_underscores``).452 - For globally scoped variables, use uppercase (``WITH_UNDERSCORES``).
98 …If enabled, variables with EXT_RAM_ATTR attribute will be placed in SPIRAM instead of internal DRA…103 Note that the variables placed in SPIRAM using EXT_RAM_ATTR will be zero initialized.110 If enabled, noinit variables can be placed in PSRAM using EXT_RAM_NOINIT_ATTR.
8 variables describing the timings and other nuances when sending or receiving data.9 These variables have been finely tuned to work in absolute majority of environments.35 … Windows, the home directory can be set with the ``HOME`` or ``USERPROFILE`` environment variables.
25 * Set the environment variables SDK_PATH to the path to an ESP8266 IoT NON-OS SDK directory (last s…29 * Set any other environment variables you'd like to override in the Makefile.
1 /* ROM version variables for esp32s3
1 /* ROM version variables for esp32c3
1 /* ROM version variables for esp32b1z
5 # some variables are only used by asserts
25 This section introduces the `example_fast_prov_server_t` strut for this demo, and its variables in …67 In the struct, there are three variables that are related to roles and states, which are described …89 The variables that are related to the address management are described in the following table:129 The variables that are related to these two timers are described below:175 …on triggered when the timers timeout, and initializes the Model-related variables in the data stru…229 …on triggered when the timers timeout, and initializes the Model-related variables in the data stru…
205 The variables of the element structure are as follows:214 …if two SIG Models and one Vendor model are supported in an element, the variables would be model_c…257 …implementation of the model structure. Although this structure has many variables, only the follow…259 - `id` and `vnd`: union variables, defining the SIG Model and the Vendor Model respectively.260 - `op`: structure with a set of variables for the Model Operation, declaring the opcode that corres…264 The other structures and variables (keys, group, element) get their values through the BLE Mesh sta…323 There are three variables in the declaration of the operation structure:371 … declaration of the structure `esp_ble_mesh_prov_t` can be defined by the following four variables:378 These variables should be set to `0` for this demo, as it uses the most basic authentication featur…
38 MAKEFLAGS += --warn-undefined-variables
