UIFlow2.0 for Paper S3 won't install.
-
I have been unable to install UIFlow 2.0 (v2.2.0-hotfix-2 ) on my Paper S3. The burn process starts out normally enough, but instead of burning incrementally like every other ESP32 installation does, it almost immediately hits 100% and finishes seemingly without having installed anything. I've restarted everything, reloaded a fresh copy of M5Burner, replaced USB cables, erased the Paper S3 memory, etc., but it's failed repeatedly in the same manner I've described. I've been able to reinstall the PaperS3 Factory Test without any difficulty, so the problem seems to be with UIFLow2 somehow. My computer is an M1 Mac Studio, MacOS 15.2; I'm using the latest version of M5Burner. I'd appreciate any help or suggestions...it seems like at least a few other people have been able to do this. Thanks.
-
Here is the M5Burner log from my most recent attempt:
--chip auto --port /dev/tty.usbmodem144101 --baud 1500000 --before default_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x9000 /Applications/M5Burner.app/Contents/Resources/packages/tmp/uiflow2-cfg.bin
esptool.py v4.7-dev Serial port /dev/tty.usbmodem144101 Connecting...
Detecting chip type... ESP32-S3 Chip is ESP32-S3 (revision v0.2) Features: WiFi, BLE Crystal is 40MHz MAC: a0:85:e3:f2:8b:98 Uploading stub... Running stub... Stub running... Changing baud rate to 1500000 Changed. Configuring flash size... Auto-detected Flash size: 16MB Flash will be erased from 0x00009000 to 0x0000efff... Compressed 24576 bytes to 475... Writing at 0x00009000... (100 %)
Wrote 24576 bytes (475 compressed) at 0x00009000 in 0.3 seconds (effective 575.1 kbit/s)... Hash of data verified. Leaving... Hard resetting via RTS pin...24576 bytes written for UIFlow2!?
-
Hello @phesterman
that small size doesn't look correct. My guess would be that the firmware file downloaded into M5Burner is corrupt (too short).
Try re-downloading the firmware into M5Burner by first clicking onto
Remove
and then ontoDownload
. Also there is a UIFlow2.2.1 version now to try.Thanks
Felix -
Thanks for the suggestion. I had tried that before and just tried it again—doesn't make any difference unfortunately. This was v2.2.1-rc1.