We are having trouble uploading the Firmware solution on Visual Micro into out ESP32 board via ESP-PROG (after burning the e-fuse). 
In attachment 2 error messages we got when performing the action. 

Thank you Simon for the reply,

I just changed my project (and .ino file) names without spaces.

I attached the Board.txt file I created in my project, I am not sure if I need to modify the tools.openocd part following the documentation you provided or not. 

efuse we burned is STRAP_JTAG_SEL

I thought I attached it, I do it now sorry for that.

Yes, we added a wire to pull GPIO3 low.

In a couple of hours, I will also share the log for a build&upload, 

thank you very much for your support

Thanks for the update, and the STRAP_JTAG_SEL Fuse looks correct:
Espressif Doc: https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/api-guides/jtag-de...

The error in the log suggests there is a wiring issue between the ESP-PROG and the ESP32S3 board, or sometimes they both need disconnecting from power then plugging back in again to reset a hung state.

It may also be worth lowering the speed in the board.txt file (adapter_khz 2000).

Can you confirm all connections are correct and the GND connection is also made between the ESPPROG and ESP32S3?

Thanks for the log and it appears to be getting further at least.

Quote:

I'm not sure why this is and on my setup (working) it only shows two entries, then continues.

Can you try uploading a program (e.g. blink) to the board using the normal USB interface, and then try uploading your desired program via ESPPROG again?

Quote:

Thanks for confirming, I wasn't sure if you had a full dev board(with USB connection) or just the ESP32S3 module (or chip on a custom board).

Thanks for clarifying the Flash Mapping entries in the logs as well.

I only see the below when connecting in my log, and the upload via ESPPROG is working here, and it maps the Flash correctly to the two regions:
** Programming Started **
Info : esp32s3.cpu0: Target halted, PC=0x403B2412, debug_reason=00000001
Info : Flash mapping 0: 0x10020 -> 0x3c030020, 58 KB
Info : Flash mapping 1: 0x20020 -> 0x42000020, 149 KB
Info : esp32s3.cpu0: Target halted, PC=0x403B2412, debug_reason=00000001
Info : Auto-detected flash bank 'esp32s3.cpu1.flash' size 16384 KB
Info : Using flash bank 'esp32s3.cpu1.flash' size 16384 KB

Can you confirm which exact ESP32S3 module you have (or upload a good quality photo to read the chip/module markings)?

It may be the Flash Size is misconfigured for OpenOCD which is causing it to read it incorrectly, generating the thousands of entries.  It may be that its a newer model of chip so a newer version of OpenOCD is required which can be temporarily configured as below.

If you amend the local board.txt to replace all "{runtime.tools.openocd-esp32-0.10.1-2021.11.11.path}" entries with "{runtime.tools.openocd-esp32-v0.12.0-esp32-20240821.path}", and also select the ESP32 DEVKIT debug probe from the vMicro >Debugger > Hardware Debugger list.  Then restart Visual Studio and try the upload again.