Forum Replies Created
-
Posts
-
Hi,
Good to know it works. Generally, we advise relying on VisualGDB’s logic for installing the drivers, as we test it with many popular boards. Installing drivers manually always has a chance of breaking something accidentally.
Sorry, that would qualify as a technical support question and hence we would kindly ask you to renew your licenses, if you would like us to help resolving this.
If you do not wish to renew, please have a look through our documentation and tutorials. They may contain the answers to your questions.
Hi,
Based on the logs you attached, the exception is happening inside the VC++ project engine (Microsoft.VisualStudio.Project.VisualC.VCProjectEngine).
Most likely, Visual Studio has recently installed a minor update on both computers that started triggering the error. You can try reverting to the previous VS version and check if it resolves the problem, or alternatively report this to Microsoft support and see if they can fix it on their side.
Based on our experience, the ObjectDisposedException may occur sporadically inside the VC++ project engine, but reloading the solution while deleting the .vs folder often solves it. Either way, if you find this annoying, please consider using the Advanced CMake project subsystem (or other advanced project subsystems shown here). They are not based on the VC++ project type and won’t trigger this error.
Edit: If you suspect that the VisualGDB’s license checking logic is incorrect, we can temporarily extend the expiration date on your licenses in our system, and you can recheck if it changes anything.
Based on our experience, the pre-release ESP-IDF versions, such as v4.2, are extremely unreliable and can be difficult to configure. They also change the internal structure relatively often, so we do not support them until they reach the “release candidate” stage (see this page for a list of stable releases). You can try troubleshooting it at your own risk, but if it turns out not working, please follow the instructions from the second link we posted earlier to get to the latest stable version.
Hi,
Please see the following pages:
No problem. It looks like the mbed cache on your machine could be corrupt. Please try deleting the %USERPROFILE%\.mbed folder with all contents.
If it doesn’t help, please try opening View->Other Windows->VisualGDB Diagnostics Console, and then run the wizard. The diagnostics console will show the command used by VisualGDB to clone the mbed repository. Please try running it manually in the Command Prompt window and check if it works as expected.
If it doesn’t help, please let us know the command recovered from the Diagnostics Console, as well as the result of running it manually, and we will help you get it running.
Hi,
Most likely, the program you are trying to debug is built without debugging symbols, hence gdb cannot set any breakpoints.
Although we don’t have a MinGW-specific tutorial for this, we do have a very detailed one showing how this works on Linux: https://visualgdb.com/tutorials/linux/symbols/
OK, we have added out-of-the-box support for MaixDuino to VisualGDB. Please make sure you update to v5.5 Preview 7 and then follow this tutorial: https://visualgdb.com/tutorials/arduino/maixduino/
Hi,
This looks like a generic Raspberry Pi question and not something VisualGDB-specific.
Please consider posting it on Stack Overflow or Raspberry Pi forums instead.
Hi,
This looks like either a broken Python environment, or a 3rd-party tool (e.g. antivirus) is interfering with mbed.
Please try installing the latest VisualGDB 5.5 Preview. Then please try resetting your Python environment as shown here: https://visualgdb.com/support/mbedpython/
Hi,
Most likely, this happens because the project is referencing entire source directories instead of specific files, and we have not fully tested this case yet.
Please try this build: VisualGDB-5.5.6.3661.msi. It should be able to handle the directory-level references correctly.
Good to know it works. We are usually able to answer most inquiries within 24-48 hours (depending on the backlog).
Either way, if you encounter strange errors, we always advise searching our tutorials and documentation first. They contain detailed explanations for many common issues and can get you up and running faster than waiting for a support ticket to get through the queue.
Please see the following tutorials for examples on adding extra files to ESP-IDF and Arduino projects:
- https://visualgdb.com/tutorials/esp32/esp-idf/components/
- https://visualgdb.com/tutorials/arduino/libraries/
You can also add existing files directly to the project by right-clicking on it in Solution Explorer and selecting Add->Existing Item.
We do not limit the software you purchased in any way and you are welcome to troubleshoot the problem using our documentation. It provides detailed explanations on many topics, including troubleshooting instructions for common problems.
However, if you would like us to provide more detailed instructions, that would qualify as product support and hence we would kindly ask you to renew it.
Hi,
We are more than happy to provide detailed on-demand instructions and tutorials, as long as our customers cover the costs of doing that. In fact, many of the BSPs and tutorials for exotic devices and rare setups were created as paid customization projects and the companies using them are extremely happy, since they were able to bypass time-consuming troubleshooting and learning stage, and got directly to solving the their business problems.
We are simply not able to do it for free, as we receive a huge amount of project-specific inquiries, and a few minutes per inquiry would very quickly add up to a point where would not have any resources left for developing and maintaining our products.
Our regular product license includes support for issues with VisualGDB itself, because they scale. E.g. once we fixed the incorrect $(ToolchainDir) substitution you previously reported, the problem has been solved for all VisualGDB users. Unfortunately, this doesn’t work for project-specific issues, as there are numerous different setups and frameworks supported by VisualGDB, and detailed instructions for a relatively rare case will not be relevant to most of the users.
