[support]

Hi,

This could be caused by several different issues. Please check if the project can be built successfully. If not, please try creating a new project via VisualGDB Project Wizard and it will automatically get all the dependencies. If the build succeeds, but IntelliSense doesn’t work, please attach a screenshot of the entire Visual Studio window here and we can check for common problems.

[support]

Hi,

Thanks, looks like VisualGDB was handling a certain type of hard links in tar archives incorrectly. We have fixed it in the following build: http://sysprogs.com/files/tmp/VisualGDB-5.3.18.1978.msi

Please note that you would need to reload the IntelliSense directories via VisualGDB Project Properties.

 

[support]

Hi,

Different Linux distros may have slightly different include directory layouts, so please double-check that the files actually exist in the same directory on the other machine (please also double-check that you are looking at a correct folder on the Windows side – the dir.txt file should contain the remote directory name).

If you can confirm this, please try reloading all include directories via VisualGDB Project Properties. If this doesn’t resolve the problem either, please check that you can access the header files from your current user account (incorrectly set permissions would prevent VisualGDB from synchronizing those files properly).

[support]

Hi,

No problem, thanks for renewing. If you encounter any further problems, feel free to contact us again.

[support]

Hi,

No problem, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.18.1977.msi

[support]

Hi,

No problem, we have added this as an experimental feature to the following build: http://sysprogs.com/files/tmp/VisualGDB-5.3.18.1977.msi

To enable it, please create a file called <name of .vgdbsettings file>.vgdbsettings.<user name>.user with the following contents:

<?xml version="1.0"?>
<VisualGDBUserPreferences xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <UserDefinedVariableValues />
  <DebugPreferences xsi:type="com.visualgdb.debug.embedded.preferences">
    <OverriddenSettings>
        <DebugMethod>
            <!-- Contents of the DebugMethod tag from the .vgdbsettings file -->
        </DebugMethod>
    </OverriddenSettings>
  </DebugPreferences>
</VisualGDBUserPreferences>

If you are not sure about the name of the file, try adding a live variable or a visual watch to your project and VisualGDB will automatically create the .user file.

The <DebugMethod> value from the .user file will now override the settings from the .vgdbsettings file (although the GUI may not edit the settings properly).

[support]

Hi,

You can set this via Tools->Options->VisualGDB->General->Files->Max. items per Makefile line.

[support]

Hi,

Please refer to our bootloader tutorial for a detailed example.

[support]

Hi,

Thanks for reaching out to us, however unfortunately it’s hard to say what is going on based on this screenshot. Please try enabling gdb logging as described here and then check the log for any irregularities. If you are not sure, please submit the log here and we can try to help you diagnose this.

[support]

Hi,

VisualGDB is licensed per seat (computer/user combination). As a special exception we allow installing personal VisualGDB licenses on one extra seat, however this is normally reserved for cases like reinstalling OS, switching computers, etc. You may use this extra seat to install VisualGDB on a second computer, however this would result in some downtime if you would need to reinstall your OS or replace your hard disk.

[support]

Hi,

Sorry, this is not supported directly yet, however we could add a quick workaround that will let you override the debug settings in the .vgdbsettings file (shared between multiple users) by manually editing the .vgdbsettings.user files. We may also support this properly in the next major release, although we cannot promise this definitively yet.

Would you like to try the manual editing workaround?

[support]

Hi,

On ESP32 the printf() output is forwarded to the serial port. Please setup the device terminal as shown in this tutorial (Custom edition or higher) or use an external terminal program (e.g. SmarTTY).

[support]

Hi,

It looks like your technical support has expired. In order to keep on receiving support please renew your license.

[support]

Hi,

This could happen if the $(IntDir) variable did not have a trailing backslash. Please double-check that your settings include it. If this doesn’t help, please try attaching a minimal repro project and we will investigate it.

[support]

Hi,

Yes, we try to update most of the popular BSPs quarterly and mbed is definitely a popular one. If you would like to share some enhancements you made to it for your own use, we will gladly accept them. Simply send us a pull request via Github.

Normally if you start debugging a project that doesn’t include any register definitions, the hardware register window will display instructions on importing the SVD file. You can also use the following code from our Github repo to convert an SVD file to the VisualGDB format directly: https://github.com/sysprogs/BSPTools/blob/master/libraries/BSPGenerationTools/SVDParser.cs

With the CLOCK_SOURCE macro, please don’t use any special escaping in VisualGDB GUI, e.g.:

VisualGDB will automatically insert the apostrophes when updating the .mak file:

PREPROCESSOR_MACROS := <...> 'CLOCK_SOURCE=USE_PLL_HSE_EXTC|USE_PLL_HSI'

Attachments:

You must be logged in to view attached files.

[Author]

Posts