Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgraded esptool.py to 4.6.2 but IDF requested 4.5.1 (IDFGH-10895) #12096

Closed
3 tasks done
eme-bennytang opened this issue Aug 18, 2023 · 9 comments
Closed
3 tasks done
Assignees
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally Type: Bug bugs in IDF

Comments

@eme-bennytang
Copy link

eme-bennytang commented Aug 18, 2023

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.

release/v5.0.2

Operating System used.

Linux

How did you build your project?

VS Code IDE

If you are using Windows, please specify command line type.

None

What is the expected behavior?

idf.py should have set-target and rebuild sdk.config for me

What is the actual behavior?

Prompt error saying the required esptool.py version should 4.5.0, but I have to upgrade it to fix a build issue with

  • ESP32S3-WROOMN16R8
  • Secure boot enabled
    So far the esptool.py upgrade did fix the problem for me, I am able to flash application now by either VS CODE IDE/esptool.py write_flash directly

But I can't use idf.py anymore

Steps to reproduce.

Upgraded esptool.py to 4.6.2 to fix this issue
#10788

Build or installation Logs.

idf.py set-target esp32s3
/home/benny/esp/esp-idf/tools/check_python_dependencies.py:12: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  import pkg_resources
The following Python requirements are not satisfied:
esptool~=4.5.0 - (esptool 4.6.2 (/home/benny/.espressif/python_env/idf5.0_py3.10_env/lib/python3.10/site-packages), Requirement.parse('esptool~=4.5.0'))
To install the missing packages, please run "install.sh"
Diagnostic information:
    IDF_PYTHON_ENV_PATH: /home/benny/.espressif/python_env/idf5.0_py3.10_env
    Python interpreter used: /home/benny/.espressif/python_env/idf5.0_py3.10_env/bin/python
Constraint file: /home/benny/.espressif/espidf.constraints.v5.0.txt
Requirement files:
 - /home/benny/esp/esp-idf/tools/requirements/requirements.core.txt
Python being checked: /home/benny/.espressif/python_env/idf5.0_py3.10_env/bin/python

ESP-IDF v5.0.2

More Information.

No response

@eme-bennytang eme-bennytang added the Type: Bug bugs in IDF label Aug 18, 2023
@espressif-bot espressif-bot added the Status: Opened Issue is new label Aug 18, 2023
@github-actions github-actions bot changed the title Upgraded esptool.py to 4.6.2 but IDF requested 4.5.1 Upgraded esptool.py to 4.6.2 but IDF requested 4.5.1 (IDFGH-10895) Aug 18, 2023
@dobairoland
Copy link
Collaborator

Hi @eme-bennytang. esptool~=4.5.0 means that the version should be at least 4.5.0 but could not be 5.0 or newer. That means 4.6.2 should be an acceptable version.

Could you please use the Doctor command to generate a status report about your environment?

@eme-bennytang
Copy link
Author

eme-bennytang commented Aug 18, 2023

Hi Roland,

Thanks for the reply, but I have upgraded my IDF version to release/v5.1 to cope with this problem.
Now I got esptool 4.7 dev version

Just for future reference, should I just execute ./install.sh to upgrade my tools (e.g. esptool.py) or should I "pip install esptool==4.6.2"? I am guessing this might be the problem

@dobairoland
Copy link
Collaborator

Just for future reference, should I just execute ./install.sh to upgrade my tools

Yes, this is the recommended way for ESP-IDF. In case this is not working with the VScode plugin then please report it in https://github.com/espressif/vscode-esp-idf-extension.

or should I "pip install esptool==4.6.2"? I am guessing this might be the problem

Yes, this can be a workaround if the above is not working.

So I guess we can close this for now.

@dobairoland
Copy link
Collaborator

Oh, correction: esptool~=4.5.0 means 4.5.0 <= x < 4.6. I reopen this issue and correct it.

Thank you @fhrbata for pointing out my mistake!

@eme-bennytang
Copy link
Author

I am a bit confused, since I saw #10788
And to fix my problem, I just "pip install esptool==4.6.2" directly

So what you mean is:

  • In Idf v5.0.2 the esptool should stay in 4.5.0 -> 4.6.0
  • If I want to use any thing newer I must use newer idf version? (as I did upgrade my IDF version to release/v5.1, so I guess its fine, just want to know if this is true)

@dobairoland
Copy link
Collaborator

No, I was confused. I thought that the newest esptool is included with ESP-IDF v5.0.x as well. I'll correct this mistake and after that I close this issue. I'm sorry for the confusion.

@eme-bennytang
Copy link
Author

so you do not expect the IDF 5.0.2 using only esptool 4.5.0 - 4.6.0 and will fix and include latest esptool version in 5.0.x, so that others can just upgrade the esptool by calling ./install.sh?

Thanks anyway, I should have no issue using IDF release/v5.1

@dobairoland
Copy link
Collaborator

so you do not expect the IDF 5.0.2 using only esptool 4.5.0 - 4.6.0 and will fix and include latest esptool version in 5.0.x, so that others can just upgrade the esptool by calling ./install.sh?

Yes, that is correct.

@dobairoland
Copy link
Collaborator

This should be fixed now. esptool>=4.5.0,<5 is set in https://dl.espressif.com/dl/esp-idf/espidf.constraints.v5.0.txt so the latest esptool should be available after re-running the install script.

@espressif-bot espressif-bot added Status: Done Issue is done internally Resolution: Done Issue is done internally and removed Status: Opened Issue is new labels Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally Type: Bug bugs in IDF
Projects
None yet
Development

No branches or pull requests

3 participants