support

Forum Replies Created

Viewing 15 posts - 3,766 through 3,780 (of 7,848 total)
  • Author
    Posts
  • in reply to: V. 5.4 prev. 8 references #22580
    support
    Keymaster

    Hi,

    The estimated time is just a linear extrapolation based on the average speed so far. If the remaining time is going up, the parsing speed must be consistently going down. It could be caused by running out of RAM, or slow disk performance. Please let us know the total/free RAM shown in Task Manager when the cache is rebuilding.

    The cache is invalidated either when some of the build options (e.g. preprocessor macros) change, or when some of the files get outdated. The v5.4R8 build will show the exact reason for cache invalidation in the Clang IntelliSense Diagnostics Console (search for “invalidating cache chunk” messages).

    in reply to: TI TIVA Stellaris ICDI #22577
    support
    Keymaster

    Hi,

    If you have tight time constraints, please consider trying Segger J-Link. It is more expensive than other debug probes, but comes with its own fully supported replacement to OpenOCD that works out-of-the-box with many devices. VisualGDB supports both Segger J-Link and OpenOCD, so you can choose the underlying tool based on your requirements.

    in reply to: V. 5.4 prev. 8 references #22576
    support
    Keymaster

    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.

    in reply to: IDF_PATH on windows platform #22566
    support
    Keymaster

    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.

    in reply to: Multiple definitions of source files #22564
    support
    Keymaster

    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.

    in reply to: Inactive code opacity #22563
    support
    Keymaster

    Hi,

    VisualGDB uses the general “Stale Code” setting from Visual Studio Options (Text Editor -> Fonts and Colors).

    in reply to: cmake #22562
    support
    Keymaster

    Hi,

    No problem, please let us know the email address associated with your license so that we could check your support status.

    in reply to: IDF_PATH on windows platform #22554
    support
    Keymaster

    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.

    in reply to: Live Variables exception #22550
    support
    Keymaster

    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.

    in reply to: Esp32 debug not working on windows 7 evaluation #22549
    support
    Keymaster

    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.

    in reply to: Toolchain shows in packages dialog but not project wizard #22545
    support
    Keymaster

    Hi,

    Please try updating to VisualGDB 5.4 Preview 8. It contains many fixes compared to v5.3.

    in reply to: Problem when using googletest on Windows 10 subsystem #22544
    support
    Keymaster

    Hi,

    Please try updating to VisualGDB 5.4 Preview 8.

    in reply to: Embedded project -> unit test greyed out #22543
    support
    Keymaster

    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.

    in reply to: STM32 huge BIN/Hex file #22535
    support
    Keymaster

    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.

    in reply to: error in STM32 develop using visualgdb, visualstudio #22534
    support
    Keymaster

    Hi,

    Please use the following link to renew your license: https://sysprogs.com/splm/mykey

Viewing 15 posts - 3,766 through 3,780 (of 7,848 total)