Forum Replies Created
-
AuthorPosts
-
support
KeymasterGood to know it works. Most likely, the files are downloaded because the paths reported by gdb don’t match the paths expected by VisualGDB. This would happen if the target had symbolic links in some directories.
You can troubleshoot it by checking the GDB Session window for the path reported by GDB and then setting a mapping via VisualGDB Project Properties -> Path Mapping.
support
KeymasterThanks for checking this. Most likely, the problem happens because VisualGDB fails to create a temporary terminal (pseudo-tty) to avoid mixing the output from the program with the output from gdb.
The easiest way to work around it would be to use gdbserver on the target (you can configure it by selecting the “gdb stub” mode in the VisualGDB Project Properties -> Debug Settings). This will eliminate the need to create a virtual terminal and should work around the problem.
support
KeymasterHi,
Strange. Just to double-check, are you able to run the program under gdb manually? I.e.:
gdb /mnt/TrollSystems/_Applications/ConTroll21_S6K2/ConTroll21_S6K2_Lin.exe b main run
If yes, does it change if you run it as “gdb –interpreter mi <path”> instead of just “gdb <path”> and use the “-exec-run” command instead of “run”?
support
KeymasterHi,
Please refer to the following page for detailed overview of VisualGDB’s IntelliSense engines and instructions for switching them: https://visualgdb.com/documentation/intellisense/
support
KeymasterSorry, this looks like something specific to the particular mbed project/board and not to VisualGDB, and hence is not under our control. Please consider the following resources for help on issues that are not specific to VisualGDB:
- Mbed forums to discuss issues specific to mbed
- StackOverflow for generic programming questions
Also if you can confirm that the problem does not happen when using a command-line debugger (e.g. gdb), but happens with VisualGDB, we can help you understand the differences and configure VisualGDB to match the command line gdb behavior.
support
KeymasterThanks for confirming your license status. We have linked your forum account to the new key.
We have also updated the VisualGDBExtensibilityExamples repository to reference the correct assembly out-of-the-box.
-
This reply was modified 5 years, 4 months ago by
support.
support
KeymasterHi,
Please try deleting the %LOCALAPPDATA%\VisualGDB\Python* folders, updating to VisualGDB 5.5 Preview 4 and then install Python 3.x via the VisualGDB Project Wizard. This will get the correct version of Python with pre-installed mbed scripts.
support
KeymasterNo problem, please try this build: VisualGDB-5.5.4.3567.msi It will remember the imported toolchain correctly.
The toolchain test failure is by design, as VisualGDB tries to run the program produced by the toolchain locally. For cross-toolchains, please select “Build under Linux over network”, pick the LXSS distro there and set the deployment target, so that VisualGDB can verify that it can run the result of a test build. Or simply ignore the error and proceed with the current setup, since it shouldn’t interfere with anything else.
support
KeymasterHi,
Looks like the second project is based on GNU Make and hence does not support property sheets. You can find a detailed overview of various project types here: https://visualgdb.com/documentation/projects/overview/
Normally, you can convert Make-based projects to MSBuild via the context menu in Solution Explorer, however this process is not 100% precise and may require manual troubleshooting afterwards.
support
KeymasterSorry, we are not able to review custom projects or board schematics as a part of our product support. If you would like to have your project reviewed via our paid consulting service, please contact our sales to get a quote.
support
KeymasterNo problem, we have updated the ESP32-WROOM tutorial, pointing to the Advanced ESP-IDF tutorial.
If you cannot get the wiring to work, please consider using a board that includes a ready-to-use JTAG programmer, e.g. ESP32-WROVER.
support
KeymasterHi,
Please make sure you use the Advanced ESP-IDF Project Wizard instead of the regular Embedded wizard: https://visualgdb.com/tutorials/esp32/esp-idf/
support
KeymasterJust wanted to share an updated that we have published detailed documentation on MSBuild property sheets with VisualGDB projects here: https://visualgdb.com/documentation/projects/msbuild/propertysheets/
April 2, 2020 at 15:22 in reply to: Stack memory overlap with file level variable memory region #27816support
KeymasterHi,
Unfortunately, it looks like your support period has expired a while ago. Please renew it here and we will be happy to help you.
support
KeymasterUnfortunately, both are way too specific, will be relevant to a very small fraction of our users, and would require non-trivial changes to fully support.
That said, we can always support it via our paid customization/consulting service. Feel free to reach out to our sales to get a quote.
-
AuthorPosts