Can I help with remote access to my computer?

safi

I'm trying to ...
Could the non-English character (s) in the paths cause errors so far?
I renamed it so there are no "bad" (non-English) characters in the paths now.
I did a trial debug boot and there was a new error.

Visual Micro + ESP32 dev module + ESP-Prog JTAG
Debugging with ESP-Prog.
Upload in series (not ESP-Prog).
----
Upload successful.
Initializes the debug, but stops with a GDB error.

I attached the screen.
What could be the solution?

safi

Sorry, the attachment is missing.
I'm replacing now:

safi

Hello!

Board: ESP32 Arduino v1.0.6 / ESP32 Dev Module.

I have attached pictures of the board and the wiring.

Hi :

safi

I installed a new ESP32 board:
ESP Arduino v2.0.2 / ESP32 Dev Module.
I tried debugging again.
Build: OK,
Serial Upload: OK.
Then I used the "Debug / Attach to Process ..." menu item.
And I got a GDB error.

I attached the pictures:

safi

Thanks for the updates.

v2.0.2 of the ESP32 board package has an issue with the GDB.exe which has been packaged (reported to the ESP32 team here).

If you add the below Local board.txt entry (change the user name as appropriate), does this improve the error?

2\tools\xtensa-esp32-elf-gcc\gcc8_4_0-esp-2021r1/bin 

You can add the local board.txt file for this entry from vMicro > Add Code > Add Local board.txt.

This will add a file to your project, which is where the entry needs to be added.

I tried to upload the program to esp32 with Esp-Prog as a programmer.
Unfortunately, this did not work either.
I attached the data.

safi

Running the x.bat file on a Win7 PC, I created a log file that I attached.
Is that good now? Although there are 4 bad lines in this as well.

safi

Just to update on the journey on the other machines where debugging did not work, so the solution is known to other users.....

Issue:
Running OpenOCD.exe command line via cmd.exe still resulted in errors.

Example Command:
(Logging increased using -d3 instead of -d2)

C:\Users\Miklos\Downloads\openocd-esp32-0.10.1-2021.07.21/bin/openocd.exe -d3 -s /" -f /interface/ftdi/minimodule-lowcost.cfg" -c "set ESP32_RTOS none" -f /board/esp-wroom-32.cfg" -c "init" 

The final error seen is below, before the program crashed and tried to report the error to Microsoft.

Debug: 512 3128 command.c:355 register_command_handler(): registering 'test_mem_access'...
Debug: 513 3137 ftdi.c:728 ftdi_initialize(): ftdi interface using shortest path jtag state transitions 

This is related to OpenOCD not being able to identify the ESP-PROG, even though Zadig.exe had been used to replace the driver.

Solution:
The solution is to configure the Esp-Prog USB driver as follows:
1. Connect the Esp-Prog panel to the PC with a USB cable.
2. If a USB driver is already installed, you must delete the driver in Device Manager.
3. After deleting, disconnect the Esp-Prog from the PC.
4. Download the VCP driver (Virtual COM Port Drivers) for the FT2232HQ chip from the FTDI website.
5. Install the downloaded VCP driver (run nn.exe).
6. Connect the Esp-Prog panel to the PC with a USB cable.
7. The USB driver will be installed so that channels 0 and 1 will be Virtual COM Port.
8. If there will be no Virtual COM port on channels 0 and 1, go to step 2. point.
9. Currently (2022.02.07) the result of the correct driver installation on channels 0 and 1 is as follows:
   "FTDIBUS (v2.12.36.4)"
10. With Zadig, the "Dual RS232-HS (Interface 0) channel driver must be replaced with a WinUSB (v6.1.7600.16385) driver.

The driver for the "Dual RS232-HS (Interface 1) channel does not need to be changed, it remains an FTDI driver!

With this USB setting, error-free debugging and uploading via the programmer is started.