Skip to content

The three things a first build got wrong - #306

Merged
engmung merged 3 commits into
mainfrom
dev
Aug 14, 2026
Merged

The three things a first build got wrong#306
engmung merged 3 commits into
mainfrom
dev

Conversation

@engmung

@engmung engmung commented Aug 14, 2026

Copy link
Copy Markdown
Owner

All from one person's first install, reported in #305 and alongside it.

"34 presets" was a promise the flash stopped keeping

The site said the image brings 34 presets. It brings one. The firmware kept only Origin when the rest moved out to the filesystem, and nobody updated the copy, so a correct install looked like a bug and got filed as one. It now says what happens, points at the Basics pack for the other 33, and names the port.

Nothing in the port picker

A module already running firmware doesn't always announce itself. The BOOT / RST sequence appeared nowhere, and it's in the build guide and under the flash button now.

That note also corrects something worth getting right. The flasher's own troubleshooting screen sends people to CP2102 and CH34x driver downloads, and on the port we tell them to use, those drivers are irrelevant. The ESP32-S3 drives its native port from a USB-Serial/JTAG controller inside the chip, so Windows binds its own CDC driver. Checked on the device rather than assumed:

hardware id  USB\VID_303A&PID_1001     Espressif, not a bridge chip
driver       usbser
inf          usbser.inf
provider     Microsoft

The driver links are for the right-hand UART port. Chasing them on the left one is a dead end, and the guide says so now.

Wi-Fi setup silently skipped on one machine

ESP Web Tools waits ten seconds for an Improv response and moves on without it, which reads as "flashed successfully" with no Wi-Fi step. It's device timing rather than anything about that PC's network, which was the reporter's guess: after flashing, the native USB re-enumerates and how long that takes varies by host.

Not reproduced here — it appeared within the default on this machine. So this is a slow-host allowance rather than a fix for a confirmed bug. Raised to twenty seconds, which costs nothing when the device is quick.

Also: the button has been called "Flash Patternflow" for a while and three docs still called it "Flash Patternflow OS".

🤖 Generated with Claude Code

All from one person's first install, reported in #305 and alongside it.

**"34 presets" was a promise the flash stopped keeping.** The site said
the image brings 34 presets. It brings one. The firmware kept only
Origin when the rest moved out to the filesystem, and nobody updated the
copy, so a correct install looked like a bug and got filed as one. It
now says what actually happens, and points at the Basics pack for the
other 33.

**Nothing in the port picker.** A module already running firmware does
not always announce itself, and the fix is the BOOT / RST sequence,
which appeared nowhere. It is in the build guide and under the flash
button now.

That note also corrects something worth getting right. The flasher's own
troubleshooting screen sends people to CP2102 and CH34x driver
downloads, and on the port we tell them to use those drivers have
nothing to do with anything. The ESP32-S3 drives its native port from a
USB-Serial/JTAG controller inside the chip, so Windows binds its own
CDC driver. Verified on the device rather than assumed:

    hardware id  USB\VID_303A&PID_1001     Espressif, not a bridge chip
    driver       usbser
    inf          usbser.inf
    provider     Microsoft

So the driver links are for the right-hand UART port, and chasing them
on the left one is a dead end. Said so.

**Wi-Fi setup silently skipped on one machine.** ESP Web Tools waits ten
seconds for an Improv response and moves on without it, which reads as
"flashed successfully" with no Wi-Fi step. It is device timing rather
than anything about that PC's own network: after flashing, the native
USB re-enumerates, and how long that takes varies by host. It appeared
within the default on the machine here, so this is a slow-host fix
rather than a reproduction. Raised to twenty seconds, which costs
nothing when the device is quick.

Also: the button has been called "Flash Patternflow" for a while and
three docs still called it "Flash Patternflow OS".

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Aug 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pattern-flow-open Ready Ready Preview Aug 14, 2026 1:16am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
pattern-flow_origin Ignored Ignored Aug 14, 2026 1:16am

The note under the flash button had grown into a manual. It was
covering the port, the pattern count, the pack and the BOOT/RST
recovery, which is more than a caption can carry and still be read.

Two lines now, and a link to the flashing guide for the rest.

The guide gained the step it was missing. It never said how to get
patterns onto a freshly flashed board, which is the exact gap that made
one person read a correct install as a broken one: the image ships
Origin alone and nothing told them where the other 33 were.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
They are the way out of that block, one to the pack that fills an empty
board and one to the guide that answers everything the caption no longer
does. On a dark panel an opacity shift alone was easy to miss.

Colour is inherited rather than accent, since two orange runs in a
two-line note reads louder than it needs to. The accent is kept for
hover.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@engmung
engmung merged commit af4d640 into main Aug 14, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant