| /hal_espressif-3.4.0/.gitlab/ci/ |
| D | build.yml | 6 variables:
17 variables:
50 variables:
71 variables:
77 variables:
83 variables:
89 variables:
109 variables:
127 variables:
135 variables:
[all …]
|
| D | host-test.yml | 5 variables:
64 variables:
89 variables:
94 variables:
100 variables:
106 variables:
177 variables:
201 variables:
220 variables:
225 variables:
[all …]
|
| D | docs.yml | 60 variables:
76 variables:
112 variables:
131 variables:
146 variables:
153 variables:
159 variables:
182 variables:
193 …# The DOCS_PROD_* variables used by this job are "Protected" so these branches must all be marked …
205 variables:
|
| D | assign-test.yml | 6 variables:
34 variables:
56 variables:
78 variables:
100 variables:
117 variables:
149 variables:
|
| D | target-test.yml | 20 variables:
43 variables:
51 variables:
207 variables:
222 variables:
308 variables:
337 variables:
377 variables:
402 variables:
466 variables:
[all …]
|
| D | pre_check.yml | 59 variables:
71 variables:
90 variables:
158 variables:
|
| /hal_espressif-3.4.0/docs/en/api-guides/ |
| D | thread-local-storage.rst | 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 by
27 :ref:`CONFIG_FREERTOS_THREAD_LOCAL_STORAGE_POINTERS` configuration value. Variables are kept in the…
30 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…
[all …]
|
| D | build-system-legacy.rst | 73 …ROJECT_NAME`` variable and (optionally) defines other project-wide make variables. It includes the…
101 Mandatory Project Variables
106 Optional Project Variables
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:
161 Preset Component Variables
[all …]
|
| D | ulp-risc-v.rst | 71 Accessing the ULP-RISC-V Program Variables
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``…
|
| D | ulp-legacy.rst | 76 Accessing the ULP Program Variables
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…
|
| D | ulp.rst | 75 Accessing the ULP Program 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…
|
| D | build-system.rst | 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…
298 Optional Project Variables
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…
[all …]
|
| D | memory-types.rst | 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 …
|
| /hal_espressif-3.4.0/components/esptool_py/esptool/ |
| D | .gitlab-ci.yml | 12 variables:
55 variables:
83 variables:
190 variables:
208 variables:
284 variables:
350 variables:
407 variables:
422 variables:
435 variables:
|
| /hal_espressif-3.4.0/docs/en/api-guides/tools/ |
| D | idf-tools.rst | 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…
|
| /hal_espressif-3.4.0/ |
| D | .gitlab-ci.yml | 20 variables:
23 variables:
27 variables:
35 …# XXX_ATTEMPTS variables (https://docs.gitlab.com/ce/ci/yaml/README.html#job-stages-attempts) are …
36 # Use values from "CI / CD Settings" - "Variables".
|
| /hal_espressif-3.4.0/examples/system/ulp_fsm/ulp/main/ |
| D | ulp_example_main.c | 55 /* Initialize some variables used by ULP program. in init_ulp_program()
57 * These variables are declared in an auto generated header file, in init_ulp_program()
59 * These variables are located in RTC_SLOW_MEM and can be accessed both by the in init_ulp_program()
62 * Note that the ULP reads only the lower 16 bits of these variables. in init_ulp_program()
|
| /hal_espressif-3.4.0/tools/cmake/ |
| D | convert_to_cmake.py | 15 def get_make_variables(path, makefile='Makefile', expected_failure=False, variables={}): argument
17 …Given the path to a Makefile of some kind, return a dictionary of all variables defined in this Ma…
23 variable_setters = [('%s=%s' % (k,v)) for (k,v) in variables.items()]
64 variables={
165 # Look up all the variables before we start writing the file, so it's not
|
| /hal_espressif-3.4.0/docs/en/contribute/ |
| D | style-guide.rst | 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 variables
359 // then private member variables
451 - For locally scoped variables, use lowercase (``with_underscores``).
452 - For globally scoped variables, use uppercase (``WITH_UNDERSCORES``).
|
| /hal_espressif-3.4.0/tools/kconfig_new/ |
| D | prepare_kconfig_files.py | 28 a file list. The inputs are the same environment variables which are used by kconfiglib:
59 # created for empty environment variables as well
82 help='Optional file to load environment variables from. Contents '
|
| /hal_espressif-3.4.0/tools/ci/ |
| D | envsubst.py | 4 # some CI related variables.
11 # Sanitize environment variables
|
| /hal_espressif-3.4.0/components/esp_common/include/ |
| D | esp_attr.h | 19 //and all variables in shared RAM. These macros can be used to redirect
20 //particular functions/variables to other memory regions.
44 // IRAM is not accessible as an 8-bit memory, put IRAM coredump variables in DRAM
146 // errors if two variables in the same source file have different linkage (maybe const & non-const)…
|
| /hal_espressif-3.4.0/components/esp_hw_support/ |
| D | Kconfig.spiram.common | 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.
|
| /hal_espressif-3.4.0/examples/bluetooth/esp_ble_mesh/ble_mesh_node/onoff_server/tutorial/ |
| D | BLE_Mesh_Node_OnOff_Server_Example_Walkthrough.md | 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…
|
| /hal_espressif-3.4.0/make/ |
| D | component_wrapper.mk | 5 # which is included as part of this process (after default variables are defined).
17 # 1) Set default variables for the component build (including configuration
80 # override variables & optionally define custom targets. Also include global
113 # 3) Set variables that depend on values that may changed by component.mk
178 # take component.mk variables COMPONENT_ADD_INCLUDEDIRS,
195 $(details) "Building component project variables list $(abspath $@)"
347 component_project_vars.mk:: # no need to add variables via component.mk
348 @echo '# COMPONENT_CONFIG_ONLY target sets no variables here' > $@
|
