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.4.4 Rebuilding the Serial Flash and Boot Utils Package for a Particular Platform

  1. For a particular platform, the extracted package consists of a 'Common' directory and a <PlatformName>' directory.
  2. Open a Cygwin prompt, which is like a Unix/Linux prompt under Windows.
    1. If using v2.36 or earlier, add necessary components to the path: 
      export PATH=<arm-compiler-root>/bin:<C6000-Compiler-Root>/bin:$PATH
    2. If using v2.40 or later, edit the ARM_TOOLS_PATH, ARM_TOOLS_PREFIX, and DSP_TOOLS_PATH variables in Common/build.mak as needed for your system.
  3. Enter into the <PlatformName> directory. 
    cd <PlatformName>
  4. Edit device.mak to include only the part number and flash type required, in order to speed up the build process. 
    vim device.mak
  5. [Optional] To rebuild only the command-line tools (not the CCS projects), cd into the GNU directory. 
    cd GNU
  6. [Optional] To rebuild only the CCS projects, cd into the CCS directory 
    cd CCS
  7. If you are rebuilding everything, stay in the <Platform> directory.
  8. Run 'make clean' and 'make' 
    make clean 
make
  9. If you wish to clean-up already built components, run 'make clean' from the path you wish to clean.