Controlling the ROM Device Address
10-35
Hex Conversion Utility Description
the section load address and places the section in the address specified
by paddr. The relationship between the hex conversion utility output file
address field and the paddr parameter can be summarized as follows:
out_file_addr
†
= pad ( load_addr – sect_beg_load_addr )
(data_width
mem_width)
out_file_addr
is the address of the output file.
paddr_val
is the value supplied with the paddr parameter
inside the SECTIONS directive.
sec_beg_load_addr
is the section load address assigned by the
linker.
† If paddr is not specified
The value of data width divided by memory width is a correction factor for
address generation. The section beginning load address factor subtracted
from the load address is an offset from the beginning of the section.
3) The –zero option. When you use the –zero option, the utility resets the
address origin to 0 for each output file. Since each file starts at 0 and
counts upward, any address records represent offsets from the beginning
of the file (the address within the ROM) rather than actual target addresses
of the data.
You must use the –zero option in conjunction with the –image option to
force the starting address in each output file to be zero. If you specify the
–zero option without the –image option, the utility issues a warning and
ignores the –zero option.
Boot-Loader Mode. When the boot loader is used, the hex conversion utility
places the different COFF sections that are in the boot table into consecutive
memory locations. Each COFF section becomes a boot table block whose
destination address is equal to the linker-assigned section load address.
The address field of the the hex conversion utility output file is not related to
the section load addresses assigned by the linker. The address fields are sim-
ply offsets to the beginning of the table, multiplied by the correction factor (data
width divided by memory width).
The beginning of the boot table defaults to the linked load address of the first
bootable section in the COFF input file, unless you use one of the following
mechanisms, listed here from low to high priority. Higher priority mechanisms
override the values set by low priority options in an overlapping range.
1) The ROM origin specified in the ROMS directive. The hex conversion
utility places the boot table at the origin of the first memory range in a
ROMS directive.
Summary of Contents for TMS320C54x
Page 38: ......
Page 39: ......
Page 40: ......
Page 41: ......
Page 42: ......
Page 43: ......
Page 44: ......
Page 45: ......
Page 46: ......
Page 47: ......
Page 48: ......
Page 49: ......
Page 50: ......
Page 51: ......
Page 52: ......
Page 53: ......
Page 54: ......
Page 55: ......
Page 56: ......
Page 57: ......
Page 58: ......
Page 59: ......
Page 60: ......
Page 61: ......
Page 62: ......
Page 276: ......
Page 277: ......
Page 278: ......
Page 279: ......
Page 280: ......
Page 281: ......
Page 282: ......
Page 283: ......
Page 284: ......
Page 285: ......
Page 286: ......
Page 287: ......
Page 288: ......
Page 289: ......
Page 290: ......
Page 291: ......
Page 292: ......
Page 293: ......
Page 294: ......
Page 295: ......
Page 296: ......
Page 297: ......
Page 298: ......
Page 299: ......
Page 300: ......
Page 301: ......
Page 302: ......