NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

OMAP-L138 Hardware Design Guide

From Texas Instruments Wiki
Jump to: navigation, search

Hardware Design Timeline →[edit]

Constructing the Block Diagram Selecting the Boot Mode Confirming Pin Multiplexing Compatibility Confirming Electrical and Timing Compatibility Designing the Power Subsystem Designing the Clocking Subsystem Floorplanning the PCB Creating the Schematics Laying out the PCB Testing / Debugging

 

Introduction[edit]

Welcome to the OMAP-L138/C6748/AM1808 Hardware Design Guide.  The purpose of this guide is to walk hardware designers through the various stages of designing a board around OMAP-L138/C6748/AM1808 .  The guide follows the structure shown in the Hardware Design Timeline above.  Each design stage in the Timeline links to a collection of useful documentation, application notes, and design recommendations pertaining to that stage.  Using this Guide, hardware designers can efficiently locate the resources they need at every step in the board design flow.

Constructing the Block Diagram[edit]

The first step in designing the hardware platform is to create a detailed block diagram.  The block diagram should contain all major system ICs and illustrate which I/O ports are used for device interconnection.  Below is a collection of resources to aid in the Block Diagram creation process.

Selecting the Boot Mode[edit]

The block diagram should also indicate which interface will be used for booting the OMAP-L138/C6748/AM1808 .  Upon coming out of reset, the processor must boot up by loading its application code from external storage. The application code can be loaded from a ROM or can be downloaded from another processor in the system.  The processor contains a primary bootloader burned into its internal ROM which is run by the processor after coming out of reset. This primary bootloader performs some critical initial tasks and then loads application code from the external interface specified by the processor boot configuration pins. See the below information for selecting an implementing the right boot mode for your system.

Confirming Pin Multiplexing Compatibility[edit]

The processor uses internal pin multiplexing to allow for maximum functionality in the smallest and lowest cost package.  Due to this pin multiplexing, not all processor interfaces are always available simultaneously.See the Terminal Functions section of the datasheet for complete details on the pin multiplexing.  Also see the below information for tools and tips related to pin multiplexing.

Confirming Electrical and Timing Compatibility[edit]

A key step in the hardware design before beginning schematic capture is to confirm both DC and AC electrical compatibility between the processor and the other ICs connected to it.  See the below collection of information to aid in confirming the system's electrical compatibility

Designing the Power Subsystem[edit]

Once the block diagram has been validated for pin multiplexing, electrical, and timing compatibility, the power sub-system can be designed. See the below resources on estimating processor power consumption and designing a matching power subsystem.

Designing the Clocking Subsystem[edit]

In addition to the power subsystem, the clocking subsystem needs to be designed to provide appropriate clocks to all ICs in the system. These clocks can be created by pairing crystals with internal oscillators within the system ICs, or they can be created by a separate clock generator. See the below information on designing the clocking subsystem for your design.

  • Key Considerations for designing the Clocking Subsystem:
    • A 100MHz reference clock is required by the processor when using SATA port.

Floorplanning the PCB[edit]

Before beginning schematic capture, it is recommended to floor plan the system PCB to determine the interconnect distances between the various system ICs. See the below information on floor planning your PCB.

  • TBD: Why and How to floor plan your PCB before starting schematic capture

Creating the Schematics[edit]

At this point in the design, it is time to start capturing the schematics. See the below collection of information to aid you in creating the schematics for your design.

  • Key Considerations for Capturing Schematics:
    • SDRAM (and other) output clocks are internally looped back
    • Don’t forget to install a JTAG connection
    • JTAG: Make sure to use the RTCK pin

Laying out the PCB[edit]

After completing schematic capture, see the below information on laying out the PCB for your system:

OMAP-L138 Complementary Products[edit]

This section serves as a repository of complimentary Devices that can be paired with the OMAP-L138 SoC devices when integrating the device into a system. The Complementary Products listed on the wiki serve a wide range of functions such as:

  • Providing basic support functions for the SoC (power, clocking, etc.)
  • Expanding the interface options beyond the on-chip peripherals
  • Creating the link between the digital domains on the SoC to the system's analog/physical domains

Click here for Wiki article on Complimentary products

Testing/Debugging[edit]

Debugging Tools[edit]

Once your custom PCB has been produced and assembled, refer to the below information on bringing-up and debugging the system.

  • See the below GEL Files that aid in configuring your design during debug/development
  • Below is a collection of information on using the TI provided Booting Tools for the processor
    • Serial UART Boot and Flash Loading Utility for OMAP-L138/C6748/AM1808
      • You need to change the code to according to your own board configure(DDR2 and flash driver) and recompile the executable program.
    • CCS flash writer can be found in the PSP release (eg. DaVinci-PSP-SDK-03.20.00.14\src\utils\)
      • Contains flash writers for NOR/NAND/SPI-FLASH/MMCSD. These writers can be run from withing CCS to write programs to flash for boot.
    • Note: The default flash storage is SPI flash on eXperimenter board and NOR/NAND flash are all on the UI board.

Hardware Debugging Tips[edit]

DDR2/mDDR[edit]

Most issues with DDR2/mDDR come from incorrect software settings. Double check your settings with the DDR timing spreadsheet:

The processor and DDR drive strength configurations can also be the cause of issues. See the following wiki for more information on this topic:

Once the software settings are confirmed, the layout itself may be at fault:

  • Double check your layout against the routing rules in the processor datasheet
    • The most common layout problem that affects DDR functionality is incorrect stackup. Verify that each DDR routing layer has an adjacent solid ground plane underneath with no cuts.
    • See the following checklist for other issues that can affect functionality:
  • Use maximum values for the timing parameters to increase timing margins
  • Slow down the DDR clock to determine if it is limited to a high speed issue
E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article OMAP-L138 Hardware Design Guide here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article OMAP-L138 Hardware Design Guide here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article OMAP-L138 Hardware Design Guide here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article OMAP-L138 Hardware Design Guide here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article OMAP-L138 Hardware Design Guide here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article OMAP-L138 Hardware Design Guide here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article OMAP-L138 Hardware Design Guide here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article OMAP-L138 Hardware Design Guide here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article OMAP-L138 Hardware Design Guide here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity