Forum Replies Created
-
AuthorPosts
-
support
KeymasterHi,
Sorry about your PhpBB experience, normally when you press ‘back’ in your browser, the text you entered on the page should reappear. if that does not happen, you may want to update your browser. We had to disable hyperlink posting for anonymous users because we were getting 20+ spam posts per day despite having a custom CAPTCHA.
Please find the answers to your questions below:
1. It is straight-forward. See the STM32 tutorial here: http://visualgdb.com/tutorials/arm/stm32/
2. You can use any GCC-based toolchain of your choice (some our customers even reported success with using the IAR compiler). However you may need to specify some GCC flags manually if your toolchain handles them differently from ours.
3. This is not directly supported by VisualGDB, however you can use the GDB tracepoint commands (https://sourceware.org/gdb/onlinedocs/gdb/Tracepoints.html) to collect data in a similar way. You can enter GDB commands directly in the GDB Session window while using VisualGDB.
4. Last time we checked, ST did not ship their own GDB Server. Hence we support OpenOCD and Texane ST-Link tool out-of-the-box. If you want to use some other GDBServer, simply choose the ‘custom mode’ and specify the path to your GDBServer manually.
5. You can support FreeRTOS threads by writing a thread visualization plugin. There is a detailed tutorial here: http://visualgdb.com/tutorials/arm/threads/
6. VisualGDB does not have any special support for profiling. You can use the built-in GCC/GDB features for it.
7. You can use the Visual Studio memory window just like when debugging Windows programs.
8. You can use the VS Registers window to view the CPU registers and the Embedded Registers pane to view the peripheral registers.
9. The problem with serial wire viewer is that ST-Link uses an undocumented protocol and hangs randomly when you try to view the output. Hence OpenOCD and Texane ST-Link tools support it, but it not very useful in practice. You could get a stable SWV output if you use Segger J-Link with Segger software.support
KeymasterHi,
Which system are you targeting? Linux, MinGW/Cygwin or Android? Are you running GDB locally (i.e. using a cross-toolchain) or remotely via SSH?
support
KeymasterHi,
What platform would you prefer? x86 Linux, Raspberry Pi or something different?
support
KeymasterHi,
You can update for free to any version released within a year from your purchase date (we usually count the date of the first beta). Hence you can start using the beta now and simply install the final release over it once it’s out.
Cygwin build of make is the root cause of the problems you are expecting. It expects the paths in the /cygdrive/c/xxx format, while our toolchains are MinGW-based and report paths in the c:/xxx format. To avoid further problems, ensure that your toolchain and your make executable are built for the same platform.
support
KeymasterHi,
We did test this specific patch. Last time we built the Android GDB was around NDK 8 and the build process was fairly straight-forward using a MinGW/MSYS environment. Please feel free to give it a try and if you encounter strange problems, feel free to post here so that we can try to help you.
support
KeymasterHi,
Most likely your library was compiled without debugging symbols. You need to rebuild it yourself with debugging mode enabled (-ggdb) in order to be able to step into it.
If you want to use Plain C, simply use files with .c extension, they will be compiled as C, not C++.
support
KeymasterHi,
We are currently working on a new IntelliSense engine that will solve the type of problems you are experiencing. As a workaround, you can update the definition of __MINGW_NOTHROW in _mingw.h:
#ifdef _MSC_VER #define __MINGW_NOTHROW #else //Original definition #if __MINGW_GNUC_PREREQ (3, 3) #define __MINGW_NOTHROW __attribute__ ((__nothrow__)) #else #define __MINGW_NOTHROW #endif /* GNUC >= 3.3 */
#endif
support
KeymasterHi,
We’ve added support for running gdb via sudo a few versions ago. See the “run debugger as root with sudo” checkbox on the Debug Settings page.
October 25, 2014 at 01:03 in reply to: Can’t pull /system/bin/app_process on Android L Preview dev. #3090support
KeymasterHi,
Please try this build: http://visualgdb.com/tmp/VisualGDB-4.3.1.180.msi
support
KeymasterHi,
This looks like either your project file got damaged, or the VS installation got damaged. Does re-creating the project with VIsualGDB wizard help? Note that the VisualGDB settings are stored in the .vgdbsettings files that are separate from VS projects and can be copied back after you re-create the project.
support
KeymasterHi,
We tried copy-pasting the XML fragment you posted into a .vgdbsettings file, but it did not cause any exceptions. If you could reproduce it and share a repro file, we should be able to fix it easily.
support
KeymasterHi,
We have added support for ‘detaching’ projects from BSPs to the upcoming VisualGDB 4.3.
Please switch to a newer version of GNU Make. The one that comes with our toolchains supports the c:/xxx path syntax in .dep files properly.
Running make.exe without cmd used to cause some random crashes in some cases. We did not investigate this further, as it looks like a bug specific to some versions of GNU Make for Windows and using cmd fixes it.support
KeymasterHi,
We could not reproduce this on our side. Could you please share the entire .vgdbsettings file?
support
KeymasterHi,
We don’t provide any officially supported tools for generating the BSP packages. However, you can generate one by modifying the existing package XML files in other BSPs. The BSP XML files are produced by the .Net serializer from objects inside the BSPEngine assembly, so you can make a new C# application, reference BSPEngine.dll and manipulate the XML files programmatically:
using BSPEngine; ... BoardSupportPackage bsp = XmlTools.LoadObject
(@"c:xxxBSP.xml");
bsp.SupportedMCUs = ...;
XmlTools.SaveObject(bsp, @"c:yyyBSP.xml");
We do have an internal tool that parses the STM32 headers and generates peripheral register definitions, but it’s highly specific to STM32, as it needs to extract the information from the comments and internal file layout. You can try extracting the register layouts from the Atmel Studio IDE if their license permits doing that.
support
KeymasterHi,
That is very strange. What happens if you start Command Prompt and manually run the following commands:
cd /d C:UsersKelsARCommLinuxHelloWorldLinuxHelloWorld "C:SysGCCraspberrybinmake.exe" CONFIG=Debug type Makefile
Does Make still complain about a missing Makefile? Does your source directory have some non-typical access rights? What happens if you try setting the access to the current user to ‘full control’?
-
AuthorPosts