FYI, I managed to sort this out by taking GPIO0 to ground on the S3 chip itself having taken the can off
So something on the PCB it's mounted on must have screwed up the GPIO0 connection to the PCB pin apparently marked as GPIO0.
Shrug; a Scalpel wired to ground works nicely

What about GPIO46?, that is also indicated within the S3 Datasheet as being involved with Boot Mode determination.

It's marked as disconnected and having a pull down.

I'm not 100% on this, but the only eFuse that I recall that would affect download mode is the one that disables download mode. That, however, would simply give you a message that says that download mode is disabled, not ignore GPIO0 all together.


OK, thanks, so something else must be going on ...

You say 's3 mini', but that's a module, not a board. What board are you using, and are you sure the line you picked indeed goes to GPIO0?


It's an obscure board someone made as an epaper sign (EPD75); just the S3 module, a bunch of LEDs, USB connector and a DC converter to get the 3.3v.
Am I ...

can't get GPIO0 to change the boot mode;

The chip just boots normally when you keep GPIO0 pulled to GND during power up/reset?

Yep, no change in the boot log output at all. Still says boot mode 0x8.
Which made me wonder if it's a fuse that's been blown, since I'm out of other ideas.

Hi,
(S3 mini )
I'm trying to do a serial reflash for the first time and can't get GPIO0 to change the boot mode; could this be a fuse issue? and if so what would a boot log look like if it was a fuse issue?
I'm always getting exactly the same boot messages (below) with the boot type 0f 0x8, but I ...