[support]

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.

[support]

Hi,

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

[support]

Hi,

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

[support]

Hi,

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

[support]

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.

[support]

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

[support]

Hi,

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

[support]

Hi,

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

[support]

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.

 

[support]

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.

[support]

Hi,

Please try relocating the BSP to a directory with a shorter path (e.g. c:\nrf51) as described in this tutorial: http://visualgdb.com/tutorials/arm/multiuser/

[support]

Are you using OpenOCD or Segger software? Segger software should have their own implementation of semihosting (activated by “monitor semihosting enable” command).

[support]

Hi,

We tried reproducing your example, but could not get anything to fail. Hence I would assume that the problem is caused by some detail omitted in your message (e.g. relative paths, some extra spaces or tabs, file name lengths). If you could send us an archive with the exact files that fail for you, we should be able to fix it fairly fast.

Clang IntelliSense parses the entire project when:

• You search for a definition (not declaration with Ctrl-F12) of a function that is not defined in the current translation unit.
• The function is not static.

If this happens in some other case, please give us an example file and we should be able to fix it quickly.

We know that our IntelliSense engine has some bugs that are not present in Eclipse and that’s why we always ask for detailed repro steps that help us nailing down those bugs and fixing them. As long as we can reproduce the bug on our side, we typically release a hotfix within 24 hours. Hence if you could provide us with the exact file that causes the bugs on your side, most likely we will resolve it very fast.

[support]

We do not allow switching toolchains for existing projects because different toolchains have different settings formats and switching them may introduce serious bugs. We would recommend creating a new project and then importing the existing files into it. If you absolutely want to override the toolchain, you can edit the <mcu>.xml and <mcu>.mak files in your project directory replacing the references manually.

[support]

Hi,

Not sure why the double dash did not work for you, but it should be double. Here is a screenshot:

Together with unchecking the “provide default implementations” field (that sets –specs=nosys.specs), this results in the following build command line:

F:\SysGCC\arm-eabi/bin/arm-eabi-g++.exe -o Debug/stm32f4test.elf -Wl,-gc-sections --specs=rdimon.specs  ... -lcompactcpp    -Wl,--end-group

If the GUI does not work, you can try manually modifying LDFLAGS in debug.mak.

Regarding live variables. As a quick fix, if you are using OpenOCD, you can try connecting to port 4444 and sending OpenOCD commands (e.g. mdw <address> to read a DWORD), however you cannot do this if you are using live variables, as VisualGDB uses the same interface.

As a long-term solution, we are actually planning to add support for running tests with VisualGDB, so we could make a much higher-level interface. We would rather provide a framework for defining test functions with test asserts in your code (that will be normally ignored) and then add a special mode where VisualGDB will build a binary with the tests enabled and run the given subset of tests. Would that be more useful than just live variables API?

[Author]

Posts