完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
起因是要测试另一个程序A,但是程序A使用的是IDF4.4.6的环境,我现在所有的程序B使用的是IDF4.4.2的环境;所以编译A的程序一直无法正常编译通过,后来只好升级环境,使用esp-idf-tools-setup-offline-4.4.6.EXE在另外一个目录下进行安装,后来安装成功后,编译A程序通过;但是编译B程序的时候出现问题,B程序无法编译,并且配置选型也无法开启;后来只好使用 esp-idf-tools-setup-offline-4.4.2.EXE对原来的4.4.2的目录做覆盖安装,但是依然无法正常编译;后来想到可能是之前使用了另一个版本的安装程序所以又在原来的4.4.2的目录下覆盖安装了esp-idf-tools-setup-espressif-ide-2.6.0-with-esp-idf-4.4.2环境; 但是依然无法执行编译; 还恳请各位大神帮忙看看如何恢复到可以编译B程序的4.4.2的环境,可以让B程序正常编译,并且可以做配置;十分感谢!
使用VScode Version Version: 1.78.1 Commit: 6a995c4f4cc2ced6e3237749973982e751cb0bf9 Date: 2023-05-04T09:48:08.683Z Electron: 22.5.1 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.22631 Sandboxed: No ESP-IDF 版本 V1.6.5 出现的问题Code: Select all -- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.35.3.windows.1") -- The C compiler identification is GNU 8.4.0-- The CXX compiler identification is GNU 8.4.0-- The ASM compiler identification is GNU-- Found assembler: D:/Espressif/tools/xtensa-esp32s3-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-gcc.exe-- Detecting C compiler ABI info-- Detecting C compiler ABI info - done-- Check for working C compiler: D:/Espressif/tools/xtensa-esp32s3-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-gcc.exe - skipped-- Detecting C compile features-- Detecting C compile features - done-- Detecting CXX compiler ABI info-- Detecting CXX compiler ABI info - done-- Check for working CXX compiler: D:/Espressif/tools/xtensa-esp32s3-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-g++.exe - skipped-- Detecting CXX compile features-- Detecting CXX compile features - done-- Project is not inside a git repository, or git repository has no commits; will not use 'git describe' to determine PROJECT_VER.-- Building ESP-IDF components for target esp32s3Solving dependencies requirementsCMake Error at D:/Espressif/frameworks/esp-idf-v4.4.2/tools/cmake/build.cmake:454 (message): Traceback (most recent call last): File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesurllib3response.py", line 443, in _error_catcher yield File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesurllib3response.py", line 566, in read data = self._fp_read(amt) if not fp_closed else b"" File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesurllib3response.py", line 532, in _fp_read return self._fp.read(amt) if amt is not None else self._fp.read() File "httpclient.py", line 458, in read File "httpclient.py", line 502, in readinto File "socket.py", line 669, in readinto File "ssl.py", line 1241, in recv_into File "ssl.py", line 1099, in read socket.timeout: The read operation timed out During handling of the above exception, another exception occurred: Traceback (most recent call last): File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesrequestsmodels.py", line 816, in generate yield from self.raw.stream(chunk_size, decode_content=True) File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesurllib3response.py", line 627, in stream data = self.read(amt=amt, decode_content=decode_content) File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesurllib3response.py", line 592, in read raise IncompleteRead(self._fp_bytes_read, self.length_remaining) File "contextlib.py", line 131, in __exit__ File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesurllib3response.py", line 448, in _error_catcher raise ReadTimeoutError(self._pool, None, "Read timed out.") urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='api.components.espressif.com', port=443): Read timed out. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_toolsapi_client.py", line 158, in _base_request response = self.session.request( File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesrequestssessions.py", line 587, in request resp = self.send(prep, **send_kwargs) File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesrequestssessions.py", line 745, in send r.content File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesrequestsmodels.py", line 899, in content self._content = b"".join(self.iter_content(CONTENT_CHUNK_SIZE)) or b"" File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesrequestsmodels.py", line 822, in generate raise ConnectionError(e) requests.exceptions.ConnectionError: HTTPSConnectionPool(host='api.components.espressif.com', port=443): Read timed out. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "runpy.py", line 194, in _run_module_as_main File "runpy.py", line 87, in _run_code File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_managerprepare_components__main__.py", line 3, in main() File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_managerprepare_componentsprepare.py", line 126, in main args.func(args) File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_managerprepare_componentsprepare.py", line 39, in prepare_dep_dirs ComponentManager(args.project_dir).prepare_dep_dirs( File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_managercore.py", line 404, in prepare_dep_dirs downloaded_component_paths = download_project_dependencies( File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_managerdependencies.py", line 99, in download_project_dependencies solution = solver.solve() File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_managerversion_solverversion_solver.py", line 29, in solve self.solve_manifest(manifest) File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_managerversion_solverversion_solver.py", line 48, in solve_manifest self.solve_component(requirement) File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_managerversion_solverversion_solver.py", line 66, in solve_component self.solve_component(dep) File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_managerversion_solverversion_solver.py", line 51, in solve_component cmp_with_versions = requirement.source.versions( File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_toolssourcesweb_service.py", line 95, in versions cmp_with_versions = self.api_client.versions(name, spec, target) File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_toolsapi_client.py", line 196, in versions body = self._base_request( File "D:Espressifpython_envidf4.4_py3.8_envlibsite-packagesidf_component_toolsapi_client.py", line 178, in _base_request raise APIClientError('HTTP request error') idf_component_tools.api_client_errors.APIClientError: HTTP request errorCall Stack (most recent call first): D:/Espressif/frameworks/esp-idf-v4.4.2/tools/cmake/project.cmake:384 (idf_build_process) CMakeLists.txt:8 (project)-- Configuring incomplete, errors occurred!See also "D:/WorkSpace/WLD/HM200-Moniter/Code/WLDmoniter/build/CMakeFiles/CMakeOutput.log". * The terminal process "C:WINDOWSSystem32WindowsPowerShellv1.0powershell.exe -Command cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -B d:WorkSpaceWLDHM200-MoniterCodeWLDmoniterbuild -S d:WorkSpaceWLDHM200-MoniterCodeWLDmoniter" terminated with exit code: 1. |
|
相关推荐
1个回答
|
|
在升级ESP-IDF版本时,可能会遇到一些兼容性问题,导致原有程序无法正常编译。以下是一些建议来解决您遇到的问题:
1. **清理旧的构建文件**: 在升级版本之前,建议您清理旧的构建文件。这可以通过删除项目目录下的`build`文件夹来实现。这有助于避免旧版本的构建文件与新版本不兼容的问题。 2. **检查依赖关系**: 确保您的项目依赖关系与新版本的ESP-IDF兼容。检查`CMakeLists.txt`文件,确保所有的依赖项都正确无误。 3. **更新组件和库**: 如果您的项目使用了ESP-IDF的组件或库,确保它们与新版本兼容。可能需要更新组件的版本或修改代码以适应新版本的API。 4. **检查环境变量**: 确保您的环境变量(如`PATH`)正确设置,指向了新版本的ESP-IDF和工具链。您可以通过在命令行中运行`echo %PATH%`(Windows)或`echo $PATH`(Linux/Mac)来检查环境变量。 5. **重新配置项目**: 使用`idf.py reconfigure`命令重新配置项目,确保所有的设置都与新版本的ESP-IDF兼容。 6. **查看错误信息**: 仔细阅读编译过程中的错误信息,它们通常会提供关于问题的具体线索。根据错误信息进行相应的代码或配置调整。 7. **查阅文档和社区**: 查看ESP-IDF的官方文档,了解新版本的特性和变更。同时,您也可以在ESP-IDF的社区论坛或GitHub上寻求帮助。 8. **逐步回退**: 如果升级到4.4.6版本后问题依然存在,您可以尝试逐步回退到之前的版本,例如先尝试4.4.4或4.4.3,看看问题是否得到解决。 9. **创建新的项目**: 如果以上方法都无法解决问题,您可以考虑创建一个新的项目,使用新版本的ESP-IDF,然后将旧项目的代码逐步迁移到新项目中。 10. **备份和版本控制**: 在进行任何升级或修改之前,确保您的代码有良好的版本控制和备份,以便在出现问题时可以快速回滚。 通过以上步骤,您应该能够解决在升级ESP-IDF版本时遇到的编译问题。如果问题依然存在,可能需要更深入地分析代码和配置文件,或者寻求社区的帮助。 |
|
|
|
只有小组成员才能发言,加入小组>>
429浏览 6评论
362浏览 5评论
有没有办法在不使用混杂模式的情况下实现Wifi驱动程序接收缓冲区访问中断呢?
343浏览 5评论
349浏览 4评论
327浏览 4评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-9-1 07:17 , Processed in 0.764523 second(s), Total 81, Slave 63 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191