Controlling the ROM Device Address
10-34
10.10 Controlling the ROM Device Address
The hex conversion utility output address field corresponds to the ROM device
address. The EPROM programmer burns the data into the location specified
by the hex conversion utility output file address field. The hex conversion utility
offers some mechanisms to control the starting address in ROM of each sec-
tion and/or to control the address index used to increment the address field.
However, many EPROM programmers offer direct control of the location in
ROM in which the data is burned.
10.10.1
Controlling the Starting Address
Depending on whether or not you are using the boot loader, the hex conversion
utility output file controlling mechanisms are different.
Nonboot-loader mode. The address field of the hex conversion utility output
file is controlled by the following mechanisms listed from low to high priority:
1) The linker command file
. By default, the address field of the hex conver-
sion utility output file is a function of the load address (as given in the linker
command file) and the hex conversion utility parameter values. The rela-
tionship is summarized as follows:
out_file_addr
†
= load_addr
(data_width
mem_width)
out_file_addr
is the address of the output file.
load_addr
is the linker-assigned load address.
data_width
is specified as 16 bits for the TMS320C54x devices.
See subsection 10.4.2,
Data Width, on page 10-10.
mem_width
is the memory width of the memory system. You can
specify the memory width by the –memwidth option
or by the
memwidth parameter inside the ROMS
directive. See subsection 10.4.3,
Memory Width, on
page 10-10.
† If paddr is not specified
The value of data width divided by memory width is a correction factor for
address generation. When data width is larger than memory width, the
correction factor
expands the address space. For example, if the load
address is 0
1 and data width divided by memory width is 2, the output file
address field would be 0
2. The data is split into two consecutive loca-
tions the size of the memory width.
2) The paddr parameter of the SECTIONS directive. When the paddr
parameter is specified for a section, the hex conversion utility bypasses
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: ......