[support]

Hi,

VisualGDB supports Segger J-Link and any programming interface supported by OpenOCD (that includes FT2232-based devices such as Olimex ARM-USB-OCD-H and almost every other popular debug probe). The only exceptions are U-Link (as it’s based on proprietary protocols not supported by OpenOCD) and generic CMSIS-DAP (it’s technically supported, although is very slow due to the USB HID poll rate limitations).

You can read more about the supported devices and debug interfaces here: http://visualgdb.com/hwsupport/

[support]

Strange, now it looks like the {upload.verbose} got expanded to an empty string. Please try removing the “{upload.verbose}” part completely from the programming command line (also remove the quotes).

[support]

The easiest way to achieve that would be to embed the simulated data into your program as an embedded resource and then reference the Fast Semihosting framework via VisualGDB Project Properties -> Embedded Frameworks and output the results via the regular printf() calls. The output will be shown in the Semihosting Output window inside Visual Studio and can be saved to a file at the end of the debug session (see VisualGDB Project Properties -> Embedded Debug Tweaking).

[support]

The platform.txt file appears correct, so most likely your project is still using the old cached command line.

Please ensure you don’t have any other versions of the ESP8266 package installed and try reproducing the problem on a new project created from scratch. If the new project works, please try reloading the existing project as we suggested earlier in order to reset its cached values.

[support]

Hi,

We usually add out-of-the-box support for new platforms once they get enough traction. Currently we are still assessing the popularity of the new nRF Connect platform and will be deciding whether to support it directly in the next 4-6 months. As a workaround, please try creating a project manually as shown in this tutorial.

Alternatively, we can support nRF Connect earlier via our paid custom BSP program. Please feel free to contact our sales to get a quote for this.

[support]

Hi,

You can add the library to your project by adding its source files to the Solution Explorer (via Add->Existing item) and then adding the paths of the header files to the Include Directories field of the VisualGDB Project Properties (or just trying to include one of the header files from your sources and then following VisualGDB’s prompts to add the necessary header directories).

[support]

Thanks for the update. Looks like VisualGDB tries to load it as a VisualGDB-specific XML file instead of using the SVD loading logic.

Please try changing the file extension to .svd and importing it again.

[support]

We have investigated the problem and it looks like a bug in the ESP8266 Arduino package triggered by the verbose mode enabled by VisualGDB.

We have created a Github issue in the ESP8266 Arduino repository suggesting a workaround. Please try patching the <HOME>\Documents\ArduinoData\packages\esp8266\hardware\esp8266\2.5.2\platform.txt file as described on the Github page, then reload the project via the context menu to ensure VisualGDB picks up the updated programming command line template.

[support]

Thanks for letting us know, however unfortunately it’s hard to suggest anything specific without knowing more details. If you could describe exactly how you were importing them and what you observed (and ideally, share the entire file you tried importing), we should be able to suggest a workaround or release a hotfix for it.

[support]

Hi,

You can find the firmware package versions used by VisualGDB in %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32\SDKVersions.xml

[support]

Hi,

It looks like the latest ESP8266 Arduino package might be broken. Could you please quickly recheck whether it works with Arduino Studio? If not, please consider filing a bug report with Espressif.

[support]

Hi,

This looks like a regular SVD file that should be already supported by VisualGDB. Simply select it when clicking on the “Locate SVD file” link in the Hardware Registers window and VisualGDB will automatically convert it to its format.

Alternatively, you can use the converter from our BSPTools repository that is equivalent to the converter used by VisualGDB.

[support]

Hi,

Good to know it works.

Regarding the major version, yes, we are currently finishing our work on supporting more device families and will start releasing preview builds on the next major version introducing new functionality in the next 1-2 months.

[support]

Hi,

Yes, VisualGDB fully supports this layout. If you are planning to continue having the Windows builds, we recommend using the Project->Add Linux Configuration command to add a VisualGDB configuration to all of the projects (if you have multiple project files, we would advise comparing the .vcxproj file before and after and scripting the necessary changes).

If you are no longer interested in maintaining the Windows builds, we would advise creating an Advanced CMake project. It fully supports multiple targets as well has an advantage of sharing common project properties (e.g. build machine, custom steps) between all targets built within the project.

If you have any further questions, please don’t hesitate to get back to us and we will be happy to provide more details.

[support]

Hi,

This looks similar to a problem that was recently fixed on our side (invalid layout computation for one of the tool windows). Please try this build: VisualGDB-5.4.112.3248.msi

If it doesn’t help, please try evaluating “$exception” in the outer VS instance and navigate to the InnerException field of it. Then check its call stack and let us know (together with the build number it was obtained from) and we should be able to fix it.

[Author]

Posts