|Re: GDB Hardware debugging feature gets lost [message #1150301 is a reply to message #1070031]
||Tue, 22 October 2013 17:27
| Ralf Jesse
Registered: October 2013
maybe my answer is too late for you. I had the same effect on my newly installed Kepler and moving from yagarto to GNU ARM Toolchain.
However, it seems I found a solution! On my (Windows7-)PC I checked the checkbox "Windows --> Preferences --> Run --> Debug --> Launch Configurations --> GDB Hardware Debugging".
My idea was, to make configuration a little bit easier for future projects. After doing this, the "GDB Hardware Debugging" entry disappeared from the "Create, manage, and run
configurations" dialog. It took me some time to remember what I did. Well, after a while I unchecked the above mentiones checkbox, and voila: The "GDB Hardware Debugging" was
What I'm doing now to create a new debugging configuration:
1. I created a configuration template (__TEMPLATE_DEBUG__) with all required settings
2. A right-click on this template offers the opportunity to --> duplicate this template.
3. Modify the project name of the duplicated project from __TEMPLATE__DEBUG__ to "whateveryouneed"
4. Under C/C++ Application change to the new project (I use the 'Search Project..." button for this) and select "wateveryouneed".elf
5. At the top of the dialog change the 'Name:' from the template's name to "whateveryouneed"
I agree, Code::Blocks seems to be much easier to handle. However, Michael Fischer (Yagarto) showed an alternative in one of his many answers:
Try emIDE (from emide.org). It seems to be a branch from Code::Blocks with a lot of improvements.
Powered by FUDForum
. Page generated in 0.14343 seconds