Forum Replies Created
-
Posts
-
Well, not exactly years 🙂
Anyway, the final WinCDEmu 4.0 is out. We have also published the source code with all dependencies on GitHub: https://github.com/sysprogs/WinCDEmu
Now that the source code can be conveniently accessed via GitHub, I would like to invite everyone to contribute to the project. I started WinCDEmu many years ago as a hobby project and during these years it has grown to be a nice and nifty tool. However, realistically speaking, I won’t have the capacity in the near future to add any major features to it. That’s why I did my best to make it as easy as possible for everyone to build WinCDEmu and contribute new code to it. The GitHub repository contains one easy-to-build solution that can be opened with VS2010-2015 and it will automatically check for missing dependencies and display instructions on getting/installing them. I will be happy to answer your questions about BazisLib/WinCDEmu structure and to suggest ways of adding the features wanted by the community. I am also open to contributions as long as they don’t break the existing functionality 🙂
Hi,
You can disable the VisualGDB GDB warning window by increasing the GDB command time-out in Tools->Options->VisualGDB->General->Tweaking->GDB command timeout.
If you want to try speeding up the debugging experience, please share a GDB log with timings as described here. It should provide enough information on which exact commands are being slow.P.S. Are you using a USB virtualization software or is ST-Link connected directly to your Windows machine?
Hi,
We do understand that the price of VisualGDB could be high for non-commercial users and hence we offer student and open-source discounts. We also provide affordable Embedded and Linux editions that support a lot of the functionality needed by hobbyists. Higher editions like Custom and Ultimate are focused on providing usability for large teams and complex multi-machine setups that are rarely used by hobbyists.
VisualGDB is a productivity tool: it makes things that could be quite complex with Eclipse and other open-source tools easy and seamless. In order to keep the high quality of our product and continue offering new exciting features like the new intuitive refactoring we do need to charge a fee for the VisualGDB licenses. If you believe the price does not justify the saved effort, we would recommend trying out free tools like Eclipse or vim.
The refactoring features are available in all editions of VisualGDB including the Embedded edition that is much cheaper than $200.
Hi,
We have just added a new tutorial explaining how to use VisualGDB with the Keil compiler: http://visualgdb.com/tutorials/arm/keil/
Hi,
VisualGDB refactoring is supported via smart tags. Currently we support the following features:
1. When you rename a variable, a smart tag will appear allowing you to update all references.
2. When you click on an interface specification that is not implemented by a class, VisualGDB will show a smart tag allowing to implement missing methods
3. Similarly when you type in a declaration for a new method, VisualGDB will show a smart tag allowing to generate implementation.
4. If you call a function/method/constructor that does not exist yet, VisualGDB will show a smart tag allowing you to create it.You can read more about the refactoring features here: http://sysprogs.com/w/visualgdb-5-0-beta-1-refactoring-and-c-codemap/
Hi,
We will add an OpenOCD 0.9.0 package as a part of the upcoming VisualGDB 5.0 release. It should improve the integration with the new ST devices. The main issue of the Texane tool is that sometimes it leaves the ST-Link in an invalid state and does not start another session unless you unplug and replug it. OpenOCD does not have this problem.
Could you provide some examples of things poorly documented in VisualGDB project samples so that we could improve that?
Hi,
The makefiles are generated on project level to avoid better flexibility (e.g. combining projects using different build systems in one solution). In order to build all projects in the solution from Linux, you can simply create a script that will invoke Make for each project, e.g.:
make -C project1 || exit 1
make -C subdir/project2 || exit 1
…
make -C projectN || exit 1Hi,
Normally VisualGDB should run the ‘chmod’ command automatically. Does it also happen with an empty “hello, world” project on the same board?
Hi,
This will be fixed in VisualGDB 5.0 Beta 2. As a workaround, use the Go To Definition (F12) command instead.There are 2 ways of achieving this:
An undocumented way that may be broken in the further versions of GCC would look like this:
extern const int nErasedFlag asm("0x0807F800");A classical “supported” approach would be similar to what CooCox version uses: put the variable into a separate section and modify the linker script to place this section at a given address.
You can read more about this here: http://sysprogs.com/w/forums/topic/bootloader/
Hi,
You can try further reducing the size of your binary by switching the libc to newlib-nano and experimenting with other libc options on the Device Settings page.
Also feel free to check out the new IntelliSense engine of VisualGDB 5.0. It is designed to handle GCC-specific code and supports refactoring and Code Map.
Most likely your daemon tries to launch some other executable before handling your command. VisualGDB “follows” that launch and ends the debug session when it exits.
Please try running the set follow-fork-mode command manually via the GDB Session window just before you expect your binary to run the child job.
You can also enable GDB logging in the Quick Debug window and examine the log for any additional clues.
