ES32-wroom 2.8 in display will not program again

Marktecwiz · October 6

I have several ESp32 2.8 in displays and two of them stopped programming with the error:

Configuring flash size...
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x0004afff...
Compressed 18992 bytes to 13110...
A fatal error occurred: Packet content transfer stopped (received 8 bytes)

The problem is that GPIO 12 is connected to the touch screen
When this pin is high it interferes with the flash voltage.
I found this reference:https://www.esp32.com/viewtopic.php?t=27365
Bottom line you need to find the program espefuse.exe on you pc.
Mine was ... \Arduino15\packages\esp32\tools\esptoolenv\Scripts
First run espefuse.exe --help to make sure you can execute espefuse.exe.
You should get all the parameters that the progam supprts.
Then find out what port your dispslay is enumerating to (mine was Com6)
Then run this command
"espefuse.exe --port Com6 set_flash_voltage 3.3V"
you should get

Connecting...
Failed to get PID of a device on Com6, using standard reset sequence.
.
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting...
Failed to get PID of a device on Com6, using standard reset sequence.
.
Detecting chip type... ESP32

=== Run "set_flash_voltage" command ===
Enable internal flash voltage regulator (VDD_SDIO) to 3.3V.

VDD_SDIO setting complete.

Check all blocks for burn...
idx, BLOCK_NAME,          Conclusion
[00] BLOCK0               is not empty
        (written ): 0x0000000401000000000008310000a00000c6b0b21cf9912000000000
        (to write): 0x00000000000000000001c00000000000000000000000000000000000
        (coding scheme = NONE)
.
This is an irreversible operation!
Type 'BURN' (all capitals) to continue.

You need to type "BURN" all caps then enter

BURN BLOCK0  - OK (all write block bits are set)
Reading updated efuses...
Successful

I was then able to burn load new programs into all the displays that would not program with this error.