support

Forum Replies Created

Viewing 15 posts - 7,171 through 7,185 (of 7,850 total)
  • Author
    Posts
  • in reply to: Recursive linking #3042
    support
    Keymaster

    Hi,

    Sorry for the delay. Can you send us an archive with your test application (or attach it here) so that we could experiment with it on our side to figure out the root cause of the problem?

    in reply to: Issue with "Start without debugging" #3294
    support
    Keymaster

    Hi,

    Thanks, the deployment was indeed skipped. We have added a default option to deploy it to the upcoming maintenance release.

    in reply to: Passing User Variables to make works weird #3299
    support
    Keymaster

    Hi,

    Your Windows itself may not have the limit, but the GNU make may have been compiled with an old version of the cygwin/MinGW runtime that does. That would explain why the shell started from the Make sees the variable, but the Make itself ignores it.
    If this is a critical issue, you could rebuild the Make binary from sources and step through it to see why the variables are lost. Let us know if you need instructions on that.

    in reply to: VisualGDB 4.2 Bugs #3319
    support
    Keymaster

    Hi,

    Sorry for the late reply. We have found and resolved the NullReferenceException issue. The fix will be available in the next maintenance release (r4). Let us know if you want an earlier build.
    Regarding the ‘clean’ problem you can go to Visual Studio Project Properties (not VisualGDB Project Properties), General page and clear the “Build log file” field or relocate it outside of the ‘Debug’ directory. Then it won’t interfere with the clean command.

    in reply to: Passing User Variables to make works weird #3297
    support
    Keymaster

    Hi,

    This looks like it may be related to the environment block size limit. The older versions of Windows had it limited to 32K and some programs may still have it hardcoded. Try cleaning up some unused environment variables and see if that solves the problem.

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

    Hi,

    The latest release of VisualGDB stores relative paths in the MCU XML file. Simply change the path to devicesstm32f407xx.xml if you have created your project using an older version.
    You can browse all VisualGDB-related settings via Tools->Options->VisualGDB.

    in reply to: Need help with MingW64 #3285
    support
    Keymaster

    Hi,

    The include/library directory settings do not support any variables. They do support relative paths, however.
    If you want to reference a VisualGDB library project, simply add it to the build dependencies of your main project and VisualGDB will figure out the path to the binary automatically.
    We don’t support multiple targets per project as it would make some things overcompilcated (e.g. project references or mapping of source files to targets) and it’s not supported by normal Visual Studio projects. You can instead use one of the following workarounds:
    1. Create several VisualGDB projects in different directories
    2. Manually edit the makefiles to add more targets (you will then have to manually track which sources belong to which targets)
    3. Create several VisualGDB projects in the same directory and override the Makefile name for them (e.g. Makefile2 instead of Makefile).

    in reply to: VisualGDB 4.2 Bugs #3320
    support
    Keymaster

    Hi,

    Sorry, we are still investigating the NullReferenceException issue. We should be able to provide an update by the end of this week.

    in reply to: Passing User Variables to make works weird #3300
    support
    Keymaster

    Hi,

    Does that happen with a stock version of make.exe that comes with MinGW, or are you using some custom make executable?

    in reply to: autocomplete/intellisense problem * SOLVED* #3245
    support
    Keymaster

    VisualGDB reuses the Visual Studio IntelliSense engine (it configures it by providing GCC-specific definitions and include paths). Sometimes, the Visual Studio IntelliSense engine produces strange results. We are currently working on a new engine that will handle the GCC-specific code natively. As a temporary workaround before we have released it you can try commenting out arbitrary include directives to see which of them breaks IntelliSense.

    in reply to: vpn connections #3279
    support
    Keymaster

    If properly configured, the VPN sever will give you an IP address inside the intranet, the software on the client side will route requests to 192.168.0.2 via the VPN transport and the VPN server will in turn forward them to your FTP server. Typically, the manual for the VPN client/server software should contain plenty of configuration examples that can provide further clues.

    in reply to: Reset MCU #3275
    support
    Keymaster

    Currently this is not possible, however if you go to the GDB Session window, select the text input and press the ‘up’ button, it will show the last entered command. Hence, you will just need to press ‘‘ each time you want to execute it.

    in reply to: VisualGDB and Raspberry PI Model A #3280
    support
    Keymaster

    Hi,

    We have not specifically tested it over WiFi, however if you can get it to work to the point where you can ping your Raspberry Pi from your PC, VisualGDB should be able to target it without any problems. Let us know if you encounter any difficulties.

    in reply to: Need help with MingW64 #3283
    support
    Keymaster

    Hi,

    The easiest thing to start with would be adding the msys binary directory to PATH when building your makefile (this can be changed on the Build Settings page in VisualGDB Project Properties). That may still require some additional tweaking, e.g. if your Makefile expects the output of ‘pwd’ to have a /cygdrive syntax.

    in reply to: Reset MCU #3273
    support
    Keymaster

    Hi,

    You can reset the CPU by running a “mon reset” command via the GDB Session window.

Viewing 15 posts - 7,171 through 7,185 (of 7,850 total)