Forum Replies Created
-
Posts
-
Hi,
You can disable the code annotations by clicking the wrench symbol at the bottom right corner of the popup to open the options window, and then disabling annotations for all C/C++ entity types.
The “updating global symbol cache” is shown when VisualGDB is doing a global search (e.g. finding a definition, or all references). The remaining time should be shown after the progress advances a bit. If it never completes, please let us know if the progress is changing at all and if all the CPU cores on your machine are in use. If not, it might be stuck somewhere and we can help you pinpoint and fix it.
Hi,
If debugging consistently works on one project and consistently doesn’t work on another one, we would advise making a list of differences between the 2 projects and eliminating them one-by-one to see which one causes the problem.
If turning on external RAM indeed interferes with debugging, please inquire with Espressif for possible workarounds.
Hi,
No problem, we can add a workaround to the first problem that will automatically restart CMake if it crashes during reconfiguration.
The second problem looks like you are using backward slashes in the path to GNU Make (configured via VisualGDB Project Properties). Please try using forward slashes instead and let us know if this solves the problem.
Hi,
VisualGDB uses the general “Stale Code” setting from Visual Studio Options (Text Editor -> Fonts and Colors).
Hi,
No problem, please let us know the email address associated with your license so that we could check your support status.
Hi,
You can manage your ESP-IDF checkouts via VisualGDB Project Properties -> ESP-IDF Project -> ESP-IDF Checkout.
Unfortunately we do not provide support for debugging scenarios outside VisualGDB. Please use the VisualGDB Project Properties to configure your debugging settings or contact Espressif if you need help with ESP32 tools that are not part of VisualGDB.
Hi,
Sorry, if gdb is not able to return the address of the variable, VisualGDB won’t be able to use it in live variables. Please consider experimenting with other variables in your program to see what triggers the address issue and then update the batteryInput variable to avoid it.
Hi,
This looks like a wiring issue. Please double-check your schematics. If you are not sure, please try the ESP-WROVER module that comes with a built-in JTAG interface.
Hi,
Most likely you are using the Embedded or Linux edition that does not support unit tests.
Please consider upgrading to the custom edition here or contact our sales if you would like to get a short trial extension to test out the unit test support.
Hi,
Please either the sections that go into the external memory with the NOLOAD attribute (so that they will be excluded from the .bin file), or use the AT syntax in the linker script (see how DATA is handled) in order to place them in the regular FLASH memory and move them to the external memory manually.
Also if you are using the Custom edition, please consider using the Additional Memories page of VisualGDB Project Properties to let VisualGDB do the necessary edits automatically.
Hi,
Please use the following link to renew your license: https://sysprogs.com/splm/mykey
