Forum Replies Created
-
Posts
-
The latest changes to gcc/gdb mostly do not affect the barebone environments, hence we are not updating our default ARM toolchain regularly. If you are looking for a newer GCC/GDB combination, please try installing the official ARM toolchain. VisualGDB should recognize it out-of-the-box as a drop-in replacement for our default toolchain. The path issue reported by @Kenzi affects all gcc versions, so there should be no difference.
Thanks for the update. It looks like the project is indeed using MSBuild, so the command line length should normally not matter.
Please try reinstalling the ARM toolchain from scratch. If it doesn’t help, please try running the following command from the project directory:
arm-eabi-gcc.exe -v @VisualGDB\Debug\<one of the .gcc.rsp files>
Then, please share the verbose log produced by gcc.
Thanks for the screenshot. It does indeed look like an MSBuild-based project, so the command line length limitation should not trigger here.
That said, MSBuild projects will normally not echo the compiler command line to the build log, so the project might be still somehow configured to use GNU Make.
Could you please share the entire build log (here or via our support form) so that we could check what is going on?
Hi,
Yes, please try using MSBuild instead of GNU Make. Our MSBuild backend automatically uses response files to bypass the command line limitation.
Hi,
VisualGDB 5.1 is very old and is no longer maintained. Please consider updating to v5.4R5. It uses the “.hex” extension by default and also allows overriding it via the IntelHexFileExtension property in the .vcxproj file.
Thanks for sharing this. From our experience, the Espressif team often breaks features in new releases, but then they fix them relatively fast once reported, so it could be worthwhile to leave an inquiry on their forum, or create a bug on Github. But if the slower GNU Make subsystem works for you, that could also be an option.
We are usually indeed able to add workarounds for issues knowing the exact repro steps, however according to our records, the @roguebear’s trial has expired, so we will not be able to offer them any technical support unless they actually purchase a license, sorry.
The sample projects for each device family generally come from the SDKs provided by the device vendor and their amount depends on the popularity of the specific device family. E.g. the STM32 SDKs come with numerous examples and frameworks and are very popular, so VisualGDB offers many examples in the project wizard and encapsulates many frameworks from the SDKs. The Tiva SDK is much simpler and the devices are less popular than STM32, hence the examples offered by VisualGDB are simpler.
The easiest way to get FreeRTOS on Tiva devices would be to download the Tiva C SDK (please use the same version as the VisualGDB’s BSP) and manually add the files from third_party\FreeRTOS\Source to the project (you would need to ensure that only one port instance and one heap instance is selected).
Hi,
The partition table is fully handled by the ESP-IDF itself. VisualGDB simply lets ESP-IDF process it, queries the resulting project structure and renders it in the Solution Explorer, hence it does not control the exact location of the CSV file, or the logic related to it.
Our best advice for locating the partition table file would be to try cloning a sample project with a custom partition table (if ESP-IDF includes one) and checking the build log for partition table-related messages. If nothing helps, please consider checking at the Espressif’s forum – you might be able to get some insights from the team that designed the ESP-IDF there.
Sorry, although we are constantly working on improving the VisualGDB’s capabilities and compatibility with various tools, we are not able to guarantee that every 3rd-party project created with an arbitrary version of the 3rd-party tool will always get 100% imported completely out-of-the-box. VisualGDB does its best at importing the common settings, such as preprocessor macros and include directories, however if you have overridden advanced Keil-specific options, you would need to adjust the imported project manually in order to reflect that. We have indeed published a detailed tutorial explaining this process step-by-step.
According to our records, it looks like your trial period has expired. In order to get further technical support, please consider purchasing a license.
Please note that installing VisualGDB on another PC, editing registry to affect the trial counter, or creating further forum accounts does not reset your trial period from the support point of view.
As providing quality technical support for our users requires continuous effort on our side, we do expect our users to play fair and are not able to offer any help once the original trial period expires.
Hi,
Please double-check that you are not trying to include STL headers from .h files that are included from plain C files.
If it doesn’t help, please follow the steps on this page to narrow it down to a specific step triggering the problem and we will try to help you. That said, it might be a limitation of the ESP32 toolchain, so it could be worthwhile to check with Espressif whether it’s a known problem.
Good to know it works. If the problem reappears, feel free to reopen the thread and we will investigate.
According to our records, it looks like your trial period has expired. In order to get further technical support, please consider purchasing a license.
Please note that installing VisualGDB on another PC, editing registry to affect the trial counter, or creating further forum accounts does not reset your trial period from the support point of view.
As providing quality technical support for our users requires continuous effort on our side, we do expect our users to play fair and are not able to offer any help once the original trial period expires.
Good to know it works.
The mbed package system has actually been replaced with the new Advanced Mbed Project Subsystem that works with the latest mbed releases out-of-the-box, supports online libraries and advanced configuration options. You can find a detailed description in this tutorial: https://visualgdb.com/tutorials/arm/mbed/mbed-cli/.
You can also greatly reduce the initial setup time by using shared mbed checkouts. Simply select it on the first page of the wizard and VisualGDB will reuse an existing mbed checkout instead of downloading it from scratch.
Once the initial compilation is done, the subsequent builds of the project should be much faster, as mbed will only rebuild the changed files.
