ESP32-S3 N16R8/When it does not work/11. The diodes behind the ports
When it does not work · 11 of 12

The diodes behind the ports

A socket that has stopped working entirely, while the other one is fine, is almost never the socket. It is the small series diode above it — the part that protects the board from a supply wired backwards, and the part that dies instead of the board.

The symptom that names itself

One socket does everything: powers the board, appears as a port, uploads. The other does nothing at all — no LED, no port, no sign of life — with the same cable that just worked.

Nothing else on this board produces that. A cable fault would affect both sockets; a driver problem leaves the board powered; a dead chip takes both down. One live socket and one completely dead one points at the one part that sits between a socket and the rest of the board, and there is one per socket.

What the part is doing there

Look above each USB-C connector on the front of the board. The small component there is a series diode: current in one direction, nothing in the other.

The part between the socket and the board
board powers up
The diode on this socket
Board powers up
Reverse protection
intact
One way through, and that is the whole job. A few tenths of a volt are lost across it — which is why a board fed through a long cable and a tired charger can brown out where a short cable is fine.

It is doing one job, and it earns its place the first time somebody connects a supply backwards — from a bench supply, a battery lead, a homemade adapter. The diode blocks it, the board sits dark, and nothing behind it is harmed. That is the good outcome, and it costs a part worth cents.

The other way it dies is current. Push enough through it for long enough and it fails open — permanently non-conducting — and the socket behind it is finished while everything else on the board still works perfectly.

The two repairs

Both are real, and they are not the same repair.

Replace it. The right fix. It is a small two-terminal part and a fine-tipped iron with a little flux will lift and place one in a couple of minutes. The board goes back to exactly what it was, protection included. If you have never done surface-mount rework, this is a good first job — two pads, nothing dense nearby.

Bridge it. A blob of solder across the two pads makes the socket live again this afternoon. It is a perfectly reasonable field repair, and it is honest to say why it is not the same thing: from then on there is nothing between a supply wired backwards and the rest of the board. The next reversed lead does not stop at a cheap part.

So the decision is about the board's life, not the technique. A board on your own desk, powered from one known-good charger: bridge it and carry on. A board that goes into a classroom, a kit, or a project other people will plug things into: replace it, or retire the socket and use the other one.

Before you reach for the iron

Two minutes of checks first, because everything above assumes the diode is actually the failure:

  1. The same cable, both sockets. One works, one does nothing at all — that is the pattern. If both are dead, this article is not your answer.
  2. A different cable. Two dead cables in a row is rare and not impossible.
  3. Look at the connector. A USB-C socket with a bent or pushed-back contact, or with a pin lifted from the pad, fails the same way and is visible under a loupe. Fix the visible thing before the invisible one.

And if the board is new, stop: talk to us before soldering. A diode that failed on its first day is a warranty question, not a repair job.

When it does not work

Both sockets are dead

Then it is not the diodes — two failing at once is not a thing that happens. Check the cable on another device first, then look for a short between 5 V or 3V3 and ground, which is what takes a whole board out.

The socket powers the board but will not upload

That is not this fault. Power is arriving, so the diode is passing current. Go back to the upload article — that is a download-mode or a link problem.

The board runs from one socket and browns out with a device attached

If you have bridged the pad, everything the device draws is going through one diode. A part running near its limit drops more voltage, and the shortfall shows up as a reset when the radio transmits rather than as an error.

You bridged the diode and now the board does not power up at all

Check the bridge is on the diode's two pads and nothing else — solder that wanders onto a neighbouring pad is a short across the supply, and a supply that is shorted delivers nothing. Under magnification, always.

Where this goes next

The same eight settings, as a file you can commit — and a build system that does not forget them when the sketch moves to another machine.

PlatformIO

Edit this page — content/boards/esp32-s3/the-diodes-behind-the-ports.mdx

Community

Questions about this product

See what other owners have asked, and read their solutions.

Ask a question ↗

ESP32-S3 Gold Edition (N16R8)

Loading discussions…

Discuss this article

Ask about this page. The answer stays here, on the page it belongs to, for whoever hits the same wall next.

Browse ESP32-S3 on the forum