ESP32 Forum

Hi all,

We are planning to use ESP32-S3-WROOM-1-N16R8 in one of our product development.

ESP32-S3-WROOM-1-N16R8 has D+ and D- lines, and can function as USB?

We would like to utilize those pins for both image download and debugging purpose.

Please let us know if we need to add any additional circuit for the same.

Regards,
Lalit Shah

ESP32-S3-WROOM-1-N16R8 has D+ and D- lines, and can function as USB?

We would like to utilize those pins for both image download and debugging purpose.

You can.

Please let us know if we need to add any additional circuit for the same.

If you follow the (bits that are applicable to modules in the) hardware design guidelines, you should be fine. Generally, no additional circuitry on D+/D- is required, but depending on your use you may want to add extra ESD protection.

Hi Sprite,

Thanks for prompt response and guiding me for reference design.

Is there any reference design or any example available where D+ and D- lines have been connected?

Regards,
Lalit

Yes. (Note schematics are linked in the bottom of that document; look at the port labeled "ESP USB" there)

Hi Sprite,

Thanks for update.

From all details my understanding is that if we just need to use for download perspective we can use USB functionality, but if we need to use from debug perspective than we need to keep external USB-UART chip.

Regards,
Lalit

It's actually the other way around: if you want to do (JTAG) debugging, you can do that using the USB port (when it uses the USB-serial-JTAG controller) but you cannot do that over an UART; you'd need an additional JTAG adapter.

Generally, there's only a few reasons why you'd want to add an external USB-to-serial chip to an ESP32-S3:
- You want to make use of the USB-OTG functionality (to connect the ESP32-S3 to an USB device, or to have it act like a specific USB device) and need to debug the device like it is in that mode. USB-OTG takes over the USB port from the USB-serial-JTAG you'd use to debug these issues.
- You need to debug issues with light/deep sleep. UARTs tend to be a bit more useful for that as they don't loose the USB connection when the chip goes to sleep.

As an extra hint: Do make sure to connect GPIO0 to something (a button as on the devboard, or at least a testpad), as you can theoretically need it to force the device into bootloader mode.

Thanks for update and clarification.