I heard from several people that they got problems getting RunCPM up and running onto the TTGO VGA32 v1.4 😦
Thats made me sad, because I want to make many people as possible happy to run RunCPM this way.

Mostly there are problems which seem to come from a non actual version of the FabGL library – which cant be updated from the Arduino-IDE to the latest version, because this is only available on the github page of the FabGL as master.zip

So as requested (and now also tested as working by me) I created a precompiled binary which can be more easily flashed to the TTGO VGA32 v1.4 with the Espressif Flash Download Tool (actual v3.8.7 for Windows)

With this binary version you shouldnt need to have hassle with
– installing the ARDUINO IDE (v1.8.3)
– installing ESP32 Board-Support in the ARDUINO IDE
– installing the SDFat Library in the ARDUINO IDE
– installing the FabGL Library in the ARDUINO IDE
– configuring the ESP32-Settings in the ARDUINO IDE

So the 1st piece of software – now – you need to download is the Espressif Flash Download Tool from the Espressif Page
The Download-Size should be around 15.3MB

And the 2nd and last 😉 piece of software is the archive of the precompiled RunCPM binary
v5.5 Rev 20210712.0 for the TTGO VGA32 v1.4

The Flash Download Tool is like the precompiled RunCPM binary only a .ZIP-File and hasnt to be installed in any way 🙂
So just unzip these 2 .ZIP-files to a place which you could find easily.

Connect your TTGO VGA32 v1.4 to your PC via USB
then open/start the flash_download_tool_3.8.7.exe -> select ESP32 & develop -> click OK
Now you have as next the most difficult part 🙂
Select (using the 3 points at every line) the files (to flash) in the shown order from the path where you extracted them.
Dont fortget to activate the ticks before each of the 4 lines and to insert the address where to flash the file.
As you can see the files would be flashed at address 0xe00 0x1000 0x10000 and 0x8000
The adress is for each file is also shown before the .bin for your convenience

After you have setup/configured the flash files adjust the other settings according the picture above:
SPI Speed 80Mhz, SPI Mode DIO, Flash Size 32MBit
and select at COM: (here COM6 in the sample) the COM:-Port of your TTGO VGA32 v1.4 device
After you have configured/adjusted all the setitings you could click/press the START-Button.
The ESP32 Download Tool will now flash your TTGO VGA32 v1.4 device
When the Flash-process has completed the Download Panel will show FINISH in green.
At this Point you could click/press the STOP-Button (there is no Auto-Reset like in the Arduino IDE).

So – now you have managed the difficult part 😉

Close the ESP Download Tool (the Tool may open Windows in the reversed order like on the start).
Disconnect your TTGO VGA32 v1.4 device from the USB-Port.

Format a MicroSD-Card with FAT(16 or 32) and copy the complete content of the folder Put_Content_on_SDCard
(from the extracted RumCPM binary archive) to the root-directory of the MicroSD-Card.

Insert the MicroSD-Card in your TTGO VGA32 v1.4 device and connect VGA-Monitor, PS/2-Keybord, Audio and the Power (via MicroUSB).

Now – when the TTGO VGA32 has started – you should be greeted by the Start-Screen which firstly shows the Boot-Info and then the Powerup-Boot-Screen.

Powerup-Boot-Screen without the Boot-Info


If you got here, then you can press F12 at the PS/2-Keyboard for configuring the Terminal-Part and Functions of your RunCPM device.

F12 Config Menu


You probably would
– disable the Boot-Info
– setup your Terminal-Emulation (best is ANSI Legacy or ANSI)
– setup your prefered Terminal-Colors
– some may disable the KeyClick (I like the sound like on a ATARI 8Bit)

Like on old DOS-programs you could jump from setting to setting with the TAB-Key and select/dis-select ticks with the
SPACE-Key.

When you have all setting how you want to use it then press F10 to save these.

Now your RunCPM should be ready to use 😉

If you may come to a problem or hanging CP/M you could press the BREAK-Key (which is Ctrl-PAUSE).
But ATTENTION your work wouldnt be saved 🙂

You could also use the Command REBOOT from the Command-Line/-Prompt.