Forum Replies Created
-
Posts
-
No 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.
Hi,
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.
Sorry, 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.
No 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.
Hi,
Please make sure you use the Advanced ESP-IDF Project Wizard instead of the regular Embedded wizard: https://visualgdb.com/tutorials/esp32/esp-idf/
Just 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/
Hi,
Unfortunately, it looks like your support period has expired a while ago. Please renew it here and we will be happy to help you.
Unfortunately, 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.
Sorry, this looks like a very niche configuration that will not be supported directly. If you could find out the exact steps and command lines to do it outside VisualGDB, we can help you configure VisualGDB to automate them, but unfortunately we cannot offer any help beyond that.
No problem. VisualGDB would create a library project when it detects that the original IAR project was a static library. The check is done using the “GOutputBinary” element in the IAR project file.
Most likely, your project was created using an older version of IAR and our importing plugin doesn’t handle it properly. If you could attach the .ewp file here (or send it via our support form), we will be happy to update our importer to handle it properly. You don’t need to share any actual source code.
If you do not want to share the project file, you can also patch the IAR project importer on your side by cloning it from Github: https://github.com/sysprogs/BSPTools/tree/master/ProjectImporters/IARProjectImporter
Hi,
Based on the log, it looks like the toolchain got imported as an embedded, not Linux toolchain. Could you please share the screenshots of how exactly you import it (including all relevant wizard pages), so that we could double-check what is going on?
Hi,
It looks like you are trying to debug a static library:
&"\"C:\\Users\\Public\\Projects\\ProvaErmesGDB\\VisualGDB\\Release\\ProvaErmesGDB.a\": not in executable format: File format not recognized\n"Please note that static libraries cannot be programmed or debugged directly. Instead, they need to be linked into an executable project, that could be programmed and debugged as expected.
You can switch between building a static library and an executable via VS Project Properties -> Configuration -> General (see this page for a detailed description of MSBuild property types).
No problem, please try this build: VisualGDB-5.5.4.3559.msi
It will automatically detect the old Windows 10 builds and will revert to using the old bash.exe syntax when targeting WSL.
Sorry, this looks like a generic C++ question and is outside of the VisualGDB support scope. For generic programming questions please consider sites like StackOverflow.
