Forum Replies Created
-
Posts
-
Hi,
Please refer to the following page for details: https://visualgdb.com/documentation/mefcache/
Hi,
This error means that gdb requests the device to read the memory at address 0x20050004 and the device responds with an error. The address would normally be computed by OpenOCD based on the debug settings (e.g. device script) and the ELF file produced by the mbed build.
The best way to troubleshoot it would be to recheck the device datasheet whether it’s a valid memory address (e.g. part of RAM). If it is, please double-check the OpenOCD debug scripts and settings for possible settings preventing memory reads from working. If it is not, please recheck the ELF file and the debug settings for possible hints pointing to the incorrect address.
Thanks for sharing this. It indeed looks like a change in ESP-IDF structure and not something VisualGDB would handle automatically. That said, if you do not want to edit the CMakeLists files manually, you can always specify the extra environment variables via the VisualGDB GUI as shown below:
No problem, we have added a detailed documentation page explaining MEF issues: https://visualgdb.com/documentation/mefcache/.
If it doesn’t help, please share your observations (the logs mentioned on the page) and we will help you get it working.
Hi,
Sorry, it looks like something specific to your project or the gcc compiler rather than a VisualGDB-specific issue. If you would like to get generic programming help, please consider creating a question on StackOverflow instead.
Thank you for your efforts. We will be happy to investigate the issue further if any other user with a valid license and active support confirms that it affects them as well.
Hi,
This looks like the VisualGDB’s anti-tampering protection has turned on, disabling various functionality in different modules. Please make sure you use an unmodified version of VisualGDB with a valid license.
No problem. Feel free to bump this thread once ESP-IDF v5 is officially released and we will provide a timeline on fully integrating it.
Hi,
Please let us know the email address associated with your license key so that we could check your support status.
Hi,
You can try following this tutorial to setup the project manually. Also, if IAR supports the device out-of-the-box, you can the IAR compiler with VisualGDB as shown here.
We can also do the necessary research and build the BSP for you for a small fee if you prefer.
Hi,
As far as VisualGDB is concerned, debugging code in RAM is not different from debugging FLASH. VisualGDB simply instructs the underlying debug tool to set breakpoints in the code and interprets the results reported by the tool.
If you believe VisualGDB is not working correctly, please provide complete and detailed steps to reproduce the issue as described below:
- The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
- Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
- The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.
You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.
Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.
You can also try checking various diagnostic output from various parts of VisualGDB as described on this page. Although we won’t be able to review it for a specific project unless the we can reproduce the problem from scratch, checking it might provide some clues on what is causing the unexpected behavior.
Please note that VisualGDB is a productivity tool for software developers. It can make developers more productive by providing convenient GUI for common time-consuming tasks, and integrating various external tools into Visual Studio, so that they are always a few mouse clicks away.
We are able to offer VisualGDB at affordable price, because we focus on developing and supporting functionality that works the same way for multiple users, hence the development and testing effort is reused between multiple license holders.
We also receive a huge amount of inquiries asking to fix a specific broken project, help make the correct design choice, explain how a specific C++ feature works, or assist porting a library to a different platform. These inquiries require considerable effort to research and communicate the best solution. They do not scale between multiple users. I.e. helping one user solve this type of problem will not automatically help other users. It also does not help the same user avoid the same type of problem in the future. Hence, we are not able to address them within our regular support. If we included this type of help in our support, we would simply not have sufficient resources to provide it at the current license prices, or to allocate any resources to VisualGDB development.
We are happy to offer project-specific help via our consulting service per Zoom, TeamViewer or any other screen sharing service of your choice. We charge a fixed rate for these sessions (billed in 1/2-hour increments), and are happy to solve any problems our users encounter. The rate includes a detailed follow-up email at the end of the session, that includes an overview of the used techniques and a summary of solved problems and future recommendations.
Alternatively, please consider browsing our documentation and tutorials. Our documentation lists most VisualGDB settings, and the tutorials show how to use VisualGDB for in many real-world scenarios. Our technical support is limited to issues in VisualGDB itself, that can be reproduced from scratch per our problem reporting guidelines (i.e. do not depend on external projects that can potentially contain errors).
​Please note that VisualGDB is a productivity tool for software developers. It can make developers more productive by providing convenient GUI for common time-consuming tasks, and integrating various external tools into Visual Studio, so that they are always a few mouse clicks away.
We are able to offer VisualGDB at affordable price, because we focus on developing and supporting functionality that works the same way for multiple users, hence the development and testing effort is reused between multiple license holders.
We also receive a huge amount of inquiries asking to fix a specific broken project, help make the correct design choice, explain how a specific C++ feature works, or assist porting a library to a different platform. These inquiries require considerable effort to research and communicate the best solution. They do not scale between multiple users. I.e. helping one user solve this type of problem will not automatically help other users. It also does not help the same user avoid the same type of problem in the future. Hence, we are not able to address them within our regular support. If we included this type of help in our support, we would simply not have sufficient resources to provide it at the current license prices, or to allocate any resources to VisualGDB development.
We are happy to offer project-specific help via our consulting service per Zoom, TeamViewer or any other screen sharing service of your choice. We charge a fixed rate for these sessions (billed in 1/2-hour increments), and are happy to solve any problems our users encounter. The rate includes a detailed follow-up email at the end of the session, that includes an overview of the used techniques and a summary of solved problems and future recommendations.
Unfortunately, it is hard to suggest anything specific based on the description you provided, as VisualGDB supports many different project types and configurations.
In order for us to provide any help with this, we need to know the exact configuration you have.
Please provide complete and detailed steps showing how you configure your project:- The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch.
- The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages involved in creating the project.
- Please describe the exact behavior you would like to achieve (e.g. some items appear in Solution Explorer in certain order) based on the previously provided steps, so that we can point out the relevant settings.
You can read more about the best way to report VisualGDB issues in our problem reporting guidelines.
It also looks like your support period has expired, so we would kindly ask you to renew it here: https://sysprogs.com/splm/mykey
