-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openocd: Remote 'g' packet reply is too long (expected 388 bytes, got 608 bytes) (IDFGH-7851) #9379
Comments
@xobs Thank you for the issue report! Just to check one detail, could you please try running:
and see what the result is? Looks like there are two issues:
|
@igrr yes, specifying I feel that the installation process is currently broken. This may be due to an inconsistency in current toolchain versions. I'm seeing the following errors. Where should I report them?
So it seems like the compilers are assuming there's a python distribution alongside them, but that python runtime is not getting shipped. Additionally, if I remove ~.espressif and ~\esp and re-run the vscode installer, then idf complains the incorrect toolchain was installed:
install esp-idf master branch via vscode
I can then run So something is definitely going wrong with the toolchain if vscode installs it, and the python libraries are definitely getting omitted by the default installer. |
I think the issue with gdb not picking up installed Python libraries will be fixed in the new GDB release, https://github.com/espressif/binutils-gdb/releases/tag/esp-gdb-v11.2_20220529. We have just merged the commit to internal IDF branch where we update GDB to that release. We will let you know once that change gets deployed to Github, so that you can test that. Regarding the second issue (about VS Code), could you please report it to https://github.com/espressif/vscode-esp-idf-extension/issues? |
I can confirm that I'm using that version of GDB, however it does not solve the underlying issue. I removed
|
Sorry for the long delay, @xobs I can not reproduce the issue. The way I do it:
after that I was able to run xtensa GDBs without any issue. But I found that if I install 32-bit Python on my 64-bit Windows I have the same behavior as you described. Could you please run a few commands in PowerShell:
|
Sure, here you go:
Normally I use Powershell, and not VSCode, but I get the same behaviour when I run it in straight powershell. I'm seeing this on both of my Windows machines, so I'm unsure if it's some cruft leftover on this machine. |
@xobs , Could you rerun
it has a typo in your output |
Sure, my mistake for not noticing that. I guess there was an error in buffering when I pasted the commands into vscode. In any case:
I get the same output when I run it from powershell:
|
I can verify that 20220729 has fixed this issue:
Thanks for the fix! |
Environment
git describe --tags
to find it): v5.0-dev-4037-g9b8c558e63xtensa-esp32-elf-gcc --version
to find it): xtensa-esp-elf-gdb-3.8 --version: GNU gdb (esp-gdb) 11.2_20220529Problem Description
The ESP toolchain was installed by vscode.
xtensa-esp32s3-elf-gdb
and friends do not run.xtensa-esp-elf-gdb-3.8
runs, but cannot connect to openocd.Expected Behavior
GDB should run, and it should be able to connect to openocd.
Actual Behavior
gdb does not run. When I get gdb to run, it fails.
Steps to reproduce
esp-idf
frommaster
The text was updated successfully, but these errors were encountered: