I was able to run my sketches on an ESP32S3 Dev module, but that stopped working at some point.
I suspected that I might have modified my configuration somehow by using the tools menu.
So I tried playing around with that, based on what I found googling this issue.
But I did not find a solution.
Then I suspected a hardware issue. So I downloaded the ESP-IDF CLI suite from Espressif. I managed to run their "Hello world" example with that. So the hardware seems ok.
The Arduino sketch I now use to get the ESP32S3 going again is very basic:
It uploads fine (see the information below). But it just won't run.
Sketch uses 298289 bytes (22%) of program storage space. Maximum is 1310720 bytes.
Global variables use 18496 bytes (5%) of dynamic memory, leaving 309184 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.6
Serial port /dev/cu.wchusbserial585A0804781
Connecting...
Chip is ESP32-S3 (revision v0.2)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 3c:84:27:c8:5e:84
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 0x00058fff...
Compressed 13744 bytes to 9822...
Writing at 0x00000000... (100 %)
Wrote 13744 bytes (9822 compressed) at 0x00000000 in 0.4 seconds (effective 305.1 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 146...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (146 compressed) at 0x00008000 in 0.1 seconds (effective 374.6 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 553.0 kbit/s)...
Hash of data verified.
Compressed 298656 bytes to 168540...
Writing at 0x00010000... (9 %)
Writing at 0x0001c133... (18 %)
Writing at 0x000242d9... (27 %)
Writing at 0x00029b75... (36 %)
Writing at 0x0002f25a... (45 %)
Writing at 0x000346e4... (54 %)
Writing at 0x00039fb5... (63 %)
Writing at 0x000433f5... (72 %)
Writing at 0x0004c2bb... (81 %)
Writing at 0x000519f1... (90 %)
Writing at 0x00057191... (100 %)
Wrote 298656 bytes (168540 compressed) at 0x00010000 in 2.6 seconds (effective 920.5 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin
The board I selected is "ESP32S3 Dev Module". The setting in the tools menu is
In my experience the easiest way to tidy up the code and add the code tags is as follows
Start by tidying up your code by using Tools/Auto Format in the IDE to make it easier to read. Then use Edit/Copy for Forum and paste what was copied in a new reply. Code tags will have been added to the code to make it easy to read in the forum thus making it easier to provide help.
My first "is it toast or still working" test is blink without delay. If the board doesn't have a simple LED I use a discrete LED with a resistor on whatever pin seems the "safest"
My board has indeed two USB connectors. I will try the Serial0 to see if I can get the Arduino upload working again. I will post the results. Note that the prints itself are not the goal, but only a way to check if it runs or not with Arduino.
Currently a "Hello world" example using the bare, CLI based, ESP-IDF suite will run perfectly. So the ESP32S3 Devkit-1 board itself is ok. It something in the Arduino environment causing it to malfunction. Looked into the tools menu and the setup of the board.
Thanks for your suggestion. My board has a LED on it. I have to a enable it by soldering bridge. I could enable the LED.
But I already know that the board is not toasted. I ran a bare C-program using the ESP-IDF CLI based suite of Espressif. Using the idf.py build command and the python based ESPtool to upload it. I compiled and uploaded the "Hello world" C-program. It ran perfectly. See also my reply to previous reaction of Wim43. The output is shown in there.
So it must be the setup in the Arduino IDE that is wrong somewhere. I use the ESP32 S3 Devkit board via the tools menu. Tried a lot of different setting of that board, but nothing worked. And previously it did work! So I think something in the Arduino setup has changed. But what could it be?
Is there a way to find out what the characteristics of my ESP32 S3 Devkit1 N16R8 board are? Other than just trying?
I have found a solution.
Instead of using the "ESP32S3 Dev Module" board, I now selected the ESP32-S3-USB-OTG board.
The tools menu looks like the picture below.