[support]

Thanks for confirming the issue on the latest version. We have followed the steps you described and were able to reproduce and fix the problem. Please try this build: VisualGDB-5.4.105.3135.msi

[support]

Hi,

Unfortunately this would be not that easy due to the differences between the VC++-based projects and projects fully controlled by VisualGDB (e.g. ESP-IDF). That said, we are planning to add support for embedded projects to the Advanced CMake Project Subsystem in the next major VisualGDB release, so we should be able to add this command there.

[support]

Thanks for the log files. We have looked through them (the links to Google Drive were OK), however unfortunately there is no obvious indication of the problem there. Generally, as the OpenOCD’s STM32L0 driver is not maintained by us, it’s hard to suggest a definitive way of fixing this.

That said, please consider one of the following workarounds:

1. Try using Segger J-Link instead of OpenOCD. Segger maintains their own fully supported replacement for OpenOCD that is specifically focused on out-of-the-box support for most of the devices on the market, so it should not share any of the OpenOCD bugs.
2. Alternatively, please try building our OpenOCD fork from sources (see this tutorial for detailed steps) and try stepping through the relevant FLASH loader code. If you could pinpoint a specific cause for this, we will be happy to include a fix in our fork as long as it doesn’t break the backward compatibility.
3. If you can reliably reproduce the problem, please consider filing a bug report via the OpenOCD mailing list. The maintainer of the STM32L0 driver might be able to pinpoint the problem and fix it based on the logs you have collected. If the fix is included in the regular OpenOCD repository, we should be able to pick it up and include in our builds promptly.

[support]

Hi,

No problem, please try this build: VisualGDB-5.4.105.3134.msi

We have added a context menu command for ESP-IDF projects to open the raw terminal (please note that the raw terminal is only supported on the Custom edition and higher, so the command won’t appear for the Embedded and Linux editions of VisualGDB).

[support]

Thanks for sharing this, it does look like the potential cause for the problem, although unfortunately it’s not something that VisualGDB could easily fix.

[support]

Sorry, it looks like something related to the wiring or layout of a specific board and is generally outside VisualGDB’s control. The only way to diagnose this that we could suggest would be to try understanding the differences between a working an a non-working setup (e.g. using a logic analyzer). Please also consider asking on the Espressif forums – you may get some insights into this from the team that designed the WROVER/WROOM boards.

[support]

Hi,

Please try updating to the latest VisualGDB 5.4R5. It includes multiple ESP-IDF-related updates and might fix this issue. If it doesn’t help, please let us know the updated stack trace and we will investigate this.

[support]

According to our records, it looks like your trial period has expired. In order to get further technical support, please consider purchasing a license.
Please note that installing VisualGDB on another PC, editing registry to affect the trial counter, or creating further forum accounts does not reset your trial period from the support point of view.
As providing quality technical support for our users requires continuous effort on our side, we do expect our users to play fair and are not able to offer any help once the original trial period expires.

[support]

Hi,

It looks like your ESP8266 Arduino core might be corrupt. The easiest way to fix this would be to delete it and let VisualGDB automatically download the latest version of the core and all related tools.

[support]

Hi,

It looks like a missing reset signal (in our experiments, some probes had to use the TRST signal, while others needed SRST), so trying a few reset options in OpenOCD configuration script might resolve this. If not, please try using Olimex ARM-USB-OCD-H (we have fully tested it on our side and covered in our tutorials), or some of the ESP32 boards with on-board JTAG, that should have the necessary wiring and matching configuration scripts.

[support]

Hi,

The exact reason behind this would depend on the project type (e.g. Make/MSBuild/CMake), so it’s hard to say anything without knowing more details.

Our best advice would be to try following the steps described in this tutorial to check the paths and then post the details here with a screenshot of the setting(s) that don’t look right. This should help us understand what is going on and help you get it to work.

[support]

Hi,

Based on what you have described, the following events take place:

1. You have created a non-relocatable project based on the STM32CubeMX project sample instead of the regular relocatable project shown in the wizard.
2. As the non-relocatable project hardcodes the paths to source/header files in the .vcxproj file instead of using the $(BSP_ROOT) variable, it does not open on another machine.
3. Per your feedback, we have patched VisualGDB to use the correct $(BSP_ROOT) syntax when creating new projects based on STM32CubeMX and provided instructions on adjusting the project manually.

The most likely reason why the project would still not build on the other machine is because it still uses incorrect paths for some of the files. The only way to diagnose this would be to look through the build log (View->Output), locate the “cannot find source file <file>.c” message, and then search the .vcxproj file for the reference to the file mentioned in the error. Most likely this reference will still use incorrect format and updating it to use $(BSP_ROOT) should solve the problem.

If you do not want to edit the .vcxproj files manually, please consider using the same project types as shown in our tutorials until you get familiar with VisualGDB settings and constraints. We publish those tutorials specifically to help new users find the working combination of settings for their setup and we always advise using them as a starting point.

[support]

Thanks for the update. If both OpenOCD and J-Link don’t recognize a specific device on a specific machine, it’s likely caused by some low-level USB driver issues. We understand that the ST-Link tool works with it, however it might be using a slightly different underlying API. Generally, using a different machine, or connecting the device to a different USB port/host controller should work around the issue.

[support]

The delay ultimately happens because Visual Studio needs to run certain commands from the GUI thread (i.e. won’t continue or respond to commands until the command is completed) and those commands altogether take a lot of time due to a slow network connection. VisualGDB does show a “command in progress” window when a command doesn’t respond for 2 seconds or longer, however this doesn’t happen in this case because each of the individual 142 commands takes less time (showing and hiding the progress window 142 times would be more confusing and distracting). Sorry, the only long-term way to solve this would be to eliminate the factors that cause the delay (i.e. speed up the connection or run gdb locally).

[support]

Thanks for the update. Most likely this is caused by an incompatibility between the libusb library used by OpenOCD and a specific USB host controller, or a specific driver version. The best workaround would be to try using the Segger J-Link firmware for ST-Link. J-Link uses its own driver and its own gdb stub, so it should not trigger any bugs that are specific to OpenOCD.

[Author]

Posts