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

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

Output Filenames
10-24
10.7 Output Filenames
When the hex conversion utility translates your COFF object file into a data
format, it partitions the data into one or more output files. When multiple files
are formed by splitting data into byte-wide or word-wide files,
filenames are
always assigned in order from least to most significant. This is true, regardless
of target or COFF endian ordering, or of any –order option.
10.7.1 Assigning Output Filenames
The hex conversion utility follows this sequence when assigning output file-
names:
1) It looks for the ROMS directive. If a file is associated with a range in the
ROMS directive and you have included a list of files (files = {. . .}) on that
range, the utility takes the filename from the list.
For example, assume that the target data is 16-bit words being converted
to two files, each eight bits wide. To name the output files using the ROMS
directive, you could specify:
ROMS
{
RANGE1: romwidth=8, files={ xyz.b0 xyz.b1 }
}
The utility creates the output files by writing the least significant bits (LSBs)
to xyz.b0 and the most significant bits (MSBs) to xyz.b1.
2) It looks for the –o options. You can specify names for the output files by
using the –o option. If no filenames are listed in the ROMS directive and
you use –o options, the utility takes the filename from the list of –o options.
The following line has the same effect as the example above using the
ROMS directive:
–o xyz.b0 –o xyz.b1
Note that if both the ROMS directive and –o options are used together, the
ROMS directive overrides the –o options.