Texas Instruments TMS320C54x, Руководство пользователя

Страница: 323 / 469

The SECTIONS Directive
10-23 Hex Conversion Utility Description
SECTIONS begins the directive definition.
sname identifies a section in the COFF input file. If you specify a sec-
tion that doesn’t exist, the utility issues a warning and ignores
the name.
paddr specifies the physical ROM address at which this section
should be located. This value overrides the section load
address given by the linker. (See Section 10.10,
Controlling the
ROM Device Address, on page 10-34).This value must be a
decimal, octal, or hexadecimal constant. It can also be the word
boot (to indicate a boot table section for use with the on-chip
boot loader).
If your file contains multiple sections, and if one
section uses a paddr parameter, then all sections must use a
paddr parameter.
= boot configures a section for loading by the on-chip boot loader. This
is equivalent to using paddr
=boot. Boot sections have a physi-
cal address determined both by the target processor type and
by the various boot-loader-specific command line options.
The commas separating section names are optional. For more similarity with
the linker’s SECTIONS directive, you can use colons after the section names
(in place of the equal sign on the boot keyboard). For example, the following
statements are equivalent:
SECTIONS { .text: .data: boot }
SECTIONS { .text, .data = boot }
In the example below, the COFF file contains six initialized sections: .text,
.data, .const, .vectors, .coeff, and .tables. Suppose you want only .text and
.data to be converted. Use a SECTIONS directive to specify this:
SECTIONS { .text, .data }
To configure both of these sections for boot loading, add the boot keyword:
SECTIONS { .text = boot, .data = boot }
Note: Using the –boot Option and the SECTIONS Directive
When you use the SECTIONS directive with the on-chip boot loader, the
–boot option is ignored. You must explicitly specify any boot sections in the
SECTIONS directive. For more information about –boot and other command
line options associated with the on-chip boot loader, see Table 10–2,
page
10-29.