Setting efuse to ESP32-S3 to enable DFU on boot press.

[chegewara]

1. I think i was not very precise about using zadig: DFU on esp32S3 is on interface 2, so to install driver you have to select "Options->List all devices"
2. i have no option to test DFU with windows because its not working with VM, but my S3 is not a regular COM port and i can select it to do DFU
3. here is website i am using: https://esp32.eu.org/esp32s2/dfu-util
4. i think the easiest and quickest way to confirm S3 is broken or not to test with linux; my S3 works perfectly fine after burn efuse
5. its driver state after installing driver

Screenshot from 2022-04-17 08-34-28.png (24.03 KiB) Viewed 3822 times

[chegewara]

Just a reminder:
https://docs.espressif.com/projects/esp ... ndows-only

[marclee]

I have the same problem here.

After burning eFuse Bit USB_PHY_SEL, ESP32-S3 doesn't show up any more at the USB port of the PC.

ESP32-S3-WROOM-1-N8R8
ESP-IDF v5.0-beta1-829-g3f2f35bd5e

The UART console shows that ESP32-S3 is in DFU mode:

Code: [Select all] [Expand/Collapse]

1. ESP-ROM:esp32s3-20210327
2. Build:Mar 27 2021
3. rst:0x1 (POWERON),boot:0x20 (DOWNLOAD(USB/UART0))
4. waiting for download

GeSHi © Codebox Plus Extension

But it doesn't show up as USB device at the PC. I used the commands lsusb and dfu-util -l.

[devlat]

Is it possible that your ESP32-S3 chip was manufactured before Date Code 2219 ?

Check this Security Advisory:

https://www.espressif.com/sites/default ... s%20EN.pdf

So, if you have burned USB_PHY_SEL eFuse, then in bootloader USB-OTG will be connected by default, but if EFUSE_DIS_USB_OTG_DOWNLOAD_MODE was already set at the factory then maybe USB interface is not activated at all and there is nothing you can do.
Could someone confirm such scenario?

[marclee]

Is it possible that your ESP32-S3 chip was manufactured before Date Code 2219 ?

In my case the date code is 2219 and ESP32-S3 does not appear as DFU USB device as described above.