Home
last modified time | relevance | path

Searched full:files (Results 1 – 25 of 796) sorted by relevance

12345678910>>...32

/hal_espressif-3.4.0/components/esp_local_ctrl/proto/
DREADME.md1 # Protobuf files for defining ESP Local Control message structures
3files under this directory are used by esp_local_ctrl for defining protobuf messages which are sen…
5 Note : These proto files are not automatically compiled during the build process.
9 …ed. Since the generated files are to remain the same, as long as the proto files are not modified,…
25 Simply run `make` to generate the respective C and Python files. The newly created files will overw…
/hal_espressif-3.4.0/tools/ci/
Dcheck_deprecated_kconfigs.py55 parser.add_argument('files', nargs='*',
56 help='Kconfig files')
58 … help='Extra paths for recursively searching Kconfig files. (for example $IDF_PATH)',
75 files = [os.path.abspath(file_path) for file_path in args.files]
83 files.append(full_path)
87 for full_path in files:
103 print('{} files have been ignored.'.format(ignore_counter))
105 print('{} files have been successfully checked.'.format(success_counter))
107 print('{} files have errors. Please take a look at the log.'.format(failure_counter))
110 if not files:
[all …]
Dcheck_codeowners.py25 …return subprocess.check_output(['git', 'ls-files'], cwd=IDF_PATH).decode('utf-8').strip().split('\…
64 Return all files in the repository matching the given regular expresion.
71 Return all the files in the repository matching the given CODEOWNERS pattern.
90 files = files_by_pattern(all_files, path_pattern)
91 if args.path in files:
104 files = files_by_regex(get_all_files(), re.compile(re_pattern))
105 for f in files:
143 files = files_by_pattern(all_files, path_pattern)
144 if not files:
145 add_error('no files matched by pattern {}'.format(path_pattern))
[all …]
Dcheck_readme_links.py3 # Checks that all links in the readme markdown files are valid
56 files = [str(f) for f in self.file]
57 …return 'URL error, url - {} in files - {} is not accessible, request returned {}'.format(self.url,…
61 def check_url(url, files, timeout): argument
67 raise UrlLinkError(files, url, str(e))
78 …future_to_url = {executor.submit(check_url, url, files, timeout=30): (url, files) for url, files i…
159 …url', '-w', action='store_true', help='Skip checking of web URLs, only check links to local files')
Dcheck_tools_files_patterns.py16 # glob.glob will ignore all files starts with ``.``
60 …parser = argparse.ArgumentParser(description='check if all tools files are in rules patterns or ex…
74 …print('This test is used for making sure of all the tools dir files are recorded in .gitlab/ci/rul…
75 'trigger the related tests, except those files should be excluded.')
77 print('Missing Files:')
80 …print('Please add these files or glob patterns to ".gitlab/ci/rules.yml" and put related files und…
Dcheck_kconfigs.py27 # regular expression for matching Kconfig files
90 # allow to source only files which will be also checked by the script
404 'Kconfig files.'.format(os.path.abspath(__file__)))
419 parser.add_argument('files', nargs='*',
420 help='Kconfig files')
424 … help='Extra paths for recursively searching Kconfig files. (for example $IDF_PATH)',
438 files = [os.path.abspath(file_path) for file_path in args.files]
446 files.append(full_path)
448 # On Windows Kconfig files are working with different cases!
452 for full_path in files:
[all …]
/hal_espressif-3.4.0/
D.pre-commit-config.yaml53 name: Validate Kconfig files
56 files: '^Kconfig$|Kconfig.*$'
61 files: 'sdkconfig\.ci$|sdkconfig\.rename$|sdkconfig.*$'
63 name: Check CMake Files Format
68 files: 'CMakeLists.txt$|\.cmake$'
74 files: '\.gitlab/CODEOWNERS'
80 files: '\.gitlab/ci/.+\.yml|\.gitlab-ci.yml'
88 files: '\.gitlab/ci/dependencies/.+|\.gitlab/ci/rules\.yml'
93 name: Check type annotations in python files
100 - id: check-tools-files-patterns
[all …]
D.gitignore21 # MacOS directory files
24 # Components Unit Test Apps files
29 # Zephyr - Folders that contains binary files
35 # Example project files
44 # Downloaded font files
48 # Unit test app files
59 # test application build files
80 # VIM files
95 # lock files for examples and components
/hal_espressif-3.4.0/components/protocomm/proto/
DREADME.md1 # Protobuf files for implementing protocol communication packets
3 …c protocol communication. These proto files define the protocomm packet structure, separated acros…
9 Note : These proto files are not automatically compiled during the build process.
13 …ed. Since the generated files are to remain the same, as long as the proto files are not modified,…
29 Simply run `make` to generate the respective C and Python files. The newly created files will overw…
/hal_espressif-3.4.0/components/wifi_provisioning/proto/
DREADME.md1 # Protobuf files for defining Wi-Fi provisioning packet structures
3 …c protocol communication. These proto files define the protocomm packet structure, separated acros…
8 Note : These proto files are not automatically compiled during the build process.
12 …ed. Since the generated files are to remain the same, as long as the proto files are not modified,…
28 Simply run `make` to generate the respective C and Python files. The newly created files will overw…
/hal_espressif-3.4.0/docs/en/api-guides/
Dulp.rst38 … code, written in assembly, must be added to one or more files with `.S` extension. These files mu…
40files found in ``SRC_DIRS`` based on their extensions. For ``.S`` files, ``{IDF_TARGET_TOOLCHAIN_P…
53files. Finally, the third argument specifies the list of component source files which include the …
59 …tes the preprocessed assembly files (foo.ulp.S) in the component build directory. This step also g…
61 …ler.** This produces object (foo.ulp.o) and listing (foo.ulp.lst) files. Listing files are generat…
65 …4. **Link the object files into an output ELF file** (``ulp_app_name.elf``). The Map file (``ulp_a…
73 8. **Add the generated binary to the list of binary files** to be embedded into the application.
89 …}.ld`` files which define the global symbols present in the ULP program. Each global symbol define…
Dulp-legacy.rst31 … code, written in assembly, must be added to one or more files with `.S` extension. These files mu…
33files found in ``COMPONENT_SRCDIRS`` based on their extensions. For ``.S`` files, ``xtensa-esp32-e…
48 …List of assembly files to be passed to the ULP assembler. These must be absolute paths, i.e. start…
51files names within the component which include the generated header file. This list is needed to b…
54 …Includes common definitions of ULP build steps. Defines build targets for ULP object files, ELF fi…
60 … the preprocessed assembly files (``foo.ulp.pS``) in the component build directory. This step also…
62 …his produces object (``foo.ulp.o``) and listing (``foo.ulp.lst``) files. Listing files are generat…
66 …4. **Link the object files into an output ELF file** (``ulp_app_name.elf``). The Map file (``ulp_a…
74 8. **Add the generated binary to the list of binary files** to be embedded into the application.
90 …ME).ld`` files which define global symbols present in the ULP program. Each global symbol defined …
Dbuild-system-legacy.rst36 - A "project" is a directory that contains all the files and configuration to build a single "app" …
42 …ar pieces of standalone code which are compiled into static libraries (.a files) and linked into a…
81 …run, this directory will contain interim object files and libraries as well as final binary output…
85 …lso include ``Kconfig.projbuild`` and ``Makefile.projbuild`` files, which are special files for `o…
104 - ``PROJECT_NAME``: Name of the project. Binary output files will use this name - ie myProject.bin,…
151 - All source files in the same directory as the makefile (``*.c``, ``*.cpp``, ``*.cc``, ``*.S``) wi…
157 …for a component to have no `component.mk` file, if it only contains other files which influence th…
168 …h of a directory inside `$(BUILD_DIR_BASE)` where this component's source files are to be built. T…
201 …nent-relative paths to files which should trigger a re-link of the ELF file if they change. Typica…
213 …t directory, which will be added to the include search path for this component's source files only.
[all …]
Dbuild-system.rst31 - A "project" is a directory that contains all the files and configuration to build a single "app" …
37 …ar pieces of standalone code which are compiled into static libraries (.a files) and linked into a…
72 …- Run CMake_ as necessary to configure the project and generate build files for the main build too…
75 …Building is incremental so if no source files or configuration has changed since the last build, n…
77files from the build directory, forcing a "full rebuild" the next time the project is built. Clean…
78 …onfigure it from scratch. Note that this option recursively deletes *all* files in the build direc…
102 - ``idf.py size`` prints some size information about the app. ``size-components`` and ``size-files`…
103 …'t necessary during normal usage, but can be useful after adding/removing files from the source tr…
116 - ``--ccache`` flag can be used to enable CCache_ when compiling source files, if the CCache_ tool …
118 Note that some older versions of CCache may exhibit bugs on some platforms, so if files are not reb…
[all …]
Dlinker-script-generation.rst39 - three source files archived under the library, ``my_src1.c``, ``my_src2.c`` and ``my_src3.c`` whi…
76 - object file (``.obj`` or ``.o`` files)
78 - archive (``.a`` files)
80 .. _ldgen-placing-object-files :
82 Placing object files
117 …up relevant code and data into source files, and :ref:`use object-granularity placements<ldgen-pla…
155 … and ``object2.o``; and when ``CONFIG_PERFORMANCE_LEVEL == 3`` all object files under the archive …
201 …ile:`freertos/CMakeLists.txt`. ``freertos`` uses this to place its object files to the instruction…
208files into an executable. It is performed by the toolchain's linker, and accepts linker scripts wh…
214 .. _ldgen-linker-fragment-files :
[all …]
/hal_espressif-3.4.0/examples/provisioning/legacy/custom_config/components/custom_provisioning/proto/
DREADME.md1 # Protobuf files for defining custom config-data packet structures
7 Note : These proto files are not automatically compiled during the build process.
11 …ed. Since the generated files are to remain the same, as long as the proto files are not modified,…
27 Simply run `make` to generate the respective C and Python files. The newly created files will overw…
/hal_espressif-3.4.0/tools/ldgen/
DREADME.md6 ### Source Files
8 The following are the source files in the directory:
12 …ments.py` - contains classes for parsing the different types of fragments in linker fragment files.
14 - `sdkconfig.py` - used for evaluating conditionals in fragment files.
17 - `ldgen_common.py` - contains miscellaneous utilities/definitions that can be used in the files me…
34 The linker fragment files are parsed by `fragments.py`, evaluating conditional expressions
42 More details about the implementation are in the respective source files.
/hal_espressif-3.4.0/tools/test_apps/system/no_embedded_paths/
Dcheck_for_file_paths.py3 # 'check_for_file_paths.py' is a CI tool that checks all the unlinked object files
8 # Checking the unlinked object files means we don't rely on anything being actually linked into the…
57 print('Checking object files in {} for mentions of {}...'.format(build_dir, idf_path))
60 files = []
62files += [os.path.join(dirpath, filepath) for filepath in filepaths if filepath.endswith('.obj')]
64 print('Found {} object files...'.format(len(files)))
69 for obj_file in files:
73 … raise SystemExit('{} source files are embedding file paths, see list above.'.format(failures))
/hal_espressif-3.4.0/tools/
Dmkuf2.py105 for addr, f in args['files']:
151 write_parser.add_argument('files',
168 files = []
169 if args.files:
170files += [(parse_addr(addr), check_file(f_name)) for addr, f_name in zip(args.files[::2], args.fil…
197files += [(parse_addr(addr), process_json_file(f_name)) for addr, f_name in iteritems(flash_dic)]
199 files = sorted([(addr, f_name) for addr, f_name in iteritems(dict(files))],
203 'files': files,
Dmkdfu.py142Files are split up into chunks in order avoid timing-out during erasing large regions. Instead of …
210 for addr, f in args['files']:
238 help='Larger files are split-up into smaller partitions of this size')
239 write_parser.add_argument('files',
250 files = []
251 if args.files:
252files += [(int(addr, 0), check_file(f_name)) for addr, f_name in zip(args.files[::2], args.files[1…
265 files += [(int(addr, 0),
268files = sorted([(addr, f_name.decode('utf-8') if isinstance(f_name, type(b'')) else f_name) for ad…
272 'files': files,
/hal_espressif-3.4.0/tools/test_idf_size/
Dtest.sh20 …&& python -m coverage run -a $IDF_PATH/tools/idf_size.py --json --files app_$1.map | python $IDF_P…
38 && echo -e "\n***\nRunning idf_size.py --files..." &>> output \
39 && python -m coverage run -a $IDF_PATH/tools/idf_size.py --files app.map &>> output \
58 && echo -e "\n***\nRunning idf_size.py diff --files with bootloader..." &>> output \
59 …&& python -m coverage run -a $IDF_PATH/tools/idf_size.py app.map --files --diff bootloader.map &>>…
60 && echo -e "\n***\nRunning idf_size.py diff --files with itself..." &>> output \
61 …&& python -m coverage run -a $IDF_PATH/tools/idf_size.py app.map --files --diff app.map &>> output…
62 && echo -e "\n***\nRunning idf_size.py diff --files with another app..." &>> output \
63 …&& python -m coverage run -a $IDF_PATH/tools/idf_size.py app.map --files --diff app2.map &>> outpu…
64 && echo -e "\n***\nRunning idf_size.py diff --files with app in reverse order..." &>> output \
[all …]
/hal_espressif-3.4.0/docs/zh_CN/hw-reference/esp32/
Dget-started-devkitc.rst29 …- `ESP32-WROOM-32E <https://www.espressif.com/sites/default/files/documentation/esp32-wroom-32e_es…
30 …- `ESP32-WROOM-32UE <https://www.espressif.com/sites/default/files/documentation/esp32-wroom-32e_e…
31 …- `ESP32-WROOM-32D <https://www.espressif.com/sites/default/files/documentation/esp32-wroom-32d_es…
32 …- `ESP32-WROOM-32U <https://www.espressif.com/sites/default/files/documentation/esp32-wroom-32d_es…
33 …- `ESP32-SOLO-1 <https://www.espressif.com/sites/default/files/documentation/esp32-solo-1_datashee…
34 …- `ESP32-WROVER-E <https://www.espressif.com/sites/default/files/documentation/esp32-wrover-e_esp3…
35 …- `ESP32-WROVER-IE <https://www.espressif.com/sites/default/files/documentation/esp32-wrover-e_esp…
36 …- `ESP32-WROOM-DA <https://www.espressif.com/sites/default/files/documentation/esp32-wroom-da_data…
213 * `《ESP32 技术规格书》 <https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_cn.pd…
214 * `《ESP32-WROOM-32 技术规格书》 <https://espressif.com/sites/default/files/documentation/esp32-wroom-32_d…
[all …]
/hal_espressif-3.4.0/docs/en/api-reference/
Dkconfig.rst9 files specify dependencies between options, default values of the options, the way the options are …
21 … directory, and will make sdkconfig options available to the project build system and source files.
33 The following attributes of ``Kconfig`` files are standardized:
50 rules. The checker checks all ``Kconfig`` and ``Kconfig.projbuild`` files in
69 1. ``confgen.py`` is used by the tool chain to pre-process ``sdkconfig`` files before anything else…
71 2. ``confgen.py`` recursively finds all ``sdkconfig.rename`` files in ESP-IDF directory which conta…
73 3. ``confgen.py`` post-processes ``sdkconfig`` files and generates all build
85 …e list of available ESP-IDF options, automatically generated from Kconfig files. Note that dependi…
87files, option names are prefixed with ``CONFIG_``. So if an option ``ENABLE_FOO`` is defined in a …
99 When generating header files for C & C++, the behaviour is not customised - so ``#ifdef`` can be us…
/hal_espressif-3.4.0/components/efuse/
DMakefile.projbuild12 # Make common files esp_efuse_table.c and include/esp_efuse_table.h files.
22 # Make custom files project/main/esp_efuse_custom_table.c and project/main/include/esp_efuse_custom…
24 # Path to CSV file is relative to project path for custom CSV files.
46 # Generates files for unit test. This command is run manually.
/hal_espressif-3.4.0/tools/esp_prov/proto/
D__init__.py34 # protocomm component related python files generated from .proto files
40 # wifi_provisioning component related python files generated from .proto files
45 # custom_provisioning component related python files generated from .proto files

12345678910>>...32