DLPU102C December   2020  – July 2024

 

  1.   1
  2.   Trademarks
  3. 1Read This First
    1. 1.1 About This Guide
    2. 1.2 Related Documentation from Texas Instruments
    3. 1.3 If You Need Assistance
  4. 2DLP LightCrafter Dual DLPC900 EVM Overview
    1. 2.1 Welcome
    2. 2.2 DLP LightCrafter Dual DLPC900 Evaluation Module (EVM) Hardware
    3. 2.3 EVM Board
    4. 2.4 Other Items Needed for Operation
    5. 2.5 DLP LightCrafter Dual DLPC900 Connections
      1. 2.5.1 DLP LightCrafter Dual DLPC900 LED Enable and PWM Outputs
      2. 2.5.2 DLP LightCrafter Dual DLPC900 Trigger Input and Output Voltage Selectors
    6. 2.6 DLP LightCrafter Dual DLPC900 EVM Flex Cable
    7. 2.7 DLP LightCrafter Dual DLPC900 EVM and DMD EVM Assembly
  5. 3Quick Start
    1. 3.1 Power-up the DLP LightCrafter Dual DLPC900 EVM
    2. 3.2 Creating A Simple Pattern Sequence
  6. 4Operating the DLP LightCrafter Dual DLPC900 EVM
    1. 4.1  DLP LightCrafter Dual DLPC900 Control Software
    2. 4.2  PC Software
    3. 4.3  System Common Controls
      1. 4.3.1 Operating Mode
      2. 4.3.2 Connected DMD Type
      3. 4.3.3 EVM Information
      4. 4.3.4 Status
    4. 4.4  System Settings
    5. 4.5  Video Mode
      1. 4.5.1 Video Support
    6. 4.6  Pattern Modes
      1. 4.6.1 Menu Bar
      2. 4.6.2 Creating a Pattern Sequence in Pattern On-The-Fly Mode
      3. 4.6.3 Creating a Pattern Sequence in Pre-Stored Pattern Mode
      4. 4.6.4 Reordering a Pattern Sequence using the Edit LUT Feature
        1. 4.6.4.1 Special Considerations for Input Triggers When Using the Edit LUT Feature
      5. 4.6.5 Creating a Pattern Sequence in Video Pattern Mode
      6. 4.6.6 Creating a Pattern Sequence With DMD Block Load
      7. 4.6.7 Pattern Settings
    7. 4.7  Batch Files
      1. 4.7.1 Execute Batch File
      2. 4.7.2 Creating and Saving Batch Files
        1. 4.7.2.1 Creating and Saving a Batch File Using the GUI
        2. 4.7.2.2 Creating a Batch File Using a Text Editor
      3. 4.7.3 Loading a Batch File
      4. 4.7.4 Adding a Batch File to the Firmware
    8. 4.8  Peripherals Panel
      1. 4.8.1 Peripherals Tab
      2. 4.8.2 Debug Tab
    9. 4.9  Firmware
      1. 4.9.1 Adding or Removing Patterns from the Firmware
        1. 4.9.1.1 Deleting Images
        2. 4.9.1.2 Adding Images
        3. 4.9.1.3 Adding Both Images and Batch Files
    10. 4.10 Reprogram Controller Board for a Different Supported DMD
    11. 4.11 Flash Device Parameters
    12. 4.12 JTAG Flash Programming
    13. 4.13 Programming an EDID
    14. 4.14 Intel (Altera) FPGA Programming
  7. 5Connectors
    1. 5.1  Input Trigger Connectors
    2. 5.2  Output Trigger Connectors
    3. 5.3  DLPC900 UART Headers
    4. 5.4  DLPC900 I2C Port 0
    5. 5.5  DLPC900 I2C Port 1
    6. 5.6  DLPC900 I2C Port 2
    7. 5.7  JTAG Boundary Scan
    8. 5.8  GPIO and PWM
    9. 5.9  Power
    10. 5.10 External Parallel Video Connector
  8. 6Power Supply Requirements
    1. 6.1 External Power Supply Requirements
  9. 7Safety
    1. 7.1 Caution Labels
  10. 8Revision History

4.8.2 Debug Tab

GUI 5.3 Added debug functions shown in Figure 4-21.

Click the Debug Tab button at the side of the Peripherals Panel to display Figure 4-21.

DLPC900 Debug Tab Figure 4-21 Debug Tab

Selecting the Enable Debug mode checkbox enables the debug functions shown in on the Debug Tab.

  • The Destination ASIC box allows the user to select whether commands apply to:
    • Default ASIC - This means the primary controller for most commands. Some commands are sent to both controllers when this option is chosen.
    • Primary Only - This selection causes command to be applied only to the primary controller and applies for commands in all areas of the GUI.
    • Secondary Only - This selection causes command to be applied only to the secondary controller and applies for commands in all areas of the GUI.

    Note:
    • The following commands require execution on both controllers regardless of the set destination controller:
      • Set System Power Mode - Normal / Standby /Software reset
      • Set Operating Mode - Video Mode / Pre-stored Pattern Mode / Video Pattern Mode / Pattern On-the-Fly Mode
      • DMD Park
      • Get/Set Destination Controller (this command)
      • Memory Read/Write commands outside of the Debug Memory Read/Write

  • The Controller Memory Read/Write box allows Reading from and Writing to memory address on either or both controllers.

    Select the desired controllers in the From box.

    CAUTION: Read from or write only to defined addresses. Reading from or writing to undefined addresses results in unpredictable behavior!

    There are two virtual interfaces to assist in debugging. For example Reading from or Writing to some addresses can result in changes in other memory locations. The result of writing to a memory using Interface 1 can be tracked in Interface 2.

    The following are valid memory address ranges:

    • 0x00000000 - 0x00003FFF
    • 0x11000000 - 0x11003FFF
    • 0x11005000 - 0x1100AFFF
    • 0x1100F000 - 0x110137FF
    • 0x11014000 - 0x110177FF
    • 0x11018000 - 0x110187FF
    • 0x11019000 - 0x110197FF
    • 0x11020000 - 0x11023A40
    • 0x11024000 - 0x11025FFF
    • 0x20000000 - 0x27FFFFFF
    • 0xA7000000 - 0xA7FFFFFF
    • 0xF7FEC000 - 0xFAFFFFFF
    • 0xFFFF0000 - 0xFFFFFFFF

  • The Debugging Trace box allows the user to enable various debug areas to report detailed debug information to Section 5.3 beyond the always printed debug messages output during regular operation. Select the Enable debug message checkbox to allow the following individual masks to be enabled or disabled separately:

    Debug Masks - detailed descriptions:

    • System information - Enable printing of debug messages regarding system functions like system initialization, memory allocation, batch command execution.
    • Datapath information - Enable printing of debug messages regarding datapath like datapath initialization to process video input, ITE, HDMI, DP information, and System state transition.
    • Projector Control Information - Enable printing of debug messages regarding projector control like initialization of USB and I2C command port, command message handler, and command processing.
    • I2C handler - Enable printing of debug messages regarding I2C communication interface.
    • UART handler - Enable printing of debug messages regarding UART communication interface.
    • USB handler - Enable printing of debug messages regarding USB communication interface.
    • Always Printed (on by default) - Enable printing of debug messages regarding system, power-up, illumination, memory initialization, state transitions, application layer command processing.
    • Mailbox message - Enable printing of debug messages regarding application mailbox interface.
    • Environment information - Not used
    • PTN Information - Enable printing of Pattern Info debug messages regarding loading of splash images to FMT memory or loading a BMP pattern.
    • PTN debug - Enable printing of Pattern Info debug messages regarding sequence database, selected sequence information, encode and decode of sequences, pattern parameter setup, etc.
    When debug messages are enabled, pressing Get retrieves the currently enabled masks. After selecting the desired masks pressing Set enables the selected masks. The Debug Mask shows, in hex, the overall mask value. The value can be used in Section 4.9 - Power up Defaults section to build a firmware with the desired masks enabled at power up.
    Note: Deselecting Enable debug message disables all debug output except Always Printed items

    Max String Length - reads the maximum allocated string size for the debug message

    Currently Used - reads the string size currently used by the debug message

  • The Memory Access Batch Files box enables special batch files that can be provided by TI during advanced debugging.

    Select the Record result check box to record the result of running a provided batch file. Results are recorded in the same directory that the batch file resides.

    Use Open memory access batch File button to navigate to a memory access batch file provided.

    Use Run memory access batch file button to run the batch file selected by the Open memory access batch File.

  • Diagnostic Window Settings

    Select the Enable or Disable button to show or hide diagnostic log windows. Enabling this option shows a command log window under the main GUI window are as shown in Figure 4-22.

    DLPC900 Diagnostic Window Figure 4-22 Diagnostic Window

    These logs are available:

    • Select the Enable Projector Control Log tab. Records every command sent to the DLPC900 and the status of transaction. Records the system initialization and status commands the first time the DLPC900 is powered up.
    • Select the Enable Command Log tab. Records information such as command name, command ID, sent and received message packet, status of transaction.
    • Select the Enable Periodic Status Log to show the periodic status polling commands in the Projector Control tab. Records the DLPC900 main, HW, system status query commands sent by the GUI. This occurs at 120 second intervals. Enabling this records these commands each time the commands are sent. This causes slow response from the GUI.

    For the Projector Control log and Command log the following options are available:

    • Select all - selects all of the contents of the selected log tab to be copied.
    • Copy - copies to the clipboard the currently selected items in the selected log tab. Drag click to select a subset of the log to copy.
    • Clear all - clears all of the current entries in the selected log tab.
    • Save to File - saves the current selected log tab entries to a file.