When I try to connect the board in Arduino IDE, I get the following:
esptool.py v3.1
Serial port COM5
Connecting…………………_____
A fatal error occurred: Failed to connect to ESP32-S2: Timed out waiting for packet header
A fatal error occurred: Failed to connect to ESP32-S2: Timed out waiting for packet header
I have tried another USB cable, linux, windows, macos, changing various settings under tools in Arduino, different usb drivers, holding down the reset button during boot, making a connection between the reset pin and the gnd pin during boot, making a connection between the en pin and the gnd pin, making a connection between the en pin and the gnd pin with a 10 ɥF capacitor. This was all the options I was able to find when looking for information about similar issues, but the problem is that almost no one have had this problem with the ESP32-S2 and the ones I was able to find didn’t provide any possible solutions to my issue. This seems to me to mainly be a problem with ESP32, but it might bepossible that it isn’t known to be a problem since the ESP32-S2 is newer?
When connecting and disconnecting the board to a computer running linux, I am able to connect to the CP2102N USB to UART Bridge Controller, but I am not able to do anything else:
[77669.117410] cp210x ttyUSB0: cp210x converter now disconnected from
ttyUSB0
[77669.117806] cp210x 1-4:1.0: device disconnected
[77681.211923] usb 1-4: new full-speed USB device number 67 using xhci_hcd
[77681.362865] usb 1-4: New USB device found, idVendor=10c4,
idProduct=ea60, bcdDevice= 1.00
[77681.362871] usb 1-4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[77681.362874] usb 1-4: Product: CP2102N USB to UART Bridge Controller
[77681.362877] usb 1-4: Manufacturer: Silicon Labs
[77681.362880] usb 1-4: SerialNumber: 68f339dfebf3ea11a271b8f5d41a0277
[77681.364619] cp210x 1-4:1.0: cp210x converter detected
[77681.367392] usb 1-4: cp210x converter now attached to ttyUSB0
What can I do to solve this?
It’s strange that it’s appearing as both COM5 and ttyUSB0…you might need to alter your tty permissions in linux https://learn.sparkfun.com/tutorials/in … /all#linux has some info for doing so (making it where you can read AND write)
Oh. I forgot to mention, that ttyUSB0 is from when it was connected to a computer running Linux Mint and it was registering as COM5 when connecting to a computer running Windows 11.
I have 6 of the ESP32 Thing Plus Vroom’s and 3 of them have a similar issue where after they have been flashed a couple of times the WiFi fails to connect to my SSID.
When I encounter this I load the wifiscan sketch and verify that their radios are working and can see the SSID(s) I’m trying to connect to but when I try to run my other sketch that actually connects, they fail. Three of the original 6 can connect and 3 cannot and they all flash without issue.
I installed the esptool and reset them to “factory” (esptool.py --chip esp32 --port com3 erase_flash) but the results were the same.
So what do you suppose is going on? Fortunately I still have 3 good ones but I hate to think these beauties will end up in the scrap parts box!
Thanx
Okay, I think I will try to get a refund for my SparkFun Thing Plus ESP32-S2 Wroom then.
It is hard to say what’s going in, and since I just started on Computer Science it’s not something I have a lot of experience with, but it would seem to be a more widespread issue, if three out of your six boards are faulty. But again it’s hard to say what it is, since it could be a lot of things, and there’s also the possibility that the issue lies with the SoC’s supplied by Espressif.
Hope SparkFun will be able to figure out what the issue is.
I ended up not returning the board. Then I decided to try if it would work today, and it was suddenly working.
Before this i had tried all my usb-c cables, and none was working. The cable I used today was apparently able to make it work. So it was apparently a case of me using the wrong usb-c cables. I just find it weird since two of the cables I had tried are from an external ssd, namely a Samsung T5 256GB, and one would think they would be more than capable of transfering data, but apparently not.
The cable I got it working with was from an 8bitdo Pro 2 controller, if anyone is curious.