Forum Replies Created
-
Posts
-
Hi,
Thanks for explaining this – it makes sense. Good to know you have found the workaround. Let us know if you run into further problems and we will be happy to help.
Hi,
Yes, that might work, although due to differences between the VC++ and the gcc compiler, some features might still not be supported properly.
Hi,
Sorry, we only provide technical support to registered users of our paid products. In order to keep on receiving technical support, please let us know the email address associated with your license.
Hi,
Please let us know the email associated with your license key so that we could check your support status.
Hi,
Sorry, the VisualGDB semihosting console only supports UTF-8 as it has become a de-facto standard encoding for all non-Latin characters. Would switching the encoding of your source files to UTF-8 be a reasonable workaround?
Hi,
Looks like you are missing the –interpreter mi argument before $(TargetPath). Specifying it (and also configuring VisualGDB to use the ‘continue’ command to start the session) should get it to work.
Hi,
Yes, please try referencing the bootloader project via Project Dependencies (not the regular Project References). This should affect the project build order without changing any actual build-related flags.
Hi,
Sorry, the native Visual Studio IntelliSense is outside our control. Please contact Microsoft regarding their plans for C++17 support/gcc compatibility.
That said, the recent versions of the Clang IntelliSense engine contain optimizations that improve the performance for huge projects (e.g. the IntelliSense-only PCH files), so you should be able to get reasonable performance out of it. Feel free to let us know if any specific scenarios are slow and we will help you set it up.
Hi,
Normally selecting a “computer used for building and debugging” will affect the following functions:
- The target machine for uploading the sources [not overridable, but can be disabled and replaced with a custom action]
- Machine where the build command is run [overridable]
- Machine where the debug command is run [overridable]
You can override #2 and #3 by setting the “Allow choosing build/clean/debug command hosts independently” checkbox on the Linux Project Properties page in VisualGDB Settings and then manually picking the host in the build command on the Build Settings page and/or the gdb command on the Debug Settings page.
Another option would be to disable the automatic source synchronization and synchronize it instead via a pre-build action (transfer a directory to a remote computer).
Please note that both options require the Custom edition or higher. If you are using a lower edition, you could work around by creating 2 project configurations (one for transferring the files and another one for building), although it would be less convenient than a 100% automatic setup described above.
Hi,
Please let us know the email associated with your license key so that we could check your support status.
Hi,
This looks like an error in the J-Link gdb server (JLinkGDBServerCL.exe). Please contact Segger support regarding this as we don’t have access to the Segger GDB stub internals and are not able to troubleshoot its crashes.
The memory we mentioned is used by the Semihosting Framework – it uses a part of the on-chip RAM to store the semihosting output (the debugger will read it in the background without stopping the target). This should not crash the J-Link gdb server, as all Fast Semihosting-related logic is handled by VisualGDB directly.
Hi,
Thanks for your feedback. We are planning to upgrade our IntelliSense engine to the latest Clang version as a part of the v5.4 release cycle (expect this to be available in the next 1-2 months). Feel free to follow us on twitter to get notified once the build with the new Clang is ready.
Hi,
This could be a wiring issue, an optimization bug (that should not happen when using out-of-the-box ESP-IDF) or a FLASH programming issue. First of all, please try simply pressing F5 to continue from the stop. Does the program resume as normal?
If not, please try creating and programming a basic “LEDBlink” project and then restart the board manually. Does the LED blink? If not, please follow this tutorial. If yes, please try disabling all breakpoints and try debugging it again.
Hi,
Not sure what toolchain you are downloading, but our ESP32 toolchain compatible with VisualGDB can be downloaded here: http://gnutoolchains.com/esp32/
Hi,
Yes, the toolchain can be installed in any location (although the path should not contain spaces).
You don’t need to re-download the toolchain. Once it is installed by running the .exe file, VisualGDB will automatically find it (you will need to restart Visual Studio if you installed the toolchain while it was running).
