 Technical Support | |
| Home Products Events Support | |
Technical Support
Support Resources
- Support Knowledgebase
- Product Manuals
- Application Notes
- File Download Area
- Product Updates
- Discussion Forum
- Books
Product Information
ARM: HOW TO CREATE ONE HEX FILE FOR MY APPLICATION
Information in this article applies to:
- RealView MDK-ARM Version 2.50a
QUESTION
In my µVision 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?
ANSWER
µVision 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:
#KARM\BIN30\fromelf.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, µVision passes the option '--i32combined' to 'fromelf' by default.
MORE INFORMATION
- RV Linker/Utilities manual (\Keil\ARM\HLP\RV_link.pdf), Using fromelf.
Last Reviewed: Thursday, January 11, 2007