Forum Replies Created
-
Posts
-
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.
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
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.
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.
Hi,
No problem. We have reproduced and fixed the problem. Please try this build: VisualGDB-5.5.2.3395.msi
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.
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.
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.
No worries and thanks for posting the full screenshot. It made it much easier for us to find and point out the cause.
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).
Hi,
Looks like you are viewing the installed packages. Please try switching to the “online” view instead.
Sorry, unfortunately we are not able to provide project-specific help as a part of our regular product support. The only advice we can give is to make sure you follow and understand each step of the tutorial mentioned in the previous post. It does explain the “undefined reference” problem and the techniques used to troubleshoot it.
Please follow the tutorial below for measuring the time between events on embedded devices: https://visualgdb.com/tutorials/arm/chronometer/
Hi,
The Cortex-A devices are typically used together with Linux and hence require a special Linux toolchain built for the exact distribution/configuration that is running on the target.
We provide toolchains for the most commonly used Cortex-A boards (e.g. Raspberry Pi, Beaglebone). If you are using a different board, please check the board vendor for a cross-toolchain.
If you are looking for a barebone environment (without Linux), please try creating a project manually as shown in this tutorial: https://visualgdb.com/tutorials/arm/legacy/
Yes, please try deleting all the toolchains and installing the one from https://gnutoolchains.com/esp32/.
Then check if you can create, build and debug a new project from scratch. If it doesn’t work please share the details and we will help.
If a new project works, but the existing one doesn’t, you may need to port your project to the new ESP-IDF (the ESP-IDF releases are not 100% backward-compatible). If you are getting errors specific to ESP-IDF API, please consider asking on the ESP32 forum.
