Forum Replies Created
-
Posts
-
Hi. Thanks for the quick response.
You got it first try. That binary is indeed missing in that location.
Oddly, I find a binary (riscv32-esp-elf-gdb.exe) in 6 different paths.
The first in a directory structure installed by VisualGdb as part of the process of trying the steps in my post.
- C:\SysGCC\esp32\tools\riscv32-esp-elf-gdb\14.2_20240403\riscv32-esp-elf-gdb\bin
- C:\Usr\Espressif\tools\riscv32-esp-elf-gdb\14.2_20240403\riscv32-esp-elf-gdb\bin
- C:\Users\pdp\.platformio\packages\tool-riscv32-esp-elf-gdb\bin
- C:\Users\pdp\.platformio\packages\toolchain-riscv32-esp\bin
- C:\Users\pdp\AppData\Local\Arduino15\packages\esp32\tools\riscv32-esp-elf-gdb\12.1_20231023\bin
- C:\Usr\Ard15\packages\esp32\tools\riscv32-esp-elf-gdb\12.1_20231023\bin
1 & 2 are identical binaries. 5 & 6 are identical binaries. 3 is about the same size as the others, while 4 is 20-times larger.
I tried the quick&dirty trick of mklink to fix the issue, trying both symbolic and hard links. No change.
I tried copying the binary in 5 to the specified directory, no change.
Tried running the copied executable in that directory with the –help option, got no output and a negative return value. Tried the same thing with that same executable in its original dir, worked – got help output.
Concluded the executable is somehow chaining to other executables in it’s directory. There are a whole set of versions there, from 3.3 to 3.12. Copied ALL of them to the specified directory,.
Debugging “started” but output window pops the msg in red “Error erasing flash with vFlashErase packet”, followed by a warning message msg in yellow “Could not set a breakpoint on main. Step into a new instance will not work”
Deleted the copied set of executables. Tried the single “large” binary in directory 4, same result, debugging starts and pops same error messages in output window about flash erase and breakpoint setting failures.
So, I conclude quick and dirty fixes are not enough. Any suggestions on a “clean” fix?
