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.
Hello everyone,
we are using ARM Compiler 5.06 and are postprocessing the map file. We would like to have a shared postprocessing routine shared by multiple projekte and multiple compilers. Neither .map nor .hex files are homogenous, but the elf files are. So we would like to directly postprocess all elf files either using "nm" from binutils or ARM Compiler 5.06 itself.
So here i have some questions: 1. Does the ARM Compiler generated .hex and .map from elf file? 2. If so, how to trigger this functionality from console? 3. Do you have any idea if nm will process hugely differnt elf formats and yet generate uniform results?
Thanks a lot :)
>1. Does the ARM Compiler generated .hex and .map from elf file?
As Andrew already pointed out, the .map and .axf file is generated by the linker at the same time. The .hex file is then generated by the tool fromelf.exe based on the .axf file.
>2. If so, how to trigger this functionality from console?
The linker and all other tools can be invoked from the command line. Please see the command line options in the manuals. Note: uVision can create a batch file where you see all the tool invocations and you could also reuse the command files. You can find the Batch-option in the uVision dialog 'Options for Target - Output - Create Batch File'. Select it and build your application and you will find the batch file in the project folder.
>3. Do you have any idea if nm will process hugely differnt elf formats and yet generate uniform results?
I have never worked with nm, but fromelf.exe can also list symbols of a .axf file. See: http://www.keil.com/support/man/docs/armutil/ Especially the option --text -s: www.keil.com/.../armutil_pge1362128925577.htm Fromelf should be able to process .axf files that were generated by other compiler/linker but please try.