Forum Replies Created
-
Posts
-
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.
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.
Please see the following page for a detailed overview of various settings for MSBuild projects: https://visualgdb.com/documentation/projects/msbuild/
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.
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.
Hi,
Please let us know the email associated with your license key so that we could check your support status.
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.
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.
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.
Looks like you are trying to import an Android Studio project without any native files. Please double-check that you have created the C/C++ sources with Android Studio, and that the original project builds and works before you try importing it into VisualGDB.
Thanks for sharing this. We have moved this post to a separate thread to make it easier for others to discover it.
The protect and mbatch commands come from the regular RISC-V debug logic and can be safely ignored for Kendryte devices.
BTW, thanks for sharing the solution you discovered with the JTAG pins. We have moved it to a separate thread to make it easier for other users to find it.
Please let us know the email associated with your license key so that we could check your support status. If you are using a trial, please update your forum profile to use your company email.
Hi,
This looks like a RaspberryPi issue and not something specific to VisualGDB. Please consider asking on the Raspberry Pi forums instead.
If the library you are using requires a different environment variable, please let us know more details and we will help you configure VisualGDB to set it.
Hi,
Looks like you are trying to use the GDB simulator that does not support your device. Generally, the built-in simulator is not usable for ARM targets and can only be used to verify that gdb is able to load the debugging symbols.
Please consider using one of the supported debug methods instead.
