Booting From A Device Peripheral - Texas Instruments TMS320C54x User Manual

10.9.3.2 Leaving Room for the Boot Table

10.9.4 Booting From a Device Peripheral

The complete boot table is similar to a single section containing all of the
header records and data for the boot loader. The address of this "section" is
the boot table origin. As part of the normal conversion process, the hex
conversion utility converts the boot table to hexadecimal format and maps it
into the output files like any other section.
Be sure to leave room in your system memory for the boot table, especially
when you are using the ROMS directive. The boot table cannot overlap other
nonboot sections or unconfigured memory. Usually, this is not a problem; typi-
cally, a portion of memory in your system is reserved for the boot table. Simply
configure this memory as one or more ranges in the ROMS directive, and use
the –bootorg option to specify the starting address.
You can choose to boot from a serial or parallel port by using the SERIAL or
PARALLEL keyword with the –bootorg option. Your selection of a keyword
depends on the target device and the channel you want to use. For example,
to boot a 'C54x from its serial port, specify –bootorg SERIAL on the command
line or in a command file. To boot a 'C54x from one of its parallel ports, specify
–bootorg PARALLEL.
Note: On-Chip Boot Loader Concerns
-
Possible memory conflicts. When you boot from a device peripheral,
the boot table is not actually in memory; it is being received through the
device peripheral. However, as explained in Step 3 on page 10-30, a
memory address is assigned.
If the table conflicts with a nonboot section, put the boot table on a
different page. Use the ROMS directive to define a range on an unused
page and the –bootpage option to place the boot table on that page. The
boot table will then appear to be at location 0 on the dummy page.
-
Why the System Might Require an EPROM Format for a Peripheral
Boot Loader Address. In a typical system, a parent processor boots a
child processor through that child's peripheral. The boot loader table
itself may occupy space in the memory map of the parent processor. The
EPROM format and ROMS directive address correspond to those used
by the parent processor, not those that are used by the child.
Building a Table for an On-Chip Boot Loader
Hex Conversion Utility Description 10-31