Zum Hauptinhalt springen

Troubleshooting

Start with the symptom you can observe. Apply one change at a time, then retry the smallest Quick Start example.

Connection and upload​

The board does not show up as a port

Some USB cables only carry power. Try a cable you know transfers data, and plug it straight into the computer rather than through a hub. The board talks to the computer through a CH340K USB-to-serial chip, so the computer needs the CH340 driver, which the chip's maker WCH publishes. On macOS, download it from WCH, open the downloaded package and follow its instructions. macOS may then ask you to allow the driver under System Settings → Privacy & Security.

The upload fails or cannot connect

Check that Tools → Board and Tools → Port match this board. Close anything else that has the port open (Serial Monitor or another terminal), because only one program can use it at a time. If it still fails, put the board into bootloader mode and upload again: hold the USER button (it pulls IO0 low), press and release RESET, then release USER. Normally you do not need this, because the upload resets the board for you through the CH340K's DTR and RTS lines.

Serial output​

Serial Monitor shows random characters

The baud rate in Serial Monitor does not match the one in the sketch. Set the dropdown in the corner of Serial Monitor to the value in Serial.begin().

Serial Monitor stays empty

Press the board's RESET button with Serial Monitor open: the sketch may have printed before the monitor connected. Also check that Tools → USB CDC On Boot is Disabled, which is the default. Enabling it sends Serial to the ESP32-S3's own USB pins, and the USB-C connector is wired to the CH340K instead.

Power and voltage​

The board resets on its own, often when Wi-Fi starts

The supply cannot keep up with the current peaks, and the chip restarts when the voltage dips (on an ESP32 the log says the brownout detector was triggered). Use a USB port on the computer itself or a powered hub, a shorter cable, or a charged battery.

A connected sensor or module does not work

The GPIO pins use 3.3 V logic. A 5 V signal on a GPIO pin can damage the board, so connect 5 V parts through a level shifter, and power each part from the voltage its own documentation asks for.

Nothing lights up, or the board gets warm

Unplug it straight away and disconnect everything wired to it. Look for a short between power and ground, then reconnect one part at a time. If a battery is connected, check its polarity against the marking next to the connector: battery plugs from different makers are not all wired the same way.

First program​

The upload worked but the LED does not blink

The Blink example drives the RGB LED on IO2. If JP1 on the underside has been cut, that LED has no power and stays dark; see the jumpers in Hardware. Otherwise, check that Tools → Board is set to Soldered NULA DeepSleep ESP32S3, because the LED pin comes from the board definition.

Still blocked?​