DLPS037F October   2014  – June 2021 DLPC900

PRODUCTION DATA  

  1. Features
  2. Applications
  3. Description
  4. Revision History
  5. Pin Configuration and Functions
  6. Specifications
    1. 6.1  Absolute Maximum Ratings
    2. 6.2  ESD Ratings
    3. 6.3  Recommended Operating Conditions
    4. 6.4  Thermal Information
    5. 6.5  Electrical Characteristics
    6. 6.6  System Oscillators Timing Requirements (1)
    7. 6.7  Power-Up and Power-Down Timing Requirements
      1. 6.7.1 Power-Up
      2. 6.7.2 Power-Down
    8. 6.8  JTAG Interface: I/O Boundary Scan Application Timing Requirements
    9. 6.9  JTAG Interface: I/O Boundary Scan Application Switching Characteristics
    10. 6.10 Programmable Output Clocks Switching Characteristics
    11. 6.11 Port 1 and 2 Input Pixel Interface Timing Requirements
    12. 6.12 Two Pixels Per Clock (48-Bit Bus) Timing Requirements
    13. 6.13 SSP Switching Characteristics
    14. 6.14 DMD Interface Switching Characteristics (1)
    15. 6.15 DMD LVDS Interface Switching Characteristics
    16. 6.16 Source Input Blanking Requirements
  7. Detailed Description
    1. 7.1 Overview
    2. 7.2 Functional Block Diagram
    3. 7.3 Feature Description
      1. 7.3.1 DMD Configurations
      2. 7.3.2 Video Timing Input Blanking Specification
      3. 7.3.3 Board-Level Test Support
      4. 7.3.4 Two Controller Considerations
      5. 7.3.5 Memory Design Considerations
        1. 7.3.5.1 Flash Memory Optimization
        2. 7.3.5.2 Operating Modes
        3. 7.3.5.3 DLPC900 Memory Space
        4. 7.3.5.4 Minimizing Memory Space
        5. 7.3.5.5 Minimizing Board Size
          1. 7.3.5.5.1 Package Selection
          2. 7.3.5.5.2 Large Density Flash
            1. 7.3.5.5.2.1 Combining Two Chip-Selects with One 32-Megabyte Flash
              1. 7.3.5.5.2.1.1 Combining Three Chip-Selects with One 64-Megabyte Flash
            2. 7.3.5.5.2.2 Combining Three Chip-Selects with One 128-Megabyte Flash
        6. 7.3.5.6 Minimizing Board Space
        7. 7.3.5.7 Flash Memory
    4. 7.4 Device Functional Modes
      1. 7.4.1 Structured Light Application
  8. Application and Implementation
    1. 8.1 Application Information
    2. 8.2 Typical Applications
      1. 8.2.1 Typical Two Controller Chipset
        1. 8.2.1.1 Design Requirements
        2. 8.2.1.2 Detailed Design Procedure
          1. 8.2.1.2.1 DLPC900 System Interfaces
            1. 8.2.1.2.1.1 Control Interface
            2. 8.2.1.2.1.2 Input Data Interfaces
            3. 8.2.1.2.1.3 DLPC900 System Output Interfaces
              1. 8.2.1.2.1.3.1 Illumination Interface
              2. 8.2.1.2.1.3.2 Trigger and Sync Interface
            4. 8.2.1.2.1.4 DLPC900 System Support Interfaces
              1. 8.2.1.2.1.4.1 Reference Clock and PLL
              2. 8.2.1.2.1.4.2 Program Memory Flash Interface
              3. 8.2.1.2.1.4.3 DMD Interface
      2. 8.2.2 Typical Single Controller Chipset
  9. Power Supply Recommendations
    1. 9.1 System Power Regulation
      1. 9.1.1 Power Distribution System
        1. 9.1.1.1 1.15-V System Power
        2. 9.1.1.2 1.8-V System Power
        3. 9.1.1.3 3.3-V System Power
    2. 9.2 System Environment and Defaults
      1. 9.2.1 DLPC900 System Power-Up and Reset Default Conditions
    3. 9.3 System Power-Up Sequence
      1. 9.3.1 Power-On Sense (POSENSE) Support
      2. 9.3.2 Power Good (PWRGOOD) Support
      3. 9.3.3 5-V Tolerant Support
    4. 9.4 System Reset Operation
      1. 9.4.1 Power-Up Reset Operation
      2. 9.4.2 System Reset Operation
  10. 10Layout
    1. 10.1 Layout Guidelines
      1. 10.1.1  General PCB Recommendations
      2. 10.1.2  PCB Layout Guidelines for Internal Controller PLL Power
      3. 10.1.3  PCB Layout Guidelines for Quality Video Performance
      4. 10.1.4  Recommended MOSC Crystal Oscillator Configuration
      5. 10.1.5  Spread Spectrum Clock Generator Support
      6. 10.1.6  GPIO Interface
      7. 10.1.7  General Handling Guidelines for Unused CMOS-Type Pins
      8. 10.1.8  DMD Interface Considerations
        1. 10.1.8.1 Flex Connector Plating
      9. 10.1.9  PCB Design Standards
      10. 10.1.10 Signal Layers
      11. 10.1.11 Trace Widths and Minimum Spacing
      12. 10.1.12 Trace Impedance and Routing Priority
      13. 10.1.13 Power and Ground Planes
      14. 10.1.14 Power Vias
      15. 10.1.15 Decoupling
      16. 10.1.16 Fiducials
    2. 10.2 Layout Example
    3. 10.3 Thermal Considerations
  11. 11Device and Documentation Support
    1. 11.1 Device Support
      1. 11.1.1 Device Nomenclature
      2. 11.1.2 Device Markings
      3. 11.1.3 DEFINITIONS - Video Timing Parameters
    2. 11.2 Documentation Support
      1. 11.2.1 Related Documentation
    3. 11.3 Receiving Notification of Documentation Updates
    4. 11.4 Support Resources
    5. 11.5 Trademarks
    6. 11.6 Electrostatic Discharge Caution
    7. 11.7 Glossary
  12. 12Mechanical, Packaging, and Orderable Information

Package Options

Mechanical Data (Package|Pins)
Thermal pad, mechanical data (Package|Pins)
Orderable Information

Minimizing Memory Space

Depending on the application design requirements of the product, the amount of memory can be reduced. This can include reducing the number of flash memory components or the memory size of the flash memory component.

As depicted in Figure 7-8, the firmware resides in CS1, and the amount of memory the firmware occupies is usually less than 128-kilobytes. With this in mind, the design engineer can conclude that memory is only required to be present on CS1 if no images are needed for the design.

For example, if the application design only requires the DLPC900 to operate in Video Mode, then the flash memory components on CS0 and CS2 are not required and can be left out. Moreover, since the firmware only occupies about 128-kilobytes of memory, then a smaller density flash memory component can be used such as a 4-megabyte rather than a 16-megabyte component. One 4-Megabyte Flash Memory shows the memory space for this example.

Figure 7-8 One 4-Megabyte Flash Memory

The same memory space shown in One 4-Megabyte Flash Memory also applies to Video Pattern Mode. In this mode, the images are streamed from an external video source directly in to the internal memory of the DLPC900. Another operating mode that can use this same memory configuration is Pattern On-The-Fly Mode because the images are streamed over the USB or I2C interfaces directly into the internal memory of the DLPC900. These three operating modes are excellent opportunities for minimizing the flash memory because they don't require images to be stored in flash memory.

However, there exists one mode that can require additional memory because this mode requires images to be stored in flash memory. When the DLPC900 is operating in Pre-Stored Pattern Mode, the DLPC900 reads all the required images from flash memory into its internal memory when the pattern sequence is started. The amount of flash memory depends on the needs of the application.

For example, if the application design requires only a few images, and the images and firmware can fit in one 4-megabyte flash component, then the memory space in One 4-Megabyte Flash Memory can be used. However, if more memory is needed, then one 8-megabyte or one 16-megabyte flash component can be used as shown in One 8-Megabyte Flash Memory and One 16-Megabyte Flash Memory.

Figure 7-9 One 8-Megabyte Flash Memory
Figure 7-10 One 16-Megabyte Flash Memory

When the memory requirement is greater than 16-megabytes but less than 32-megabytes, then two 16-megabyte flash components can be used as shown in Two 16-Megabyte Flash Memory Components. Use CS1 and CS2 when using only two flash components.

Figure 7-11 Two 16-Megabyte Flash Memory Components

When memory requirement exceeds 32-megabytes, use the flash memory space shown in Figure 7-11 or use a single large flash device as described in Section 7.3.5.5.2. Notice that in all examples, there is a 1-megabyte space reserved at the end of the Firmware space. The default and maximum size of this reserved space is 1-megabyte; however, depending on the operating mode, the reserved space is customizable and can be reduced by the design engineer when configuring the firmware. Whatever size is chosen, this reserved area must be taken into consideration when calculating the required amount of memory.