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

OMAP-L138 EVM

  1. Compile the source code:
    1. Two projects are provided: one for the UBL and one for the DSP LED blinking program. Open each project file in CCS and click'Build' in the respective processor window. Precompiled .out files are located in the Debug directories of the software package.
  2. Generate the AIS image.
  3. Open the AISgen tool and select File -> Load Configuration.
  4. Choose the .cfg file (located in the base directory of the OMAPL138-DSP-LED folder) corresponding to the desired boot medium.
  5. Choose the correct Device Type for the silicon revision you are using. If you are unsure, use the GEL file provided in Section 4 to determine this.
  6. Fill in the " Application File" field with both the UBL and the DSP program. When given two source application files, the AISgen tool combines them into a single image in the order that they are listed.
    1. First, click the "..." button and provide the path to the OMAPL138-DSP-LED-ARM.out file.
    2. Next, click the "+" button and choose the OMAPL138-DSP-LED-DSP.out file.
  7. Fill in the "AIS Output File" field by giving the path where the destination AIS file will be created.
  8. Click Generate AIS.

Flash the AIS image:

  1. For NAND, NOR, and SPI bootmodes, use the serial flasher to flash the image to the desired boot medium using the "-flash_noubl" option. For more information, see Section 2.2.3.
  2. For UART bootmode, use the serial loader to boot from the UART host as follows:
    1. ./slh_OMAP-L138.exe -waitForDevice OMAPL138-ARM-LED-uart.bin