[support]

Hi,

Could you please try evaluating the variable via the GDB Session window (“print <variable name>”)? Does this show correct values?

Perhaps the variable name is confused with something else, like a global variable with the same name of a register? Does the Watch window show correct value?

[support]

Hi,

We do have plans on adding more mbed tutorials, but not before the v5.2 release at the end of summer. If you have some specific topics you would like to see covered, let us know and we will address those first.

[support]

Hi,

Please try the __attribute__((__interrupt__(vector))) syntax described here: http://stackoverflow.com/questions/15500826/how-to-declare-an-interrupt-handler-isr-in-mspgcc

[support]

Hi,

VisualGDB has its own mechanism for handling signal behavior. Please use the ‘signals’ button in the GDB Session window (the yellow lightning bolt icon). This will set the signal settings properly and remember them for the next session.

Regarding C# debugging, gdb does not support this out-of-the-box, however VisualGDB SDK has an interface for parsing high-level frames (i.e. extracting code location and variable values by manually interpreting the values of the normal C/C++ variables or CPU registers). If you are willing to figure out how to extract that data for Mono frames, yes you can easily hook that up to VisualGDB and we can provide more details on that.

[support]

Thanks for reporting this. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.1.719.msi

[support]

Hi,

So far it looks like a fairly rare scenario that could be easily automated with custom actions, however we’ll keep on watching this thread. If we get more feedback from other users that this would simplify things a lot, we will add it to one of the next releases.

[support]

Hi,

VisualGDB already supports mbed. Please see this tutorial for details (step 9 shows how to reference various libraries).

[support]

Hi,

Yes, you can right-click on the Source Files folder in Solution Explorer and select “Add->Import Folder Recursively”. VisualGDB will then allow automatically adding all files from a given directory and subdirectories to the project. You can choose to either copy those files to the project directory, or reference them in their current location (that can be a directory shared between several projects as you suggested).

You can also set a checkbox to automatically add all directories containing .h files to the include directory list in your project so you won’t need to do that manually.

Let us know if this does not work.

[support]

Hi,

You can do that via custom pre-debug actions. Simply open VisualGDB Project Properties, go to the Debug Customization page and add steps to upload your DLLs. Note that this feature is available in the Custom and Ultimate editions.

[support]

Most likely while deleting and reinstalling everything you installed the new version of the debug package that includes the fix as we suggested above.

Now that you have the latest version installed, the problem should not occur anymore.

[support]

OK, then please post the contents of the OpenOCD window in Visual Studio here so that we could help you figure out what is causing the problems.

[support]

Yes, the problem happens because arm_abs_f32.c does not include stm32f407xx.h.

You could edit the arm_abs_f32.c file (or one of the central headers it includes), forcibly include stm32f407xx.h into all source files via CFLAGS or explicitly add _FPU_PRESENT to preprocessor defines like you did. Either one of those workarounds is fine.

[support]

Hi,

Most likely one of your files ends up including the core_cmX.h file that checks for the _FPU_PRESENT macro before including stm32f407xx.h file  that defines it.

First of all, please identify the source file that is showing the error (you can remove the -j<number of CPUs> flag from Makefile arguments and check the last built file in the output log). Then try including the stm32f407xx.h file before any other files.

If this does not help, please try reducing the source file to just one include statement that still causes the error and then post the source file a build log showing the include directories here.

[support]

Hi,

Please check the OpenOCD window for errors. There was a bug in our recent OpenOCD release that could have caused it and it was fixed in VisualGDB 5.1r6.

Please upgrade to that version or alternatively re-download the latest OpenOCD debug package via Embedded Tools Manager. Then open the Debug Settings page, change any setting there and press “OK”. This should fix the problem.

[support]

Not sure what you meant. Adding a non-existent path to IntelliSense should have no effect and be the same as not adding any path there.

[Author]

Posts