Bootloader Options - Texas Instruments Concerto F28M35 Series Technical Reference Manual

Application Notes to Use Boot ROM
that the initialized sections are where you expect them to be.
The linker -w option is also very useful. This option will tell you if the linker has assigned a section to a
memory region on its own. For example, if you have a section in your code called ramfuncs.
3. Run the hex conversion utility.
Choose the appropriate options for the desired boot mode and run the hex conversion utility to convert
the COFF file produced by the linker to a boot table.
See the TMS320C28x Assembly Language Tools User's Guide (SPRU513) and the TMS320C28x
Optimizing C/C++ Compiler User's Guide (SPRU514) for more information on the compiling and linking
process.
Table 6-31 summarizes the hex conversion utility options available for the bootloader. See the
TMS320C28x Assembly Language Tools User's Guide (SPRU513) for a detailed description of the
hex2000 operations used to generate a boot table. Updates will be made to support the I2C boot. See the
Codegen release notes for the latest information.
Option
-boot
-sci8
-spi8
-gpio8
-gpio16
-bootorg value
-lospcp value
-spibrr value
-e value
-i2c8
-i2cpsc value
-i2cclkh value
-i2cclkl value
6.8.2.2 Example: Preparing a COFF File For eCAN Bootloading
This section shows how to convert a COFF file into a format suitable for CAN based bootloading. This
example assumes that the host sending the data stream is capable of reading an ASCII hex format file. An
example COFF file named GPIO34TOG.out has been used for the conversion.
Build the project and link using the -m linker option to generate a map file. Examine the .map file produced
by the linker. The information shown in
(GPIO34TOG.map). This shows the section allocation map for the code. The map file includes the
following information:
• Output Section
This is the name of the output section specified with the SECTIONS directive in the linker command
file.
• Origin
The first origin listed for each output section is the starting address of that entire output section. The
following origin values are the starting address of that portion of the output section.
626
ROM Code and Peripheral Booting
Table 6-31. Bootloader Options
Description
Convert all sections into bootable form (use instead of a SECTIONS directive)
Specify the source of the bootloader table as the SCI-A port, 8-bit mode
Specify the source of the bootloader table as the SPI-A port, 8-bit mode
Specify the source of the bootloader table as the GPIO port, 8-bit mode
Specify the source of the bootloader table as the GPIO port, 16-bit mode
Specify the source address of the bootloader table
Specify the initial value for the LOSPCP register. This value is used only for the spi8 boot table format
and ignored for all other formats. If the value is greater than 0x7F, the value is truncated to 0x7F.
Specify the initial value for the SPIBRR register. This value is used only for the spi8 boot table format and
ignored for all other formats. If the value is greater than 0x7F, the value is truncated to 0x7F.
Specify the entry point at which to begin execution after boot loading. The value can be an address or a
global symbol. This value is optional. The entry point can be defined at compile time using the linker -e
option to assign the entry point to a global symbol. The entry point for a C program is normally _c_int00
unless defined otherwise by the -e linker option.
Specify the source of the bootloader table as the I2C-A port, 8-bit
Specify the value for the I2CPSC register. This value will be loaded and take effect after all I2C options
are loaded, prior to reading data from the EEPROM. This value will be truncated to the least significant
eight bits and should be set to maintain an I2C module clock of 7-12 MHz.
Specify the value for the I2CCLKH register. This value will be loaded and take effect after all I2C options
are loaded, prior to reading data from the EEPROM.
Specify the value for the I2CCLKL register. This value will be loaded and take effect after all I2C options
are loaded, prior to reading data from the EEPROM.
Example 6-5
Copyright © 2012–2019, Texas Instruments Incorporated
has been copied from the example map file
SPRUH22I – April 2012 – Revised November 2019
www.ti.com
Submit Documentation Feedback