support

Forum Replies Created

Viewing 15 posts - 6,826 through 6,840 (of 7,847 total)
  • Author
    Posts
  • in reply to: Moving a VisualGDB license to another computer/VM #6903
    support
    Keymaster

    Hi,

    Yes, simply contact our support with your license key and they will reset your activation.

    in reply to: ESP8266 and XT-OCD Settings #6902
    support
    Keymaster

    Hi,

    Good to know you got it to work. Let us know if you encounter further problems.

    in reply to: preprocessor define with content of a build variable #6901
    support
    Keymaster

    Hi,

    The “propagate to the environment” flag is only supported for the per-user variables, not for variables set from commands. In the case you mentioned, specifying GitRevision=$(GitRevision) explicitly is the recommended way to go.

    in reply to: preprocessor define with content of a build variable #6894
    support
    Keymaster

    Please double-check that your custom variable has the “propagate to the environment” flag. This can be also caused by a bug in the .Net framework that changes all environment variables to lowercase. You can try $(git_revision) instead. If this does not help, you can explicitly specify it in GNU Make arguments: GIT_REVISION=$(GIT_REVISION). Then VisualGDB will expand $(GIT_REVISION) and pass the actual value to the Make command line.

    in reply to: JLinkGDBServerCL #6893
    support
    Keymaster

    Hi,

    You could select the “custom mode” as the debug method and specify “gdb –interpreter mi $(TargetPath)” as your command and “target remote :<port>” as the target selection command.

    Then VisualGDB won’t take any extra steps like trying to run a GDB stub.

    in reply to: Command-line action failed when build via SSH. #6892
    support
    Keymaster

    Hi,

    Please open VisualGDB Project Properties and check the build command there. If you are not sure, please send us your .vgdbsettings file so that we could help you locate the command.

    in reply to: STM32F7 Disco LED Blink #6884
    support
    Keymaster

    Hi,

    No problem. If you encounter further problems, feel free to contact us.

    in reply to: JLinkGDBServerCL #6881
    support
    Keymaster

    Hi,

    Good to know you got it to work. If you encounter further problems, feel free to let us know.

    in reply to: STM32F7 Disco LED Blink #6880
    support
    Keymaster

    Hi,

    According to the STM32F7-Discovery schematics, an LED is connected to GPIOI1. Please select it in the wizard, or adjust the code afterwards.

    in reply to: ARM Semihosting console not work in Example #6874
    support
    Keymaster

    Hi,

    The extensibility interfaces are not documented as they are used by a fairly small amount of our users. If you have specific questions about those, feel free to ask here or direct them to our support.

    in reply to: GDB + Register View #6873
    support
    Keymaster

    This is a known bug in 4.3 that has been fixed in 5.0.

    in reply to: GNU Profiling (gprof) with ARM Cortex-M #6872
    support
    Keymaster

    Hi,

    Thanks for the link, we will investigate it and see if we can add similar functionality to VisualGDB.

    in reply to: Beginner – 5.0 can't debug on STM32F072 discovery #6871
    support
    Keymaster

    Hi,

    Please try using OpenOCD as it is more stable than Texane ST-Link.

    in reply to: SIGTRAP semihosting #6870
    support
    Keymaster

    Please add the following commands to the GDB Startup commands (after target selection) in VisualGDB Project Properties:

    mon semihosting enable
    mon semihosting IOClient 2

    Then call the initialise_monitor_handles() function in your main():

    #include <stdio.h>
    
    extern "C" void initialise_monitor_handles();
    
    int main(void)
    {
        initialise_monitor_handles();
        printf("test\n");
    }

    Finally switch the GDB Session window to “All GDB Interaction” to see the semihosting output from the Segger GDB stub.

    You can also change “IOClient 2” to “IOClient 1” to direct semihosting output to a telnet port 2333.

     

    in reply to: 5.0 STM32 Devices BSP has outdated files #6869
    support
    Keymaster

    Thanks for letting us know. We usually update our STM32 libraries quarterly. We will ensure that the next update includes the latest Cube files for F0.

Viewing 15 posts - 6,826 through 6,840 (of 7,847 total)