[support]

Thanks for renewing your license. Regarding the frequency, most likely the program triggers several breakpoints before the USB requests get properly handled.

Please try removing all the breakpoints and make sure the device responds to the USB requests. If it still doesn’t work, please try programming the FLASH memory without debugging, restart the device, make sure it is recognized, and then try attaching to it as shown here: https://visualgdb.com/tutorials/arm/attach/

If attaching a debugger breaks further USB functionality, please try connecting to the device using the native debugger tool (e.g. ST-Link tool or J-Link Commander) instead. If this also breaks the USB functionality, most likely the board has insufficient power, or has some wiring issues.

[support]

No problem, we do not mind sharing the instructions. We simply prioritize requests for documentation based on the amount of affected users (we have recently published a lot of new documentation on common topics). As you have seconded the topic, we are happy to provide more details.

Once you import an Atmel START SDK into VisualGDB, it creates a BSP.XML file in the SDK directory that contains the information extracted from the SDK. Then, the BSP is registered with VisualGDB by creating a %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\arm-eabi\<id>.bsplink file pointing to the SDK directory.

The easiest way to support multiple imported SDKs would be to manually edit the BSP.XML file, changing the following elements:

• BoardSupportPackage/PackageID – change to unique names in order to avoid collision between multiple versions
• BoardSupportPackage/PackageDescription – set to any arbitrary string to help you distinguish the packages
• BoardSupportPackage/SupportedMCUs/MCU/UserFriendlyName – add an arbitrary suffix, such as ” (Basic)” or ” (Full)”. The suffix will be shown in VisualGDB GUI when selecting the device in the device list and won’t affect anything else.

Once you have changed the file, reopen the Tools->VisualGDB->Manage VisualGDB Packages window to trigger a reload of all packages. After that, you will be able to import another Atmel START SDK from another directory, and VisualGDB will keep both instances, since they will have different package IDs.

[support]

If the build always works, but the clean always fails, most likely some clean-specific setting (e.g. a custom post-clean step or a custom clean command) refers to an invalid hostname.

If you are not sure what causes it and cannot easily revert to a previous version of the project that worked successfully, please consider doing a side-by-side comparison of the broken project against a similar working project. I.e. compare the .vcxproj and .vgdbsettings files and try merging them until you can pinpoint a specific setting that triggers it.

[support]

Hi,

This looks like a network error:

The specified network name is no longer available.

Please double-check your DNS configuration or try using IP address instead of a host name for the target.

[support]

Sorry, MSBuild projects share the same project structure (i.e. the set of source files) across all platforms and configurations, hence global settings like the test framework/BSP affect all configurations.

You can work around it by defining per-configuration preprocessor macros and #ifdef-ing out the code that calls test framework functionality, but the test sources will be still present in Solution Explorer.

[support]

Hi,

No problem, please see our answers below:

1. There is no special GUI for custom mbed targets yet. As a workaround, please consider following the regular mbed instructions to create a custom target, and then patch the .vgdbproj file manually to specify the new target name. We are working on supporting custom targets properly and will release an update including this feature next week.
2. Please make sure you use the Custom edition of VisualGDB and create a separate testing configuration per our tutorial. If it doesn’t work, please share the screenshots of the steps you perform and the output you observe, and we will help you troubleshoot this.
3. VisualGDB manages the mbed profiles automatically. It will pick the debug/release profile based on the active configuration in Solution Explorer, and can additionally apply any changes made via the regular VS property pages of the project node (e.g. optimization level) by generating a temporary profile file.

[support]

Hi,

We usually remove the packages that have been superseded by bugfix updates. As long as the compiler and ESP-IDF version are the same, we remove the older versions to save space.

If you are looking for a specific older version of the ESP-IDF framework, please consider manually pulling it from git, replacing the version that is shipped with the toolchain.

[support]

No problem. We have added it to the backlog. As we are prioritizing several other issues over it, it may take a few weeks for us to fully investigate this and provide a workaround. We will post an update here once the issue is resolved.

[support]

Please see the following page for a detailed overview of various settings for MSBuild projects: https://visualgdb.com/documentation/projects/msbuild/

[support]

Hi,

Visual Studio has a similar concept. Solutions (.sln files) can include multiple projects (.vcxproj files), one for every target.

You can also consider using the new Embedded CMake Project Subsystem (requires VisualGDB 5.5 RC1) that supports multiple targets within the same project, so you won’t need to setup the toolchain/debugging settings multiple times.

[support]

Sorry, we could not find any licenses associated with your company domain name.

If you know your previous license key, please forward it to our support and we will link it to your forum profile.

Edit: thanks for sending us your key information. We have linked it to your profile. Please use this link to renew your support and we will help you troubleshoot this.

• This reply was modified 5 years, 4 months ago by support.

[support]

Hi,

Please let us know the email associated with your license key so that we could check your support status.

[support]

Based on what we could tell from the Particle site, their main focus is on the cloud platform. I.e. providing higher-level APIs for centrally managing and communicating to the IoT devices. The on-device debugging (the only part where VisualGDB would come into play) isn’t used very often.

Also the Particle SDK is relatively complex, so properly supporting it by VisualGDB, similar to the nRFConnect SDK would only make sense if it had a much larger use base.

Our best advice currently would be to import the project into VisualGDB as an external Make-based project. You will still be able to build and debug it, although the Makefile contents won’t be automatically reflected in Solution Explorer the way it’s done for nRFConnect.

[support]

Hi,

This is supported starting from the new VisualGDB 5.5 RC1 using the Embedded CMake Project Subsystem. You can now define arbitrary platforms/configurations with arbitrary CMake variables and use the if() syntax in CMakeLists.txt to conditionally enable/disable various features. You can also have multiple targets per project (e.g. one unit test target and one regular application, both referencing a common library).

We will be publishing a few tutorials on the new Embedded CMake Project subsystem soon, explaining the new layout in details.

[support]

No problem, we can point out a setting that will allow replicating this behavior, however we would kindly ask you to confirm your support status first.

Please let us know the email associated with your license key so that we could link it to your profile. If you are using a trial, please update your forum profile to use your company email.

[Author]

Posts