why is not the esp32-p4 silicon version 3.2 problem released to stable ASAP ? (ESPTOOL-1329)

[savenlid]

Operating System

windows

Esptool Version

5.2

Python Version

unclear

Chip Description

esp32-p4 silicion revision 3.2

Device Description

custom

Hardware Configuration

just flashing, via txd0, rxd0 using a standard usb dongle to serial with 2 pins doing reset etc.

olimox espprog C

How is Esptool Run

windows poershell

Full Esptool Command Line that Was Run

No response

Esptool Output

More Information

i cannot understand why this is not released and we need to get fetch on a special commit.

created problem in production instantly.

Other Steps to Reproduce

No response

I Have Read the Troubleshooting Guide

• I confirm I have read the troubleshooting guide.

[github-actions]

Hi @savenlid! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.

---

ESP32-P4 v3.2 Support in esptool

The fix for ESP32-P4 chip revision v3.2 flashing support has been released in stable versions of esptool. Here's the current status:

What versions include the fix?

• esptool v5.3.dev3 (for use with ESP-IDF v6.0+)
• esptool v4.12.dev2 (for use with ESP-IDF v5.5.3+)

The fix for the flash power-on sequence with the stub flasher on ESP32-P4 v3.2 (ECO6) was included in esptool v5.2.0, which added ECO6 stub flasher support and the ability to power on the SPI flash chip during the connection process on ECO6. [esptool v5.2.0]

Why you may still be seeing issues with v5.2

The error you're encountering is a known issue specifically when using ESP-IDF v5.5.3 or v5.5.4 with the ESP32-P4X board (v3.2 chip). Even though esptool v5.2 includes some fixes, the required minimum version for full v3.2 support is v5.3.dev3 (or v4.12.dev2 for the v5.5.x branch). [Firmware flashing FAQ]

How to fix it now

Install the required esptool version directly via pip:

pip install esptool==5.3.dev3

or for the v4.x line:

pip install esptool==4.12.dev2

If you're using idf.py flash and get a version constraint error after upgrading, you'll need to update the constraint file:

• Windows: %USER_PROFILE%\.espressif\espidf.constraints.v5.5.txt

Open the file, find the line with the esptool constraint (e.g., esptool==5.2.dev1), and update it to esptool~=5.3.dev3 or esptool~=4.12.dev2. [Firmware flashing FAQ]

Alternatively, if you re-run the ESP-IDF install script after updating to a supported ESP-IDF version (v5.5.3+ or v6.0+), esptool will be upgraded automatically. [Compatibility Advisory]

[savenlid]

I don't have the problem on my laptop during development.
I run 6.0.1 personally.

This relates to production environment where nothing else but esp tool in installed with the sole purpose of flashing firmware.

[dobairoland]

The suggestion contains also how to use the right version in a standalone esptool installation.

Either

pip install esptool==5.3.dev3

or

pip install --upgrade --pre esptool

installs it. Of course, other installation methods beside pip work as well.

But you are right that 27463b2 and 3f6cb59 are available only in DEV release and not in a final release. The reason is that we were testing it in our production environment before final release.

The final release will come in the following days. The final release will be functionally the same as the published DEV release in regard of ESP32-P4 rev 3.2, so you can use it even right now.