ESP32 Forum

Hello everyone,
I recently setup a new development machine for ESP32 devices (Linux, ESP-IDF v4.3). Everything goes smoothly as expected and I'm able to compile and flash my firmware. However there is one additional warning that I had never seen before and doesn't come up in my usual setup (same ESP-IDF version): when interacting with the device through the serial port there is always a step where the chip type is not detected:
After this there is a new attempt and the chip is recognized as an ESP32. It is part of esptool.py (https://github.com/espressif/esptool/bl ... ol.py#L384). What could be the cause? Should I be concerned or can I safely ignore it?

This behavior is explained few lines sooner in this comment. First, ESP32-C3 and newer is tried to be detected; if that fails, detection falls down to the "legacy" way for older chip models.

So, this message is what you'd expect to get printed for ESP32 (or to be precise, any chip older than ESP32-C3).

Just add the chip option then you won't get the warning message
e.g. esptool.py --chip esp32 --port COM4 --baud 115200 flash_id
or esptool.exe --chip esp32 --port COM4 --baud 115200 flash_id
Simples