Hm you might want to try the same command but with pio run -v --upload-port COM3 -t upload > compileLog.txt
.
Seems like maybe the Arduino IDE upload fixed the bootloader and you can upload only via PIO now?
Hm you might want to try the same command but with pio run -v --upload-port COM3 -t upload > compileLog.txt
.
Seems like maybe the Arduino IDE upload fixed the bootloader and you can upload only via PIO now?
Bei denm ciomand bekomm ich wieder den error das windows den zugriff verweigert hat
That doesnât matter because up to this point it should have already compiled and tried to upload it and itâs the commands which matter. Can you upload the log file to pastebin.org?
Where do I find it?
If I folow the path which I executed the comand for I only come to the .platformio folder and than ther does not exists a projects folder
In the same terminal where you have execute that other command, execute cd
and it will return the current directory of the terminal.
https://pastebin.com/gQiEcAm1
here is the link to pastebin
Please pio run -t clean
and then generate a new log (pio run -v --upload-port COM3 -t upload > compileLog.txt.
), this run didnât generate the compile outputs because the firmware was already compiled.
Hm I couldnât find any significant difference between our compile logs. All filesystem paths are properly escaped.
Can you check if you have a 3KB partitions.bin
inside .pioenvs\esp32doit-devkit-v1
of the project?
If you erase the flash of your ESP32 and then reflash it with PIO, does the same error still occur? And it goes away after you flash it once with the Arduino IDE?
To erase the chip in the terminal when the ESP32 is connected:
"c:\users\vs code\.platformio\penv\scripts\python.exe" "C:\Users\vs code\.platformio\packages\tool-esptoolpy\esptool.py" erase_flash
yes there is that file
The error in the terminal comes from the fast that its actually a powershell and it seems to interpret it weirdly. Use Windows+R -> cmd.exe -> copy-paste and execute command in there.
After you erase_flash
and upload on the PIO firmware, is it still the case that hterm.exe
shows the correct output but PIOs serial monitor doesnât?
yes it does still Show it corectly in hterm and nothing in platformio
Are you absolutely sure thatâs not old output? You see the correct output live on hterm
but the wrong output with PIO?
Can you do a side-by-side screenshot with hterm.exe
(connect on hterm, press reset on ESP32, wait a little, then disconnect) and with PIOs serial monitor?
Can you close all serial monitors again (Ctrl+C in the terminal), open a cmd.exe
and execute
"c:\users\vs code\.platformio\penv\scripts\python.exe" -m serial.tools.miniterm COM3 115200
is the output correct now?
You need to execute it in a cmd.exe
again