• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 15 subscribers
  • Views 2056 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

µVision debugger: enabling source level debug for already built ELF file

PAUL MOREAU

Hello,

I have an existing test.elf that I built with an external MAKE utility.
I use the µVision debugger to debug my test.elf.
I can flash my hardware with test.elf in µVision.
My test.elf is compiled with debug info.
I can debug my test.elf in other Eclipse-based IDE, but I want to switch to µVision, because Eclipse-based IDE is Java-based and very slow.

The problem:
- When I start debugging (Ctrl+F5) the disassembly code opens.
- I don't want to debug test.elf in disassembly mode.
- I want to debug test.elf in regular source level debugging mode.

I tried to use SET SRC command. Without success.
Just spent a lot of time to enable source level debugging mode for my test.elf.

Questions:
1. How to see which path are already stored in the debug info in my test.elf?
2. My test.elf was built with files that are in multiple directories.
Like this:
test/dir1
test/dir2
test/dir2/subdir1
test/dir2/subdir2
...
Do I need to set all of them to SET SRC or just root one?
Like this: SET SRC = test/dir;test/dir2;test/dir2/subdir1;test/dir2/subdir2
Or like this:SET SRC = test
3. Can µVision enable source level debugging mode if test.elf contains debug info in absolute path? How I can configure GCC to store absolute path in debug info?

Many thanks.
P.M.