[support]

Hi,

No problem. Please try setting the Tools->Options->VisualGDB->Advanced Build->Build Results Window Stickiness option to 0.

You can find more about various VisualGDB settings, including a searchable list of them on this page.

[support]

Hi,

OpenOCD support for specific devices is usually contributed by the device vendors or someone from the OpenOCD community. We periodically release builds based on the latest OpenOCD source, however we do not maintain device-specific parts of it.

The OpenOCD code base is evolving very fast, so there is a high chance the issue is already fixed in the latest OpenOCD build released today. Please try installing it via VisualGDB Package Manager.

Alternatively, please consider using Segger J-Link with the J-Link software. The J-Link software is a proprietary replacement to OpenOCD that is maintained and tested by Segger, and it usually works more reliably than open-source tools. VisualGDB is integrated with both tools equally well, so you can chose the best one for your setup based on your requirements.

[support]

Thanks for letting us know and good to know it works.

[support]

Hi,

This might be related to a recent update to CMake that changed the format used to report command lines. Please try updating to VisualGDB 5.6 Beta 4.

[support]

Unfortunately, it’s hard to suggest anything specific based on this description.

Please provide the steps we could follow on our side to reproduce the problem per our problem reporting guidelines and we will try to investigate this further.

[support]

It’s hard to say why the connection between 2 J-Link tools would not always work. Please try reproducing the problem outside VisualGDB by launching JLinkGDBServer manually with the command-line arguments shown in the Advanced view. If the problem persists, please contact Segger support for further help.

If running JLinkGDBServer manually works, please let us know more details (e.g. successful vs. failing logs and the exact command line used) and we will help you configure VisualGDB to replicate that setup.

[support]

Hi,

Normally, the paths should be remembered. If it doesn’t happen, please try installing the latest VisualGDB 5.6 Beta (you would need to renew your support here), make sure your can reproduce the problem from scratch, and share the steps we could follow on our side to reproduce the problem per our problem reporting guidelines.

[support]

Hi,

This could be something specific to ESP-IDF itself. E.g. the USB is not enabled for this project, hence the setting gets reverted back. Please try changing the same setting via ESP-IDF menuconfig (you can launch it via the context menu in Solution Explorer).

If menuconfig works as expected, please follow the steps below to narrow down the problem

1. Make a backup of the <project directory>\sdkconfig file before changing the setting.
2. Change the setting via VisualGDB Project Properties
3. Restore the backed up file
4. Change the same setting with menuconfig
5. Send us the 3 versions of the sdkconfig file (before, after editing with VisualGDB, after editing with menuconfig) along with the test project name, the ESP-IDF version and the device type, and we will try to reproduce the issue on our side.

[support]

Hi,

VisualGDB uses the J-Link Software to communicate to Segger J-Link. You can configure it to connect to a remote J-Link by selecting “Connection: TCP/IP” in VisualGDB Project Properties -> Debug Settings. This will pass the “-select IP” argument to JLinkGDBServerCL.exe (expand the Advanced Settings view to preview the command line).

You can find more details about remote mode of the Segger J-Link GDB Server in the J-Link documentation.

[support]

Hi,

You can use the same techniques that would work for any other IDE or a directly built project. VisualGDB does not change anything from that perspective.

[support]

Hi,

When you install a new ESP-ADF instance with VisualGDB, it simply clones the Espressif’s ESP-ADF repository and checks out the selected tag/branch. The v2.3 tag of ESP-ADF still references ESP-IDF v3.3.2, so that’s the version that gets installed when you use VisualGDB (or any other tool) to clone it from Github. ESP-IDF 3.x still requires the old toolchain.

If you are confident that ESP-ADF can work with the newer ESP-IDF, you can replace it manually using the git commands and use it with a newer toolchain, however this is something to do at your own risk. We generally try to provide out-of-the-box support for the SDK versions available as official releases, but if you want to try other combinations, please expect to do some research and troubleshooting, as they may need some adjustment.

If you have managed to successfully use VS code to install a different combination of ESP-IDF and ESP-ADF, please share the complete steps you followed to get this setup working (including the screenshots of each step) and we can help you configure VisualGDB to replicate the same results. Please make sure you follow our problem reporting guidelines, as we are not able to provide any help unless we have the specific steps we can analyze/follow on our side.

[support]

Hi,

VisualGDB does not manage it directly. It simply launches the open-source OpenOCD tool that handles the low-level communication with the target.

You might be able to configure OpenOCD to change the reset behavior by editing the OpenOCD script files, however this is something to do at your own risk and it may require extensive research into OpenOCD internals.

If you are looking for an easy out-of-the-box solution, please consider using Segger J-Link instead.

[support]

Hi,

This is somewhat tricky due to the way encoding is handled on the VisualGDB side. We might be able to look into supporting it during the next major VisualGDB release, however it would take more than several months.

As a workaround, we would advise creating a wrapper for the external tool that would run the original tool, and then change the encoding of the generated file to UTF-8. As it will be done automatically each time after the tool is invoked, it won’t result in any extra changes in git. From the source control point of view, it will look as if the tool was generating UTF-8 files in the first place.

[support]

Hi,

This looks like a device connectivity issue rather than something VisualGDB-specific. Our best advice would be to try using Segger J-Link. It comes with its own fully supported replacement for OpenOCD, that generally works better in many edge cases. VisualGDB supports both OpenOCD and J-Link software, so all the features you previously used will continue working the same way.

[support]

Hi,

Yes, please see the following tutorial: https://visualgdb.com/tutorials/arm/openocd/build/

[Author]

Posts