We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi everyone,
I'm trying to debug a file compiled in Eclipse with the uVision version V5.14.0.0 in a microcontroller STR912FAW47. I can insert breakpoints in the assembler windows but the option is disable when I try to do the same in the windows with the C code (figure). Do I need to add something on the makefile to activate the debbuging?
Thanks in advance
Regards
Alan Blumenstein
Presumably, when you say Eclipse - that means that the code was compiled with GCC ?
It's the Compiler (and Linker, etc) that's significant - rather than the IDE it's hiding behind.
In theory, it should be possible - but, yes, you do need to make special efforts to get everything lined-up and compatible:
https://community.arm.com/developer/tools-software/tools/f/keil-forum/43230/build-with-gcc-arm-embedded-debug-with-uvision
It might be easier to just do the debugging in Eclipse ...
That's what I did in the end.
(especially as ST now have a ready-to-go Eclipse-based IDE for their products - which wasn't the case back then)
Thanks for the reply Andy, I tried to change the symbols for debugging, but the options to set the breakpoints in the C code are not yet activated.
Alan
Did you follow the link to the 'launchpad' thread - where user 'steven_cooreman' suggested some settings to try ?
Or try Eclipse?
I tried adding the flags in the post but -gdwarf-3 and -gstrict-dwarf creates some problems (-gdwarf-2 works fine). I have the message "debug output level not recognized" dwarf-3 ""
Oh.
Like I said, I ended up just using Eclipse to debug Eclipse-generated code.
Back in the days of that thread, setting up debugging on Eclipse was a bit of a pain - but it worked fine once I got it going.
Now that ST have their own solution, I have found that "just works" ...