Hi,
I'm starting to work with the Keil MDK_ARM_4.14 and I have some problems with setting up a project for debugging. I build my software with an external build process using a makefile. The output format is dwarf2 and the file extension of the debug file is *.elf.
My first problem is to change the file extension of the debug file in the uVision environment. uV always requires a *.axf file. Is it possible to change this standard extension? My current workaround is to rename my elf-file to *.axf.
My second problem is the debugging behaviour of the uVision environment. When I compile a project completely in uV then the debugger automatically opens a source file when a function call is executed outside of the current file. When I use my externally build debug file the debugger doesn't do this. That means if a function call is executed, I need to open the file manually and then the executed position is shown properly after the first single step command. Does anybody know the reason for this behaviour?
I hope anyone can help me.
Cheers, Ralf
Thanks for the fast reply!
I thought that the complete path information is located in the *.elf file isn't it? I made a dump of the elf using the fromelf tool and it contains all pathes of my linked objects.
Where does the debugger take the path information from?
My folder strcture is as follows:
<project>\build <project>\prog => contains the application code and make file <project>\uses => contains library files
My elf-file is generated in the prog folder. The uV project is located in the <project> root folder, i.e. one step above the elf-fle in the prog folder.
rgds, Ralf
But does it store absolute or relative paths?
Now I have found that when I create the project in the prog subfolder the uV environment finds my source files and opens them automatically. But there is one problem left. Library source files are still not opened. The symbols window of the debugger tells me, that uV searches my library files one step above the prog folder. So it seems that the uV uses relative pathes. But when I dump the elf content I can only find absolute pathes in the debug file. This seems a little bit strange for me.
Sorry,
now I've found that the elf contains a mixture of relative and absolute pathes. Thats the reason for my problems.
Thanks a lot for your help!
Is it possible to force the linker to include absolute path names in the output elf file?