SPRACM8A June   2019  – January 2021 OMAP-L132 , OMAP-L132 , OMAP-L138 , OMAP-L138 , TMS320C6742 , TMS320C6742 , TMS320C6746 , TMS320C6746 , TMS320C6748 , TMS320C6748

 

  1.   Trademarks
  2. 1OMAP-L138 Boot Process
    1. 1.1 During Reset
    2. 1.2 After Reset
  3. 2Boot Utilities
    1. 2.1 AISgen
    2. 2.2 Serial Boot and Flash Loading Utility
      1. 2.2.1 Compiling
        1. 2.2.1.1 Under Windows
        2. 2.2.1.2 Under Linux
      2. 2.2.2 Running
        1. 2.2.2.1 Under Windows
        2. 2.2.2.2 Under Linux
      3. 2.2.3 Serial Flasher Options
    3. 2.3 Modifications for Custom Boards
    4. 2.4 Rebuilding and Customization of Boot Utilities
      1. 2.4.1 Download the Flash and Boot Utilities
      2. 2.4.2 Install and Configure the Required Software
        1. 2.4.2.1 Cygwin
        2. 2.4.2.2 Microsoft .NET Framework
      3. 2.4.3 Compiler Tools
        1. 2.4.3.1 Compiler Tools (CODESOURCERY G++ LITE)
        2. 2.4.3.2 C6X Compiler Tools
        3. 2.4.3.3 Newer CCS
      4. 2.4.4 Rebuilding the Serial Flash and Boot Utils Package for a Particular Platform
      5. 2.4.5 Rebuilding the HexAIS Utility for OMAPL13x
  4. 3Boot Examples
    1. 3.1 Booting Binaries
      1. 3.1.1 Description
      2. 3.1.2 Obtaining the Software
      3. 3.1.3 Running
    2. 3.2 Booting DSP Binaries on AM1808/OMAPL138
      1. 3.2.1 Description
      2. 3.2.2 Obtaining the Software
      3. 3.2.3 Running
        1. 3.2.3.1 OMAP-L138 EVM
        2. 3.2.3.2 C6748 EVM
  5. 4Debugging Bootloader
  6. 5OMAP-L138 Boot Benchmarks
    1. 5.1 Host Boot Performance
    2. 5.2 Test Details
      1. 5.2.1 Methodology
      2. 5.2.2 43
      3. 5.2.3 Software
      4. 5.2.4 Hardware
      5. 5.2.5 Discussion
  7. 6OMAP-L138 Bootloader FAQ
  8. 7References
  9.   A Setting c_int00 Using SYS/BIOS
  10.   Revision History

2.2.3 Serial Flasher Options

There are three modes for using the serial flasher:

  • Erase the target flash type - This erases the entire contents of the flash.
    • ..\sfh_OMAP-L138.exe -erase
  • Flash the memory with a single application image - This places an application image at address 0x0 of the flash. This must be an AIS format binary that can be created with the AISgen utilities bundled with the Using the OMAP-L132/L138 Bootloader and associated files.
    • ..\sfh_OMAP-L138.exe -flash_noubl <binary application file>
  • Custom usage of secondary bootloader: A third option is supported in a tool to allow users to use a user defined secondary bootloader (SBL) that uses a two step boot process. In this setup the secondary bootloader is programmed at address 0x0 of the flash and the application is flashed at offset 0x10000.
    Example usage:
    • ..\\sfh_OMAP-L138.exe -flash <UBL binary file> <binary application file>

      For use of secondary boot approach for these devices, see the Processor SDK RTOS.

For C6748 devices, use the following option: "-targetType C6748".

For AM1808 devices, use the following option: "-targetType AM1808".

Note:
  • Only the UBL found in the OMAP-L138/GNU/UBL directory can be used with the serial flasher. Other UBLs are not compatible with the serial flasher format.
  • The 'flash_noubl' and 'flash' options automatically erases the necessary amount of memory in order to fit the UBL or application image.

Currently, the only supported flash types are NAND, NOR, and SPI.

Additional options are shown below:

-targetType            : Specifies exact target type within OMAP-L138 family (default OMAP-L138)
-flashType             : Specifies exact flash type (default SPI_MEM)
-p <COM PORT NAME>     : Allows specifying com port other than default 'COM1' or '/dev/ttyS0'.
-h                     : Show help text.
-v                     : See verbose output from target device
-baud <BAUD RATE>      : Allows specifying baud rate other than default (115200)
-APPStartAddr          : Changes entry point of application (default 0xC1080000)
-APPLoadAddr           : Changes load address of application (default 0xC1080000)
-APPFlashBlock         : Changes the block to flash the image into (only for no_ubl mode)

Once any command is run, the "Waiting for BOOTME..." prompt shows. Power cycle the board or press the reset button to continue.