| /hal_espressif-3.4.0/components/esptool_py/esptool/espefuse/ |
| D | __init__.py | 47 "esp32": DefChip("ESP32", esp32_efuse, esptool.targets.ESP32ROM),
48 "esp32c2": DefChip("ESP32-C2", esp32c2_efuse, esptool.targets.ESP32C2ROM),
49 "esp32c3": DefChip("ESP32-C3", esp32c3_efuse, esptool.targets.ESP32C3ROM),
50 "esp32c6": DefChip("ESP32-C6", esp32c6_efuse, esptool.targets.ESP32C6ROM),
51 "esp32h2": DefChip("ESP32-H2", esp32h2_efuse, esptool.targets.ESP32H2ROM),
53 "ESP32-H2(beta1)", esp32h2beta1_efuse, esptool.targets.ESP32H2BETA1ROM
55 "esp32s2": DefChip("ESP32-S2", esp32s2_efuse, esptool.targets.ESP32S2ROM),
56 "esp32s3": DefChip("ESP32-S3", esp32s3_efuse, esptool.targets.ESP32S3ROM),
58 "ESP32-S3(beta2)", esp32s3beta2_efuse, esptool.targets.ESP32S3BETA2ROM
|
| /hal_espressif-3.4.0/tools/ |
| D | idf_tools.py | 1051 def export_targets_to_idf_env_json(targets): # type: (list[str]) -> None argument
1053 targets = list(set(targets + get_user_defined_targets()))
1057 idf_env_json['idfInstalled'][env]['targets'] = targets
1075 targets = targets_str.replace('-', '').split(',')
1076 if targets != ['all']:
1077 invalid_targets = [t for t in targets if t not in targets_from_tools_json]
1082 targets = list(set(targets))
1083 export_targets_to_idf_env_json(targets)
1086 return targets
1097 targets = []
[all …]
|
| /hal_espressif-3.4.0/tools/test_apps/ |
| D | README.md | 35 …st app test supports more targets than just `ESP32`, then the `app_test.py` file needs to specify …
42 If the app test supports multiple targets but you only want some of these targets to be run automat…
49 (If no ci_target list is specified, all supported targets will be tested in CI.)
|
| /hal_espressif-3.4.0/tools/kconfig/ |
| D | mconf.c | 360 struct menu **targets; member
379 data->targets[k] = pos->target; in update_text()
435 struct menu *targets[JUMP_NB]; in search_conf() local
439 .targets = targets, in search_conf()
453 conf(targets[i]->parent, targets[i]); in search_conf()
|
| D | Makefile | 84 simple-targets := oldconfig allnoconfig allyesconfig allmodconfig \
86 PHONY += $(simple-targets)
88 $(simple-targets): conf-idf
|
| /hal_espressif-3.4.0/components/hal/ |
| D | README.md | 3 The `hal` component provides hardware abstraction and implementation for targets supported by ESP-I…
7 …er level components can make use of in order to have code portable to all targets ESP-IDF supports.
14 …specific subdirectories exist for wildly different implementations among targets; while code that …
|
| /hal_espressif-3.4.0/examples/build_system/cmake/idf_as_lib/ |
| D | CMakeLists.txt | 15 # targets and file generation
34 # Attach additional targets to the executable file for flashing,
|
| /hal_espressif-3.4.0/tools/cmake/ |
| D | build.cmake | 83 # all library targets built under the ESP-IDF build system. These build specifications are added
207 # Build a list of components (in the form of component targets) to be added to the build
496 # of build component targets given the requirements set by each component.
516 # Get a list of common component requirements in component targets form (previously
531 # All targets built under this scope is with the ESP-IDF build system
536 # subdirectories, creating library targets, linking libraries, etc.)
548 # files used for linking, targets which should execute before creating the specified executable,
556 # Propagate link dependencies from component library targets to the executable
|
| D | component.cmake | 142 # On the other hand, component targets are created early in the build
146 # so later in the build, these component targets actually contain the properties meant for the
180 … # and to link IDF components to external targets.
311 …message(FATAL_ERROR "Component ${COMPONENT_NAME} only supports targets: ${__REQUIRED_IDF_TARGETS}")
399 # @brief Register a component to the build, creating component library targets etc.
412 # @param[in, optional] REQUIRED_IDF_TARGETS (multivalue) the list of IDF build targets that the com…
484 # Alias the static/interface library created for linking to external targets.
606 # Compatibility function for requiring IDF build targets for 3.xx style components.
|
| /hal_espressif-3.4.0/tools/unit-test-app/configs/ |
| D | spi_flash_legacy | 1 # This config is for all targets
|
| D | aes_no_hw | 1 # This config is for all targets
|
| D | test_utils | 1 # This config is for all targets
|
| D | default_s2_2 | 1 # This config is split between targets since different component needs to be included (esp32, esp32…
|
| D | default_s2_1 | 1 # This config is split between targets since different component needs to be included (esp32, esp32…
|
| D | freertos_compliance | 1 # This config is split between targets since different component needs to be included (esp32, esp32…
|
| D | freertos_compliance_c3 | 1 # This config is split between targets since different component needs to be included (esp32, esp32…
|
| D | freertos_compliance_s2 | 1 # This config is split between targets since different component needs to be included (esp32, esp32…
|
| D | default_c3 | 1 # This config is split between targets since different component needs to be included
|
| D | default_s3 | 1 # This config is split between targets since different component needs to be included
|
| D | single_core_s2 | 1 # This config is split between targets since different component needs to be included (esp32, esp32…
|
| D | default | 1 # This config is split between targets since different component needs to be included (esp32, esp32…
|
| D | release_s2 | 1 # This config is split between targets since different component needs to be included (esp32, esp32…
|
| /hal_espressif-3.4.0/ |
| D | install.sh | 19 "${ESP_PYTHON}" "${IDF_PATH}/tools/idf_tools.py" install --targets=${TARGETS}
|
| D | install.fish | 16 "$ESP_PYTHON" "$IDF_PATH"/tools/idf_tools.py install --targets=$TARGETS
|
| /hal_espressif-3.4.0/examples/build_system/cmake/multi_config/ |
| D | sdkconfig.defaults | 2 # targets a hypothetical development platform.
|
