[support]

Hi,

Yes, please try using the older toolchain based on the Raspbian Stretch distribution (you would also need the older SD card image). It is compatible with QMake and will work out-of-the-box.

Unfortunately, we are not able to provide guidance on porting a 3rd-party framework to an unsupported 3rd-party platform as a part of our regular product support, however we might be able to create a port for you as a part of our paid consulting services. Please feel free to reach out to our sales if you would like a quote.

[support]

Thanks for clarifying this. Normally, VisualGDB should automatically detect the /usr/include/c++/8 directory after querying your toolchain, so you wouldn’t need to specify this directory manually. If you ever find the manual setup too annoying, feel free to get back to us and we will help you get the fully automatic setup to work correctly.

[support]

Hi,

Please make sure you use the VisualGDB 5.5 Preview 1, not v5.4.

Also you need to install the IAR compiler separately, and make sure you have a valid license for it (see this tutorial). We are not affiliated with IAR Systems, so VisualGDB can integrate with an existing IAR installation, but cannot redistribute it independently.

[support]

Hi,

Sorry, the latest Raspberry Pi toolchain is not compatible with QMake anymore. Please try using VisualGDB 5.5 Preview 1 and create a CMake-based Qt project as shown here: https://visualgdb.com/tutorials/linux/qt/cmake/. This should work out-of-the-box.

[support]

Hi,

You might be able to build one yourself, however in our experience, building Linux cross-toolchains almost always involves troubleshooting weird problems specific to a particular combination of target settings. You are welcome to try it, however we won’t be able to offer any support for this outside of our paid toolchain building service.

[support]

Hi,

This should be possible as long as you have a cross-toolchain specifically built for your target (with matching ABI, CPU/FPU settings and system library versions). If the board vendor provides such a toolchain, you can import it into VisualGDB as shown in his tutorial: https://visualgdb.com/tutorials/linux/edison/

If there is no ready-to-use toolchain, we can build one for you. Please contact our sales with details about your board and target OS version to get a quote.

[support]

Hi,

Sorry, the Keil component view requires the Custom edition or higher. If you are using a lower edition, you can always upgrade here: https://sysprogs.com/splm/mykey

[support]

Hi,

Good to know it works.

Not sure what you meant by mapping all #includes. Normally, this could happen automatically. If you believe it doesn’t, feel free to describe the repro steps starting from creating a project and we will investigate this further.

[support]

Hi,

Sorry, our AVR debugging support is based on an open-source tool called AVaRICE, that has somewhat limited support for debug probes. As the AVR devices use undocumented proprietary debugging protocols and are generally much less popular than ARM-based devices, the debugging experience is indeed much less straight-forward.

Our best advice would be to check the AVaRICE forums/mailing lists regarding support for new debugging probes.

[support]

Hi,

No problem. We have reproduced and fixed the problem. Please try this build: VisualGDB-5.5.2.3395.msi

[support]

Thanks for the repro steps. We have reproduced the problem, however it looks like it’s limited to showing incorrect value in the status bar. Indeed, canceling an Arduino package installation will immediately stop the download, but the Visual Studio’s status bar will only get updated when another component uses it to display the progress.

Due to the relatively low impact of the issue, we will fix it during the next update of the progress-related logic.

[support]

Thanks for the link. We have reproduced the problem. Indeed, when using Internet Explorer (not Edge) to download the temporary builds that don’t go through our CDN system, the extension changes to .man. it should be indeed trivial to fix it, however due to relatively low impact, we will delay it until the upcoming upgrade of our server framework, so that we could fully test it as a part of the post-upgrade tests. If this becomes more annoying, feel free to ping us and we will consider raising the priority for this.

[support]

The chronometer does show the time since the last event, even if it was of another type. You can double-check it by setting 2 breakpoints inside the LEDBlink loop. If it doesn’t work as expected, please share the repro steps along with the relevant screenshots per our problem reporting guidelines and we will investigate it.

You can also switch the chronometer to show the absolute timestamps (i.e. from the beginning of the session) to minimize confusion.

P.S. If the absolute timestamps don’t make sense, some code inside your project might be resetting the ARM cycle counter that is used by the chronometer. E.g. VisualGDB’s profiler does that to avoid overflows.

[support]

No worries and thanks for posting the full screenshot. It made it much easier for us to find and point out the cause.

[support]

Hi,

Just wanted to share an update that we have added support for embedded code coverage (including Live Coverage) to the following build: VisualGDB-5.5.2.3390.msi

You can enable it via VisualGDB Project Properties -> Code Coverage.

For most accurate results, please consider upgrading to the latest GCC 9.2.1-based ARM toolchain (that is a repackaged version of the official GNUARM toolchain).

[Author]

Posts