[support]

Hi,

Good to know it works. If you encounter any further problems, please do not hesitate to contact us again.

[support]

Hi,

The new advanced ESP-IDF project subsystem was added to VisualGDB 5.4 Preview. Most likely you have installed v5.3 that doesn’t have this feature yet (and won’t install the latest toolchain). Please ensure you install the v5.4 preview version. Also if the old toolchain cannot be removed from VisualGDB, please try closing all Visual Studio instances and simply deleting the toolchain directory from Windows Explorer.

[support]

Hi,

According to our records, your inquiry was answered on 06/20/2018 8:18 pm in less than 8 hours from the time we received it.

Please double-check your spam folder and let us know if you would like us to resend the reply.

[support]

Hi,

This might be caused by changes to some mbed components. Please try opening VisualGDB Project Properties on the first page and then either change the MCU forth and back, or click “Regenerate MCU-specific files”. This should automatically update all project properties and remove any deprecated settings.

[support]

Hi,

 

The sample projects like “LwIP_HTTP_Server_Netconn_RTOS” come from the ST examples, so if the original example is written in C, VisualGDB will not automatically change it to C++, as simply renaming files may introduce build errors.

There are quite a few things to watch for when converting Plain C code to C++ (the most notorious one is extern “C”), however as this is a generic C/C++ development question and is not specific to VisualGDB, we cannot provide step-by-step instructions for converting each sample. That said, such a conversion is a very commonly performed task, so searching resources like StackOverflow for the errors you encounter will most likely give you detailed answers from other users that performed a similar conversion.

[support]

Hi,

No problem, please find the answers below:

1. If you are not using the Custom edition, you can only have 1 version of the SDK installed at once. It doesn’t have to be the latest version from our servers, but it has to be the same version for all the projects. If you want to use multiple versions without upgrading to the Custom edition, you can simply rename the BSP folder and edit the ID in the BSP.XML file – VisualGDB will then treat it as a separate BSP. You can then switch projects between different versions of the SDK by editing the BSP ID in the nrf5x.xml file.
2. The “shared files location” points to a directory of the VisualGDB-supplied BSP package. It is generated from the original SDK and includes fixes necessary for the project to build out-of-the-box (e.g. patches to linker scripts that allow including the softdevice into the main project binary). You can download BSP packages generated from older SDKs here and install them via VisualGDB Package Manager, however using the raw SDK itself won’t work as it will not include the necessary patches. Our tool for generating the packages from the original SDK is open-source through, so you can experiment with it if you want to support some specific version of the SDK (note that SDK 15.0 support is currently in development and is close to being released).
3. The Embedded Frameworks is a convenient way to add sources and include directories from various nRF5x components to the project. It doesn’t edit the configuration file and only affects the list of source files, include directories and sometimes preprocessor macros. You can find out what exactly each framework does by locating the <EmbeddedFramework> element in BSP.XML, however for Nordic devices the frameworks are just convenience wrappers around the corresponding directories in the SDK.

[support]

Hi,

We are not aware of this issue, so it might be caused by some project-specific configuration (e.g. mismatch between the project and the ESP-IDF version). Normally the ESP-IDF configuration entries are handled by the ESP-IDF itself, so VisualGDB should not change the related logic.

Does the issue happen for any newly created project, some newly created projects, or a specific project you are trying to import? If it is limited to a specific project, does the error also happen when building it from command line?

[support]

Hi,

This is already supported (using the same semantics as PuTTY) – any text selected in the console is automatically copied to the Clipboard and you can paste text via Shift+Insert or via middle mouse button click.

[support]

Hi,

Yes, we have added a new command-line option to VisualGDB to export test results in the VSTest format to this build. Please use the following command line:

VisualGDB.exe /runtests <settings file> /vsoutput:<file.trx>

Then publish it using the regular “Publish Test Results” task (ensure you select the VSTest format). Let us know if you have any feedback/suggestions.

[support]

Hi,

Good to know it works with the older OpenOCD version.

Based on the debug output you provided, it looks like the issue is somewhere between the libusb library and your USB controller driver. Unfortunately this appears to be specific to either your USB controller, or some additional software installed on your machine, so it’s hard for us to narrow this down. That said, we regularly release new OpenOCD packages based on the latest sources, so if this issue gets fixed by the OpenOCD/libusb maintainers, our builds will automatically pick up the fix.

If you would like to use the latest OpenOCD, our best advice would be to try checking if you have any USB-related software installed (e.g. USB-over-network) and try uninstalling it. You could try running this setup on a different machine to confirm that it’s specific to the USB driver and not to that specific ST-Link instance.

[support]

Hi,

It looks like the command-line mode might be leaving ST-Link in a state where it doesn’t respond to regular commands. A short-term workaround would be to simply plug it out and back in.

Long-term, please let us know how to reproduce it. Are you simply using VisualGDB.exe /runtests, or some other way to run the tests?

[support]

Hi,

One of the ways to migrate the code would be to create a new project and then add existing sources (either one-by-one, or via Add->Import Directory Recursive command provided by the Custom edition).

Another option would be to select “Import Existing Project” in the VisualGDB Project Wizard. It will let you pick a folder with your source files and will add them to the created project.

[support]

Hi,

The TinyEmbeddedTest framework is intended to be used with the barebone devices that don’t have a concept of command line (unless you are using semihosting anyway), so it doesn’t support any command-line switches. Instead you can use the Visual Studio GUI to select which of the tests to run.

If you are running tests via the VisualGDB.exe /runtests command line, we could add an option to run specific tests only there as well.

[support]

Hi,

We could easily add a registry setting that would override the temporary directory for downloaded files. Would that work for you?

[support]

Hi,

Normally VisualGDB should display a manual activation window if there is no Internet connection. If you don’t have Visual Studio installed on the build machine, please try running VisualGDB.exe /about to open the “About VisualGDB” window and enter the license key there.

[Author]

Posts