Just a crazy question here. What is the point for all that circuitry for the TX pin to the RS485 ?
Why didn't you just route the TX to the DI pin?
Are you aware that ESP has a driver for RS485, in which you can simply supply the Tx, Rx & RE/DE pins?

FWIW. I had the same issue. Holding down GPIO0 alone did not do the trick for me. I had to hold down GPIO0 & EN, then release EN.

We have been using the ESP32-S3-DevKitC-1 v1.1 to help develop one of our new products. We are using the "USB" connector to flash the unit this entire time, and has worked great. Our first pass we made 100 pcb's using the ESP32-S3-WROOM-1U-N16 module. We did not put any headers on the board to flash...

I think this is what you need.
https://github.com/espressif/esp-idf/tr ... e/tusb_msc

awesome! Next time I do my online order I'll pick one up and try.

Can you try these 2 things to see if it helps.

trasactionHandle.flags = 0;
.duty_cycle_pos = 0

Thanks rudi for the update.
I have to ask... Wonder why they didn't choose 240mhz. looks like they have it set to 160mhz.
Lastly, though it boots, what can we really do with such limited ram?

I did this many years ago, so I am not sure what has changes in the software. But back then you could configure to use GPIO0 as the clk. The problem with this was that it did not allow uploading the firmware automatically. You had to manually keep GPIO0 low then reset to put it in bootloader mode fo...

You can use GPIO0