IoT Cloud insists my ESP32-S2 is an ESP32

[AdamHI1]

Hi all,
Today i went to add four Espressif ESP32-S2 DevKitM-1 boards to the IoT Cloud. When i uploaded the first Sketch (with my Network Credentials), it verified OK, but when it was uploading, I got an error I had never seen before with other ESP32's and ESP32-S3's.

esptool.py v4.5.1
Serial port COM14
Connecting....
A fatal error occurred: This chip is ESP32 not ESP32-S2. Wrong --chip argument?
Executing command: exit status 2

I went back to the regular PC based Arduino IDE (2.3.4), and uploaded the ChipID example sketch in the "Examples for ESP32S2 Dev Module" section . It seems to show that the board IS an ESP32-S2:

ESP-ROM:esp32s2-rc4-20191025
Build:Oct 25 2019
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3ffe5110,len:0x1270
load:0x4004a000,len:0x4
load:0x4004a004,len:0xa28
load:0x4004e000,len:0x3554
entry 0x4004a164
ESP32 Chip model = ESP32-S2 Rev 100
This chip has 1 cores
Chip ID: 15298846

I checked another DevKitM board, and had the same issue.

This looks like a bug in the IoT Cloud system. Any suggestions on how to proceed? I'd like to be able to have the option of using those boards.

If you need any other info, let me know.

--adam

[ahsrabrifat]

I think you can follow this thread regarding how to connect S2 to the IoT clouds. How to connect ESP32 s2 board to Arduino IoT cloud(Using API Keys and Arduino IDE)

[AdamHI1]

Thank you.

I'll have to look at that and see what's involved. It might work for me, since i really don't need OTA or web-editor, and i had some past experience with Adafruit's API (with CircuitPython however).

It surprises me that both my ESP32 DevKit and my ESP32-S3 DevKit work well, but the ESP32-S2 (in the middle age-wise) doesn't. Maybe it was the top model for only a very short time.

-=adam

[AdamHI1]

Update:
Today i booted up my PC from power-off, and the first boards i worked with on IoT Cloud were the -S2's. Everything worked just right today. Not sure if it was some kind of cache'ing issue - i had used some ESP32's yesterday before working with the -S2's, and i neglected to try powering everything down. I'm going to be ignorantly happy , and not try to reproduce the problem.