Skip to content
DeckConnectorSet it up
Skip to Content

Flashing problems

Flashing the ESP32-P4 board fails? Every error the flasher shows, what causes it, and how to fix it.

This browser cannot flash

Cause. The flasher uses Web Serial. Only Chrome, Edge and other Chromium browsers on a computer have it. Firefox, Safari, phones and tablets do not.

Fix. Open the page in Chrome or Edge on Windows, macOS or Linux. Without them, use esptool.

The page is not https

Cause. Browsers allow Web Serial only on https:// pages and on localhost.

Fix. Open the flasher from its https:// address.

No port in the list

CauseFix
The cable only chargesUse a cable that carries data. If a phone shows no files over it, it is a charge-only cable
The cable is in the USB-A portUse the USB-C port. USB-A is for the deck
A hub or dock in betweenPlug the board straight into the computer
The list hides other chipsClick Show all ports. The flasher first lists only the board's USB serial chip
No driver for the USB serial chipSee Driver

Driver

The USB-C port goes through a WCH CH343 USB serial chip. Windows 10 and 11, macOS and Linux usually need no extra driver. If the port still does not show up, install the driver from WCH, then replug the board.

On Linux the board shows up as /dev/ttyACM0. If Chrome cannot open it, add your user to the dialout group (uucp on Arch) and log in again.

Port busy

Cause. Only one program can open a serial port. Common ones: the Arduino IDE, PuTTY, idf.py monitor, screen, a 3D printer tool, or a second flasher tab.

Fix. Close that program or tab, then click Connect again. If you do not know which one, unplug and replug the board.

The board does not answer

Cause. The flasher could not reset the board into download mode by itself.

Fix. Put it into download mode by hand:

  1. Hold BOOT.
  2. Press and release RST.
  3. Release BOOT.
  4. Click Connect again.

Wrong chip

Cause. The port belongs to another board, for example an ESP32-S3 that is also plugged in.

Fix. Click Use another board and pick the right port. DeckConnector runs only on the ESP32-P4.

Chip revision too old

Cause. Early ESP32-P4 chips (before v3.1, often v1.3) cannot run this firmware. Some boards of this model shipped with them. The flasher stops before it writes anything.

Fix. None in software. Use a board with chip revision v3.1 or a later v3. The flasher shows the revision it found.

The install stops midway

Cause. The USB connection dropped. Usually a loose or long cable, a hub, a power-saving USB port, or the computer going to sleep.

Fix. Use a short data cable straight into the computer, keep the tab open, and start again. The board is not damaged. It can always be flashed again.

If it keeps failing, flash slower with esptool and -b 115200.

Read-back does not match

Cause. The flasher reads each part back after writing. A mismatch means bytes got lost on the way, almost always the cable or the USB port.

Fix. Another cable or port, then start again. If it repeats, choose Full install, which erases the flash first.

Firmware does not load

Cause. The download broke, or the browser has an old copy.

Fix. Reload the page. With Use local files you can load a manifest.json and its .bin files from a release instead.

Wi-Fi over USB does not answer

CauseFix
The connector is still startingWait 15 seconds
Setup is already done, and the connector started more than 5 minutes agoPress RST, then save again within 5 minutes
An old firmware without USB setupInstall the current firmware

You can always skip this step. Plug in a network cable or use the setup Wi-Fi.

Wi-Fi join fails

CauseFix
A 5 GHz networkThe Wi-Fi chip, an ESP32-C6, has 2.4 GHz only. Turn on 2.4 GHz in the router, or pick its 2.4 GHz network
Wrong passwordIt has 8 to 63 characters, or 64 hex digits. Check capital letters
A hidden networkIt is not in the list. Choose Other network and type the name
Out of rangeMove the connector closer, or use a network cable

Cannot find the connector afterwards

  • The flasher's last step shows the address and the .local name.
  • The deck shows the address on the touch strip.
  • Some networks block .local names. Use the IP address instead.
  • Look in your router's device list for a name like deckconnector-a1b2c3.
  • The computer must be in the same network, not a guest Wi-Fi.
  • Before setup is done and without a network, the connector opens its own setup Wi-Fi after a minute. The deck shows its name and password.

On this page