ESP32-P4 v1.0 Silicon idf.py flash issue. (IDFGH-14514)

[csalinasonline]

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.

General issue report

I am using esp-idf 5.4.

I have new ESP32-P4 v1.0 Silicon.
Before I had v0.1 Silicon. working on a prototype that mirrors most of the hardware on ESP32-P4-eval board.

But since changing to ESP32-P4 v1.0 Silicon i have issues programming this new chip.

I get this error "A fatal error occurred: bootloader/bootloader.bin requires chip revision in range [v0.1 - v0.99] (this chip is revision v1.0). Use --force to flash anyway."

Please look at my attached log file, old vs new silicon log, and sdkconfig below.

idf_py_flash_issue_012425.txt

sdkconfig.txt

[chegewara]

Hi,
you may want to switch to master branch (at least for now), there is version 1.0+ supported.

PS it is just suggestion before/if its backported to v5.4

[csalinasonline]

Thanks for update. I will try master branch and let u know status soon! I am switching from release/v5.4.

[csalinasonline]

@chegewara your recommendations have worked great to get around the boot issue with wrong chip id wrt to esp32p4 v1.0 silicon. But I still have issue after programming a 'getting_started/blink' project.

I have pulled latest https://github.com/espressif/esp-idf.git and checked out the master branch.

I set up env in root esp-idf directory.

• ./install.sh
• . ./export.sh

Then navigated and opened 'examples/get-started/blink' project and build flash and monitor.

• idf.py set-target esp32p4
• idf.py build
• -idf.py flash monitor

But now I get this issue after flashing and monitoring chip.

Please see log files here.
idf_py_flash_issue_012525.txt

Im programming via direct USB-C via these lines okay.

• GPIO_24 as USB1P1_N
• GPIO_25 as USB1P1_P

Might my bootselect pins be an issue?
I have

• GPIO_35 pulled to 3.3V High
• GPIO_36 pulled to 3.3V High

[suda-morris]

HI @csalinasonline Have you configured the console output to choose the "USB Serial JTAG"?