|ARM Technical Support Knowledge Articles|
Applies to: OH251 Object-HEX Converter
Information in this article applies to:
I have created a project that uses NCONST space. I have verified the MAP file and all NCONST segments are correctly placed in the MAP file. However the HEX file does not contain any of my NCONST data. What's wrong?
By default, the 251 toolchain creates a 64KB HEX file for the address range 0xFF0000-0xFFFFFF which is the 8051-compatible address range.
To get a HEX file that contains the memory image for the whole 16MB address space of the 251, you must select the INTEL HEX386 format and specify the address range 0x000000-0xFFFFFF.
Use the following command line if you OH251 from the command prompt.
OH251 filename H386 RANGE (0 - 0xFFFFFF)
If you use uVision2, you must make the following selections on the Output Tab of the Project Options dialog.
Article last edited on: 2006-10-29 19:04:30
Did you find this article helpful? Yes No
How can we improve this article?