I’m a software developer and new to Platformio and the ESPEasy project. Because I wanted to build ESPEasy for ESP32 I had the same problem while uploading to the target and after short internet search I’ve found this thread here.
I have played around e.g. with the Platformio example projects and maybe have found the cause of the esptool issue while uploading the built ESPEasy image:
The platformio.ini seems to be sensitive with commented statements between not-commented. After removing the commented lines with ‘platform’ in the [core_esp32] section the upload works perfectly in my environment. So, only the active line (platform = espressif32@0.12.0) is left in this section.
BTW, the image built from the ESPEasy_mega-20180615 snapshot is showing errors on the console on my ESP32-PICO-KIT. But this is an other issue.
I have done further investigations and my first suspicion was wrong.
In my platformio.ini (which I have uploaded) I have done a second modification: I have specified a upload_port.
So here’s my current conclusion:
If I take the unmodified platform.ini from the ESPEasy_mega-20180615 source package I get the known esptool error.
If I only remove the comment line with the text " # directly from Platformio, Atom …" (below the commented upload_port line), my upload runs without problems. Maybe this line is responsible for the problem because the comment doesn’t start at the beginning of the line?
I’m glad to hear that your problem is also solved!
The problematic line is indeed #139 with the intended comment.
May I finally ask you, which source version you are using? I still have problems to boot ESPEasy_mega-20180615 on a PICO board.
If I use platform=espressif32@1.0.2 my build ends with error:
D:/ESP32dev/ESPEasy_mega/Source/src/ESPEasy.ino: In function ‘void setup()’:
D:/ESP32dev/ESPEasy_mega/Source/src/ESPEasy.ino:116:17: error: ‘WiFiEventFullCb’ was not declared in this scope