#ESP32-S3 Failing to Connect to CC with Latest Version of Program

199 messages · Page 1 of 1 (latest)

patent wharf
#

Went ahead and updated now that I have ZA, but I have been getting error messages after re-flashing the board. At first, it wasn't properly rewriting when programming (and gave an "incompatible protocol" error). Now, it gives this error after using the webtool to re-flash.

Unsure how relevant this is, but device manager is refreshing every 3 ish seconds.

#

upon further investigation, refreshes are absolutely causing the connection failure and it has to do with my usb cable
why? i dunno, it worked fine before updating

#

swapped cables as a last-ditch effort, and now the port is back to COM5 and the flash tools can't find the board (even tho it's there in device manager)

#

uninstalled and reinstalled drivers, same ol' perpetual connecting error

#

-# if anyone wants to jump in and help a snom out i'd really appreciate it

lucid hearth
#

do u have ur switch dock plugged in to power source?

patent wharf
#

yep

lucid hearth
#

is it sw1 or sw2?

patent wharf
#

sw1

lucid hearth
#

ok hmm

patent wharf
#

it was working just fine before updating

lucid hearth
#

weird

patent wharf
#

i had it running shard farming and decided to update for some of the newer program

lucid hearth
#

today's update?

patent wharf
#

yep

lucid hearth
#

the file to flash should say 20260104 I think then right?

patent wharf
lucid hearth
#

I just got home from work so I need to download new version too

#

looks like the Correct file

#

ur using this to flash it right?

#

same software?

patent wharf
#

yep

#

i was also sent a webtool because it wasn't correctly flashing earlier

lucid hearth
#

ok mine is working fine with new version growlithe_think

#

uhave it plugged in correctly right?

patent wharf
#

yea? i hope so

#

com cable to com port
usb cable to the other port

lucid hearth
#

like com to computer and uart to switch dock right?

patent wharf
#

yis

lucid hearth
#

could be a damaged or faulty cable growlithe_think

patent wharf
#

-# how ???

#

-# it was running fine earlier today

lucid hearth
#

usually i have the "connecting..." message whenever i forget to plug in dock

patent wharf
#

both cables would be damaged then somehow

lucid hearth
#

idk then growlithe_think

patent wharf
#

cuz i swapped them after dealing with nonsense

lucid hearth
#

are u using the original power cable for the dock?

patent wharf
#

yea

lucid hearth
#

huh

patent wharf
#

plugged into the wall and everything

lucid hearth
#

switch is docked too?

patent wharf
#

yep

lucid hearth
#

might have to ask someoen a bit more tech saavy then

#

idk what's causing the issue

patent wharf
#

-# me neither cryingaboutit

#

updating was a mistake
shoulda stayed with safe old version

lucid hearth
#

lol

#

u did choose "esp32-s3" from the dropdown on the flashing software right?

patent wharf
#

yep

lucid hearth
#

idk then GrowlShrug

#

i usually have these settings upon opening it

#

and then this for flashing

#

maybe one those settings mightve gotten changed somehow on ur end

#

i mean it appears to be working fine for me

#

but i have it set up on my sw2 rn

patent wharf
#

maybe they forgot about the poor sw1 users

lucid hearth
#

looks fine

#

do u have the BAUD setting at bottom set to 460800 ?

patent wharf
#

yea

lucid hearth
#

idk then

#

maybe try reflashing ?

patent wharf
#

i just did

lucid hearth
#

see if that works

patent wharf
#

still purgatory

lucid hearth
#

huh

#

u plugging the computer end cable in for flashing or the sw dock end?

#

i usually flash with the cable for the computer end

patent wharf
#

i have them both plugged in

#

does it matter?

lucid hearth
#

idk

#

probably not

#

ik the arduino leonardo u had to use the micro usb cable for the dock end, but u also had to use that one for flashing

patent wharf
#

this is an esp32-s3 tho

lucid hearth
#

yeah, so with esp32-s3 idk if it matters or not

patent wharf
#

maybe i try to downgrade to an older version

lucid hearth
#

but i've always used the one for computer end to flash

#

maybe try that

#

good idea

#

u r using folder for v0.61.4 right?

patent wharf
#

yea

lucid hearth
#

huh

patent wharf
#

i delete the old one before installing the new one so i don't goof them lol

lucid hearth
#

bc they also just had a v0.61.3 just a few days ago

patent wharf
#

mine was like v0.59 tho

#

v old

lucid hearth
#

oh

#

nvm then

#

yeah

#

maybe try changing "console type" from auto detect to switch1?

#

i doubt thatll fix it tho

#

also make sure its set to correct com port

#

also does it let u click on the blank dropdown next to com port one?

patent wharf
#

nope

lucid hearth
#

hmm

patent wharf
#

older version (0.60.9) also isn't working

lucid hearth
#

r u using a usb hub for the esp32s3?

patent wharf
#

it's plugged into my computer directly

lucid hearth
#

oh ok

#

if u were id say flash without the hub but nvm

patent wharf
#

lemme see if i can go back to the version i had earlier

lucid hearth
#

ok

#

maybe try v0.60.2? #automation-releases message

#

or v0.60.3

patent wharf
#

still connecting.......

lucid hearth
#

huh

patent wharf
#

-# what happened today to make it break

lucid hearth
#

maybe something overheated the power cable?

#

have u tried unplugging the dock power & both esp32s3 cables?

#

lettign it sit unplugged for like 30 seconds then plugging back in?

patent wharf
#

i can

lucid hearth
#

a lot of tech helpdesks usually say wait 30 seconds after unplugging

#

i think it causes the device to refresh itself or cool down or something like that

patent wharf
#

no dice

#

if i had another cable to test with i'd grab it :<

lucid hearth
#

good luck

#

maybe kuro or one of the other devs might be able to help

patent wharf
#

hopefully they stumble in here and solve all my problems :>

lucid hearth
#

yeah 🤞

patent wharf
#

my hunch is one of my board cables bit the dust (cuz it was acting funky earlier and refreshing device manager)

#

but i dunno

lucid hearth
#

yeah thats probably it

#

probably one of the usb-c cables

#

hopefully not the power cable

patent wharf
#

i highly doubt its the power cable

lucid hearth
#

ik with the switch2, automation wouldnt work for me unless i used the provided sw2 power cable with the dock

#

i think sw1 worked with 3rd party cables iirc

patent wharf
#

mine's the og power cable

#

so that's another reason it's not the problem

lucid hearth
#

yeah, but that's why im hoping it not the power cable that hit the dust lol

#

more likely one of the board cables tho

patent wharf
#

-# sw2 is in the future aro purchases so eh?

#

-# i can wander by target after work tomorrow and see if they have a cable

lucid hearth
#

i use a walgreens brand 3ft usb c cable for automation & it works fine for me

#

i work at walgreens so thats why i have those lol

#

i think theyre usb 2.0

patent wharf
#

target's just close by lol
i can go anywhere tho i work close to home

lucid hearth
#

same

#

i work like 5 minute drive from home

patent wharf
#

🤝

#

-# 10 mins for me but still

lucid hearth
#

sorry i couldnt be of more help

patent wharf
#

all good
it's what i get for messing around with things

#

perhap a dev can offer some advice before i waste money on a cable

lucid hearth
#

if it was acting wonky earlier its probably the cable

#

yeah, tho any cheap usb c cable should work imo

patent wharf
lucid hearth
#

i personally wouldnt overspend on a super good quality one rn

patent wharf
#

i spent like 6 dollars for 2 lol

lucid hearth
#

lol

patent wharf
#

i'm in the business of cheap af cables

lucid hearth
#

i think i spent around the same amount on my 2 cables KEKW

#

maybe even a bit less (i get employee discount at walgreens)

#

(25% off of walgreens brand items & 10%? off of most name brand)

#

i forgot what % off the name brand tbh, its either 10% or 15%

#

i think it was more like $7 or $8 after employee discount for the 2 cables

#

i dont rly remember tho

#

i would still ask a dev before buying a new cable tho

patent wharf
#

in summary (if any devs poke their heads in here):

  • esp32-s3 isn't connecting to latest cc update
  • have tried reflashing (multiple times) with various errors ("incompatible protocol", "serial connection failed", and "connecting...")
  • tried rebooting computer and switch (1) with esp unplugged, no luck
  • swapped cables (the one that was connected to the dock is now connected to the computer and vice versa) with no luck
  • based on what i'm seeing, the cable that is now connected to the dock broke somehow (was working earlier today when i was running mega shard farming) b/c when it was plugged into the COM port, device manager would refresh every 1-3 seconds (which happens when a faulty usb is plugged in)

i'll collect a new cable tomorrow, but before i spend my money, i'd like a dev's opinion :3

patent wharf
#

bought a new cable
still unresolved

ruby sorrel
#

What does the flash tool look like after you flash?

#

Send screenshots

patent wharf
ruby sorrel
#

Did you check the top left box?

#

The top row should be green

patent wharf
#

just tried again (cuz i didn't check the box)
still isn't connecting

#

-# reflashing again got it working??

#

-# i hate technology sometimes lol

#

it really do be the simplest things sometimes
thanks for the words of wisdom SnomBlelele

patent wharf
#

verdict: keep spam flashing until it decides to work lol

ruby sorrel
#

Once you flash it. you don't need to reflash, unless CC says the firmware is out of date.

#

Why are you reflashing once it's working?

patent wharf
ruby sorrel
#

If it happens again the in future, I wouldn't try re-flashing if it works currently.

#

I would double check your cables.

#

Maybe even unplug all cables to the ESP32-S3, so that it can power cycle.

patent wharf
#

when i’m not running anything i keep it unplugged
i also got a new cable yesterday jic the problem had to do with bad cables

karmic glacier
#

i'm having the same issue with 61.4 with both my ESP32-S3s. after flashing latest firmware and pressing the reset button on the boards, CC simply displays "connecting"

rolled back to 61.3 and they both connect perfectly fine

south wave
karmic glacier
#

ESP32-S3 61.4 firmware in 61.3 CC: connected successfully
ESP32-S3 61.3 firmware in 61.4 CC: connected successfully

and i tested 61.4 firmware in 61.4 CC again and now that's working too 🙃 with both ESP32-S3s. all good for now then i guess thonk

just to be clear my process every time:

  1. close CC if open
  2. run flash_download_tool
  3. click "..." and select correct firmware
  4. click start and wait until "finish"
  5. close flash_download_tool
  6. press "reset" on ESP32-S3
  7. open CC
south wave
#

We'll see if more people hit this. Both FW and CC did change between 61.3 and 61.4. Things like this don't land on my radar until multiple people start hitting it. lul

patent wharf
#

didn’t disconnect the controller overnight and it’s working monkaHmm

patent wharf
#

seems if the esp turns off or disconnects in any way then cc won't be able to detect it again (just gives "connecting...")
dunno why that is but reflashing fixes the problem, so i'm not gonna complain (and not disconnect the esp on purpose SnomBlelele )

south wave
#

What if you completely unplug the ESP32-S3 and plug it back in. It still says fails connect without a reflash? Thonk

patent wharf
#

yis

#

well it doesn't say fails to connect

south wave
#

That almost sounds like the flash chip is defective or something. Because flash memory is non-volatile - or at least supposed to be.

patent wharf
#

it was working fine before this update tho monkaHmm

south wave
#

Maybe you fried it. All it takes is one bad static discharge to damage these boards with all the expose circuitry.

patent wharf
#

tis true (tis also my irl job lol)
so i try to be careful with the guys but i'm not whipping out full esd gear for a microcontroller

#

when it fully stops working and can't be reflashed then i'll just get a new one gayge

south wave
#

Only way to find out is to try a different ESP32-S3. But given that you're the only one reporting this issue would suggest it's either your board that's fried or you doing something very unusual that we're not aware of.

patent wharf
#

i'm too cheap to buy a new one when this one still does the job
but i prolly did indeed fry him in my endeavors and didn't even realize

untold juniper
#

Hello, just to weigh in - I am now getting the same issue with mine. I reverted back to an older version, and it is working fine, but for some reason, the last 2 versions state "Incompatible Protocol" as well.

#

@patent wharf after messing around a bit, I managed to fix it. Turns out the flash programme changed its default behaviour.

All I needed to do was click the checkbox:
Once you check this, and start the flash, the bar should be green. This fixed it for me.