|ARM Technical Support Knowledge Articles|
Applies to: ARM Development Tools
Information in this article applies to:
In my uVision project I have defined different Read/Only Memory Areas in the dialog Project - Options for Target - Target. The option Create HEX File in the dialog Project - Options for Target - Output is also selected. When I build my application, a folder is created which contains a separate HEX file for each memory area rather than a single HEX file for the complete application. How can I prevent this?
uVision invokes the 'fromelf' utility with the option '--i32' in order to create a Intel Hex-32 file. With this option, a separate HEX file is created for each memory area. This can be used for programming different flash devices or different application parts (boot/application).
If one single HEX file should be generated, fromelf needs to be invoked with the option '--i32combined'. This can be done in the dialog Options for Target - Output - After Make - Run User Program. The command line may look like:
#KARMBIN30fromelf.exe #L.axf --i32combined --nodebug --output #H
The Create HEX File option in the same dialog must be turned off.
Since MDK-ARM version 3.0, uVision passes the option '--i32combined' to 'fromelf' by default.
Article last edited on: 2007-01-11 07:04:38
Did you find this article helpful? Yes No
How can we improve this article?