support

Forum Replies Created

Viewing 15 posts - 1,981 through 1,995 (of 7,989 total)
  • Author
    Posts
  • in reply to: Payment Required After Upgrade? #29273
    support
    Keymaster

    We do our best to avoid confusion. We show the expiration date in the Help->About VisualGDB window and if VisualGDB fails to activate due to an old key, it directs to the MyKey page that lists renewal/upgrade options and also allows downloading the older VisualGDB versions.

    Edit: the poster below pointed out the confusion here, so we will try to clarify. Any version released while the update period was active should be able to activate. Preview builds of VisualGDB may activate even beyond that, however updating to the next stable release will require active renewal period at the time of that release.

    in reply to: Payment Required After Upgrade? #29271
    support
    Keymaster

    No problem. Also please note that as you have used the 50% renewal discount, your previous support/update expiration date has been extended by 1 year, placing it at 49 days from now. If this was not intended, you can instead use the 10% late renewal discount that will place it to 1 year from now (please contact our sales if you need a link to pay the difference). Or you could do another 50% renewal any time (before or after expiration) to add another year to the current expiration date.

    in reply to: Payment Required After Upgrade? #29269
    support
    Keymaster

    Thank you for your feedback. As it takes continuous effort on our side to keep VisualGDB up-to-date, and test it with the new devices, tools and frameworks, we have to limit free updates to 1 year since the license purchase, and ask for license renewal afterwards.

    We try to be very explicit about our renewal policy. Our buy page mentions the 1-year period and the renewal page provides a link to the latest version that can run with your key if you do not want to renew the license. Due to the way the installer framework works, it can only verify the license key after VisualGDB has been installed and you load it in Visual Studio.

    That said, you can always uninstall the new VisualGDB version and install back the old one without losing any settings.

    in reply to: MBED Project: "Missing hardware register defintions" #29263
    support
    Keymaster

    No problem, we have updated VisualGDB to remember the custom hardware register definitions selected for mbed projects. Please try this build: VisualGDB-5.5.101.3866.msi

    in reply to: STM32 frequency floats when debugging #29259
    support
    Keymaster

    Based on what you have described, it looks like a specific code snippet is not working as expected. It looks like an issue with a specific piece of code, rather than a VisualGDB bug. Also, unfortunately, you have not provided sufficient context for us to understand what is going on.

    If the same project behaves differently when built with the Keil IDE vs. VisualGDB, please consider following this tutorial to track down the changes.

    If it doesn’t help and you believe VisualGDB is not working as expected, please provide us the steps we could follow on our side to reproduce the problem per our problem reporting guidelines and we will try to investigate it further.

    support
    Keymaster

    Hi,

    Please refer to the following page for an overview of IntelliSense engines and settings: https://visualgdb.com/documentation/intellisense/

    support
    Keymaster

    Sorry, we have tried reproducing this issue, but could not get the behavior you described. Please make sure you update to the latest VisualGDB 5.5 and also try disabling other Visual Studio extensions.

    If this doesn’t help, please try reproducing it on a clean project created from scratch and share the steps we could follow on our side to reproduce the issue (see our problem reporting guidelines).

    in reply to: Menue inconsistency? #29248
    support
    Keymaster

    Hi,

    Unfortunately, we were not able to reproduce the problem based on the description you provided.

    If VisualGDB behaves differently than you expect, please share the steps to reproduce the problem per our problem reporting guidelines and we will try to investigate this further.

    in reply to: Doesn't work #29247
    support
    Keymaster

    Hi,

    Most likely, you have selected an incompatible combination of settings at some point. Unfortunately, it’s hard to suggest anything specific without knowing the exact setting you changed that started triggering the issue.

    Hence, our best advice would be to reset Arduino Settings, delete all Arduino packages and create the project from scratch. You can find more details in our recently updated Arduino documentation.

    If you believe that editing a specific settings has unintended consequences, please share the steps we could follow to reproduce the problem on our side (see our problem reporting guidelines) and we will try to investigate it further.

    You can also find more information on observing the project output on the following documentation page: https://visualgdb.com/documentation/projects/arduino/#output

    in reply to: Nginx VisualGDB #29244
    support
    Keymaster

    Hi,

    Sorry, VisualGDB does not have any special support for nginx modules. Please try following generic instructions for building nginx modules and then try importing the project into VisualGDB.

    in reply to: Multiple FTDI Debug ports #29242
    support
    Keymaster

    Thanks for the suggestion. This is in our roadmap, however as it involves changes beyond a trivial change of IDs, it has a relatively low priority. We should be able to add this feature next time we update the device selection GUI, or if other users request it as well.

    in reply to: No source code debugging in Visual Studio 2019 #29234
    support
    Keymaster

    Sorry, VisualGDB uses the gdb debugger to debug the code, while Ozone uses its own debugging engine. If the specific project produces an image that breaks gdb, it is outside of VisualGDB’s control to fix this, as it relies on gdb internally. The only workaround we can suggest would be to try a different Keil/GDB version.

    in reply to: No source code debugging in Visual Studio 2019 #29230
    support
    Keymaster

    No problem. It looks like the gdb debugger is not able to properly report the source location of the breakpoint event:

    *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame={addr="0x08013366",func="main",args=[],arch="armv3m"},thread-id="1",stopped-threads="all"

    This sometimes happens due to a bug in the Keil compiler that produces invalid DWARF debug symbols and typically affects code in a specific file beyond a certain line. As a workaround, please consider using the GCC compiler, or try splitting the source file into multiple smaller files. You can also experiment with setting breakpoints in different files to see if there is any pattern.

    in reply to: STM32 frequency floats when debugging #29229
    support
    Keymaster

    Sorry, not sure what the question was. In the last post in the thread you mentioned that both frequencies work now.

    If you have any other questions, please feel free to repeat them here and we will do our best to answer them.

    in reply to: No source code debugging in Visual Studio 2019 #29225
    support
    Keymaster

    It looks like you are setting breakpoints in one project and are trying to debug another one. Based on the gdb log, the breakpoint is set in the following file:

    C:/Users/dlp/source/repos/MbedProject_testCDC/mbed-os/targets/TARGET_STM/TARGET_STM32L0/TARGET_STM32L072xZ/TARGET_DISCO_L072CZ_LRWAN1/system_clock.c

    The -file-list-exec-source-files command reports a different file:

    C:/Users/dlp/source/repos/MbedProject_LoRa/mbed-os/targets/TARGET_STM/TARGET_STM32L0/TARGET_STM32L072xZ/TARGET_DISCO_L072CZ_LRWAN1/system_clock.c

    Please double-check your settings and make sure you debug the correct project.

Viewing 15 posts - 1,981 through 1,995 (of 7,989 total)