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.7.4 Adding a Batch File to the Firmware

A batch file can be added to the firmware to be used as the default batch file to be executed during the power-up sequence of the DLPC900. Or a batch file can be added to be executed at any time after the power-up sequence has completed to perform some action. Some special considerations must be taken if adding pattern images and a batch file to the firmware image. See the note at end of Section 4.9.1.2 for a description of these considerations. Follow these steps to add the example batch file from the previous section to the firmware.

CAUTION:

The user must exercise caution when selecting the correct firmware file. Install DLP LightCrafter GUI version 5.x or later and FW version 6.x or later. Operating or updating the firmware on the DLP LightCrafter DLPC900 GUI version 4.x (or earlier) renders the EVM inoperable.

  1. Power-up the EVM and verify the EVM is operating as expected.
  2. Start the GUI and verify the connection has been established with the EVM.
  3. Click the Batch File button at the top of the GUI.
  4. Check the Enable Command Logging box to enable logging.
  5. Click the Clear All button to clear the contents.
  6. Click the Load Batch File button and browse for the text file that was saved in Section 4.7.2.
  7. The panel displays the commands as the commands are in the file.
  8. Click the Firmware button at the top of the GUI.
  9. Click the Browse button and select the firmware files for the EVM being used.
    Note:

    When updating firmware for the DLP LightCrafter Dual DLPC900 EVM, the GUI creates two firmware files. One for the primary controller and one for the secondary controller. When selecting a firmware file or an updated version, select both of the files named [firmwareimg]-primary.img and [firmwareimg]-secondary.img by clicking each while holding the Ctrl key.

  10. Within the Batch File and Patterns group box, check the Add Batch File box.
  11. In the Batch File Name edit box, enter a name for the batch file. Up to 16 characters are allowed without spaces and special characters.
    Note:

    If the batch file is to be a default batch file to be executed during the power-up sequence, then continue to step 12, otherwise go to step 13.

  12. Within the Batch File and Patterns group box, check the box next to Set as Default Batch File.
  13. Click the Update Firmware button. The GUI displays a pop-up box providing the name of the updated firmware file.
  14. Click the Browse button and locate the firmware file from step 13.
  15. Click the Upload button. The GUI performs the necessary steps to update the firmware in the EVM.
Note:

When updating firmware for the DLP LightCrafter Dual DLPC900 EVM, the GUI creates two firmware files. One for the primary controller and one for the secondary controller. When selecting a firmware file or an updated version, select both of the files named (firmwareimg)-primary.img and (firmwareimg)-secondary.img by clicking each while holding the Ctrl key.

Note:

The name of the firmware file created by the GUI includes a timestamp, verifying that new firmware does not overwrite any previously created firmware files.