Auto Detect of COM Port with ESP32-S3 not working

i often use board configs for other self developed boards.
Does the WHID come from the Wroom/Wrover part or from the UART to USB chip used on almost all ESP board?
What happens if i want to upload using a FTDI breakout board / port ?

I’m not currently sure what happens when you use an official board that has HWIDs registered but want to upload to it using a different serial adapter or port… Probably won’t work.

wouldn’t it then be the best solution to add an option like board_upload.hwid with a possible value “ignore” or something like that ?

or just make the HWID check disable-able. I have a feeling this check might cause more problems at it solves

i just ran into the described problem

i’m tyring to flash a LILYGO® TTGO T-SIM7000G (link to official store) Board using the Wrover Kit board config and I’m getting


Looking for upload port...
TimeoutError: Could not automatically find serial port for the `Espressif ESP-WROVER-KIT` board based on the declared HWIDs=[['0x0403', '0x6010']]
Error: Please specify `upload_port` for environment or use global `--upload-port` option.
For some development platforms it can be a USB flash drive (i.e. /media/<user>/<device name>)
*** [upload] Explicit exit, status 1

What should i do? as far as i know there is no specific board config for this board

also some board do not get the same com port number after re-plug. that also kind of breaks the upload_port = COMXX solution

I know, it’s bad. I can only recommend a PlatformIO core downgrade now so that you can continue working like you did before. Can you try that through TimeoutError: Could not automatically find serial port - #20 by maxgerhardt?

Could you provide an output of pio device list?

ESP32-S3 Dev Kit

Hardware ID: USB VID:PID=10C4:EA60 SER=CA5626245619EC11B5F73ABFF95A09B1 LOCATION=1-1.1.3
Description: Silicon Labs CP210x USB to UART Bridge (COM28)

ESP32 TTGO SIM7000G:

Hardware ID: USB VID:PID=1A86:55D4 SER=533D003390 LOCATION=1-1.1.2
Description: USB-Enhanced-SERIAL CH9102 (COM20)

ESP32-C3 NodeMCU

Hardware ID: USB VID:PID=1A86:7523 SER= LOCATION=1-1.1.3
Description: USB-SERIAL CH340 (COM7)

ESP32-C3 auto detection works but upload still failes with


Auto-detected: COM7
Uploading .pio\build\BOARDS_ESP32_C3\firmware.bin
esptool.py v3.3
Serial port COM7
Connecting....
Chip is ESP32-C3 (revision 3)
Traceback (most recent call last):
Features: Wi-Fi
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 5387, in <module>
Crystal is 40MHz
MAC: 84:f7:03:39:d2:98
    _main()
Uploading stub...
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 5380, in _main
Running stub...
Stub running...
    main()
Changing baud rate to 921000
Changed.
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 4802, in main
Configuring flash size...
    esp.flash_set_parameters(flash_size_bytes(args.flash_size))
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 1056, in flash_set_parameters
    self.check_command("set SPI params", ESP32ROM.ESP_SPI_SET_PARAMS,
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 495, in check_command
    val, data = self.command(op, data, chk, timeout=timeout)
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 468, in command
    p = self.read()
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 413, in read
    return next(self._slip_reader)
StopIteration

Never had upload problems with the C3 before

It means that PlatformIO found the port. Autodetection works as expected. Could you try to erase flash and upload again?

what is the command to erase the flash ?

Okay i found the Erase Flash button but didn’t help. still getting error while upload


Looking for upload port...
Auto-detected: COM7
Uploading .pio\build\BOARDS_ESP32_C3\firmware.bin
esptool.py v3.3
Serial port COM7
Connecting....
Chip is ESP32-C3 (revision 3)
Traceback (most recent call last):
Features: Wi-Fi
Crystal is 40MHz
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 5387, in <module>
MAC: 84:f7:03:39:d2:98
Uploading stub...
    _main()
Running stub...
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 5380, in _main
Stub running...
    main()
Changing baud rate to 921000
Changed.
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 4802, in main
Configuring flash size...
    esp.flash_set_parameters(flash_size_bytes(args.flash_size))
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 1056, in flash_set_parameters
    self.check_command("set SPI params", ESP32ROM.ESP_SPI_SET_PARAMS,
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 495, in check_command
    val, data = self.command(op, data, chk, timeout=timeout)
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 468, in command
    p = self.read()
  File "C:\Users\Save_\.platformio\packages\tool-esptoolpy\esptool.py", line 413, in read
    return next(self._slip_reader)
StopIteration
*** [upload] Error 1
======================================================================= [FAILED] Took 283.33 seconds =======================================================================

thx for the link. i’ll revert back to the previous PIO Version tomorrow. there is too much broken for me at the moment

You don’t need to downgrade PlatfomIO Core. There is no problem with it. The esptool.py fails. Please read the log above carefully.

P.S: @valeros, do you have any ideas?

Hi @savejeff ! The topic title says you are using an ESP32-S3 and I see Chip is ESP32-C3 (revision 3) in the logs. What’s the correct board in your case? Could please disconnect unused boards, for the sake of debugging the issue? Also, have you tried lower upload baud rates? Any chance you could upload a minimal sketch using the Arduino IDE?

Sorry what this got a little bit confusing.
At first i just posted this because of upload problems with the ESP32-S3.
I then got the same error with com port detection using an ESP32 (No S3/C3)
i then also tested this with ESP32-C3 and got correct COM port detection but a new error i to this point had not encountered.

The C3 upload problem is thus off-topic but might have started with the same update that has the new HWID check.

on every test i had only the board under test connected with no addition board.

About the C3 issue. to this point every upload worked without a single error. i have not changed settings like baud rate or flash memory size. I can test further tomorrow

I tested it with the ESP32 S3 Dev Kit again and now I’m getting this


CURRENT: upload_protocol = esptool
Looking for upload port...
Error: Please specify `upload_port` for environment or use global `--upload-port` option.
For some development platforms it can be a USB flash drive (i.e. /media/<user>/<device name>)
*** [upload] Explicit exit, status 1

i did the pio upgrade --dev like described here TimeoutError: Could not automatically find serial port - #32 by ivankravets

But there is an actual COM port present that PIO also sees. this shows on the serial monitor

upload using upload_port = COM27 works fine

@maxgerhardt Would it be possible to add a Dialog like in the serial monitor to select a port manually if auto detect failed? the upload command takes quite long with the whole dependency graph and other stuff

Just tested: ESP32-C3 uploads fine on Arduino IDE


esptool.py v3.3
Serial port COM24
Connecting....
Chip is ESP32-C3 (revision 3)
Features: Wi-Fi
Crystal is 40MHz
MAC: 84:f7:03:39:d2:98
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00003fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x00040fff...
Flash params set to 0x022f
Compressed 12528 bytes to 9002...
Writing at 0x00000000... (100 %)
Wrote 12528 bytes (9002 compressed) at 0x00000000 in 0.3 seconds (effective 295.2 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 128...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (128 compressed) at 0x00008000 in 0.1 seconds (effective 403.9 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 591.9 kbit/s)...
Hash of data verified.
Compressed 200128 bytes to 112443...
Writing at 0x00010000... (14 %)
Writing at 0x0001a8f3... (28 %)
Writing at 0x0002090b... (42 %)
Writing at 0x00026b94... (57 %)
Writing at 0x0002cd6e... (71 %)
Writing at 0x000330f8... (85 %)
Writing at 0x0003b92f... (100 %)
Wrote 200128 bytes (112443 compressed) at 0x00010000 in 3.2 seconds (effective 506.1 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Please try the following:

  1. Disconnect all boards
  2. Connect the board you want to test
  3. Run pio device list. Do you see this board on the list?
  4. Run pio run -t upload. Does it still ask you to specify the upload port?

nope. it does not upload

here the console output when i try to upload to a ESP32 Wrover Module. Same thing happens when i try to upload to an ESP32-S3 (with the correct board config ofcourse)


PS C:\XXX> pio run --target upload --environment RELEASE_TTGO_SIM7000G_CELL
Processing RELEASE_TTGO_SIM7000G_CELL (board: esp-wrover-kit; framework: arduino; platform: espressif32@4.3.0)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp-wrover-kit.html
PLATFORM: Espressif 32 (4.3.0) > Espressif ESP-WROVER-KIT
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (ftdi) On-board (ftdi) External (cmsis-dap, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
 - framework-arduinoespressif32 @ 3.20003.0 (2.0.3)
 - tool-esptoolpy @ 1.30300.0 (3.3.0)
 - tool-mkfatfs @ 2.0.1
 - tool-mklittlefs @ 1.203.210628 (2.3)
 - tool-mkspiffs @ 2.230.0 (2.30)
 - toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch3
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 61 compatible libraries
Scanning dependencies...
Dependency Graph
|-- ArduinoJson @ 6.19.4
|-- jCAN @ 1.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|   |-- Wire @ 2.0.0
|-- jNetwork
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- WebSockets @ 2.3.1
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |-- TinyGSM @ 0.11.4
|   |   |   |-- jDisplay @ 1.0
|   |   |   |   |-- jOS @ 0.1
|   |   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |   |-- Wire @ 2.0.0
|   |   |   |-- jOS @ 0.1
|   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |-- Wire @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |   |-- SPI @ 2.0.0
|   |   |-- WiFi @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |   |-- SPI @ 2.0.0
|   |   |-- jDisplay @ 1.0
|   |   |   |-- jOS @ 0.1
|   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |-- Wire @ 2.0.0
|   |   |-- Ethernet @ 2.0.0
|   |   |   |-- WiFi @ 2.0.0
|   |   |-- WiFiClientSecure @ 2.0.0
|   |   |   |-- WiFi @ 2.0.0
|   |-- WiFi @ 2.0.0
|-- jOS @ 0.1
|   |-- SPI @ 2.0.0
|   |-- Wire @ 2.0.0
|-- ICM20948_WE @ 1.0.2
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|-- jMPU6050 @ 1.0.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|-- MPU9250_WE @ 1.1.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|-- WebSockets @ 2.3.1
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- TinyGSM @ 0.11.4
|   |   |-- jDisplay @ 1.0
|   |   |   |-- jOS @ 0.1
|   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |-- Wire @ 2.0.0
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |   |-- SPI @ 2.0.0
|   |-- WiFi @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|   |-- jDisplay @ 1.0
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |-- Ethernet @ 2.0.0
|   |   |-- WiFi @ 2.0.0
|   |-- WiFiClientSecure @ 2.0.0
|   |   |-- WiFi @ 2.0.0
|-- WiFi @ 2.0.0
|-- Wire @ 2.0.0
|-- SPI @ 2.0.0
|-- ESP32 BLE Arduino @ 2.0.0
|-- jDisplay @ 1.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|-- StreamDebugger @ 1.0.1
|-- TinyGSM @ 0.11.4
|   |-- jDisplay @ 1.0
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|-- jFS @ 0.1
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- FS @ 2.0.0
|   |-- SdFat @ 2.1.0
|   |   |-- SPI @ 2.0.0
|   |-- SD @ 2.0.0
|   |   |-- FS @ 2.0.0
|   |   |-- SPI @ 2.0.0
|   |-- SPI @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SD_MMC @ 2.0.0
|   |   |-- FS @ 2.0.0
|   |-- SPIFFS @ 2.0.0
|   |   |-- FS @ 2.0.0
|-- jDisplay @ 1.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- ssd1306 @ 1.8.2
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |   |-- SPI @ 2.0.0
|   |-- SPI @ 2.0.0
|-- LoRa @ 0.8.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|-- jMemory @ 1.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|   |-- EEPROM @ 2.0.0
|   |-- jFS @ 0.1
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |-- FS @ 2.0.0
|   |   |-- SdFat @ 2.1.0
|   |   |   |-- SPI @ 2.0.0
|   |   |-- SD @ 2.0.0
|   |   |   |-- FS @ 2.0.0
|   |   |   |-- SPI @ 2.0.0
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |   |-- SD_MMC @ 2.0.0
|   |   |   |-- FS @ 2.0.0
|   |   |-- SPIFFS @ 2.0.0
|   |   |   |-- FS @ 2.0.0
|-- Update @ 2.0.0
|-- FS @ 2.0.0
|-- SdFat @ 2.1.0
|   |-- SPI @ 2.0.0
|-- SD @ 2.0.0
|   |-- FS @ 2.0.0
|   |-- SPI @ 2.0.0
|-- Adafruit_VL53L0X @ 1.1.1
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|   |-- Wire @ 2.0.0
|-- VL53L1X @ 1.3.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|-- SparkFun LSM9DS1 IMU @ 1.2.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|-- DHT_sensor_library @ 1.4.3
|   |-- Adafruit Unified Sensor @ 1.1.4
|-- Adafruit Unified Sensor @ 1.1.4
|-- DS3231 @ 1.0.2
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
|-- jFAT16 @ 0.1.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- jFS @ 0.1
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |-- FS @ 2.0.0
|   |   |-- SdFat @ 2.1.0
|   |   |   |-- SPI @ 2.0.0
|   |   |-- SD @ 2.0.0
|   |   |   |-- FS @ 2.0.0
|   |   |   |-- SPI @ 2.0.0
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |   |-- SD_MMC @ 2.0.0
|   |   |   |-- FS @ 2.0.0
|   |   |-- SPIFFS @ 2.0.0
|   |   |   |-- FS @ 2.0.0
|-- ESPmDNS @ 2.0.0
|   |-- WiFi @ 2.0.0
|-- Ethernet @ 2.0.0
|   |-- WiFi @ 2.0.0
|-- WiFiClientSecure @ 2.0.0
|   |-- WiFi @ 2.0.0
|-- ESP32WebServer @ 1.0
|   |-- WebSockets @ 2.3.1
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |-- TinyGSM @ 0.11.4
|   |   |   |-- jDisplay @ 1.0
|   |   |   |   |-- jOS @ 0.1
|   |   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |   |-- Wire @ 2.0.0
|   |   |   |-- jOS @ 0.1
|   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |-- Wire @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |   |-- SPI @ 2.0.0
|   |   |-- WiFi @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |   |-- SPI @ 2.0.0
|   |   |-- jDisplay @ 1.0
|   |   |   |-- jOS @ 0.1
|   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |-- Wire @ 2.0.0
|   |   |-- Ethernet @ 2.0.0
|   |   |   |-- WiFi @ 2.0.0
|   |   |-- WiFiClientSecure @ 2.0.0
|   |   |   |-- WiFi @ 2.0.0
|   |-- jOS @ 0.1
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |-- WiFi @ 2.0.0
|   |-- jFS @ 0.1
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |-- FS @ 2.0.0
|   |   |-- SdFat @ 2.1.0
|   |   |   |-- SPI @ 2.0.0
|   |   |-- SD @ 2.0.0
|   |   |   |-- FS @ 2.0.0
|   |   |   |-- SPI @ 2.0.0
|   |   |-- SPI @ 2.0.0
|   |   |-- Wire @ 2.0.0
|   |   |-- SD_MMC @ 2.0.0
|   |   |   |-- FS @ 2.0.0
|   |   |-- SPIFFS @ 2.0.0
|   |   |   |-- FS @ 2.0.0
|   |-- jNetwork
|   |   |-- jOS @ 0.1
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |-- WebSockets @ 2.3.1
|   |   |   |-- jOS @ 0.1
|   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |-- Wire @ 2.0.0
|   |   |   |-- TinyGSM @ 0.11.4
|   |   |   |   |-- jDisplay @ 1.0
|   |   |   |   |   |-- jOS @ 0.1
|   |   |   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |   |   |-- Wire @ 2.0.0
|   |   |   |   |-- jOS @ 0.1
|   |   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |   |-- Wire @ 2.0.0
|   |   |   |   |-- Wire @ 2.0.0
|   |   |   |   |-- SPI @ 2.0.0
|   |   |   |-- WiFi @ 2.0.0
|   |   |   |-- Wire @ 2.0.0
|   |   |   |-- SPI @ 2.0.0
|   |   |   |-- jDisplay @ 1.0
|   |   |   |   |-- jOS @ 0.1
|   |   |   |   |   |-- SPI @ 2.0.0
|   |   |   |   |   |-- Wire @ 2.0.0
|   |   |   |-- Ethernet @ 2.0.0
|   |   |   |   |-- WiFi @ 2.0.0
|   |   |   |-- WiFiClientSecure @ 2.0.0
|   |   |   |   |-- WiFi @ 2.0.0
|   |   |-- WiFi @ 2.0.0
|   |-- FS @ 2.0.0
|   |-- SdFat @ 2.1.0
|   |   |-- SPI @ 2.0.0
|   |-- SD @ 2.0.0
|   |   |-- FS @ 2.0.0
|   |-- Wire @ 2.0.0
|   |-- SPI @ 2.0.0
Building in debug mode
Retrieving maximum program size .pio\build\RELEASE_TTGO_SIM7000G_CELL\firmware.elf
Checking size .pio\build\RELEASE_TTGO_SIM7000G_CELL\firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM:   [==        ]  17.2% (used 56388 bytes from 327680 bytes)
Flash: [===       ]  29.9% (used 1962677 bytes from 6553600 bytes)
Configuring upload protocol...
AVAILABLE: cmsis-dap, esp-prog, espota, esptool, ftdi, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esptool
Looking for upload port...
Error: Please specify `upload_port` for environment or use global `--upload-port` option.
For some development platforms it can be a USB flash drive (i.e. /media/<user>/<device name>)
*** [upload] Explicit exit, status 1
======================================================================================================================================================================== [FAILED] Took 56.41 seconds ======================================================================================================================================================================== 

Environment                 Status    Duration
--------------------------  --------  ------------
RELEASE_TTGO_SIM7000G_CELL  FAILED    00:00:56.409
=================================================================================================================================================================== 1 failed, 0 succeeded in 00:00:56.409 =================================================================================================================================================================== 
PS C:\XXX> pio device list
COM26
-----
Hardware ID: USB VID:PID=1A86:55D4 SER=5185013477 LOCATION=1-1.1.2
Description: USB-Enhanced-SERIAL CH9102 (COM26)


PS C:\XXX>

Could you provide a remote session to debug this issue? I don’t understand how it is possible. Please get in touch with me@ikravets.com for further details.

1 Like

thx. that would be cool.

i have send you an email

Thanks for the session! Fixed in

The PlatformIO Core 6.1.1 is coming soon.

1 Like