-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
A fatal error occurred: Invalid head of packet (0x6F) (ESPTOOL-858) #979
Comments
Hello @mbastida123,
Please let me know if any of these made a difference! |
|
You can get a |
Tested in 4.7 and it works! Thank you :) One question though: All the esp tools where downloaded and installed automatically via the vscode extension. What would then be the correct way of updating said tools? Can I just update them manually? Is there a magic button in the vscode extension that does that? |
Are you speaking about the ESP-IDF VSCode extensions? If so, it uses an installation of ESP-IDF (which comes bundled with the necessary tools - including esptool.py). So one option is to update IDF. Or if you are talking about PlatformIO extension, then you need to update the esp32 core. |
|
The tools are part of the installation. ESP-IDF v4.4.* uses esptool.py v3.* under the hood, while IDF v5.* uses esptool v4.*. Updating ESP-IDF means the necessary tools get updated as well. |
Understood, thank you! :) |
Operating System
Windows 11
Esptool Version
esptool.py v3.3.4-dev
Python Version
Python 3.11.2
Full Esptool Command Line that Was Run
esptool.py --baud 38400 read_flash 0xB90000 4194304 test.bin
Esptool Output
What is the Expected Behaviour?
Before you tell me this is an issue with the device or the connection:
I have tried on two different ESP32 boards and both of them return the error at the same progress 458752 (10 %).
Moreover, both of the boards flash just fine, the issue is with the read_flash command.
The slower baud rate was to try to discard a noise issue.
More Information
No response
Other Steps to Reproduce
No response
The text was updated successfully, but these errors were encountered: