Tessera 0.4.95 · firmware 0.60.0
A hotfix for installing from the browser: a screen with an ESP32-P4 installed over USB from this computer starts by itself again. No firmware change: the screens keep 0.60.0.
What was broken
Installing a screen with an ESP32-P4 (reTerminal D1001, Guition 10.1 and 7 inch, Waveshare P4 panels, M5Stack Tab5, CrowPanel Advanced) from the browser, in New screen or under Firmware & USB with "Via this computer": the image was written, the page said "Installed, the screen restarts", and the screen stayed dark. The wizard then waited for a screen that never came, and only pulling the cable started it. The reset the page sent after writing was esptool-js's "USB JTAG serial reset", which puts such a chip in download mode rather than restarting it.
The fix
After writing, the page pulses the chip's EN line, as it does for a board behind a USB-UART bridge. Measured on a reTerminal D1001 (ESP32-P4 v1.3) with the same signals: the old sequence ends in boot:0x207 (DOWNLOAD), "waiting for download"; the new one in boot:0x20f (SPI_FAST_FLASH_BOOT), and the firmware runs. The ESP32-S3, S2, C2 and C3 keep their watchdog reset, so nothing changes for them. Tested with the New screen wizard on a reTerminal D1001 from Chrome.
How to get it
Update Tessera Screen Manager in Home Assistant. No screen needs an update for this.