Skip to content

pkg/esptool: force installation of version 4.9.0 #21588

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 10, 2025
Merged

pkg/esptool: force installation of version 4.9.0 #21588

merged 1 commit into from
Jul 10, 2025

Conversation

gschorcht
Copy link
Contributor

@gschorcht gschorcht commented Jul 9, 2025 •
edited
Loading

Contribution description

It seems that Espressif recently released version 5.0.0 of esptool.py and uploaded the corresponding Python package. This version throws a number of depcrecation warnings when compiling applications for any ESP board:

Warning: DEPRECATED: 'esptool.py' is deprecated. Please use 'esptool' instead. The '.py' suffix will be removed in a future major release.
Warning: Deprecated: Option '--flash_mode' is deprecated. Use '--flash-mode' instead.
Warning: Deprecated: Option '--flash_size' is deprecated. Use '--flash-size' instead.
Warning: Deprecated: Option '--flash_freq' is deprecated. Use '--flash-freq' instead.

This PR pins the installation of the esptool.py Python package to version 4.9.0 so that compilation works without these deprecation warnings.

Testing procedure

Compile any application for any ESP32 board, for example:

BOARD=esp32-wroom-32 make -C tests/sys/shell

Without the PR, you should get the deprecation warnings, with the PR the compilation should work without the deprecation warnings.

Issues/PRs references

@github-actions github-actions bot added the Area: pkg Area: External package ports label Jul 9, 2025
@gschorcht gschorcht added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Platform: ESP Platform: This PR/issue effects ESP-based platforms Area: toolchain Area: toolchains; everything related to compilation, libc, linking, … labels Jul 9, 2025
@crasbe crasbe enabled auto-merge July 9, 2025 16:23
@riot-ci
Copy link

riot-ci commented Jul 9, 2025

Murdock results

✔️ PASSED

071eeee pkg/esptool: force installation of version 4.9.0

Success Failures Total Runtime
10522 0 10522 17m:12s

Artifacts

@crasbe crasbe added this pull request to the merge queue Jul 9, 2025
Merged via the queue into RIOT-OS:master with commit 2b8c1f1 Jul 10, 2025
30 checks passed
@gschorcht
Copy link
Contributor Author

@crasbe Thanks for reviewing and merging.

@gschorcht gschorcht deleted the pkg/esptool_fix_version branch July 10, 2025 14:28
@Teufelchen1 Teufelchen1 added this to the Release 2025.07 milestone Jul 14, 2025
@gschorcht gschorcht mentioned this pull request Jul 15, 2025
Merged
@benpicco
Copy link
Contributor

Why not change the arguments as suggested (--flash_mode -> --flash-mode) and go with version 5.0?

@gschorcht
Copy link
Contributor Author

Why not change the arguments as suggested (--flash_mode -> --flash-mode) and go with version 5.0?

This will be done in a follow-up PR. Independent on that we have to pin esptool.py to a certain version to avoid future problem when Espressif releases a new Python package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@crasbe crasbe crasbe approved these changes

Assignees
No one assigned
Labels
Area: pkg Area: External package ports Area: toolchain Area: toolchains; everything related to compilation, libc, linking, … CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Platform: ESP Platform: This PR/issue effects ESP-based platforms Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Milestone
Release 2025.07
Development

Successfully merging this pull request may close these issues.
5 participants
@gschorcht @riot-ci @benpicco @crasbe @Teufelchen1