DLPC3439 Software Programmer s Guide - TI.com · DLPC3439 Software Programmer’s Guide User's Guide Literature Number: DLPU035 August 2015

DLPC3439 Software Programmer’s Guide

User's Guide

Literature Number: DLPU035August 2015

Contents

1 Introduction......................................................................................................................... 41.1 Software Programmer’s Guide Overview................................................................................. 4

1.1.1 I2C-Based Command Data Interface ............................................................................. 5

2 Interface Specification .......................................................................................................... 72.1 Electrical Interface ........................................................................................................... 7

2.1.1 System Power-up Associated Signals ........................................................................... 72.2 System Initialization ......................................................................................................... 8

2.2.1 Boot ROM Concept................................................................................................. 82.2.2 Internal vs External Boot Software ............................................................................... 82.2.3 Flash and Flashless Product Configurations .................................................................... 82.2.4 Resident Boot Software (EXT-BOOT-EN = 0) .................................................................. 8

2.3 Software Interface .......................................................................................................... 102.3.1 Software Command Philosophy ................................................................................. 102.3.2 I2C Considerations ................................................................................................ 102.3.3 List of System Write/Read Software Commands ............................................................. 11

2 Contents DLPU035–August 2015Submit Documentation Feedback

Copyright © 2015, Texas Instruments Incorporated

http://www.go-dsp.com/forms/techdoc/doc_feedback.htm?litnum=DLPU035

www.ti.com

List of Figures1-1. DLPC3439 Accessory Configuration with DLPA3000................................................................... 41-2. DLPC3439 Accessory Configuration with DLPA3005................................................................... 52-1. Boot Code Flow Chart....................................................................................................... 92-2. Example of Solid Field Test Pattern (Red).............................................................................. 262-3. Example of Fixed Step Horizontal Ramp Test Pattern ................................................................ 272-4. Example of Fixed Step Vertical Ramp Test Pattern ................................................................... 282-5. Example of Horizontal Lines Test Pattern .............................................................................. 292-6. Example of Vertical Lines Test Pattern.................................................................................. 302-7. Example of Diagonal Lines Test Pattern ................................................................................ 312-8. Example of Grid Lines Test Pattern ..................................................................................... 322-9. Example of Checkerboard Test Pattern ................................................................................. 332-10. Example of Color Bars Test Pattern .................................................................................... 342-11. Short Axis Flip .............................................................................................................. 422-12. Bit Weight and Bit Order for Duty Cycle Data ......................................................................... 552-13. Pillar-Box Border Example ................................................................................................ 922-14. Bit Order and Definition for System Temperature .................................................................... 109

List of Tables2-1. Summary of Settings for Power up Associated Signals ................................................................ 72-2. I2C Write and Read Transactions ........................................................................................ 102-3. Supported TI Generic Commands ....................................................................................... 112-4. Source-Specific Associated Commands ................................................................................ 142-5. Common Commands ...................................................................................................... 152-6. Foreground and Background Color Use ................................................................................ 242-7. Descriptions and Bit Assignments for Parameters 1-4 ................................................................ 252-8. Number of Bytes Required based on Pattern Selection .............................................................. 252-9. Splash Screen Header Definitions ...................................................................................... 382-10. Partial List of Commands that may Benefit from use of Image Freeze ............................................ 472-11. TPG Example Using Image Freeze ..................................................................................... 472-12. Test Pattern Generator Example using Image Freeze ............................................................... 472-13. 3-D Reference Source Applicability for Display Data Ports .......................................................... 502-14. List of Commands Excluded from Batch File Use ..................................................................... 582-15. Input Source Limits for Active Data ...................................................................................... 592-16. Available Commands Based on LED Control Method................................................................. 742-17. Bit Weight Definition for LABB Gain Value ............................................................................. 862-18. Bit Weight Definition for the CAIC Maximum Gain Value ............................................................. 882-19. Bit Weight Definition for the CAIC Clipping Threshold Value......................................................... 882-20. Bit Weight Definition for the CAIC RGB Intensity Gain Values....................................................... 882-21. ASIC Device ID Decode ................................................................................................. 1072-22. 2nd Command Parameter for Partial Flash Data Set Updates (Writes)........................................... 1182-23. Additional Command Parameters for Partial Flash Data Set Reads .............................................. 1182-24. LUT Mailbox Packing Information ...................................................................................... 128

3DLPU035–August 2015 List of FiguresSubmit Documentation Feedback


http://www.ti.com


FLASH, SDRAM

Keypad

Included in DLP® Chip Set

PROJ_ON

eDRAM

Flash

Projector Module Electronics

Non-TI components

I2C

28Parallel

Front-EndChip

- OSD- AutoLock - Scaler- KS Corr.- µController

HOST_IRQ

DLPC3439

SPI_0

HDMI Receiver

Triple ADC

DC Supplies

ChargerDC_IN

BAT+ ±

6-20VDC

VDD

On/Off

RESETZ

eDRAM

INTZPARKZ

SPI_0

Parallel

Sub-LVDS DATA

LS_RDATA

1.1V

1.8V

VCORE

VIO

VCC_INTF

VCC_FLSH

1.1V1.8V

VCOREVIO

VCC_INTF

VCC_FLSH

HDMI

VGA

I2C_1

I2C_2

I2C_1

SD Card Reader, Video

Decoder, etc.

DSI I/F, CPU I/F, and BT656 I/F are not supported for dual ASIC.

LED_SEL(2)

WVGADDR DMD

1080PDMD

RESETZ

CMP_PWM

PROJ_ON

CMP_OUT

INTZ

Illumination

Optics

3VBIAS, VRST, VOFS

Thermistor

LABB

4

L3SYSPWR

1.1VReg

L1

L2

VLED

BLUEGREEN

RED

CurrentSense

WPC

GPIO_8 (Normal Park)1.8V VSPI

PARKZ

SPI_1

Sub-LVDS DATACTRL

L41.8VReg

L6Fan

Drive

DLPC3439

DLPA3000

PAD Control

L7Fan

DriveFan #1

Fan #2

3.3V (to front-end chip)2.5V (to front-end chip)

LDO#1LDO#2

GPIO_14-19Image Sync

L5SpareFan #3 or programmable DC supply

1.8V for DMD and DPP3439s

1.1V for DPP3439sVIN

3DR

3D L/R (GPIO_09)

3DRFlash

Oscillator

Chapter 1DLPU035–August 2015

Introduction

1.1 Software Programmer’s Guide OverviewThis guide details the software interface requirements for a DLPC3439 DUAL ASIC based system. Itdefines all applicable communication protocols including I2C, initialization, default settings and timing. TheDLPC3439 system can be used in accessory products with LED controller DLPA3000 or DLPA3005 inFigure 1-1 and Figure 1-2.

Figure 1-1. DLPC3439 Accessory Configuration with DLPA3000

Composer is a trademark of Texas Instruments Inc..

4 Introduction DLPU035–August 2015Submit Documentation Feedback



FLASH, SDRAM

Keypad

Included in DLP® Chip Set

PROJ_ON

eDRAM

Flash

Projector Module Electronics

Non-TI components

I2C

28Parallel

Front-EndChip

- OSD- AutoLock - Scaler- KS Corr.- uController

HOST_IRQ

DLPC3439

SPI_0

HDMI Receiver

Triple ADC

DC Supplies

ChargerDC_IN

BAT+ ±

6-20VDC

VDD

On/Off

RESETZ

eDRAM

Flash

INTZPARKZ

SPI_0

Parallel

Sub-LVDS DATA

LS_RDATA

1.1V

1.8V

VCORE

VIO

VCC_INTF

VCC_FLSH

1.1V1.8V

VCOREVIO

VCC_INTF

VCC_FLSH

HDMI

VGA

I2C_1

I2C_2

I2C_1

SD Card Reader, Video

Decoder, etc.

DSI I/F, CPU I/F, and BT656 I/F are not supported for dual ASIC.

LED_SEL(2)

WVGADDR DMD

1080PDMD

RESETZ

CMP_PWM

PROJ_ON

CMP_OUT

INTZ

Illumination

Optics

3VBIAS, VRST, VOFS

Thermistor

LABB

4

L3SYSPWR

1.1VReg

L1

L2 RLIM Current Sense

WPC

GPIO_8 (Normal Park)1.8V VSPI

PARKZ

SPI_1

Sub-LVDS DATACTRL

L41.8VReg

L6Fan

Drive

DLPC3439

DLPA3005

PAD Control

L7Fan

DriveFan #1

Fan #2

3.3V (to front-end chip or other)

2.5V (to front-end chip or other)

LDO#1

LDO#2

GPIO_14-19Image Sync

L5SpareFan #3 or programmable DC supply

1.8V for DMD and DPP3439s

1.1V for DPP3439sVIN

SYSPWRVLED

FB

FB

Five External

FETs

3DR

3D L/R (GPIO_9)

3DR

Oscillator

www.ti.com Software Programmer’s Guide Overview

Figure 1-2. DLPC3439 Accessory Configuration with DLPA3005

1.1.1 I2C-Based Command Data InterfaceThe legacy interface configurations make use of an I2C interface for commands (conforming to the PhilipsI2C specification, up to 400 KHz) and a 24-bit parallel interface.

Note: Currently, we only support I2C speed of up to 100 kHz.

5DLPU035–August 2015 IntroductionSubmit Documentation Feedback


http://www.ti.com


Software Programmer’s Guide Overview www.ti.com

6 Introduction DLPU035–August 2015Submit Documentation Feedback


http://www.ti.com


Chapter 2DLPU035–August 2015

Interface Specification

2.1 Electrical InterfaceThis section discusses the requirements for a number of interface signals that are not command or databusses. These signals are used for different boot options.

2.1.1 System Power-up Associated Signals

2.1.1.1 EXT-BOOT-ENThe EXT-BOOT-EN signal is used by the ASIC hardware at system power-up to determine whether theinternal boot application, or an external boot application (located in FLASH), is to be used during the ASICinitialization process. This is discussed further in Section 2.2.

2.1.1.2 DIS-PGM-LDThe DIS-PGM-LD signal is used by the boot application during system power-up to direct the function ofthe system boot application during the ASIC initialization process. This is discussed further in Section 2.2.

2.1.1.3 SPI-FLS-ENThe SPI-FLS-EN signal is used by the boot application during system power-up to direct the function ofthe system boot application during the ASIC initialization process. This is discussed further in Section 2.2.

2.1.1.4 High-Level DefinitionAs noted, a more detailed discussion of these signals is provided in Section 2.2; however, a briefsummary is in Table 2-1.

Table 2-1. Summary of Settings for Power up Associated Signals (1)

EXT-BOOT-EN DIS-PGM-LD SPI-FLS-EN Use/Definition0 0 0 Normal Flash Operation0 0 1 SPI Flashless Operation0 1 0 Bad Flash Flashless Operation0 1 1 N/A1 0 0 TI Debug1 0 1 N/A1 1 0 TI Debug1 1 1 N/A

(1) TI only supports Normal Flash Operation for DLPC3439.

7DLPU035–August 2015 Interface SpecificationSubmit Documentation Feedback



System Initialization www.ti.com

2.2 System InitializationThis section discusses the methodologies used for system initialization.

2.2.1 Boot ROM ConceptIn the DLPC3439, a boot ROM, with associated boot software, will be employed. This resident boot codewill consist of the minimum code needed to complete the various tasks required based on the state of theDIS-PGM-LD (Disable Program Load) pin and the SPI-FLS-EN (SPI Flashless Enable) pin.

2.2.2 Internal vs External Boot SoftwareIn the DLPC3439, the state of the EXT-BOOT-EN (External Boot Enable) pin allows the external user tospecify whether the hardware points the microprocessor to the internal boot ROM for the boot application(EXT-BOOT-EN = 0), or points it to an external FLASH for the boot application (EXT-BOOT-EN = 1).Allowing for the use of an external boot program in FLASH is to provide for debug and boot codedevelopment purposes only (since uP code execution out of serial flash will be extremely slow).

2.2.3 Flash and Flashless Product ConfigurationsFor most DLPC3439 product configurations, an external FLASH device will be used to store the mainapplication code, along with all of the other configuration and operational data required by the system fornormal operation.

In certain applications it may be desirable to eliminate this external FLASH part (for cost reasons). Inthese Flashless configurations, the expectation is that the main application code will be downloaded (bycommand) to iRAM by the Boot Application via the SPI port. All other configuration and operational datanormally obtained from Flash will be obtained by the Main Application code via the SPI port.

For all discussions in this document, unless stated otherwise, it is assumed that an external FLASH devicewill be used.

2.2.4 Resident Boot Software (EXT-BOOT-EN = 0)As noted previously, an internal boot ROM, with associated boot software, will be employed. This residentboot code will consist of the minimum code needed to complete the various tasks required based on thestate of the DIS-PGM_LD and SPI-FLS_EN pins (with EXT-BOOT-EN = ‘0’). An overview of these tasks isshown in Figure 2-1.

8 Interface Specification DLPU035–August 2015Submit Documentation Feedback


http://www.ti.com


EXT-BOOT-EN = 1

System Power-Up

DIS-PGM-LD = 1

Enable DSI Port

DSICmd

New full Flash image programmed in Flash

New main app loaded into iRAM

Start FDMA

FDMADone

Give Main app execution control

Done

DSICmd

Done

DSICmd

Interrupt w/ ICE to push

new software

DSI FlashlessConfiguration

Main Application Disabled: In the DSI NO FLASH case, the boot code is always responsible for receiving the main app via DSI and loading into iRAM. Control is then transferred (by DSI cmd) to the main app. (The main app is responsible for requesting all register data via the DSI port, along with the subsequent distribution of this data throughout the ASIC)

No

Yes

No

Yes

Yes

Yes

Yes

Yes

No

Yes

No

No

No

YesNo

No

Main Application Disabled: In this FLASH case, the main app is corrupted (for example). The boot code is responsible for receiving the entire flash build via DSI and programming entire build into Flash. Once done, the host must set the DSI-PGM-LD pin low and reset the system to allow for normal operation.

Normal operational mode: In this FLASH case, the boot code is responsible for transferring the main app from Flash (via FDMA) into iRAM. Control is then transferred to the main app.

External Boot Code: In this FLASH case, the internal boot code is corrupted (for example) and external boot code in Flash must be used. In one case, external Flash boot code to transfer main app from Flash to iRAM via FDMA. Control is then transferred to the main app. In other case, external boot code waits in NOP loop for ICE box

For lab use, the ICE box can be connected via JTAG, allowing a new main app to be loaded into iRAM while boot is waiting for DSI commands or is in a small NOP loop

Boot Code Flow Chart

DIS-PGM-LD = 1NoYes

Loop

Interrupt w/ ICE to push new software

Setup FDMA(Main App from Flash to iRAM)

- Send Data CMD- Read Data- UCA to iRAM

No



Erase Entire Flash

DoneNo

Yes

Everything in this box is handled by code in an external flash. This is NOT in the internal Boot Code

Decision made by HW

Setup SPI Interface for UCA Operation

SPI FlashlessConfiguration

SPI-FLS-EN = 1No Yes

Yes

Setup FDMA(Main App from Flash to iRAM)

FDMADone

No

Start FDMA


Yes

No

Verify Flash Programmed(ID = ³)7$%´)

³)7$%´

Setup SPI Interface (Flash Parameters)

Normal FLASHConfiguration

Interrupt w/ ICE to push

new software

Send Data Request (address

& length)

Yes

No

Send Status Request

DataReady?

DataDone?

Has all of Main App been Received?

Yes

NoMain

Done?

Main Application Disabled: In the SPI NO FLASH case, the boot code is always responsible for receiving the main app via SPI and loading into iRAM. Control is then transferred (by Boot Code) to the main app. (The main app is responsible for requesting all register data via the SPI port, along with the subsequent distribution of this data throughout the ASIC) - Normal Flash

Configuration - Boot Replaces Corrupted Flash via DSI

EXTERNALSet DSI-PGM-LD = 0

Power Cycle or System Reset

Send Status Request

Yes

NoHostReady?

Check GPIO(2:1) for number of DSI

Data Lanes

www.ti.com System Initialization

Figure 2-1. Boot Code Flow Chart



http://www.ti.com


Software Interface www.ti.com

2.2.4.1 DIS-PGM-LD = 0 (With EXT-BOOT-EN = 0)

2.2.4.1.1 SPI-FLS-EN = 0This should be the normal operational mode of the boot application for a Flash based productconfiguration during normal ASIC use.

2.2.4.1.2 SPI-FLS-EN = 1This should be the normal operational mode of the boot application for an SPI Flashless based productconfiguration during normal ASIC use. In this case, the boot application will expect to get the mainapplication from the host via the SPI port in response to TI command requests. The only SPI interfaceinstructions that will be supported by the boot code are associated with requesting and read data from thehost via this port.

2.3 Software InterfaceIn general, there will be one set of software commands supported by the DLPC3439 DUAL ASIC. Thiscustom set of TI specific commands will be applicable for use on I2C command interface.

2.3.1 Software Command PhilosophyWith DLPC3439, all commands via I2C will be processed by software. As such, no commands will directlyaddress or access ASIC registers, ASIC mailboxes, or any attached flash parts. All commands will be of ahigh level, more abstract nature, decoupling the OEM from the internal hardware of the ASIC.

2.3.2 I2C Considerations

2.3.2.1 I2C TransactionsSince all I2C commands will be processed by software, there is just one type of I2C transaction to besupported. This transaction type is shown in Table 2-2 for both writes and reads. It should be noted thatthe I2C interface is able to support variably sized transactions (that is, a one byte transaction, a nine bytetransaction) to match the TI commands discussed later in this document.

Table 2-2. I2C Write and Read Transactions

Transaction Address (1) Sub-Address (2) Remaining Data Bytes (3)

Write 8-bits 8-bits 8-bit parameter bytes (0 -> N)36h (or 3Ah) Command Value Parameter Values

Read Request 8-bits 8-bits 8-bit parameter bytes (0 -> N)36h (or 3Ah) Command Value Parameter Values

Read Response 8-bits 8-bit parameter bytes (0 -> N)37h (or 3Bh) Parameter Values

(1) The address corresponds to the chip address of the ASIC.(2) The sub-address will correspond to a TI command.(3) The data (if present) will correspond to any required command parameters.

2.3.2.2 Data Flow ControlWhile the I2C interface inherently supports flow control by holding the clock, this will likely not be sufficientfor all transactions (sequence and CMT updates for example). In this case, the host software should makeuse of the Read Short Status to determine if the system is busy.



http://www.ti.com


www.ti.com Software Interface

2.3.3 List of System Write/Read Software CommandsThe commands supported by the IC interfaces are discussed in the following sections.

2.3.3.1 List of TI-Specific Generic Commands

Table 2-3. Supported TI Generic Commands

Command OpCodeCommand Description Reset Value Default Action Page #Type (hex)General OperationWrite Write Input Source Select 1 05 Test Pattern 21Read Read Input Source Select 06 25Write Write External Video Source Format Select 43h 07 RGB888 26Read Read External Video Source Format Select 08 27

Write External Video Chroma Processing 28Write 0 09 Chroma InterpolationSelectRead External Video Chroma Processing 30Read 0ASelect

Write Write Test Pattern Select 7000h 0B White Solid Field 30Read Read Test Pattern Select 0C 43Write Write Splash Screen Select 0D Composer Specified 44Read Read Splash Screen Select 0E 46Read Read Splash Screen Header 0F 47Write Write Image Crop ffffffff00000000h 10 No Crop 49Read Read Image Crop 11 50Write Write Display Size DMD Res 12 51Read Read Display Size 13 53Write Write Display Image Orientation 14 Composer Specified 54Read Read Display Image Orientation 15 56Write Write Display Image Curtain 1 16 Black 57Read Read Display Image Curtain 17 58

Unused 18-19Write Write Image Freeze 0 1A No Freeze 59Read Read Image Freeze 1B 62Write Write 3-D Control 0 20 Automatic 63Read Read 3-D Control 21 65Write Write LOOK Select 22 Composer Specified 66Read Read LOOK Select 23 67Read Read Sequence Header Attributes 26 68Write Write Degamma/CMT Select 27 Composer Specified 70Read Read Degamma/CMT Select 28 71Write Write CCA Select 29 Composer Specified 72Read Read CCA Select 2A 73Write Write Execute Batch File 0 2D 74Write Write External Input Image Size DMD Res 2E 76Read Read External Input Image Size 2F 78Write Write 3-D Reference 0 30 Next Frame Left 79Write Write GPIO[19:00] Control 31 Composer Specified 80Read Read GPIO[19:00] Control 32 83Write Write GPIO[19:00] Outputs 33 Composer Specified 86Read Read GPIO[19:00] Outputs 34 90



http://www.ti.com



Table 2-3. Supported TI Generic Commands (continued)Command OpCodeCommand Description Reset Value Default Action Page #Type (hex)

Write Write Splash Screen Execute 35 92Read Read GPIO[19:00] Inputs 36 93Write Write External Parallel I/F Data Mask Control 0 37 94Read Read External Parallel I/F Data Mask Control 38 96

Unused 39-4FIllumination ControlWrite Write LED Output Control Method 50 Composer Specified 97Read Read LED Output Control Method 51 99Write Write RGB LED Enable 7h 52 Enabled 100Read Read RGB LED Enable 53 101Write Write RGB LED Current 54 Composer Specified 102Read Read RGB LED Current 55 104Read Read CAIC LED Max Available Power 57 105Write Write RGB LED Max Current 5C Composer Specified 106Read Read RGB LED Max Current 5D 107Read Read Measured LED Parameters 5E 107Read Read CAIC RGB LED Current 5F 109Image Processing Control

Manual Strength 110Write Write Local Area Brightness Boost Control 1 80 ControlRead Read Local Area Brightness Boost Control 81 111Write Write CAIC Image Processing Control 84 Composer Specified 112Read Read CAIC Image Processing Control 85 115Write Write CCA Control 1 86 Enabled 116Read Read CCA Control 87 117Write Write Border Color 0 B2 Black 118Read Read Border Color B3 120Write Write External Parallel I/F SYNC Polarity 0 B6 0 121Read Read External Parallel I/F SYNC Polarity B7 122

Write External Parallel I/F Manual Image 123Write 0 B8 DisabledFramingRead Read External Parallel I/F Manual Image B9 124

FramingRead Read Auto Framing Information BA 125Administrative CommandsRead Read Short Status D0 126Read Read System Status D1 128Read Read System Software Version D2 133Read Read Communication Status D3 134Read Read ASIC Device ID D4 137Read Read DMD Device ID D5 138Read Read System Temperature D6 139Read Read Flash Build Version D9 140Write Write Batch File Delay DB Composer Specified 141Read Read DMD I/F Training Data DC 141Read Flash Update PreCheck DD 145Write Flash Data Type Select 0 DE Entire Flash 147Write Flash Data Length 0 DF 151



http://www.ti.com



Table 2-3. Supported TI Generic Commands (continued)Command OpCodeCommand Description Reset Value Default Action Page #Type (hex)

Write Erase Flash Data E0 152Write Write Flash Start E1 153Write Write Flash Continue E2 153Read Read Flash Start E3 154Read Read Flash Continue E4 156Write Write Internal Register Address 0 E5 157Write Write Internal Register E6 158Read Read Internal Register E7 159Write Write Internal Mailbox Address 0 E8 160Write Write Internal Mailbox E9 163Read Read Internal Mailbox EA 164Write Write External PAD Address 0 EB 165Write Write External PAD Data EC 167Read Read External PAD Data ED 168

Reserved F8-FF



http://www.ti.com



2.3.3.2 Write Input Source Select (05h)

2.3.3.2.1 WriteThis command is used to select the image input source for the display module.

2.3.3.2.2 Write ParametersThe command parameter descriptions follow:

Parameter Bytes DescriptionByte 1 See Below

msb Byte 1 lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:2) Reserved–

b(1:0) Input Source–

0h: External Video Port1h: Test Pattern Generator2h: Splash Screen3h: Reserved

Default: 01h

Note 1: When selecting the External Video Port, there is a set of associated commands that are onlyapplicable to this source selection. These associated commands are the Write External InputImage Size (Section 2.3.3.33), the Write External Video Source Format Select(Section 2.3.3.4), the Write External Video Chroma Processing Select (Section 2.3.3.6), theWrite External Parallel I/F Manual Image Framing (Section 2.3.3.42), and Write External CPUI/F Video Sync Method commands.When selecting the Test Pattern Generator, there is one associated command that is onlyapplicable to this source selection. This associated command is the Write Test Pattern Select(Section 2.3.3.8) command.When selecting the Splash Screen, there are two associated commands that are onlyapplicable to this source selection. These associated commands are the Write Splash ScreenSelect (Section 2.3.3.10) and Write Splash Screen Execute (Section 2.3.3.40) commands.

These associations are also shown in Table 2-4.

Table 2-4. Source-Specific Associated Commands

Input Source Select OptionsSource Specific Associated Commands External Video Port Test Pattern Generator Splash Screen (1)

Write External Video Source Format Select Only N/A N/AWrite External Video Chroma Processing Select Only N/A N/AWrite External Input Image Size Only N/A N/AWrite External Parallel I/F Manual Image Framing Only N/A N/AWrite Test Pattern Select N/A Only N/AWrite Splash Screen Select N/A N/A OnlyWrite Splash Screen Execute N/A N/A Special

(1) The Write Splash Screen Execute command is special in that there is no maintained state or history. Thus, this command has nosettings to be stored and reused by the system.



http://www.ti.com



These commands (except for Write Splash Screen Execute ) describe the unique characteristics of theirassociated source, and once these settings have been defined, the system will store them. Then, eachtime an input source selection is made (using the Write Input Source Select command), the system willremember the settings described by the commands associated with the selected source and automaticallyapply them. As such, the user only needs to send these associated commands when the source firstneeds to be defined, or when the source characteristics for that port need to be changed. It is important tonote that the appropriate associated commands must be updated when source characteristics do change.

If the user wants to send source associated commands each time an input source selection is made, thisis allowed. In this case, it is recommended that the source associated commands be sent prior to sendingthe Write Input Source Select command. When source associated commands are sent when that sourceis not active, the ASIC software will save the new settings, but will not execute these commands. Whenthat source becomes active (via the Write Input Source Select command), the ASIC will apply these newsettings. An example is shown below:1. User sends the following commands (active Input Source = Test Pattern Generator)

(a) Write Image Freeze = Freeze(b) Write External Video Source Format Select (settings stored, command not executed)(c) Write External Video Chroma Processing Select (settings stored, command not executed)(d) Write External Input Image Size (settings stored, command not executed)(e) Write Input Source Select = External Port (See b, below)(f) Write Image Freeze = Unfreeze

2. When the Write Input Source Select command is received, software will apply the settings from theseExternal Video Port associated commands.(a) External Video Source Format Select(b) External Video Chroma Processing Select(c) External Input Image Size(d) External Parallel Manual Image Framing (as appropriate – that is, if parallel port selected)(e) External CPU Video Sync Mode (as appropriate – that is, if CPU port selected)

If source associated commands are sent for a source that is already active, the ASIC software will executethese commands when received. An example is shown below:1. User sends the following commands (active Input Source = External Video Port)

(a) Write Image Freeze = Freeze(b) Write External Video Source Format Select (command executed)(c) Write External Video Chroma Processing Select (command executed)(d) Write Image Freeze = Unfreeze

Note 2: The rest of the commands that apply to image setup are those commands whose settings areapplicable across all source selections, and indeed, these command settings would typicallyremain the same across the three Input Source selections. A few examples are Write DisplaySize and Write Display Image Orientation. A more representative list of these commands isshown in Table 2-5.

Table 2-5. Common Commands

Input Source Select OptionsCommon Commands External Video Port Test Pattern Generator Splash Screen

Write Image Crop Common Common CommonWrite Display Image Size Common Common CommonWrite Display Image Orientation Common Common CommonWrite Display Image Curtain Common Common CommonWrite Look Select Common Common Common



http://www.ti.com



Table 2-5. Common Commands (continued)Input Source Select Options

Common Commands External Video Port Test Pattern Generator Splash ScreenWrite Sequence Select Common Common CommonWrite Local Area Brightness Boost Control Common Common CommonWrite CAIC Image Processing Control Common Common Common

It is important to note that while the values for these commands may be the same across thedifferent input source types, this does not mean that hardware settings will not change (Hereis one example: Display Image Size = 1080p = DMD size – The external port input source sizeis WXGA which is scaled up to the display size of 1080p. If the user changes to the TPG InputSource, our rule is that the size of the test pattern is to match the size of the DMD. Therefore,the scaler settings would have to be changed). The ASIC software is responsible formanaging the underlying hardware settings. This also applies to those commands whichspecify automatic operation (for example, Write Idle Mode Select = Auto Idle Mode Enable).While the setting of automatic would remain the same, the actual underlying algorithm mightchange its settings based on the characteristic of the selected source.

Note 3: The user is required to specify the active data size for all external input sources using theWrite Input Image Size (Section 2.3.3.33) command. In addition, for input image data on theParallel bus that does not provide data framing information, the user is required to providemanual framing data using the Parallel I/F Manual Image Framing command(Section 2.3.3.42).

Note 4: When a test pattern is selected, it will be generated at the resolution of the DMD, modified bythe settings specified by the Write Image Crop command (Section 2.3.3.13), and displayed atthe resolution specified by the Write Display Size command (Section 2.3.3.15).

Note 5: The user should see the Write Image Freeze command (Section 2.3.3.21) for information onhiding on-screen artifacts when selecting an input source



http://www.ti.com



2.3.3.3 Read Input Source Select (06h)

2.3.3.3.1 ReadThis command is used to read the state of the image input source for the display module.

2.3.3.3.2 Read ParametersThis command has no command parameters.

2.3.3.3.3 Return ParametersThe return parameters are described below.



b(7:2) – Reserved

b(1:0) – Input Source0h: External Video Port1h: Test Pattern Generator2h: Splash Screen3h: Reserved



http://www.ti.com



2.3.3.4 Write External Video Source Format Select (07h)

2.3.3.4.1 WriteThis command is used to specify the active external video port and the source data type for the displaymodule.


Parameter Bytes DescriptionByte 1 See CMD Parameter Below

CMD Port Bits/Pixel Data Type Bus Width Clks/Pixel Note (3)ParameterParallel Port User Selection

40h Parallel 16 RGB565 16 1 Auto-select RGB CSC41h Parallel 18 RGB 666 18 1 Auto-select RGB CSC42h Parallel 24 RGB 888 8 3 Auto-select RGB CSC43h Parallel 24 RGB 888 24 1 Auto-select RGB CSC

50h Parallel 18 YCbCr 666 18 1 Auto-select YCbCr CSC51h Parallel 24 YCbCr 888 24 1 Auto-select YCbCr CSC

Auto-select YCbCr CSC60h Parallel 16 YCbCr 4:2:2 88 8 2 Auto-select 4:2:2 -> 4:4:4Auto-select YCbCr CSC61h Parallel 16 YCbCr 4:2:2 88 16 1 Auto-select 4:2:2 -> 4:4:4

Default: 43h

Note 1: This command is used in conjunction with the Write Input Source Select command(Section 2.3.3.2). This command specifies which input port is to be displayed when the WriteInput Source Select command selects External Video Port as the image source. The settingsfor this command will be retained until changed using this command. These settings will beautomatically applied each time the External Video Port is selected.

Note 2: When the external video port is selected as the input source, software will automatically selectand load the proper CSC based on the selected parameter of this command (appropriatematrix for RGB, selected matrix for YCbCr including offset). It will also automatically select theappropriate data path for 4:2:2 vs. 4:4:4 processing. It should be noted that the OEM isresponsible for ensuring the appropriate source Chroma parameters are set using the WriteExternal Video Chroma Processing Select command (Section 2.3.3.6).

Note 3: It is important that the user review the notes for the Write Input Source Select command inSection 2.3.3.2 to understand the concept of source associated commands. This concept willdetermine when source associated commands are executed by the system. Note that thiscommand is a source associated command.



http://www.ti.com



2.3.3.5 Read External Video Source Format Select (08h)

2.3.3.5.1 ReadThis command is used to read the state of the active external video port and the source data type for thedisplay module.



Parameter Bytes DescriptionByte 1 See CMD Parameter Below

CMD Parameter Port Bits/Pixel Data Type Bus Width Clks/Pixel Notes (3)Parallel Port User Selection

40h Parallel 16 RGB565 16 1 Auto-select RGB CSC41h Parallel 18 RGB 666 18 1 Auto-select RGB CSC42h Parallel 24 RGB 888 8 3 Auto-select RGB CSC43h Parallel 24 RGB 888 24 1 Auto-select RGB CSC

50h Parallel 18 YCbCr 666 18 1 Auto-select YCbCr CSC51h Parallel 24 YCbCr 888 24 1 Auto-select YCbCr CSC

60h Parallel 16 YCbCr 4:2:2 88 8 2 Auto-select YCbCr CSCAuto-select 4:2:2 -> 4:4:4

61h Parallel 16 YCbCr 4:2:2 88 16 1 Auto-select YCbCr CSCAuto-select 4:2:2 -> 4:4:4



http://www.ti.com



2.3.3.6 Write External Video Chroma Processing Select (09h)

2.3.3.6.1 WriteThis command is used to specify the characteristics of the selected YCbCr source, as well as specifyingthe type of chroma processing to be used for this YCbCr source by the display module.


Parameter Bytes DescriptionByte 1 See BelowByte 2 See Below


b(7:5) – Reserved

b(4) – Chroma Interpolation Method0h: Chroma Interpolation1h: Chroma Copy2h: Splash Screen3h: Reserved

b(3) – Reserved

b(2) – Chroma Channel Swap0h: CbCr1h: CrCb

b(1:0) – Reserved

Byte 1 Default: 00h


b(7:2) – Reservedb(1:0) – CSC Coefficient Set (Color Space)

Byte 2 Default: 00h

Note 1: This command is used in conjunction with the Write Input Source Select command(Section 2.3.3.2). The settings for this command will be retained until changed using thiscommand. These settings will be automatically applied each time the External Video Port isselected.

Note 2: The system will assume RGB sources have a dynamic range of 0 to 255, with an offset of 0.

Note 3: Bits 3:0 for Byte 1 are used to specify the characteristics for the current YCbCr source. Bits 7:4for Byte 1, as well as Byte 2, are used to specify the type of processing to be done on thecurrent YCbCr source.

Note 4: CSC coefficient sets are stored in Flash until needed.



http://www.ti.com



Note 5: CSC coefficient sets are specified in Byte 2 by an enumerated value (such as 0, 1, 2, or 3).The set stored in ‘0' is ITU-R BT. Rec. 601. The other three sets are customer definable viaComposer™.It should be noted that regardless of the setting for this command, set 0 will always be used forthe conversion of Splash Screen images stored as YCbCr (since this is the CSC that is used byComposer to convert from RGB to YCbCr). This will be done internally by TI software, and thesetting of this command will not be changed.


Note 7: Luma Offset and YCbCr Dynamic Range are to be specified at the beginning of the CSCcoefficient set by Composer.



http://www.ti.com



2.3.3.7 Read External Video Chroma Processing Select (0Ah)

2.3.3.7.1 ReadThis command is used to read the specified characteristics for the selected YCbCr source, as well as thetype of chroma processing being used for this YCbCr source by the display module.



Parameter Bytes DescriptionByte 1 See BelowByte 2 See Below


b(7:5) – Reserved

b(4) – Chroma Interpolation Method0h: Chroma Interpolation1h: Chroma Copy

b(3) – Reserved

b(2) – Chroma Channel Swap0h: CbCr1h: CrCb

b(1:0) – Reserved


b(7:0) – CSC Coefficient Set



http://www.ti.com



2.3.3.8 Write Test Pattern Select (0Bh)

2.3.3.8.1 WriteThis command is used to specify an internal test pattern for display on the display module.


Parameter Bytes DescriptionByte 1 TPG Pattern Select (See Below)Byte 2 Foreground / Background Color (See Below and Table 2-6)Byte 3 Parameter 1 (See Table 2-7)Byte 4 Parameter 2 (See Table 2-7)Byte 5 Parameter 3 (See Table 2-7)Byte 6 Parameter 4 (See Table 2-7)


b(7) – Test Pattern Border00h: Disabled01h: Enabled

b(6:4) – Reserved

b(3:0) – Left Pattern Select00h: Solid Field01h: Fixed Step Horizontal Ramp02h: Fixed Step Vertical Ramp03h: Horizontal Lines04h: Diagonal Lines05h: Vertical Lines06h: Horizontal and Vertical Grid07h: Checkerboard08h: Color Bars09h-0Fh: Reserved

Byte 1 Default: 00h


b(7) – Reserved

b(6:4) – Foreground Color0h: Black1h: Red2h: Green3h: Blue



http://www.ti.com



4h: Cyan5h: Magenta6h: Yellow7h: White

b(3) – Reserved

b(2:0) – Background Color0h: Black1h: Red2h: Green3h: Blue4h: Cyan5h: Magenta6h: Yellow7h: White

Table 2-6. Foreground and Background Color Use

Byte 2Pattern Foreground Background

Color ColorSolid Field Yes NoFixed Step Horizontal Ramp Yes NoFixed Step Vertical Ramp Yes NoHorizontal Lines Yes YesVertical Lines Yes YesDiagonal Lines Yes YesGrid Lines Yes YesCheckerboard Yes YesColor Bars No No

Byte 2 Default: 70h



http://www.ti.com



Table 2-7. Descriptions and Bit Assignments for Parameters 1-4Byte 6 Byte 5 Byte 4 Byte 3

(Parameter 4) (Parameter 3) (Parameter 2) (Parameter 1)

Pattern Description Bits Description Bits Description Bits Description Bits

Solid Field n/a n/a n/a n/a

Fixed Step n/a n/a End Value 8 Start Value 8Horizontal Ramp

Fixed Step n/a n/a End Value 8 Start Value 8Vertical Ramp

Horizontal Lines n/a n/a Background Line Width 8 Foreground Line Width 8

Vertical Lines n/a n/a Background Line Width 8 Foreground Line Width 8

Diagonal Lines n/a n/a Vertical Spacing 8 Horizontal Spacing 8

Vertical Background Vertical Foreground Horizontal Background Line Horizontal Foreground LineGrid Lines 8 8 8 8Line Width Line Width Width Width

Number of Vertical Number of Vertical Number of Horizontal Number of HorizontalCheckerboard 3 8 3 8Checkers Checkers Checkers Checkers

Color Bars n/a n/a n/a n/a

Note 1: This command is used in conjunction with the Write Input Source Select command(Section 2.3.3.2). This command specifies which test pattern is to be displayed when the WriteInput Source Select command selects Test Pattern Generator as the image source. Thesettings for this command are to be retained until changed using this command. These settingswill be automatically applied each time the Test Pattern Generator is selected.

Note 2: Write Execute Batch files (Section 2.3.3.32) can be created and stored in Flash and used torecall the settings for predefined test patterns.

Note 3: Test Patterns will be created at the resolution of the display (DMD), however, they can bemodified by the Write Image Crop command (Section 2.3.3.13), and will be displayed at theresolution specified by the Write Display Size command (Section 2.3.3.15).

Note 4: Test Patterns will be displayed at the frame rate of 60 Hz.

Note 5: The Test Pattern border selection creates a single pixel wide/tall white border around thespecified test pattern.


Note 7: When a Foreground or Background Color is not used, the bit values will be ignored (SeeTable 2-6). If both Foreground and Background Color are not used, or when a Parameter Byte(Bytes 3 thru 6) is not used, the byte should not be sent. This is shown in Table 2-8, whichshows the number of bytes required based on the specified pattern.

Table 2-8. Number of Bytes Required based on Pattern Selection

Specified Solid Fixed Step Fixed Step Horz Checker ColorVert Lines Diag Lines Grid LinesPattern Field Horz Ramp Vert Ramp Lines board BarsNumber of

Bytes 2 4 4 4 4 4 6 6 1Required

Note 8: As noted in Table 2-6 the color for the Solid Field pattern is specified using the Foregroundcolor. An example of a Solid Field pattern is shown in Table 2-8.



http://www.ti.com



Figure 2-2. Example of Solid Field Test Pattern (Red)



http://www.ti.com



Note 9: As noted in Table 2-6, the color for the Fixed Step Horizontal Ramp pattern is specified usingthe Foreground color. As noted in Table 2-7, the user specifies the start value and the stopvalue for the ramp. For this pattern, the system will automatically determine the step sizebased on the start/stop values and the size of the display (DMD). The minimum start value =0, the maximum stop value = 255, and the start value must always be smaller than the stopvalue. As an example, if the start value = 0, the stop value = 255, and the DMD resolution is1280 wide – the step size would be 5 (1280 pixels / 256 values = 5). Thus every gray shadevalue from 0 to 255 would have a step size of 5 pixels (that is, each step would have 5columns of pixels with the same gray scale value). The gray scale value always increments by1 for each step between the start and stop values. An example of a Fixed Step HorizontalRamp pattern is shown in Table 2-6.

Figure 2-3. Example of Fixed Step Horizontal Ramp Test Pattern



http://www.ti.com



Note 10: As noted in Table 2-6, the color for the Fixed Step Vertical Ramp pattern is specified usingthe Foreground color. As noted in Table 2-7, the user specifies the start value and the stopvalue for the ramp. For this pattern, the system will automatically determine the step sizebased on the start/stop values and the size of the display (DMD). The minimum start value= 0, the maximum stop value = 255, and the start value must always be smaller than thestop value. As an example, if the start value = 0, the stop value = 255, and the DMDresolution is 768 tall – the step size would be 3 (768 pixels / 256 values = 3). Thus everyvalue from 0 to 255 would have a step size of 3 pixels (that is, each step would have 3 rowsof pixels with the same gray scale value). The gray scale value always increments by 1 foreach step between the start and stop values. An example of a Fixed Step Vertical Ramppattern is shown in Figure 2-4.

Figure 2-4. Example of Fixed Step Vertical Ramp Test Pattern



http://www.ti.com



Note 11: As noted in Table 2-6, the colors for the Horizontal Lines pattern are specified using both theForeground and Background colors. The foreground color is used for the horizontal lines, andthe background color is used for the space between the lines. As noted in Table 2-7, the userspecifies the Foreground Line Width, as well as the Background Line Width. It is up to theuser to determine the line spacing that will meet their needs for each resolution display. As anexample, if the foreground line width = 1, and the background line width = 9, there would be asingle pixel horizontal line on every 10th line. An example of a Horizontal Lines pattern isshown in Figure 2-5.

Figure 2-5. Example of Horizontal Lines Test Pattern



http://www.ti.com



Note 12: As noted in Table 2-6, the colors for the Vertical Lines pattern are specified using both theForeground and Background colors. The foreground color is used for the vertical lines, and thebackground color is used for the space between the lines. As noted in Table 2-7, the userspecifies the Foreground Line Width, as well as the Background Line Width. It is up to theuser to determine the line spacing that will meet their needs for each resolution display. As anexample, if the foreground line width = 1, and the background line width = 9, there would be asingle pixel vertical line on every 10 th line. An example of a Vertical Lines pattern is shown inFigure 2-6.

Figure 2-6. Example of Vertical Lines Test Pattern



http://www.ti.com


HORZSPACING

VERTSPACING


Note 13: As noted in Table 2-6, the colors for the Diagonal Lines pattern are specified using both theForeground and Background colors. The foreground color is used for the diagonal lines, andthe background color is used for the space between the lines. As noted in Table 2-7, the userspecifies the Horizontal and Vertical Line Spacing. The line width will always be one pixel. It isup to the user to determine the line spacing that will meet their needs for each resolutiondisplay. It should be noted that both horizontal and vertical line spacing must use the samevalue, and are limited to values of 3, 7, 15, 31, 63, 127, 255. Invalid values will result in acommunication error (invalid command parameter). An example of a Diagonal Lines pattern isshown in Figure 2-7.

Figure 2-7. Example of Diagonal Lines Test Pattern



http://www.ti.com



Note 14: As noted in Table 2-6, the colors for the Grid Lines pattern are specified using both theForeground and Background colors. The foreground color is used for the grid lines, and thebackground color is used for the space between the lines. As noted in Table 2-7, the userspecifies the Horizontal Foreground and Background Line Width, as well as the VerticalForeground and Background Line Width. It is up to the user to determine the line spacing thatwill meet their needs for each resolution display. As an example, if the horizontal foregroundline width = 1, and background line width = 9, there would be a single pixel horizontal line onevery 10th line. And if the vertical foreground line width = 1, and background line width = 9,there would be a single pixel vertical line on every 10 th line. An example of a Grid Linespattern is shown in Figure 2-8.

Figure 2-8. Example of Grid Lines Test Pattern



http://www.ti.com



Note 15: As noted in Table 2-6, the colors for the Checkerboard pattern are specified using both theForeground and Background colors. The foreground color is used for one of the checkers,and the background color is used for the alternating checker. As noted in Table 2-7, the userspecifies the Number of Horizontal Checkers and the Number of Vertical Checkers. For thispattern, the system will automatically determine the checker size in each direction based onthe number of checkers and the size of the display (DMD). As an example, if the number ofhorizontal checkers = 4, the number of vertical checkers = 4, and the DMD resolution is1280x720, the size of the horizontal checkers would be 320 pixels, and the size of thevertical checkers would be 180 pixels (1280 pixels / 4 checkers = 320 pixels: 720 pixels / 4checkers = 180 pixels). An example of a Checkerboard pattern (16 checker by 12 checker) isshown in Figure 2-9.

Figure 2-9. Example of Checkerboard Test Pattern



http://www.ti.com



Note 16: As noted in Table 2-6 and Table 2-7, there is no user programmability associated the ColorBars test pattern. This pattern is made up of eight vertical color bars, where the colors arewhite, yellow, cyan, green, magenta, red, blue, and black. For this pattern, the system willautomatically determine the width for each color bar based on the size of the display (DMD).An example of the Color Bars pattern is shown in Figure 2-10.

Figure 2-10. Example of Color Bars Test Pattern



http://www.ti.com



2.3.3.9 Read Test Pattern Select (0Ch)

2.3.3.9.1 ReadThis command is used to read the state of the test pattern select command for the display module.




Parameter Bytes DescriptionByte 1 TPG Pattern Select (See Below)Byte 2 Foreground / Background Color (See Table 2-6)Byte 3 Parameter 1 (See Table 2-7)Byte 4 Parameter 2 (See Table 2-7)Byte 5 Parameter 3 (See Table 2-7)Byte 6 Parameter 4 (See Table 2-7)

Note 1: This command will always return six bytes, since the host will not know how many bytes will bevalid until they know which pattern has been selected. All unneeded bytes (See Table 2-8) willbe set to 0.

Note 2: If a batch file was used to specify the parameters of the test pattern generator, those are theparameters that will be returned by this command.



http://www.ti.com



2.3.3.10 Write Splash Screen Select (0Dh)

2.3.3.10.1 WriteThis command is used to select a stored splash screen to be displayed on the display module.


Parameter Bytes DescriptionByte 1 Splash screen reference number (integer)

Default: Composer specified

Note 1: This command is used in conjunction with the Write Input Source Select (Section 2.3.3.2) andthe Write Splash Screen Execute (Section 2.3.3.40) commands. It specifies which splashscreen is to be displayed when the Input Source Select command selects splash screen asthe image source. The settings for this command will be retained until changed using thiscommand.

Note 2: The steps required to display a splash screen are: select the desired splash screen (thiscommand), change the input source to splash screen (using Write Input Source Select), andstart the splash screen retrieval process (using Write Splash Screen Execute).

Note 3: The Splash Screen is a unique source since it is read from Flash and sent down theprocessing path of the ASIC one time, to be stored in memory for display at the end of theprocessing path. As such, all image processing settings (for example, image crop, imageorientation, display size, splash screen select, splash screen as input source, and so forth)should be set appropriately by the user before executing the Write Splash Screen Executecommand.


Note 5: The availability of splash screens is limited by the available space in flash memory.

Note 6: All splash screens must be landscape oriented.

Note 7: For single ASIC applications which support DMD resolutions up to 1280 × 720, the minimumsplash image size allowed for flash storage is 427 × 240, with the maximum being theresolution of the product DMD. Typical splash image sizes for flash are 427 × 240 and 640 ×360. The full resolution size is typically used to support an Optical Test splash screen.

Note 8: For dual ASIC applications which support DMD resolutions up to 1980 ×1080, the minimumsplash image size allowed for flash storage is 854 × 480, with the maximum being theresolution of the product DMD. Typical splash image sizes for flash are 854 × 480. The fullresolution size is typically used to support an Optical Test splash screen.

Note 9: The user is responsible for specifying how the splash image will be displayed on the screen.Key commands for this are Write Image Crop (Section 2.3.3.13) and Write Display Size(Section 2.3.3.15).

Note 10: When this command is received while Splash Screen is the active source, other than storingthe specified splash screen value, the only action that will be taken by the ASIC software willbe to obtain the header information from the selected splash screen and store this in internalmemory. Then, when the Write Splash Screen Execute command is received, the ASICsoftware will use this stored information to set up the processing path prior to pulling thesplash data from flash.



http://www.ti.com



2.3.3.11 Read Splash Screen Select (0Eh)

2.3.3.11.1 ReadThis command is used to read the state of the splash screen select command for the display module.



Parameter Bytes DescriptionByte 1 Splash Screen Selected (integer)

Note 1: See Section 2.3.3.10 for more information on splash screens.



http://www.ti.com



2.3.3.12 Read Splash Screen Header (0Fh)

2.3.3.12.1 ReadThis command is used to read the splash screen header information for the selected splash screen for thedisplay module.

2.3.3.12.2 Read Parameters

Parameter Bytes DescriptionByte 1 Splash screen reference number (integer)

Note 1: The read parameter is used to specify the splash screen for which the header parameters areto be returned. If a splash screen value is provided for which there is no splash screenavailable, this will be considered an error (invalid command parameter value – communicationstatus) and the command will not be executed.

Note 2: See Section 2.3.3.10 for more information on splash screens.


Parameter Bytes DescriptionByte 1 Splash Image Width in Pixels (LSByte)Byte 2 Splash Image Width in Pixels (MSByte)Byte 3 Splash Image Height in Pixels (LSByte)Byte 4 Splash Image Height in Pixels (MSByte)Byte 5 Splash Image Size in Bytes (LSByte)Byte 6 Splash Image Size in BytesByte 7 Splash Image Size in BytesByte 8 Splash Image Size in Bytes (MSByte)Byte 9 Pixel Format (See below)Byte 10 Compression Type (See below)Byte 11 Color Order (See below)Byte 12 Chroma Order (See below)Byte 13 Byte Order (See below)

Note 1: Parameter definitions referenced are in Table 2-9.

Table 2-9. Splash Screen Header Definitions

Parameter Values Parameter ValuesPixel Format ‘0h' = 24-bit RGB Unpacked (not used) Chroma Order ‘0h' = Cr is first pixel

‘1h' = 24-bit RGB Packed (not used) ‘1h' = Cb is first pixel‘2h' = 16-bit RGB 5-6-5‘3h' = 16-bit YCbCr 4:2:2

Compression Type ‘0h' = Uncompressed Bytes Order ‘0h' = Little Endian‘1h' = RGB RLE Compressed ‘1h' = Big Endian‘2h' = User Defined (not used)‘3h' = YUV RLE Compressed

Color Order ‘0h' = 00RRGGBB‘1h' = 00GGRRBB



http://www.ti.com



2.3.3.13 Write Image Crop (10h)

2.3.3.13.1 WriteThis command image crop can only set non-crop operation, actual crop is not supported in DLPC3439system.

2.3.3.14 Read Image Crop (11h)This command Read Image Crop is not supported in DLPC3439.



http://www.ti.com



2.3.3.15 Write Display Size (12h)

2.3.3.15.1 WriteThis command is used to specify the size of the active image to be displayed on the display module.


Parameter Bytes DescriptionByte 1 Pixels per Line (LSByte)Byte 2 Pixels per Line (MSByte)Byte 3 Lines per Frame (LSByte)Byte 4 Lines per Frame (MSByte)

Default: DMD Resolution

Note 1: This specifies the size of the image to be output from the scaler function, which will be thesize of the active displayed image.

Note 2: The parameter values are to be ‘1' based. (in other words, a value of 1280 pixels will display1280 pixels per line).

Note 3: All sub-images (images smaller than the DMD display) will be horizontally and verticallycentered on the display (DMD)

Note 4: If the display size exceeds the resolution of the DMD, this will be considered an error (invalidcommand parameter value – communication status) and the command will not be executed.Specifically, the display size parameters will be checked against the DMD resolution, and ifthe DMD resolution is exceeded in the orientation, it will be considered an error. Note that thesystem will not check for proper image orientation setup.DMD resolution = 854 × 480:Example 1: Display size parameter = 480 × 854 (not an error)Example 2: Display size parameter = 900 × 320 (error )Example 3: Display size parameter = 500 × 600 (error )

Note 5: If the source, crop, and display parameter combinations exceed the capabilities of the scaler,the system will implement what was requested by the user as best it can, and the displayedimage will be what it will be (in other words, a broken image may be displayed). It will be up tothe user to provide updated parameters to fix the image.



http://www.ti.com



2.3.3.16 Read Display Size (13h)

2.3.3.16.1 ReadThis command is used to read the state of the display size command for the display module




Note 1: The parameter values are to be 1 based. (In other words, a value of 1920 pixels will display1920 pixels per line.)



http://www.ti.com


Flip Disabled Flip EnabledDMD


2.3.3.17 Write Display Image Orientation (14h)

2.3.3.17.1 WriteThis command is used to specify the image orientation of the displayed image for the display module.




b(7:3) – Reserved

b(2) – Short Axis Image Flip0h: Image not flipped1h: Image flipped

b(1) – Long Axis Image Flip0h: Image not flipped1h: Image flipped

b(0) – Reserved


Note 1: Image rotation is not supported in DLPC3439.

Note 2: Short axis flip is as shown in Figure 2-11.

Figure 2-11. Short Axis Flip



http://www.ti.com



2.3.3.18 Read Display Image Orientation (15h)

2.3.3.18.1 ReadThis command is used to read the state of the displayed image orientation function for the display module.





b(7:3) – Reserved

b(2) – Short Axis Image Flip0h: Image not flipped1h: Image flipped

b(1) – Long Axis Image Flip0h: Image not flipped1h: Image flipped

b(0) – Reserved



http://www.ti.com



2.3.3.19 Write Display Image Curtain (16h)

2.3.3.19.1 WriteThis command is used to control the display image curtain for the display module.




b(7:4) – Reserved

b(3:1) – Select Curtain Color0h: Black1h: Red2h: Green3h: Blue4h; Cyan5h: Magenta6h: Yellow7h: White

b(0) – Curtain Enable0h: Curtain Disabled1h: Curtain Enabled

Default: 01h

Note 1: The Image Curtain fills the entire display with a user specified color.

Note 2: The curtain color specified by this command is separate from the border color defined in theWrite Border Color command (Section 2.3.3.61), even though they are both displayed using thecurtain capability.



http://www.ti.com



2.3.3.20 Read Display Image Curtain (17h)

2.3.3.20.1 ReadThis command is used to read the state of the image curtain control function for the display module.





b(7:4) – Reserved

b(3:1) – Select Curtain Color0h: Black1h: Red2h: Green3h: Blue4h; Cyan5h: Magenta6h: Yellow7h: White

b(0) – Curtain Enable0h: Curtain Disabled1h: Curtain Enabled



http://www.ti.com



2.3.3.21 Write Image Freeze (1Ah)

2.3.3.21.1 WriteThis command is used to enable or disable the image freeze function for the display module.




b(7:1) – Reserved

b(0) – Image Freeze0h: Image Freeze Disabled1h: Image Freeze Enabled

Default: 00h

Note 1: Normal use of the Image Freeze capability typically has two main functions. The first function isto allow the end user to freeze the current image on the screen for their own uses. The secondfunction is to allow the user (host system/OEM) to reduce/prevent system changes fromshowing up on the display as visual artifacts. In this second case, the image would be frozen,system changes would be made, and when complete, the image is unfrozen. In all cases, whenthe image is unfrozen, the display starts showing the most resent input image. Thus input databetween the freeze point and the unfreeze point is lost. Suggestions to the host system for thetypes of image changes likely to necessitate the use of the image freeze command to hideartifacts are discussed in Section 2.3.3.21.3.

Note 2: It should be noted that the ASIC software will never automatically or under-the-hood freeze orunfreeze the image. Basically, the ASIC software will not freeze or unfreeze the image for anyreason except when explicitly commanded by the Write Image Freeze command.

Note 3: It is important that the user review the notes for the Write Input Source Select command inSection 2.3.3.2 to understand the concept of source associated commands. This concept willdetermine when source associated commands are executed by the system. Note, Freezecommand doesn’t work on Splash screen on dual DLPC3439 system.

Note 4: If the OEM chooses not to make use of Image Freeze, is recommended that they change thesource itself before changing image parameters to minimize transition artifacts.

2.3.3.21.3 Use of Image Freeze to Reduce On-Screen ArtifactsCommands that take a long time to process, require a lot a data to be loaded from Flash, or change theframe timing of the system, have the potential to create on-screen artifacts. The Write Image Freezecommand can be used in these cases to try and minimize, if not eliminate, these artifacts. The processwould be:1. Send Write Image Freeze command to enable freeze.2. Send commands with the potential to create image artifacts.3. Send Write Image Freeze command to disable freeze.



http://www.ti.com



Since commands to the ASIC are processed serially, no special timing or delay is required between thesecommands. It is suggested that the number of commands placed between the freeze and unfreeze bekept small, as it is likely not desirable for the image to be frozen for a long period of time. A list ofcommands that may product image artifacts are listed in Table 2-10. This is not an all inclusive list,however, and the user is ultimately responsible for determining if and when use of the image freezecommand will meet their product needs.

Table 2-10. Partial List of Commands that may Benefit from use of Image Freeze

Command (1) (2) Command OpCode Paragraph NotesWrite Input Source Select 05h Section 2.3.3.2Write External Video Source Format 07h Section 2.3.3.4SelectWrite Test Pattern Select 0Bh Section 2.3.3.8Write Look Select 22h Section 2.3.3.25

(1) If changed while this source is the active source.(2) Freeze command does not work on Splash screen.

A few examples of how to use the image freeze command are shown in Table 2-11 and Table 2-12.

Table 2-11. TPG Example Using Image Freeze

Command NotesWrite Display Image Curtain = Enable May want to apply curtain if already displaying unwanted image (For

example, a broken source)Write Image Freeze = FreezeWrite Image Crop, Write Display Size, Write Display Potential data processing commands that may be required for properImage Orientation. display of TPGWrite TPG Select Set up TPGWrite Input Source Select = TPGWrite Image Freeze = Unfreeze

Table 2-12. Test Pattern Generator Example using Image Freeze

Command NotesWrite Image Freeze = FreezeWrite Image Crop, Write Display Size, Write Display Potential data processing commands that may be required for properImage Orientation, Write Test Pattern Select. display of test pattern image. These would be used as appropriate. It is

recommended that these be set before the Write Input Source Selectcommand.

Write Input Source Select = Test PatternGeneratorWrite Image Freeze = Unfreeze



http://www.ti.com



2.3.3.22 Read Image Freeze (1Bh)

2.3.3.22.1 ReadThis command is used to read the state of the image freeze function for the display module.





b(7:1) – Reserved

b(0) – Image Freeze0h: Image Freeze Disabled1h: Image Freeze Enabled



http://www.ti.com



2.3.3.23 Write 3-D Control (20h)

2.3.3.23.1 WriteThis command is used to control 3-D functionality for the display module.




b(7) – Reserved

b(6) – Polarity of 3-D Reference (External Only)0h: Correct – No Inversion Required1h: Incorrect – Inversion Required

b(5) – Frame Dominance0h: Left Dom. (Data sent left eye first)1h: Right Dom. (Data sent right eye first)

b(4:2) – Reserved

b(1) – Source of 3-D Reference0h: Internal Reference Generator NOT supported1h: External (SLT_3DR Pin)

b(0) – Reserved

Default:00h

Note 1: The system will automatically enable 3-D operation when appropriate, basing this decision onthe source frame rate and whether 3-D sequences are available to the system (that is, loadedin flash). The 3-D parameters specified by this command will take effect following the nextVSYNC.

Note 2: 3-D image data must always be sent frame sequential (that is, syncs and blanking to be sentbetween every eye frame), at frame rates greater than approximately 94Hz (ASIC does notsupport frame rate multiplication). Internal Reference Generator is not supported in Dual ASICsystem.

Note 3: Internal reference generator is not supported on dual ASIC DLPC3439.

Note 4: The 3-D Reference is used to specify whether a frame of data contains left eye data or righteye data. This 3-D reference can be provided to the display by an external hardware signal.Table 2-13 shows which 3-D Reference source can be used with which image data port.When using the external hardware signal as the reference, it must be provided for every frameof data. If the external 3-D Reference is misaligned with the data, it can be corrected using thePolarity of 3-D Reference (External Only) parameter. As noted, the Polarity of 3-D Referenceparameter is only applicable when the External Signal is selected as the 3-D Reference source.



http://www.ti.com



Table 2-13. 3-D Reference Source Applicability for Display Data Ports

Display Data Port 3-D Reference Source (1) Applicable NotesParallel External Hardware Signal Yes RecommendedParallel Internal Reference Generator No

(1) The Write 3-D Reference command should be use with this selection.

Note 5: For frame sequential 3-D, Frame Dominance determines which eye frames in the data streamgo together to make up a single 3-D image. Left Dominance indicates that the first eye frame ofa pair is Left, the second eye frame is Right. Right Dominance indicates that the first eye frameof a pair is Right, the second eye frame is Left). This is important for proper operation of displayhistograms (which span both eye frames of a single image), and when the image is frozen, aswe want to be sure we display the correct two eye frames together. The frame dominancecontrol must not be used to attempt correction for misalignment of the 3-D reference signal tothe image data.



http://www.ti.com



2.3.3.24 Read 3-D Control (21h)

2.3.3.24.1 ReadThis command is used to read the state of the 3-D control function for the display module.





b(7) – Reserved

b(6) – Polarity of 3-D Reference (External Only)0h: Correct – No Inversion Reqd.1h: Incorrect – Inversion Reqd

b(5) – Frame Dominance0h: Left Dom. (Data sent left eye first)1h: Right Dom. (Data sent right eye first)

b(4:2) – Reserved

b(1) – Source of 3-D Reference0h: Internal Reference Generator NOT supported1h: External (SLT_3DR Pin)

b(0) – 3-D Mode Control0h: 2-D Operation1h: 3-D Operation

Note 1: The system automatically enables and disables 3-D operation. Bit(0) will indicate the state of 2-D/3-D operation.



http://www.ti.com



2.3.3.25 Write LOOK Select (22h)

2.3.3.25.1 WriteThis command is used to specify the LOOK for the image on the display module.




b(7:0) – LOOK Number


Note 1: In this product, a LOOK typically specifies a target white point.

Note 2: This command allows the host to select a LOOK (target white point) from a number of looksstored in flash. Based on the look selected, along with measured data obtained from anappropriate light sensor, software will automatically select and load the most appropriatesequence/duty cycle set available in the Look to get as close as possible to the target whitepoint.

Note 3: The number of LOOKs available may be limited by the available space in flash memory.

Note 4: LOOKs are specified in this byte by an enumerated value (that is, 0, 1, 2, 3, and so forth.).There must always be at least one look, whose enumerated value will be 0.

Note 5: The OEM may also specify the desired white point manually using the Write Manual DutyCycle Select command. This manual command would most likely be used when there is nolight sensor in the system, in which case, the host becomes responsible for sequence/dutycycle selection from the sequences available in the selected Look. Note that duty cycle setsare associated with sequences which are stored in Flash until needed.

Note 6: There are two other items that the host will likely want to specify in addition to the LOOK.These are:

● A desired degamma curve: This is achieved by selecting the appropriate Degamma/CMTwhich has the desired degamma curve and correct bit weights for the sequence selected. Thisis selected using the Degamma/CMT Select command discussed in Section 2.3.3.29.

● The desired color points: This is achieved by selected the appropriate CCA parameters, and isselected using the CCA Select command discussed in Section 2.3.3.30.



http://www.ti.com



2.3.3.26 Read LOOK Select (23h)

2.3.3.26.1 ReadThis command is used to read the state of the look select command for the display module.



Parameter Bytes DescriptionByte 1 Look number See BelowByte 2 Sequence number See BelowByte 3 Current Sequence Frame Rate (lsb) See Note 3Byte 4 Current Sequence Frame RateByte 5 Current Sequence Frame RateByte 6 Current Sequence Frame Rate (msb)


b(7:0) – LOOK Number


b(7:0) Sequence Number–

Note 1: LOOKs are specified by an enumerated value (that is, 0, 1, 2, 3, and so forth.)

Note 2: Sequences are specified by an enumerated value (that is, 0, 1, 2, 3, and so forth.), and thevalue returned by this command is the sequence currently selected by the LOOK algorithmwhen this command is received.

Note 3: The current sequence frame rate is returned as a count that is specified in units of 66.67ns(based on the internal 15MHz clock used to time between input frame syncs), and is validregardless of whether ASIC software made the sequence/duty cycle selection, or the usermade the selection. The frame rate is specified in this way to enable fast and simple comparesto the frame count by software.



http://www.ti.com



2.3.3.27 Read Sequence Header Attributes (26h)

2.3.3.27.1 ReadThis command is used to read sequence header information for the active sequence of the displaymodule.



Parameter Bytes DescriptionByte 1 Red Duty Cycle (LSByte) (Look Structure)Byte 2 Red Duty Cycle (MSByte) (Look Structure)Byte 3 Green Duty Cycle (LSByte) (Look Structure)Byte 4 Green Duty Cycle (MSByte) (Look Structure)Byte 5 Blue Duty Cycle (LSByte) (Look Structure)Byte 6 Blue Duty Cycle (MSByte) (Look Structure)Byte 7 Maximum Frame Count (LSByte) (Look Structure)Byte 8 Maximum Frame Count (Look Structure)Byte 9 Maximum Frame Count (Look Structure)Byte 10 Maximum Frame Count (MSByte) (Look Structure)Byte 11 Minimum Frame Count (LSByte) (Look Structure)Byte 12 Minimum Frame Count (Look Structure)Byte 13 Minimum Frame Count (Look Structure)Byte 14 Minimum Frame Count (MSByte) (Look Structure)Byte 15 Max # of Seq Vectors (See below) (Look Structure)Byte 16 Red Duty Cycle (LSByte) (Sequence Structure)Byte 17 Red Duty Cycle (MSByte) (Sequence Structure)Byte 18 Green Duty Cycle (LSByte) (Sequence Structure)Byte 19 Green Duty Cycle (MSByte) (Sequence Structure)Byte 20 Blue Duty Cycle (LSByte) (Sequence Structure)Byte 21 Blue Duty Cycle (MSByte) (Sequence Structure)Byte 22 Maximum Frame Count (LSByte) (Sequence Structure)Byte 23 Maximum Frame Count (Sequence Structure)Byte 24 Maximum Frame Count (Sequence Structure)Byte 25 Maximum Frame Count (MSByte) (Sequence Structure)Byte 26 Minimum Frame Count (LSByte) (Sequence Structure)Byte 27 Minimum Frame Count (Sequence Structure)Byte 28 Minimum Frame Count (Sequence Structure)Byte 29 Minimum Frame Count (MSByte) (Sequence Structure)Byte 30 Max # of Seq Vectors (See below) (Sequence Structure)

Note 1: The sequence header data is stored in two separate Flash data structures (the LOOKStructure and the Sequence Structure), and the values from each should match.

Note 2: The bit weight and bit order for the duty cycle data is shown in Figure 2-12.



http://www.ti.com


Active Image Area

DMD Display Area

DMD Display

Area

Pillar-BoxBorder

Pillar-BoxBorder


Figure 2-12. Bit Weight and Bit Order for Duty Cycle Data

Note 3: The duty cycle data is specified as each colors percent of the frame time. The sum of the threeduty cycles must add up to 100.(ex. R = 30.5 = 1E80h , G = 50 = 3200h, B = 19.5 = 1380h)

Note 4: The sequence maximum and minimum frame counts are specified in units of 66.67ns (basedon the internal 15MHz clock used to time between input frame syncs). These are specified inthis way to enable fast and simple compares to the frame count by software.

Note 5: The Max # of Sequence Vectors byte is defined below.

msb Byte 15 and 30 lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:4) – Reserved

b(3:0) – Max # of Sequence Vectors



http://www.ti.com



2.3.3.28 Write Gamma/CMT Select (27h)

2.3.3.28.1 WriteThis command is used to select a specific Degamma/CMT LUT for the display module.




b(7:0) – Degamma/CMT LUT Index Number

Default: Composerspecified

Note 1: Degamma/CMT LUTs are stored in Flash until needed.

Note 2: The Degamma/CMT LUT Number specified by the user determines the degamma applied bythe system.

Note 3: For TI software purposes, this Degamma/CMT LUT number is the CMT Index # in the Flashstructure. Thus, if there is a degamma of 1.5 (for example) at CMT Index #0, then everysequence will have a CMT Index #0 that references a degamma of 1.5 that is appropriate foreach respective sequence.

2.3.3.29 Read Degamma/CMT Select (28h)

2.3.3.29.1 ReadThis command is used to read the status of the degamma/CMT select command for the display module.





b(7:0) – Degamma/CMT LUT Number



http://www.ti.com



2.3.3.30 Write CCA Select (29h)

2.3.3.30.1 WriteThis command is used to select a specific set of CCA parameters (to specify the color points) for thedisplay module.




b(7:0) – CCA Parameter Set

Default:Composerspecified

Note 1: CCA parameter sets are used to set a target color points for the system. The sets are stored inFlash until needed.

Note 2: CCA parameter sets are specified in this byte by an enumerated value (that is, 0, 1, 2, 3, andso forth.). This number specifies the actual CCA number reference in the flash structure.

2.3.3.31 Read CCA Select (2Ah)

2.3.3.31.1 ReadThis command is used to read the status of the CCA select command for the display module.





b(7:0) – CCA Parameter Set

Note 1: CCA parameter sets are specified in this byte by an enumerated value (that is, 0, 1, 2, 3, andso forth.)



http://www.ti.com



2.3.3.32 Write Execute Flash Batch File (2Dh)

2.3.3.32.1 WriteThis command is used to command the execution of a Flash batch file for the display module.


Parameter Bytes DescriptionByte 1 Batch File Number

Note 1: This command is used to command the execution of a batch file stored in the Flash of thedisplay module. Any system write command that can be sent by itself can be groupedtogether with other system commands or command parameters into a Flash batch file, withthe exception of those listed in . Flash batch files are created using the DLP Composer tool,and then stored in the Flash build. One example for a Flash batch file might be thecommands and command parameters required for initialization of the system after power-up.

Note 2: The Flash batch file numbers to be specified in this byte are enumerated values (that is, 0,1, 2, 3, and so forth.).

Note 3: Flash batch file 0 is a special Auto-Init batch file that is run automatically by the DLPC3439software immediately after system initialization has been completed. As such, Flash batchfile 0 will not typically be called using the Write Execute Batch File command (although thesystem will allow it). This special Flash batch file would typically be used to specify thesource to be used (for example, splash screen or data port) once the system is initialized.

Note 4: Embedding Flash batch file calls within a Flash batch file is not allowed (that is, callinganother batch file from within a batch file is not allowed). If it is desired to have two batchfiles executed back to back, they should be called by back to back execute batch filecommands.

Note 5: The system provides the ability to add an execution delay between commands within aFlash batch file. This is done using the Write Flash Batch File Delay command(Section 2.3.3.76).

Note 6: The order of command execution for commands within a Flash batch file will be the same asif the commands had been received over the I2C port.

Table 2-14. List of Commands Excluded from Batch File Use

Command Op-Code ParagraphWrite Command Synchronization N/A -Write Execute Flash Batch File 2D Section 2.3.3.32Flash Data Type Select DE Section 2.3.3.78Flash Data Length DF 0Erase Flash Data E0 Section 2.3.3.81Write Flash Start E1 Section 2.3.3.82Write Flash Continue E2 Section 2.3.3.83Write Internal Mailbox Address E8 Section 2.3.3.89Write Internal Mailbox E9 Section 2.3.3.90Write External PAD Address EB Section 2.3.3.92Write External PAD Data EC Section 2.3.3.93All Read commands Various Various



http://www.ti.com



2.3.3.33 Write External Input Image Size (2Eh)

2.3.3.33.1 WriteThis command is used to specify the active data size of the external input image to the display module.



Default: DMD Resolution

Note This command is used in conjunction with the Write Input Source Select command1: (Section 2.3.3.2). This command specifies the active data size of the input image to the system

for all external video interfaces when the Write Input Source Select command selects ExternalVideo Port as the image source. The settings for this command are to be retained until changedusing this command. These settings will be automatically applied each time the External VideoPort is selected.

Note When the source data for the parallel interface does not provide an active data framing signal,2: the user must specify where the active data is located within the frame using the Write Parallel

I/F Manual Image Framing command (Section 2.3.3.42) in addition to this command.

Note The parameter values are to be 1 based. (That is, a value of 1280 pixels will specify 1280 pixels3: per line.)

Note It is important that the user review the notes for the Write Input Source Select command in4: Section 2.3.3.2 to understand the concept of source associated commands. This concept will

determine when source associated commands are executed by the system. Note that thiscommand is a source associated command.

Note The maximum and minimum input values are shown in Table 2-15. Values outside of these5: ranges will be flagged as an error (invalid command parameter), and the command will not be

executed.

Table 2-15. Input Source Limits for Active Data

Parameter Minimum Value Maximum ValueInput Source Active Pixels (Single ASIC) 320 1280per LineInput Source Active Lines (Single ASIC) 200 800per FrameInput Source Active Pixels (Dual ASIC) 1280 (1) 1920 (1)

per LineInput Source Active Lines (Dual ASIC) 720 (1) 1080 (1)

per Frame(1) Limited Scaling is supported for dual ASIC configurations.



http://www.ti.com



2.3.3.34 Read External Input Image Size (2Fh)

2.3.3.34.1 ReadThis command is used to read the specified data size of the external input image to the display module




Note 1: The parameter values are to be 1 based. (That is, a value of 1280 pixels will specify 1280pixels per line.)

Note 2: This command returns the value specified by the Write External Input Image Size command(Section 2.3.3.33).



http://www.ti.com



2.3.3.35 Write 3-D Reference (30h)

2.3.3.35.1 WriteThis command is used to provide a 3-D reference for the display module.




b(7:1) – Reserved

b(0) – 3-D Reference0h: Next Frame Left1h: Next Frame Right

Default: 00h

Note 1: The 3-D Reference is used to specify whether a frame of data contains left eye data or righteye data. The 3-D reference can be provide to the display as a GPIO hardware signal or byusing this command (selection is made using the Write 3-D Control command(Section 2.3.3.23)). When using this command as the reference, it is recommend that thecommand be sent every frame, or at least at the start of each eye pair (for example, sentbefore each left eye frame). At a minimum, it must be sent once at the start of 3-D operation. Ifthe 3-D Reference is misaligned with the data, it can be corrected using this command or byusing the Polarity of 3-D Reference parameter in the Write 3-D Control command.

Note 2: When the Write 3-D Reference command is received, its parameter value will be applied at thenext VSYNC (In other words, the parameter value will be applied to the image data followingthe next VSYNC or Start of Frame command.)

Note 3: When this command is received, software must set up the internal ASIC 3-D referencegenerator. If the command is sent every frame, software can just monitor to insure that theoutput of the internal ASIC 3-D reference generator is still correct.



http://www.ti.com



2.3.3.36 Write GPIO[19:00] Control (31h)

2.3.3.36.1 WriteThis command is used to specify how GPIO(19:09) and GPIO(07:04) of the display module are to beused.


Parameter Bytes DescriptionByte 1 See BelowByte 2 See BelowByte 3 See BelowByte 4 See Below


b(7:6) – GPIO(12) b(1:0) – GPIO(09)0h: Composer Defined 0h: Composer Defined1h: Input 1h: Input2h: Output (Standard) 2h: Output (Standard)3h: Output (Open Drain) 3h: Output (Open Drain)








http://www.ti.com



b(7:6) – Reserved b(3:2) – GPIO(18)0h: Composer Defined 0h: Composer Defined1h: Input 1h: Input2h: Output (Standard) 2h: Output (Standard)3h: Output (Open Drain) 3h: Output (Open Drain)






Note 1: GPIO(19:09) and GPIO(07:04) can individually function as defined by the OEM in Composer,or their function can be redefined on-the-fly using this command. When their functions areredefined by this command, the Write GPIO[19:00] Outputs (Section 2.3.3.38) and ReadGPIO[19:00] Inputs (Section 2.3.3.41) commands are used to write or read the redefinedGPIO. GPIO(08) has a fixed function, and the functions of GPIO(03:00) can only be specifiedvia Composer.

Note 2: The OEM must insure that signal conflicts do not arise when switching GPIO signal directions(for example, external signal driving a GPIO that is configured as an output).



http://www.ti.com



2.3.3.37 Read GPIO[19:00] Control (32h)

2.3.3.37.1 ReadThis command is used to read back the control state for GPIO(19:09) and FPIO(07:04) of the displaymodule.



Parameter Bytes DescriptionByte 1 See BelowByte 2 See BelowByte 3 See BelowByte 4 See Below









http://www.ti.com




b(7:6) – Reserved b(3:2) – GPIO(18)0h: Composer Defined 0h: Composer Defined1h: Input 1h: Input2h: Output (Standard) 2h: Output (Standard)3h: Output (Open Drain) 3h: Output (Open Drain)







http://www.ti.com



2.3.3.38 Write GPIO[19:00] Outputs (33h)

2.3.3.38.1 WriteThis command is used to write the output values for GPIO(19:09) and GPIO(07:00) of the display module.


Parameter Bytes DescriptionByte 1 GPIO Mask (See Below)Byte 2 GPIO Mask (See Below)Byte 3 GPIO Mask (See Below)Byte 4 GPIO Value (See Below)Byte 5 GPIO Value (See Below)Byte 6 GPIO Value (See Below)


b(7) – GPIO(7) b(3) – GPIO(3)0h: Not Selected 0h: Not Selected1h: Selected 1h: Selected








b(4) – GPIO(4) b(0) – GPIO(0)



http://www.ti.com



0h: Not Selected 0h: Not Selected1h: Selected 1h: Selected


b(7:3) – Reserved b(1) – GPIO(18)0h: Not Selected 0h: Not Selected1h: Selected 1h: Selected



b(7) – GPIO(7) b(3) – GPIO(3)

b(6) – GPIO(6) b(2) – GPIO(2)

b(5) – GPIO(5) b(1) – GPIO(1)

b(4) – GPIO(4) b(0) – GPIO(0)


b(7) – GPIO(16) b(3) – GPIO(312)

b(6) – GPIO(15) b(2) – GPIO(11)

b(5) – GPIO(14) b(1) – GPIO(10)

b(4) – GPIO(13) b(0) – GPIO(9)


b(7:3) – Reserved b(1) – GPIO(18)

b(2) – GPIO(19) b(0) – GPIO(9)


Note 1: GPIO(19:09) and GPIO(07:04) can function as defined by the OEM in Composer, or theirfunction can be redefined on-the-fly using the Write GPIO[19:00] Control command(Section 2.3.3.36) .GPIO(08) is not re-definable on-the-fly, and is not available for use as an OEM GPIO.GPIO(03:00) can only function as defined by the OEM in Composer. One of the choices inComposer is to define one or more of these GPIO to be OEM GPIO Outputs.



http://www.ti.com



Note 2: When one or more of GPIO(19:09) and GPIO(07:04) are defined as output signals (using theWrite GPIO[19:00] Control command), and/or one or more of GPIO(03:00) are defined asoutput signals by the OEM in Composer, this command is used to specify the values of thoseoutput signals. All of these values will be retained for later application if required, and for readback using the Read GPIO(19:00) Outputs command (Section 2.3.3.40).This command will have no effect on GPIO(19:09) and GPIO(07:04) that are not defined asoutput signals by the Write GPIO[19:00] Control command, although any values entered forthese GPIO will be retained (and used if/when these GPIO are later specified to be outputs).This command will have no effect on GPIO(03:00) that are not defined as output signals byComposer. Even so, any values entered for these GPIO will be retained for read back(although they will not be applied to the GPIO).

Note 3: In order to set the value of a GPIO, the GPIO must be selected using bytes 1 to 3 of thiscommand, with the appropriate value then being specified using bytes 3 to 6.



http://www.ti.com



2.3.3.39 Read GPIO[19:00] Outputs (34h)

2.3.3.39.1 ReadThis command is used to read the output values for GPIO(19:09) and GPIO(07:00) of the display module.



Parameter Bytes DescriptionByte 1 GPIO Value (See Below)Byte 2 GPIO Value (See Below)Byte 3 GPIO Value (See Below)


b(7) – GPIO(7) b(3) – GPIO(3)

b(6) – GPIO(6) b(2) – GPIO(2)

b(5) – GPIO(5) b(1) – GPIO(1)

b(4) – GPIO(4) b(0) – GPIO(0)


b(7) – GPIO(16) b(3) – GPIO(12)

b(6) – GPIO(15) b(2) – GPIO(11)

b(5) – GPIO(14) b(1) – GPIO(10)

b(4) – GPIO(13) b(0) – GPIO(9)



b(2) – GPIO(19) b(0) – GPIO(17)

Note 1: This command will return the values specified by the Write GPIO[19:00] Outputs command(Section 2.3.3.38). Any GPIO not having a value specified by the Write GPIO[19:00] Outputscommand will return a value of zero. The value returned may or may not be the value at theGPIO. See the Write GPIO[19:09] Control (Section 2.3.3.36) and Read GPIO[19:00] Inputs(Section 2.3.3.41) command for further information.



http://www.ti.com



Note 2: When one or more of GPIO(19:09) are defined as input signals (using the Write GPIO[19:09]Control command), and/or one or more of GPIO(07:00) are defined as input signals by theOEM in Composer, this command is used to read back the current value of those specificGPIO. Each time a read request is made the ARM software will de-bounce, sample, andreturn the current value on these GPIO. This command will return zero for any GPIO(19:09)and GPIO(07:00) not defined as an input signal.

2.3.3.40 Write Splash Screen Execute (35h)

2.3.3.40.1 WriteThis command is used to start the process of retrieving a splash screen from Flash for display on thedisplay module.

2.3.3.40.2 Write ParametersThis command has no command parameters.

Note 1: This command is used in conjunction with the Write Input Source Select (Section 2.3.3.2) andthe Write Splash Screen Select (Section 2.3.3.10) commands. It is used to start the process ofretrieving a splash screen from Flash for display.

Note 2: The Splash Screen is a unique source since it is read from Flash and sent down theprocessing path of the ASIC one time, to be stored in memory for display at the end of theprocessing path. As such, all image processing settings (for example, image crop, imageorientation, display size, splash screen select, splash screen as input source, and so forth.)should be set appropriately by the user before executing this command. Any data pathprocessing changed after the splash screen has been executed will require this command tobe re-executed before the result will be seen on the display. Thus, the splash screen retrievalprocess will be repeated each time this command is received. See also the Write ImageFreeze command (Section 2.3.3.21) for information on hiding on-screen artifacts whenselecting and retrieving a splash image.

Note 3: It is important that the user review the notes for the Write Input Source Select command inSection 2.3.3.2 to understand the concept of source associated commands. This concept willdetermine when source associated commands are executed by the system. Note that thiscommand is a source associated command; however, this command is special in that there isno maintained state or history. Thus, this command has no settings to be stored or reused bythe system.

Note 4: When this command is processed, the system will automatically set up the system colorprocessing based on the splash header information prior to sending the splash image downthe data path.



http://www.ti.com



2.3.3.41 Read GPIO[19:00] Inputs (36h)

2.3.3.41.1 ReadThis command is used to read the input values for GPIO(19:09) and GPIO(07:00) of the display module.



Parameter Bytes DescriptionByte 1 GPIO Value (See Below)Byte 2 GPIO Value (See Below)Byte 3 GPIO Value (See Below)


b(7) – GPIO(7) b(3) – GPIO(3)

b(6) – GPIO(6) b(2) – GPIO(2)

b(5) – GPIO(5) b(1) – GPIO(1)

b(4) – GPIO(4) b(0) – GPIO(0)


b(7) – GPIO(16) b(3) – GPIO(12)

b(6) – GPIO(15) b(2) – GPIO(11)

b(5) – GPIO(14) b(1) – GPIO(10)

b(4) – GPIO(13) b(0) – GPIO(9)



b(2) – GPIO(19) b(0) – GPIO(17)

Note 1: GPIO(19:09) can function as defined by the OEM in Composer, or their function can beredefined on-the-fly using the Write GPIO[19:09] Control command (Section 2.3.3.36).GPIO(08) is not re-definable on-the-fly, and is not available for use as an OEM GPIO.GPIO(07:00) can only function as defined by the OEM in Composer. One of the choices inComposer is to define one or more of these GPIO to be OEM GPIO Inputs



http://www.ti.com



Note 2: When one or more of GPIO(19:09) are defined as input signals (using the Write GPIO[19:09]Control command), and/or one or more of GPIO(07:00) are defined as input signals by theOEM in Composer, this command is used to read back the current value of those specificGPIO. Each time a read request is made the ARM software will de-bounce, sample, andreturn the current value on these GPIO. This command will return zero for any GPIO(19:09)and GPIO(07:00) not defined as an input signal.

2.3.3.42 Write External Parallel I/F Data Mask Control (37h)

2.3.3.42.1 WriteThis command is used to control the masking function for the external parallel port I/F of the displaymodule.




b(7:2) – Reserved

b(1) – Polarity Select for Data Mask Control0h: Unmasked = 0, Masked = 11h: Unmasked = 1, Masked = 0

b(0) – Data Mask Enable0h: Mask Disable1h: Mask Enabled

Default: 00h

Note 1: When this function is enabled, the DLPC3439 input pin PDM_CVS_TE functions as a DataMask control for the image data on the Parallel Port interface. When this function is enabledand the mask control is active, input image frames will be ignored and the source image will notbe propagated to the display. During image frames that are masked, the last unmasked imageframe received will continue to be displayed. The mask control signal (PDM_CVS_TE) shouldonly be updated during vertical blanking.

Note 2: The Polarity Select specifies the active state for the mask control signal. The polarity shouldonly be updated when the mask function is disabled (via this command).



http://www.ti.com



2.3.3.43 Read External Parallel I/F Data Mask Control (38h)

2.3.3.43.1 ReadThis command is used to used to read the state of the masking function for the external parallel port I/F ofthe display module.





b(7:2) – Reserved

b(1) – Polarity Select for Data Mask Control0h: Unmasked = 0, Masked = 11h: Unmasked = 1, Masked = 0

b(0) – Data Mask Enable0h: Mask Disabled1h: Mask Enabled



http://www.ti.com



2.3.3.44 Write LED Output Control Method (50h)

2.3.3.44.1 WriteThis command is used to specify the method for controlling the LED outputs for the display module.




b(7:2) Reserved–

b(1:0) LED Control Method–

00h: Manual RGB LED Currents (disables CAIC algorithm)01h: CAIC (automatic) RGB LED Power (enables CAIC algorithm)10h: Reserved11h: Reserved


Note This command selects the method to be used to control the output of the red, green, and blue1: LEDs. Based on the method chosen, a specific set of commands are available for controlling the

LED outputs. These are shown in Table 2-16.

Note The Manual RGB LED Currents method provides for manual control of the LED currents, and as2: such, the CAIC algorithm (Section 2.3.3.57) will be disabled.

Note The CAIC (Automatic) RGB LED Current Control method provides automatic control of the LED3: currents using the CAIC algorithm.

Table 2-16. Available Commands Based on LED Control Method

Available Commands Reference SectionManual RGB LED Current Control (CAIC Disabled)Write RGB LED Enable (52h) Section 2.3.3.46Read RGB LED Enable (53h) Section 2.3.3.47Write RGB LED Current (54h) Section 2.3.3.46Read RGB LED Current (55h) Section 2.3.3.49Write RGB LED Max Current (5Ch) Section 2.3.3.51Read RGB LED Max Current (5Dh) Section 2.3.3.52CAIC Automatic RGB LED Current Control (CAIC Enabled)Write RGB LED Enable (52h) Section 2.3.3.46Read RGB LED Enable (53h) Section 2.3.3.47Write RGB LED Current (54h) Section 2.3.3.48Read RGB LED Current (55h) Section 2.3.3.49Read CAIC LED Max Available Power (57h) Section 2.3.3.50Read CAIC RGB LED Current (5Fh) Section 2.3.3.54



http://www.ti.com



2.3.3.45 Read LED Output Control Method (51h)

2.3.3.45.1 ReadThis command is used to read the state of the LED output control method for the display module.





b(7:2) – Reserved

b(1:0) – LED Control Method00h: Manual RGB LED Currents (CAIC algorithm disabled)01h: CAIC (automatic) RGB LED PowerCurrent Control (CAIC algorithm enabled)10h: Reserved11h: Reserved



http://www.ti.com



2.3.3.46 Write RGB LED Enable (52h)

2.3.3.46.1 WriteThis command is used to enable the LEDs for the display module.




b(7:3) – Reserved

b(2) – Blue LED Enable0h: Blue LED Disabled1h: Blue LED Enabled

b(1) – Green LED Enable0h: Green LED Disabled1h: Green LED Enabled

b(0) – Red LED Enable0h: Red LED Disabled1h: Red LED Enabled

Default: 07h



http://www.ti.com



2.3.3.47 Read RGB LED Enable (53h)

2.3.3.47.1 ReadThis command is used to read the state of the LED enables for the display module.





b(7:3) – Reserved

b(2) – Blue LED Enable0h: Blue LED Disabled1h: Blue LED Enabled

b(1) – Green LED Enable0h: Green LED Disabled1h: Green LED Enabled

b(0) – Red LED Enable0h: Red LED Disabled1h: Red LED Enabled



http://www.ti.com



2.3.3.48 Write RGB LED Current (54h)

2.3.3.48.1 WriteThis command is used to set the current for the red, green, and blue LEDs of the display module.


Parameter Bytes DescriptionByte 1 Red LED current parameter (LSByte)Byte 2 Red LED current parameter (MSByte)Byte 3 Green LED current parameter (LSByte)Byte 4 Green LED current parameter (MSByte)Byte 5 Blue LED current parameter (LSByte)Byte 6 Blue LED current parameter (MSByte)


Note 1: When an all white image is being displayed, this command allows the system white point to beadjusted while also establishing the total LED power. This is true whether the CAIC algorithmis enabled or disabled.

Note 2: The parameters specified by this command will have a resolution of 10 bits, and are to be asdefined by the appropriate PAD specification.

Note 3: When the CAIC algorithm is disabled, this command will directly set the LED currents (that is,the R, G, and B values provided will be sent directly to the PAD device) regardless of theimage being displayed.

Note 4: When CAIC algorithm is enabled:● This command will directly set the LED currents when an all-white image is displayed. If

the image is changed from an all-white image, depending on the image, the CAICalgorithm may alter one or more of the LED currents from those specified by thiscommand and the total LED power may also drop. Command Read CAIC RGB LEDCurrent (5Fh) can be used to read the actual LED currents for the image currently beingdisplayed.

● In the case of an all-white image, the values read by command Read CAIC RGB LEDCurrent (5Fh) will closely match but may not exactly match those requested usingcommand Write RGB LED Current (54h) . For an all-white image command Read CAICRGB LED Current (5Fh) will give currents within ±4 PAD device current steps for eachLED color relative to those requested by command Write RGB LED Current (54h).

● When command Write RGB LED Current (54h) is used to change the LED currents, theLED current for any color should not be changed by more than ±25% from the nominalcurrent used for that color when the CAIC LUTs were created. Furthermore, no LEDcurrent should be set to a current value beyond the maximum value supported in theCAIC Intensity-to-Current LUT for the corresponding color.

● The maximum total LED power for any displayed image occurs for an all-white imagesince in this case the CAIC algorithm will request the CAIC LED max available power.The max available LED power for CAIC is controlled by command Write RGB LEDCurrent since this command controls currents for an all-white image. After the currents areadjusted, command Read CAIC LED Max Available Power (57h) can be used to see themax power in Watts that CAIC derived.



http://www.ti.com



2.3.3.49 Read RGB LED Current (55h)

2.3.3.49.1 ReadThis command is used to read the state of the current for the red, green, and blue LEDs of the displaymodule.




Note 1: See the Write RGB LED Current Control command 54h for a detailed description of the returnparameters.

Note 2: Unused, most significant bits will be set to 0.



http://www.ti.com



2.3.3.50 Read CAIC LED Max Available Power (57h)

2.3.3.50.1 ReadThis command is used to read the maximum LED power allowed for the display module at the LEDcurrent settings set by the Write RGB LED Current (54h) command.



Parameter Bytes DescriptionByte 1 Maximum LED Power (LSByte)Byte 2 Maximum LED Power (MSByte)

Note 1: The value will be specified in Watts × 100Example: 25.75 W = A0Fh

Note 2: This command is only applicable when CAIC is enabled.

Note 3: The maximum available LED power associated with the CAIC algorithm is specific to an allwhite displayed image where the LED currents are set by the Write RGB LED Currentcommand (Section 2.3.3.48).

The calculation is:

Max Avail Pwr = (Rdc × Rledc × Rledv) + (Gdc × Gledc × Gledv) + (Bdc × Bledc × Bledv)1. Rdc = Red Duty Cycle; Rledc = Red LED Current; Rledv = Red LED Voltage2. Gdc = Green Duty Cycle; Gledc = Green LED Current; Gledv = Green LED Voltage3. Bdc = Blue Duty Cycle; Bledc = Blue LED Current; Bledv = Blue LED Voltage

Example: (.30 × .49 A × 2.0 V) + (.50 × .39 A × 3.1 V) + (.20 × .39 A × 3.1 V) = 1.140 W



http://www.ti.com



2.3.3.51 Write RGB LED Max Current (5Ch)

2.3.3.51.1 WriteThis command is used to specify the maximum LED current allowed for each LED in the display modulewhen CAIC is disabled.


Parameter Bytes DescriptionByte 1 Maximum Red LED Current (LSByte)Byte 2 Maximum Red LED Current (MSByte)Byte 3 Maximum Green LED Current (LSByte)Byte 4 Maximum Green LED Current (MSByte)Byte 5 Maximum Blue LED Current (LSByte)Byte 6 Maximum Blue LED Current (MSByte)


Note 1: The parameters specified by this command will have a resolution of 10 bits, and are to be asdefined by the appropriate PAD specification.

Note 2: This command sets the maximum LED currents that can be used when the CAIC algorithm isdisabled. When the CAIC algorithm is enabled, the maximum LED currents are determined bythe CAIC algorithm LUTs stored in Flash.

Note 3: For further information about LED current and the CAIC algorithm, see the notes for the WriteRGB LED Current (54h) command.

Note 4: Unused, most significant bits should be set to 0.



http://www.ti.com



2.3.3.52 Read RGB LED Max Current (5Dh)

2.3.3.52.1 ReadThis command is used to read the specified maximum LED current allowed for each LED in the displaymodule.



Parameter Bytes DescriptionByte 1 Maximum Red LED Current (LSByte)Byte 2 Maximum Red LED Current (MSByte)Byte 3 Maximum Green LED Current (LSByte)Byte 4 Maximum Green LED Current (MSByte)Byte 5 Maximum Blue LED Current (LSByte)Byte 6 Maximum Blue LED Current (MSByte)

Note 1: See the Write RGB LED Current Control command for a detailed description of the returnparameters.




http://www.ti.com



2.3.3.53 Read Measured LED Parameters (5Eh)

2.3.3.53.1 ReadThis command is used to read the measured values for a number of LED-based parameters in the displaymodule.



Parameter Bytes DescriptionByte 1 Measured Red LED Current (LSByte)Byte 2 Measured Red LED Current (MSByte)Byte 3 Measured Green LED Current (LSByte)Byte 4 Measured Green LED Current (MSByte)Byte 5 Measured Blue LED Current (LSByte)Byte 6 Measured Blue LED Current (MSByte)Byte 7 Measured Red LED Voltage (LSByte)Byte 8 Measured Red LED Voltage (MSByte)Byte 9 Measured Green LED Voltage (LSByte)Byte 10 Measured Green LED Voltage (MSByte)Byte 11 Measured Blue LED Voltage (LSByte)Byte 12 Measured Blue LED Voltage (MSByte)Byte 13 Measured Red LED Power (LSByte)Byte 14 Measured Red LED Power (MSByte)Byte 15 Measured Green LED Power (LSByte)Byte 16 Measured Green LED Power (MSByte)Byte 17 Measured Blue LED Power (LSByte)Byte 18 Measured Blue LED Power (MSByte)Byte 19 Total LED Power (LSByte)Byte 20 Total LED Power (MSByte)

Note 1: Current will be specified as Milliamps × 2, with the maximum value = 32,767.5 mAExample: 1287.5 mA = 0A0Fh

Note 2: Voltage will be specified as Voltage × 1700, with the maximum value = 38.550 VExample: 1.548 mA = 0A48h

Note 3: Power will be specified as Watts × 325, with the maximum value = 201.64 WExample: 7.923 W = A0Fh



http://www.ti.com



2.3.3.54 Read CAIC RGB LED Current (5Fh)

2.3.3.54.1 ReadThis command is used to read the state of the current for the red, green, and blue LEDs of the displaymodule.




Note 1: The parameters returned by this command will have a resolution of 10 bits, and will be asdefined by the appropriate PAD specification.

Note 2: When the CAIC algorithm is enabled using the LED Output Control Method command:● The Write RGB LED Current command will directly set the LED currents when an all white

image is being displayed. If the image is changed from an all white image, depending onthe image, the CAIC algorithm may alter one or more of the LED currents from thosespecified the Write RGB LED current command and the total LED power may also drop.The actual LED currents for the image currently being displayed can be read using thiscommand (the Read CAIC RGB LED Current (5Fh) command).

● In the case of an all white image, the values returned by this command will closely match,but may not exactly match, those specified using the Write RGB LED Current command.For an all white image, this command will provide values within +/- 4 PAD device currentsteps for each LED color relative to those specified with the Write RGB LED Currentcommand.

Note 3: Use of this command is only appropriate when the LED Output Control Method is set toCAIC (Automatic) RGB LED Current Control.




http://www.ti.com



2.3.3.55 Write Local Area Brightness Boost Control (80h)

2.3.3.55.1 ReadThis command is used to control the local area brightness boost image processing functionality for thedisplay module.


Parameter Bytes DescriptionByte 1 See BelowByte 2 LABB Strength setting


b(7:4) – Sharpness Strength

b(3:2) – Reserved

b(1:0) – LABB Control0h: Disabled1h: Enabled: Manual Strength Control (nolight sensor)2h: Enabled: Automatic Strength Control(uses light sensor)3h: Reserved

Default: 0001h

Note 1: The key function of the LABB is to adaptively gain up darker parts of the image to achieve anoverall brighter image.

Note 2: For automatic strength control, a light sensor will be used to automatically adjust the appliedimage strength based on the measured black level of the screen, or the ambient lighting levelof the room.

Note 3: For LABB Strength, 0 indicates no boost applied, and 255 indicates the maximum boost that isconsidered viable in a product. The strength is not a direct indication of the gain since the gainwill vary depending on image content.

Note 4: Sharpness strength can range from 0 to 15, with 0 indicating sharpness disabled, and 15indicating the maximum sharpness. The LABB function must be enabled (either Manual orAutomatic) to make use of Sharpness.

Note 5: LABB is supported in TPG, Splash, External Input mode, but auto-disabled in curtain mode.



http://www.ti.com



2.3.3.56 Read Local Area Brightness Boost Control (81h)

2.3.3.56.1 ReadThis command is used to read the state of the local area brightness boost image processing functionalityfor the display module.



Parameter Bytes DescriptionByte 1 See BelowByte 2 LABB Strength settingByte 3 LABB Gain Value


b(7:4) – Sharpness Strength

b(3:2) – Reserved

b(1:0) – LABB Control0h: Disabled1h: Enabled: Manual Strength Control (nolight sensor)2h: Enabled: Automatic Strength Control(uses light sensor)3h: Reserved

Note 1: Shows the bit order and weighting for the LABB Gain value, which can range from 1 to almost8 (ASIC software should limit the lower value to 1).

Table 2-17. Bit Weight Definition for LABB Gain Value

b7 b6 b5 b4 b3 b2 b1 b022 21 20 2-1 2-2 2-3 2-4 2-5

Note 2: The software equation to calculate LABB Gain as a fixed point value is shown below:

LABB_gain = add_8lsb(APL) / pre_LABB_APL (//add 8 LSBs (u8.0 / u8.0 = u8.8 / u8.0 = u8.8)



http://www.ti.com



2.3.3.57 Write CAIC Image Processing Control (84h)

2.3.3.57.1 WriteThis command is used to control the CAIC functionality for the display module.


Parameter Bytes DescriptionByte 1 See BelowByte 2 CAIC Maximum Lumens GainByte 3 CAIC Clipping Threshold


b(7) – CAIC Gain Display Enable0h: Disabled1h: Enabled

b(6) – CAIC Gain Display Scale0h: 100% = 1024 Pixels1h: 100% = 512 Pixels

b(5:3) – Reserved

b(2:0) – CAIC WPC Control0h: White Point Correction Disabled1h: White Point Correction Enabledelse: Reserved


Note 1: The CAIC algorithm (Content Adaptive Illumination Control) provides adaptive control of theLED currents and the digital gain applied to the image. In addition, when an external sensor isprovided by the OEM (and when WPC is enabled by this command), the algorithm will provideautomatic white point correction.

Note 2: The CAIC algorithm is enabled or disabled based on the method of LED current controlselected by the OEM using the Write LED Output Control Method (Section 2.3.3.44) command.When enabled, the CAIC algorithm provides automatic control of the LED currents as specifiedby this command and the Write LED Output Control Method command.

Note 3: The CAIC Gain Display provides a visual presentation of the instantaneous gain provided bythe CAIC algorithm. This is typically used as a debug tool and to show the performance of thealgorithm. It should never be used for normal operation. The display is made up of 5 bars,where the bottom three bars (green, red, and blue) show the respective CAIC gain for eachcolor. The top two bars are for TI debug use only. For SW, the CAIC Gain Display Enable iscontrolled by CAIC_DEBUG_MODE (2:0), where Disabled = 0h, and Enabled = 3h. TheDisplay Scale is set using CAIC_DEBUG_MODE(3).

Note 4: Table 2-18 shows the bit order and weighting for the CAIC Maximum Lumens Gain value,which has a valid range from 1.0 to 4.0. Values outside of this range will be considered an error(invalid command parameter value – communication status) and the command will not beexecuted.



http://www.ti.com



Table 2-18. Bit Weight Definition for the CAIC Maximum Gain Value

b7 b6 b5 b4 b3 b2 b1 b022 21 20 2-1 2-2 2-3 2-4 2-5

Note 5: The CAIC Maximum Lumens Gain parameter sets the maximum lumens gain that a pixel canhave as a result of both digital gain and increasing LED currents. It also serves to bias theCAIC algorithm towards either Constant Power (variable brightness) or Constant Lumens(variable power). Some examples are listed below:● Maximum Gain value = 1.0: This biases performance to Constant Lumens. In this case,

LED power is reduced for those images where this is possible, but lumens do notincrease or decrease.

● Maximum Lumens Gain value = 4.0: This biases performance to Constant Power. In thiscase, power is held constant for most images, while the lumens are gained up. It shouldbe noted that for the small percent of images where the gain would exceed 4.0, lumenswill stop increasing and the power is reduced instead.

Note 6: Table 2-19 shows the bit order and weighting for the CAIC Clipping Threshold value, whichhas a valid range from 0.0% to 2.0%. Values outside of this range will be considered an error(invalid command parameter value – communication status) and the command will not beexecuted.

Table 2-19. Bit Weight Definition for the CAIC Clipping Threshold Value

b7 b6 b5 b4 b3 b2 b1 b021 20 2-1 2-2 2-3 2-4 2-5 2-6

Note 7: The CAIC Clipping Threshold parameter sets the percentage of pixels that can be clipped bythe CAIC algorithm over the full frame of active data due to the digital gain being applied by theCAIC algorithm.

Note 8: Table 2-20 shows the bit order and weighting for the CAIC RGB Intensity Gain values, whichhave a valid range from 0.0 to almost 1.0. Values outside of this range will be considered anerror (invalid command parameter value – communication status) and the command will not beexecuted.

Table 2-20. Bit Weight Definition for the CAIC RGB Intensity Gain Values

b1 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b05Re Res Res Res Res Res 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10s

Note 9: CAIC can be enabled in TPG and External Input mode, but auto-disabled in Splash and Curtainmode.

Feature TPG Splash Curtain External InputLABB Supported Supported Auto-Disabled SupportedCAIC Supported Auto-Disabled Auto-Disabled Supported



http://www.ti.com



2.3.3.58 Read CAIC Image Processing Control (85h)

2.3.3.58.1 ReadThis command is used to read the state of the CAIC functionality within the display module.


2.3.3.58.3 Return Parameters



b(7) – CAIC Gain Display Enable0h: Disabled1h: Enabled

b(6) – CAIC Gain Display Scale0h: 100% = 1024 Pixels1h: 100% = 512 Pixels

b(5:3) Reserved–

b(2:0) CAIC WPC Control–

0h: White Point Correction Disabled1h: White Point Correction Enabledelse: Reserved

Note 1: Information on these parameters can be found in the notes for the Write CAIC ImageProcessing Control command (Section 2.3.3.57).



http://www.ti.com



2.3.3.59 Write Color Coordinate Adjustment Control (86h)

2.3.3.59.1 WriteThis command is used to control the CCA image processing functionality for the display module.




b(7:1) – Reserved

b(0) – CCA Enable0h: Disabled1h: Enabled

Default: 01h

Note 1: This command is for TI debug purposes only. This function should remain enabled duringnormal operation.

Note 2: When CCA is disabled, and identity matrix should be used.

2.3.3.60 Read Color Coordinate Adjustment Control (87h)

2.3.3.60.1 ReadThis command is used to read the state of the CCA image processing within the display module.





b(7:1) – Reserved

b(0) – CCA Enable0h: Disabled1h: Enabled



http://www.ti.com



2.3.3.61 Write Border Color (B2h)

2.3.3.61.1 WriteThis command is used to specify the on screen border color for the display module.




b(7:3) – Reserved

b(2:0) – Display Border Color0h: Black1h: Red2h: Green3h: Blue4h: Cyan5h: Magenta6h: Yellow7h: White

Default: 00h

Note 1: Whenever the display image size is smaller than the active area of the DMD, this border colorwill be used for all non image pixels. Some examples where a border might come into playwould be for a Window Box, Pillar Box, or Letterbox image.

Note 2: For the special case of displaying a pillar box image (Figure 2-13), the OEM can make use ofthe border color defined by this command, or make use of a dithered 24-bit border color. Thedefinition of this dithered 24-bit border color, as well as the decision whether to use it, or usethe color selected by this command is made with the DLP Composer software tool and storedin flash.

Note 3: The border color specified by this command is separate from the curtain color defined in theDisplay Image Curtain command (Section 2.3.3.19), even though they are both displayed usingthe curtain capability.

Note 4: The dithered 24-bit border color is specified in the VGP/CCP.



http://www.ti.com


Sign of Temperature:0 = Positive Temperature1 = Negative Temperature

Magnitude of Temperature:Divide by 10 (Decimal) to Find Magnitude

Example #1: b(11:0) = 000110101010 426d / 10d = +42.6°C

Example #2: b(11:0) = 100110101010 426d / 10d = í42.6°C

b11 b10 ... b0


Figure 2-13. Pillar-Box Border Example



http://www.ti.com



2.3.3.62 Read Border Color (B3h)

2.3.3.62.1 ReadThis command is used to read the state of the on screen border color for the display module.





b(7) – Pillar-Box Border Color Source0h: Defined by this command1h: Flash defined 24-bit color

b(6:3) – Reserved

Display Border Color0h: Black1h: Red2h: Green3h: Blue4h: Cyan5h: Magenta6h: Yellow7h: White

Note 1: For the special case of a pillar box image (Figure 2-13), the OEM can make use of the bordercolor defined by the Write Border Color command (Section 2.3.3.61), or make use of a dithered24-bit border color. The definition of this dithered 24-bit border color, as well as the decisionwhether to use it, or use the color selected by this command is made with the DLPComposer™ software tool and stored in flash. The use decision stored in flash is shown by bit-7 of this command.



http://www.ti.com



2.3.3.63 Write External Parallel I/F SYNC Polarity (B6h)

2.3.3.63.1 WriteThis command is used to specify the SYNC polarity for the external parallel interface of the displaymodule.




b(7:3) Reserved–

b(2) – Manual Mode – Parallel Port HSYNC Polarity0h: Falling Edge Active (Negative Pulse)1h: Rising Edge Active (Positive Pulse)

b(1) – Manual Mode – Parallel Port VSYNC Polarity0h: Falling Edge Active (Negative Pulse)1h: Rising Edge Active (Positive Pulse)

b(0) – Parallel Port Sync Polarity Mode0h: Automatic Mode1h: Manual Mode

Default: 00h

Note 1: This command is required whenever the source makes use of the Parallel port input, except forBT656 sources. This command is not applicable for BT656 sources. In Automatic mode, thesystem can typically determine the appropriate polarity of the syncs. In Manual mode, the OEMis allowed to specify these polarities should the need arise.



http://www.ti.com



2.3.3.64 Read External Parallel I/F SYNC Polarity (B7h)

2.3.3.64.1 ReadThis command is used to read the state of the SYNC polarity for the external parallel interface of thedisplay module.





b(7:2) – Reserved

b(1) – Parallel Port HSYNC Polarity0h: Falling Edge Active (Negative Pulse)1h: Rising Edge Active (Positive Pulse)

b(0) – Parallel Port VSYNC Polarity0h: Falling Edge Active (Negative Pulse)1h: Rising Edge Active (Positive Pulse)



http://www.ti.com



2.3.3.65 Write External Parallel I/F Video Manual Image Framing (B8h)

2.3.3.65.1 WriteThis command is used to specify the external parallel interface video manual image framing parametersfor the display module.


Parameter Bytes DescriptionByte 1 See BelowByte 2 Start Pixel (LSByte)Byte 3 Start Pixel (MSByte)Byte 4 Start Line (MSByte)Byte 5 Start Line (MSByte)


b(7:1) – Reserved

b(0) – External Video Manual Image FramingEnable0h: Disabled1h: Enable

Default: All bytes: 00h

Note 1: This command is only required when the source data for the parallel interface does not providean active data valid framing signal (vertical and horizontal syncs are still required). These arereferenced to the appropriate sync signal (for example, start pixel referenced to each horizontalsync). This command is used in conjunction with the Write Video Input Image Size command(Section 2.3.3.33).

Note 2: The user must enable or disable manual framing as appropriate. If manual framing is specified,it will be used even if an active data valid framing signal is provided with the input. (In otherwords, manual framing will override the active data valid signal.)

Note 3: The parameter values are to be 1 based. (That is, a value of 1 will specify the first pixel of aline, of the first line of the frame.)

Note 4: This function is NOT applicable to BT656 sources. Framing for these sources will be handledautomatically by the system.



http://www.ti.com



2.3.3.66 Read External Parallel I/F Video Manual Image Framing (B9h)

2.3.3.66.1 ReadThis command is used to read the state of the external parallel interface video manual image framingparameters for the display module



Parameter Bytes DescriptionByte 1 See BelowByte 2 Start Pixel (LSByte)Byte 3 Start Pixel (MSByte)Byte 4 Start Line (MSByte)Byte 5 Start Line (MSByte)


b(7:1) – Reserved

b(0) – External Video Manual Image Framing Enable0h: Disabled1h: Enable

Note 1: The parameter values are to be 1 based. (That is, a value of 1 will specify the first pixel of aline, of the first line of the frame.)



http://www.ti.com



2.3.3.67 Read Auto Framing Information (BAh)

2.3.3.67.1 ReadThis command is used to read the external input framing information that is automatically determined bythe display module



Parameter Bytes DescriptionByte 1 External Input VSYNC Rate (LSByte)Byte 2 External Input VSYNC RateByte 3 External Input VSYNC RateByte 4 External Input VSYNC Rate (MSByte)Byte 5 External Input Total Pixels per Line (LSByte)Byte 6 External Input Total Pixels per Line (MSByte)Byte 7 External Input Total Lines per Frame (LSByte)Byte 8 External Input Total Lines per Frame (MSByte)Byte 9 External Input Active Pixels per Line (LSByte)Byte 10 External Input Active Pixels per Line (MSByte)Byte 11 External Input Active Lines per Frame (LSByte)Byte 12 External Input Active Lines per Frame (MSByte)Byte 13 Pixel/Line Reference Clock Rate (LSByte)Byte 14 Pixel/Line Reference Clock Rate (MSByte)

Note 1: In most cases, the above data can be measured by the system (even when manual dataframing is used). This data is provided for debug purposes only.

Note 2: The external input frame rate is returned as a count that is specified in units of 66.67ns (basedon the internal 15MHz clock used to time between input frame syncs).

Note 3: The pixels per line and lines per frame parameters are to be 1 based. (That is, a value of 1280active pixels indicates that there are 1280 active pixels per line.)

Note 4: The pixels per line and lines per frame parameters are based on measurement of the actualinput pixel clock for the Parallel Bus. This clock rate is returned as the Pixel/Line ReferenceClock Rate. This parameter value is the clock rate times 100 in MHz (for example, 60.00MHz =1770h).



http://www.ti.com



2.3.3.68 Read Short Status (D0h)

2.3.3.68.1 ReadThis command is used to provide a short system status for the display module.




msb Byte 1 - General Status lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7) – Boot/Main Application0h: Boot1h: Main

b(6) – Reserved

b(5) – Flash Error0h: No Error1h: Error

b(4) – Flash Erase Complete0h: Complete1h: Not Complete

b(3) – System Error0h: No Error1h: Error

b(2) – Reserved

b(1) – Communication Error0h: No Error1h: Error

b(0) – System Initialization0h: Not Complete1h: Complete

Note 1: The Flash Erase Complete status bit will be set at the start of the Flash erase process, and willbe cleared when the erase process is complete. The flash status can be obtained during orafter the erase process. To obtain this status during the erase process, only this command canbe sent after the start of the flash erase. If any other command is sent during the eraseprocess, it will be held without processing until the flash erase has completed (thus blockingany following status requests until the previously sent command is processed).



http://www.ti.com



Note 2: The Flash Error bit is used to indicate an error during any Flash operation. For Flash writes,this bit will be updated at the end of each write transaction, however, once an error has beendetected, this bit will remain in the error state until cleared. This will allow the OEM the optionof checking the status between each write transaction, or at the end of the update. Once awrite transaction has started, the flash status (and this error bit) will not be accessible until thewrite transaction has completed.

Note 3: The Communication Error bit is used to indicate any error on the I2C command interfaces.Specific details about communication errors are available using the Read CommunicationStatus command (Section 2.3.3.71).

Note 4: Any errors other than Flash Error and Communication Error are indicated by the System Errorbit. Specific details about system errors are available using the Read System Status command(Section 2.3.3.69).

Note 5: The Flash Error, Communication Error, and System Error bits will be cleared when the ReadShort Status is read.

Note 6: The Read Short Status command should only be checked periodically, not continuously. It islikely that continuous access will severely impact system performance.



http://www.ti.com



2.3.3.69 Read System Status (D1h)

2.3.3.69.1 ReadThis command is used to read system status information for the display module.



Parameter Bytes DescriptionByte 1 DMD Interface StatusByte 2 LED StatusByte 3 Internal Interrupt StatusByte 4 Misc. Status

Note 1: All system status error bits will be cleared when the Read System Status is read.

msb Byte 1 – DMD Interface Status lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:3) – Reserved

b(2) – DMD Training Error0h: No Error1h: Error

b(1) – DMD Interface Error0h: No Error1h: Error

b(0) – DMD Device Error0h: No Error1h: Error

Note 1: The system will set the DMD Device Error for the following conditions:● The system cannot read the DMD Device ID from the DMD● The Composer specified DMD Device ID does not match the actual DMD Device ID

Note 2: The system will set the DMD Interface Error when there are power management setup conflictson this interface.

Note 3: The system will set the DMD Training Error when the training algorithm can’t find a data eyethat will meet the specified requirements.

msb Byte 2 – LED Status lsbb7 b6 b5 b4 b3 b2 b1 b0



http://www.ti.com



b(7:6) – Reserved

b(5) – Blue LED Error0h: No Error1h: Error

b(4) – Green LED Error0h: No Error1h: Error

b(3) – Red LED Error0h: No Error1h: Error

b(2) – Blue LED State0h: Off1h: On

b(1) – Green LED State0h: Off1h: On

b(0) – Red LED State0h: Off1h: On

msb Byte 3 – Internal Interrupt Status lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:2) – TBD

b(1) – Sequence Error0h: No Error1h: Error

b(0) – Sequence Abort Error0h: No Error1h: Error

msb Byte 4 – Misc. Status lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:6) – Reserved

b(5) – Watchdog Timer Timeout0h: No Timeout1h: Timeout

b(4) – Product Configuration Error0h: No Error1h: Error

b(3) – Master vs. Slave Operation



http://www.ti.com



0h: Master1h: Slave

b(2) – Single vs. Dual ASIC Configuration0h: Single1h: Dual

b(1) – SPI Flashless Communication Error0h: No Error1h: Error

b(0) – SPI Flashless Data Request Error0h: No Error1h: Error

Note 1: The system will set the SPI Flashless Data Request Error bit if the display does not startsending the requested data before the SPI flashless data request timeout is exceeded. Oncethe timeout is exceeded, the display will abort the current request, and then try again.

Note 2: The system will set the SPI Flashless Communication Error bit if the display has threeconsecutive SPI Flashless Data Request Errors. If this happens, it is assume that the SPIcommunication link is not operational, and system operations will halt. A reset will be requiredto restart operations.

Note 3: The system will set the Master vs. Slave bit as appropriate in both single and dual ASICconfigurations.

Note 4: The system will set the Product Configuration Error bit if it determines that some piece of theproduct configuration is not correct. Some examples are:● Invalid ASIC/DMD Combination● Invalid ASIC/DLPA300x Combination● Invalid Flash build for current ASIC, DMD, and/or DLPA300x configuration

Note 5: The system will set the Watchdog Timer Timeout bit if the system has been reset due to awatchdog timer timeout.



http://www.ti.com



2.3.3.70 Read System Software Version (D2h)

2.3.3.70.1 ReadThis command is used to read the main application software version information for the display module.



Parameter Bytes DescriptionByte 1 ASIC Main Application Software Version Patch LSByteByte 2 ASIC Main Application Software Version Patch MSByteByte 3 ASIC Main Application Software Version MinorByte 4 ASIC Main Application Software Version Major



http://www.ti.com



2.3.3.71 Read Communication Status (D3h)

2.3.3.71.1 ReadThis command is used to read system status information for the display module.


Parameter Bytes DescriptionByte 1 Command Bus Status Selection

msb Byte 1 – Command Bus Status Selection lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:2) – Reserved

b(1:0) – Command Bus Status Selection0h: Reserved1h: Reserved10h: I2C only11h: Reserved

Note 1: This command will return the communication status for the command bus specified.● Reserved: This selection will return status bytes 1 through 6● Reserved: This selection will return status bytes 1 though 4● I2C only: This selection will return status bytes 5 though 6

Return ParametersThe return parameters are described below.

Parameter Bytes DescriptionByte 1 ReservedByte 2 ReservedByte 3 ReservedByte 4 ReservedByte 5 I2C Communication StatusByte 6 I2C Aborted Op-Code

Note 1: All communication status error bits will be cleared when the Read Communication Status isread.

msb Byte 5 – I2C Communication Status lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7) – Reserved

b(6) – Bus Timeout by Display Error0h: No Error



http://www.ti.com



1h: Error

b(5) – Invalid Number of Command Parameters0h: No Error1h: Error

b(4) – Read Command Error0h: No Error1h: Error

b(3) – Flash Batch File Error0h: No Error1h: Error

b(2) – Command Processing Error0h: No Error1h: Error

b(1) – Invalid Command Parameter Value0h: No Error1h: Error

b(0) – Invalid Command Error0h: No Error1h: Error

Note 1: The system will set the Invalid Command Error bit when it does not recognize the commandop-code. The invalid command op-code will be reported in the I2C CMD Error Op-Code byte ofthis status.

Note 2: The system will set the Invalid Command Parameter Error bit when the it detects that the valueof a command parameter is not valid (for example, out of allowed range).

Note 3: The system will set the Command Processing Error bit when a fault is detected whenprocessing a command. In this case, the command will be aborted with the system moving onto the next command. The op-code for the aborted command will be reported in the I2C CMDError Op-Code byte of this status.

Note 4: The system will set the Flash Batch File Error bit when an error occurs during the processing ofa flash batch file. When this bit is set, typically another bit will be set to indicate what kind oferror was detected (for example, Invalid Command Error).

Note 5: The system will set the Read Command Error bit when the host terminates the read operationbefore all of the requested data has been provided, or if the host continues to request readdata after all of the requested data has been provided.

Note 6: The system will set the Invalid Number of Command Parameters Error bit when too many ortoo few command parameters are received. In this case, the command will be aborted with thesystem moving on to the next command. The op-code for the aborted command will bereported in the I2C CMD Error Op-Code byte of this status.

Note 7: The system will set the Bus Timeout by Display Error bit when the display releases control ofthe bus because the bus timeout value was exceeded.

msb Byte 6 – I2C CMD Error Op-Code lsbb7 b6 b5 b4 b3 b2 b1 b0



http://www.ti.com



b(7:0) – I 2C CMD Error Op-Code

Note 1: The CMD Error Op-Code is associated with various I 2C communication status bits, and reportsthe op-code for an I 2C command as noted.

2.3.3.72 Read ASIC Device ID (D4h)

2.3.3.72.1 ReadThis command is used to read the ASIC Device ID for the display module.



Parameter Bytes DescriptionByte 1 Device ID


b(7:4) – Reserved

b(3:0) – ASIC Device ID

Note 1: The ASIC Device ID can be decoded using Table 2-21.

Table 2-21. ASIC Device ID Decode

ASIC Device ID Device Number DMD Resolution # of ASICs Package LED Driver00h DLPC3430 ≤ 1280 × 720 1 7 mm × 7 mm DLPA200x

(0.4-mm pitch)01h DLPC3433 ≤ 1280 × 720 1 7 mm × 7mm DLPA200x/

(0.4-mm pitch) DLPA300004h DLPC3435 ≤ 1280 × 720 1 13 mm × 13 mm DLPA200x

(0.8-mm pitch)05h DLPC3438 ≤ 1280 × 720 1 13 mm × 13 mm DLPA200x/

(0.8-mm pitch) DLPA300009h DLPC3439 1920 × 1080 2 13 mm × 13 mm DLPA3000/

(0.8-mm pitch) 3005



http://www.ti.com



2.3.3.73 Read DMD Device ID (D5h)

2.3.3.73.1 ReadThis command is used to read the DMD Device ID for the display module.


Parameter Bytes DescriptionByte 1 DMD Register Selection

msb Byte 1 – DMD Register Selection lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:3) – Reserved

b(0:0) – DMD Data Selection0h: DMD Device ID1h to 7h: Reserved


Parameter Bytes DescriptionByte 1 See DMD Device ID Reference Table.Byte 2 See DMD Device ID Reference Table.Byte 3 See DMD Device ID Reference Table.Byte 4 See DMD Device ID Reference Table.

DMD Device ID Reference TableDMD Device ID Device Description

Byte 1 Byte 2 Byte 3 Byte 4 (Resolution and Type)(Identifier) (Byte Count) (ID-MSByte) (ID-LSByte)0.2 WVGA60h 0Dh 00h 64h (854 × 480, Sub-LVDS)0.3 720p60h 0Dh 00h 68h (1280 × 720, Sub-LVDS)

0.47 1080p60h 0Dh 00h 6Bh (1920 × 1080, Sub-LVDS)



http://www.ti.com


Sign of Temperature:0 = Positive Temperature1 = Negative Temperature

Magnitude of Temperature:Divide by 10 (Decimal) to Find Magnitude

Example #1: b(11:0) = 000110101010 426d / 10d = +42.6°C

Example #2: b(11:0) = 100110101010 426d / 10d = í42.6°C

b11 b10 ... b0


2.3.3.74 Read System Temperature (D6h)

2.3.3.74.1 ReadThis command is used to read the system temperature for the display module.



Parameter Bytes DescriptionByte 1 See Below (LSByte)Byte 2 See Below (MSByte)

Note 1: Figure 2-14 shows the bit order and definition for the signed magnitude system temperaturedata, which will be returned in °C. The unspecified msbits (bits 15:12) will be set to 0.

Figure 2-14. Bit Order and Definition for System Temperature



http://www.ti.com



2.3.3.75 Read Flash Build Version (D9h)

2.3.3.75.1 ReadThis command is used to read the ASIC flash version for the display module.

2.3.3.75.2 Read ParametersThe command has no command parameters.


Parameter Bytes DescriptionByte 1 Flash Build Version Patch LSByteByte 2 Flash Build Version Patch MSByteByte 3 Flash Build Version MinorByte 4 Flash Build Version Major

Note 1: The OEM is allowed to specify (via Composer) a version number for the ASIC flash build in theformat specified by this command. This command allows the OEM to read back this versioninformation.

2.3.3.76 Write Flash Batch File Delay (DBh)

2.3.3.76.1 WriteThis command is used to specify an execution time delay within a Flash batch file for the display module.


Parameter Bytes DescriptionByte 1 Flash Batch File Delay LSBByte 2 Flash Batch File Delay MSB


Note 1: This command is used to specify an execution delay time within a Flash batch file. It can onlybe used within a Flash batch file, and is not a valid command on the I2C interfaces. (It will beflagged as a TBD command.)

Note 2: The Flash batch file delay is to be specified in units of 1 ms.Example: 500ms = 1F4h

Note 3: Typical use of this command will be in the Auto-Init Flash batch file (batch file 0), but is valid foruse in any batch file. (See Write Execute Flash Batch File in Section 2.3.3.32)

Note 4: Software should make use of the available hardware timers.



http://www.ti.com



2.3.3.77 Read DMD I/F Training Data (DCh)

2.3.3.77.1 ReadThis command is used to read back the DMD interface training data for the display module.

2.3.3.77.2 Read ParametersThe command parameter descriptions follow:

Parameter Bytes DescriptionByte 1 DMD I/F Training Data Selection (See Below)

msb Byte 1 – DMD I/F Data Selection lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:5) – Reserved

b(4) – Training Data Selection0h: High/Low/Selected1h: Full Profile

b(3:0) – ASIC Pin Pair Selection0h: A1h: B2h: C3h: D4h: E5h: F6h: G7h: H8h-Fh: Reserved

Note 1: This command will return the DMD I/F training data specified for the ASIC pin pair specified

● High/Low/Selected: This selection will return bytes 1 through 4.● Full Profile: This selection will return bytes 5 though 11.

2.3.3.77.2.1 Return ParametersThe return parameters are described below.

Parameter Bytes DescriptionByte 1 High/Low/Selected (See Below) (LSByte)Byte 2 High/Low/Selected (See Below)Byte 3 High/Low/Selected (See Below)Byte 4 High/Low/Selected (See Below) (MSByte)Byte 5 Full Profile (Bits 7-0) (LSByte)Byte 6 Full Profile (Bits 15-8)Byte 7 Full Profile (Bits 23-16)Byte 8 Full Profile (Bits 31-24)Byte 9 Full Profile (Bits 39-32)



http://www.ti.com



Parameter Bytes DescriptionByte 10 Full Profile (Bits 47-40)Byte 11 Full Profile (Bits 50-48) (MSByte)

msb Byte 1 – High/Low/Selected lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:6) – Reserved

b(5) – Training Error0h: No Error1h: Error

b(4) – Pin Pair Selected for Training0h: No1h: Yes

b(3:0) – ASIC Pin Pair Selected0h: A1h: B2h: C3h: D4h: E5h: F6h: G7h: H8h-Fh: Reserved


b(7:6) – Reserved

b(5:0) – Selected DLL Value


b(7:6) – Reserved

b(5:0) – Low Pass DLL Value




http://www.ti.com



b(7:6) – Reserved

b(5:0) – High Pass DLL Value

Note 1: This command is typically used for debug or characterization of the ASIC to DMD interface.

Note 2: The return data is specified by the read parameter data.

Note 3: DMD I/F training tests/calibrates the DLL that is associated with each ASIC pin pair, trying eachof the DLL parameter values (0 to 50), looking for a pass (0) or fail (1) response for each value.Thus, the full training profile for each pin pair is made up of a 51-bit pass/fail result. This resultis provided on Full Profile bits 50:0.

Note 4: The full profile response should have a region of contiguous passing DLL values. The highestDLL value for this contiguous region is returned as the High, the smallest DLL value is returnedas the Low, and the algorithm selected value as the Selected.

Note 5: This command does not run the DMD I/F training algorithm. This is done automatically by thesystem. This command returns the result from the most resent training event.



http://www.ti.com



2.3.3.78 Flash Update PreCheck (DDh)

2.3.3.78.1 ReadThis command is used to verify that a pending flash update (write) is appropriate for the specified block ofthe display module flash.

2.3.3.78.2 Read ParametersThe command parameter descriptions follow:

Parameter Bytes DescriptionByte 1 Flash Build Data Size (LSByte)Byte 2 Flash Build Data SizeByte 3 Flash Build Data SizeByte 4 Flash Build Data Size (MSByte)


msb Byte 1 – Flash PreCheck Results lsbb7 b6 b5 b4 b3 b2 b1 b0

b(7:3) – Reserved

b(2) – Package Configuration (Identifier)0h: No Error1h: Error

b(1) – Package Configuration (Collapsed)0h: No Error1h: Error

b(0) – Package Size0h: No Error1h: Error

Note 1: This command is used in conjunction with the Flash Data Type Select (Section 2.3.3.79)command. This command would be sent after the flash data type has been selected, but beforeany other flash operation. The purpose is to verify that the desired flash update is compatible,and will fit within the existing flash space, for the current flash configuration.

Note 2: The Flash Build Data Size specifies the size of the flash update package in bytes.

Note 3: When the ASIC software receives the flash build data size, it will verify that the package isappropriate for the specified location. This to include size, identifier, sequence build type, andso forth.

Note 3: A Package Size error indicates that the flash package is too large to fit into the specifiedlocation. A few examples are listed below.

● If replacing the entire flash, the size of the flash build exceeds the size of the flash devicein the system.

● If replacing the entire flash except for the OEM blocks, the size of the flash build will eitheroverwrite some portion of the existing OEM blocks, or exceeds the size of the flash devicein the system.



http://www.ti.com



● If replacing the LOOK block, the size of the flash build exceeds the size of the existingLOOK block in the flash.

● If replacing a single sequence (that is, partial update), the size of the flash build exceedsthe size of the existing splash screen.

Note 5: A Package Configuration error indicates that the flash package is not appropriate for the flashupdate requested. An example is listed below.● If replacing a single splash screen (that is, partial update), and the specified splash screen

index value (Identifier) is not being used in the flash build. Partial updates can onlyreplace an existing flash entity.

Note 6: If an error is returned by this command, the OEM is responsible for correcting the error beforeupdating the flash. If the OEM chooses to ignore the error and update the flash anyway, thesystem will allow this. In this case, the OEM is responsible for any problems or systembehaviors that arise from this. It should also be noted that this PreCheck does NOT cover allpossible mismatches that might arise when replacing blocks or partial blocks in the flash.



http://www.ti.com



2.3.3.79 Flash Data Type Select (DEh)

2.3.3.79.1 WriteThis command is used to specify the type of data that will be written to or read from the Flash of thedisplay module.


Parameter Bytes DescriptionByte 1 Flash Data Type

(See Below)Byte 2 Optional: Partial Data Identifier

(See Byte 1 and Notes 1, 4 and 5)Byte 3 Optional: Partial Data Identifier

(See Byte 1 and Notes 1, 4 and 5)Byte 4 Optional: Partial Data Identifier

(See Byte 1 and Notes 1, 4 and 5)

Default: 00h


b(7:0) – Flash Data Type

–––––– Entire Flash ––––––00h – Entire Flash02h – Entire Flash except OEM Calibration Data and OEM Scratchpad Data01h, 03h- Reserved0Fh –

––– TI Software –––10h – Main Software Application11h-1Fh – Reserved

––– TI Application Data –––20h – TI Application Data Set (AOM)21h-2Fh – Reserved

––– OEM Batch Files –––30h – OEM Batch Files31h-3Fh – Reserved

––– Look Data –––40h – Look Data Set41h-4Fh – Reserved

––– Sequence Data –––50h – Entire Sequence Data Set51h – Partial Sequence Data Set (Reads Only)52h-5Fh – Reserved

––– Degamma/CMT Data –––



http://www.ti.com



60h – Entire Degamma/CMT Data Set61h – Partial Degamma/CMT Data Set (Reads

Only)62h-6Fh – Reserved

––– CCA Data –––70h – CCA Data Set71h-7Fh – Reserved

––– General LUT Data –––80h – General LUT Data Set81h-8Fh – Reserved

––– OEM Splash Screen Data –––90h – Entire OEM Splash Screen Data Set91h – Partial OEM Splash Screen Data Set92h-9Fh – Reserved

––– OEM Calibration Data –––A0h – OEM Calibration Data SetA1h-AFh – Reserved

––– OEM Scratchpad Data –––B0h – Entire OEM Scratchpad Data Set 0B1h – Partial OEM Scratchpad Data Set 0B2h – Entire OEM Scratchpad Data Set 1B3h – Partial OEM Scratchpad Data Set 1B4h – Entire OEM Scratchpad Data Set 2B5h – Partial OEM Scratchpad Data Set 2B6h – Entire OEM Scratchpad Data Set 3B7h – Partial OEM Scratchpad Data Set 3B8h-BFh – Reserved

Note 1: The flash data type command must be provided each time a new flash write or readoperation is desired to ensure that the appropriate data type parameters are provided. Thesystem expects four parameter bytes regardless of whether all four bytes are needed. Anyunused bytes should be set to zero.

Note 2: The Flash Data Length (Section 2.3.3.80) must be provided to indicate the amount of flashdata that will be provided for each write or read transaction.

Note 3: The specified flash data will be written to or read from Flash using the Write Flash Start,Write Flash Continue, Read Flash Start , and Read Flash Continue commands discussed inSection 2.3.3.82, Section 2.3.3.83, Section 2.3.3.84, and Section 2.3.3.85, and respectively.

Note 4: While all of the flash data sets indicated can be written/replaced in their entirety, a few willalso support partial writes/updates. Partial update command parameters will use an oddcommand number (such as 91h or B1h) which will indicate that one to three additionalcommand parameter bytes of information must be provided to specify which subset of datais to be updated. The additional command parameter data required is described in Table 2-22.



http://www.ti.com



Table 2-22. 2nd Command Parameter for Partial Flash Data Set Updates (Writes)

3rd CMD 4th CMDData Type 2nd CMD parameter parameter parameter Comments(Writes Only) (Byte 2) (Byte 2) (Byte 2)Partial OEM A Splash screen will be specified by its SplashSplash Screen Splash Number N/A N/A screen number (see Section 2.3.3.10)SetPartial OEM If this data set is allocated more than one sector,Scratchpad Data Sector Number N/A N/A each sector can be specifiedSet (0 = 1 st sector, 1 = 2 nd sector, and so forth.)

Note 5: While all of the flash data sets indicated can be read starting at the beginning of the data set, afew will also support read starts at the beginning of a data subset. The partial update commandparameters which use an odd command number (such as 41h, 43h, and 75h) will indicate thatone to three additional command parameter bytes must be provided to specify the start locationfor these reads. The additional command parameter data required is described in Table 2-23.

Note 6: It is expected that all TI formatted factory calibration data, including the Golden Ratio, thePower-up RGB Currents, and the OEM Thermister LUT Trim data, will be stored in the OEMCalibration block of the flash. It will be the responsibility of the OEM to manage updates to thisblock, which may require the OEM to read the entire block, modify, and then rewrite the entireblock when making an update within the block.

Table 2-23. Additional Command Parameters for Partial Flash Data Set Reads

2nd CMD 3rd CMDData Type 4th CMD parameterparameter parameter Comments(Writes Only) (Byte 2)(Byte 2) (Byte 2)Partial Look A sequence data set will be specified by itsSequence Data Sequence Index N/ANumber sequence index numberSetPartial CMT Look Degamma/CMT Index A CMT data set will be specified by its CMT indexSequence IndexData Set Number Number number (see Section 2.3.3.28)Partial OEM Splash A Splash screen will be specified by its SplashSplash Screen N/A N/ANumber screen number (see Section 2.3.3.10)Set

If this data set is allocated more than one sector,each sector can be specified (0 = 1st sector, 1 = 2nd

sector, and so forth)Partial OEM The host is also allowed to specify the startSector Sub-Sector Sub-Sector AddressScratchpad Data address within the sector specified in byte 2. ThisNumber Address (LSB) (MSB)Set address to be a relative address within the

specified sector (that is, the value can range from 0to 4096), and must be a 32-bit aligned byteaddress.

Note 7: While flash processing requires that flash commands be executed in the proper order (forexample, flash must be erased prior to being written), due to the flexibility provided for flashupdates, command order checking is not provided.

Note 8: It is recommended that the OEM make use of the Flash Update PreCheck command(Section 2.3.3.78) before updating an existing flash build.

Note 9: The system allows the OEM to allocate up to four separable blocks of flash space for their ownuse (OEM Scratchpad Data). The OEM can also specify the size of each of these blocks,where each block can be one or more sectors in (one sector = 4KB). This is all defined viaComposer. It is the responsibility of the OEM to manage these data sets, including updates,which may require the OEM to read an entire sector, modify, and then rewrite the entire sectorwhen making an update within a sector. References to an unavailable data set will result in anInvalid Command Parameter Value Error in the Communication Status (Section 2.3.3.71).



http://www.ti.com



2.3.3.80 Flash Data Length(DFh)

2.3.3.80.1 WriteThis command is used to specify the length of the data that will be written to or read from the Flash of thedisplay module.


Parameter Bytes DescriptionByte 1 Flash Data Length (lsb)Byte 2 Flash Data Length (msb)

Default: 0000h

Note 1: Flash data length must be a multiple of four bytes.

Note 2: The flash data length applies to each write or read transaction, not to the length of the datatype selected.

Note 3: The maximum data length allowed for each write transaction is 1024 bytes. The maximum datalength allowed for each read transaction is 256 bytes.




http://www.ti.com



2.3.3.81 Erase Flash Data (E0h)

2.3.3.81.1 WriteThis command directs the display module to erase the specified Flash data.


Parameter Bytes DescriptionByte 1 Signature: Value = AAhByte 2 Signature: Value = BBhByte 3 Signature: Value = CChByte 4 Signature: Value = DDh


Note 1: When this command is executed, the system will erase all sectors associated with the datatype specified by the Flash Data Type Select (Section 2.3.3.76) command. As such, thiscommand does not make use of the Flash Data Length parameter.

Note 2: Since the process of erasing Flash sectors can take a significant amount of time, the FlashErase Complete status bit in the Read Short Status command (Section 2.3.3.68) should bechecked periodically (not continuously) to determine when this task has been completed. Thisbit will be set at the start of the erase process, and will be cleared when the erase process iscomplete. Flash writes should not be started before the erase process has been completed.


Note 4: The signature bytes are used to minimize unintended flash erases. The command OpCode andfour signature bytes must be received correctly before this command will be recognized andexecuted.



http://www.ti.com



2.3.3.82 Write Flash Start (E1h)

2.3.3.82.1 WriteThis command is used to write data to the Flash for the display module.


Parameter Bytes DescriptionByte 1 Data Byte 1Byte 2 Data Byte 2Byte 3 Data Byte 3Byte 4 Data Byte 4Byte 5 … n Data Byte 5 … n

Note 1: The Flash Data Length command (Section 2.3.3.80) must be used to specify how much datawill be sent by the Write Flash Start command.

Note 2: The Write Flash Start command is used to write up to 1024 bytes of data starting at the firstaddress of the data type selected. If more than 1024 bytes are to be written, the Write FlashContinue (Section 2.3.3.83) command must be used. Up to 1024 bytes of data can be writtenwith each Write Flash Continue command, which starts at the end of the last data written.

Note 3: The Flash Error bit of the Write Short Status command (Section 2.3.3.67) will indicate if theFlash update was successful. This bit will be set for an error at the end of each writetransaction, however, once an error has been detected, this bit will remain in the error stateuntil a new data type is selected (selecting a new data type will clear this bit). This will allow theOEM the option of checking the status between each write transaction, or at the end of theupdate of a specific data type. Once a write transaction has started, the flash status (and thiserror bit) will not be accessible until the write transaction has completed.




http://www.ti.com



2.3.3.83 Write Flash Continue (E2h)

2.3.3.83.1 WriteThis command is used to write data to the Flash for the display module.



Note 1: The Flash Data Length command must be used to specify how much data will be sent by theWrite Flash Continue command.

Note 2: The Write Flash Start command (Section 2.3.3.82) is used to write up to 1024 bytes of datastarting at the first address of the data type selected. If more than 1024 bytes are to be written,the Write Flash Continue command must be used. Up to 1024 bytes of data can be written witheach Write Flash Continue command, which starts at the end of the last data written.

Note 3: The Flash Error bit of the Write Short Status command (Section 2.3.3.67) will indicate if theFlash update was successful. This bit will be set for an error at the end of each writetransaction, however, once an error has been detected, this bit will remain in the error stateuntil a new data type is selected (selecting a new data type will clear this bit). This will allow theOEM the option of checking the status between each write transaction, or at the end of theupdate of a specific data type. Once a write transaction has started, the flash status (and thiserror bit) will not be accessible until the write transaction has completed.




http://www.ti.com



2.3.3.84 Read Flash Start (E3h)

2.3.3.84.1 ReadThis command is used to read data from the Flash for the display module.


2.3.3.84.3 Return ParametersThis command has a variable number of return parameters as described below.


Note 1: The Flash Data Length command (Section 2.3.3.80) must be used to specify how much data isto be read by the Read Flash Start command.

Note 2: The Read Flash Start command is used to read up to 256 bytes of data starting at the specifiedaddress, or at the first address, of the data type selected. If more than 256 bytes are to beread, the Read Flash Continue command (Section 2.3.3.85) must be used. Up to 256 bytes ofdata can be read with each Read Flash Continue command, which starts at the end of the lastdata read.




http://www.ti.com



2.3.3.85 Read Flash Continue (E4h)

2.3.3.85.1 ReadThis command is used to read data from the Flash for the display module.


2.3.3.85.3 Return ParametersThis command has a variable number of return parameters as described below.


Note 1: The Flash Data Length command (Section 2.3.3.80) must be used to specify how much data isto be read by the Read Flash Continue command.

Note 2: The Read Flash Start command (Section 2.3.3.84) is used to read up to 256 bytes of datastarting at the specified address, or at the first address of the data type selected. If more than256 bytes are to be read, the Read Flash Continue command must be used. Up to 256 bytes ofdata can be read with each Read Flash Continue command, which starts at the end of the lastdata read.




http://www.ti.com



2.3.3.86 Write Internal Register Address (E5h)

2.3.3.86.1 WriteThis command is used to specify the address of an internal register in the display module. This commandis applicable to both register writes and reads. This command is typically used for debug purposes.


Parameter Bytes DescriptionByte 1 Register Address (lsb)Byte 2 Register AddressByte 3 Register AddressByte 4 Register Address (msb)


Note 1: If a register address requires less than 4 bytes, the unused MSBytes and/or bits should be setto 0.

Note 2: Register data will be written to or read from the system at the address specified using thecommands discussed in Section 2.3.3.87 and Section 2.3.3.88.

2.3.3.87 Write Internal Register (E6h)

2.3.3.87.1 WriteThis command is used to write data to an internal register of the display module. This command istypically used for debug purposes.


Parameter Bytes DescriptionByte 1 Data Byte 1Byte 2 Data Byte 2Byte 3 Data Byte 3Byte 4 Data Byte 4

Note 1: If a register holds less than 4 bytes of data, the unused MSBytes and/or bits should be set to 0.

Note 2: This command is to be used in conjunction with the Write Internal Register Address commanddiscussed in Section 2.3.3.86.



http://www.ti.com



2.3.3.88 Read Internal Register (E7h)

2.3.3.88.1 ReadThis command is used to read data from an internal register of the display module. This command istypically used for debug purposes.



Parameter Bytes DescriptionByte 1 Data Byte 1Byte 2 Data Byte 2Byte 3 Data Byte 3Byte 4 Data Byte 4

Note 1: If a register holds less than 4 bytes of data, the unused MSBytes and/or bits will be set to 0.

Note 2: This command is to be used in conjunction with the Write Internal Register Address commanddiscussed in Section 2.3.3.86.

Note 3: For an internal register read, no pre-fFh will be done.



http://www.ti.com



2.3.3.89 Write Internal Mailbox Address (E8h)

2.3.3.89.1 WriteThis command is used to specify the parameters for an internal mailbox transaction in the display module.This command is applicable to both mailbox writes and reads. This command is typically used for debugpurposes.


Parameter Bytes DescriptionByte 1 Mailbox Select (LSByte)Byte 2 Mailbox SelectByte 3 Mailbox SelectByte 4 Mailbox Select (MSByte)Byte 5 Mailbox LUT Start Address (LSByte)Byte 6 Mailbox LUT Start AddressByte 7 Mailbox LUT Start AddressByte 8 Mailbox LUT Start Address (MSByte)Byte 9 Mailbox LUT Select (LSByte)Byte 10 Mailbox LUT SelectByte 11 Mailbox LUT SelectByte 12 Mailbox LUT Select (MSByte)Byte 13 Mailbox Data Length (LSByte)Byte 14 Mailbox Data LengthByte 15 Mailbox Data LengthByte 16 Mailbox Data Length (MSByte)Byte 17 (See Below)



b(7:3) – Reserved

b(2:1) – LUT Packed0h: No: 1 to 11h: Yes: 1 to 40h: Yes: 1 to 21h: Yes: 3 to 4

b(0) – Write/Read0h: Write1h: Read

Note 1: Data length must be a multiple of four bytes.

Note 2: Mailbox data will be written/read using the Write Internal Mailbox and Read Internal Mailboxcommands discussed in Section 2.3.3.90 and Section 2.3.3.91, respectively.



http://www.ti.com



Note 3: Software will automatically open the specified mailbox upon receipt of this command, and willautomatically close the opened mailbox once the data length has been reached (using thecommands discussed in Section 2.3.3.90 and Section 2.3.3.91).

Note 4: The Mailbox Select parameter specifies the register address of the mailbox to be accessed.Examples of mailboxes to be selected are: FMT Mailbox 0 [40001800], RSC Mailbox 1[40002820], VGP Mailbox 2 [40005840]. The parameter will be the actual address of thespecified mailbox register.

Note 5: The Mailbox LUT Start Address parameter is the start address for the LUT selected, and istypically zero. This is the data value passed to the Mailbox Select register.

Note 6: The Mailbox LUT Select parameter specifies the specific LUT within the selected mailbox thatis to be accessed. This is the data value passed to the Mailbox Access Control Register.

Note 7: The address for the Mailbox Access Control Register to be determined by adding four to theMailbox Select value.

Note 8: The address for the Mailbox Data Register is to be determined by adding sixteen to the MailboxSelect value.

Note 9: The Mailbox Data Length specifies how much data is to be written to or read from the specifiedmailbox, on a transactional basis.

Note The maximum data length allowed for a write transaction is 1024 bytes. The maximum data10: length allowed for a read transaction is 256 bytes.

Note The write/read information in this command is only used to indicate a read pre-fetch should be11: done. This enables the system to more efficiently process read commands. The actual mailbox

operation is based on the mailbox write or read command used. Since this is a TI debugcommand (and because error handling is complex), no error checking will be done to verify thatthese match (address-specified write/read operation versus write/read command). The outcomeof a mismatch: For writes, the mailbox address will be off (since we already did a read pre-fetch) – this is acceptable. For reads, no pre-fetch will be done – this is also acceptable.

Note It is expected that all mailbox data will be just the raw LUT data, with no header information12: included. Any ancillary information that might be required (for example, color space for a splash

image) must be set by another means (for example, using register accesses).

Note All data sent using the mailbox must be uncompressed. The FDMA is not available from the I2C13: ports, thus decompression would have to be done using software. It was decided that this was

not practical.

Note Data unpacking is supported by the mailbox command. Thus, the LUT Packed parameter14: indicates whether the LUT to be written will require unpacking prior to writing to the specified

mailbox. Details are shown in Table 2-24.

Table 2-24. LUT Mailbox Packing Information

LUT Packing Flash PBCNO: 1 to 1 One 32-bit word One 32-bit wordYES: 1 to 4 One 32-bit word Four 8-bit wordsYES: 1 to 2 One 32-bit word Two 16-bit wordsYES: 3 to 4 Three 32-bit words Four 24-bit words



http://www.ti.com



2.3.3.90 Write Internal Mailbox (E9h)

2.3.3.90.1 WriteThis command is used to write data to an internal mailbox of the display module. This command istypically used for debug purposes.

2.3.3.90.2 Write ParametersThis command has a variable number of parameters as described below.


Note 1: This command is to be used in conjunction with the Write Internal Mailbox Address commandSection 2.3.3.89.

Note 2: The address for the mailbox will be auto-incremented. Auto-decrement is not supported.

Note 3: The maximum data length allowed for a write transaction is 1024 bytes.



http://www.ti.com



2.3.3.91 Read Internal Mailbox (EAh)

2.3.3.91.1 ReadThis command is used to read data from an internal mailbox of the display module. This command istypically used for debug purposes.


2.3.3.91.3 Return ParametersThe variable number of return parameters are described below.

Parameter Bytes DescriptionByte 1 See BelowByte 2 Data Byte 2Byte 3 Data Byte 3Byte 4 Data Byte 4Byte 5 … n Data Byte 5 … n

Note 1: This command is to be used in conjunction with the Write Internal Mailbox Address commandSection 2.3.3.89.

Note 2: The address for the mailbox will be auto-incremented. Auto-decrement is not supported.

Note 3: The maximum data length allowed for a read transaction is 256 bytes.



http://www.ti.com



2.3.3.92 Write External PAD Address (EBh)

2.3.3.92.1 WriteThis command is used to specify the parameters for an external PAD device transaction. This command isapplicable to both writes and reads.

2.3.3.92.2 Write Parameters

Parameter Bytes DescriptionByte 1 PAD Register Start Address (lsb)Byte 2 PAD Register Start AddressByte 3 PAD Register Start Address (msb)Byte 4 Data LengthByte 5 See Below


b(7:1) – Reserved

b(0) – Write/Read0h: Write1h: Read


Note 1: This command is to be used in conjunction with the Write External PAD Data(Section 2.3.3.93 ) and the Read External PAD Data (Section 2.3.3.94) commands.

Note 2: The maximum data length is 32 bytes, and the minimum data length is 1 byte. This is true forwrite or read transactions.

Note 3: If a read operation is specified, software will immediately proceed to obtain the requested readdata so that it will be available when the Read External PAD Data command is received.

Note 4: The PAD registers feature an address auto-increment. As such, single or multiple registeraccesses only need the indicated start address.

Note 5: No error checking will be done to verify that the address command specified write/readoperation matches the actual write/read command. The outcome of a mismatch: For writes,software will write the provided data to the previously provided address – thus no error. Forreads, since no read data was obtained, software can return any values it wants (can be all F's- if memory has been allocated, it can be whatever was previously in the allocated memory –whatever is easiest for software to provide with no error checking) – it is accepted that the readdata in this case will not be valid.



http://www.ti.com



2.3.3.93 Write External PAD Data (ECh)

2.3.3.93.1 WriteThis command is used to write data to an external PAD device.

2.3.3.93.2 Write ParametersThis command has a variable number of parameters as described below.

Parameter Bytes DescriptionByte 1 Data Byte 1Byte 2 Data Byte 2Byte 3 Data Byte 3Byte 4 Data Byte 4Byte 5 ... n Data Byte 5 ... n

Note 1: This command is to be used in conjunction with the Write External PAD Address(Section 2.3.3.92) and the Read External PAD Data (Section 2.3.3.94) commands.

Note 2: The maximum data length allowed for a write transaction is 32 bytes.

2.3.3.94 Read External PAD Data (EDh)

2.3.3.94.1 ReadThis command is used to read data from an external PAD device.


2.3.3.94.3 Return ParametersThe variable numbers of return parameters are described below.

Parameter Bytes DescriptionByte 1 Data Byte 1Byte 2 Data Byte 2Byte 3 Data Byte 3Byte 4 Data Byte 4Byte 5 ... n Data Byte 5 ... n

Note 1: This command is to be used in conjunction with the Write External PAD Address(Section 2.3.3.94) and the Write External PAD Data (Section 2.3.3.92) commands.

Note 2: The maximum data length allowed for a read transaction is 32 bytes.



http://www.ti.com


IMPORTANT NOTICE

Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and otherchanges to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service per JESD48, latestissue. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current andcomplete. All semiconductor products (also referred to herein as “components”) are sold subject to TI’s terms and conditions of salesupplied at the time of order acknowledgment.TI warrants performance of its components to the specifications applicable at the time of sale, in accordance with the warranty in TI’s termsand conditions of sale of semiconductor products. Testing and other quality control techniques are used to the extent TI deems necessaryto support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not necessarilyperformed.TI assumes no liability for applications assistance or the design of Buyers’ products. Buyers are responsible for their products andapplications using TI components. To minimize the risks associated with Buyers’ products and applications, Buyers should provideadequate design and operating safeguards.TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work right, orother intellectual property right relating to any combination, machine, or process in which TI components or services are used. Informationpublished by TI regarding third-party products or services does not constitute a license to use such products or services or a warranty orendorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of thethird party, or a license from TI under the patents or other intellectual property of TI.Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without alterationand is accompanied by all associated warranties, conditions, limitations, and notices. TI is not responsible or liable for such altereddocumentation. Information of third parties may be subject to additional restrictions.Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or servicevoids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice.TI is not responsible or liable for any such statements.Buyer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirementsconcerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or supportthat may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards whichanticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of failures that might causeharm and take appropriate remedial actions. Buyer will fully indemnify TI and its representatives against any damages arising out of the useof any TI components in safety-critical applications.In some cases, TI components may be promoted specifically to facilitate safety-related applications. With such components, TI’s goal is tohelp enable customers to design and create their own end-product solutions that meet applicable functional safety standards andrequirements. Nonetheless, such components are subject to these terms.No TI components are authorized for use in FDA Class III (or similar life-critical medical equipment) unless authorized officers of the partieshave executed a special agreement specifically governing such use.Only those TI components which TI has specifically designated as military grade or “enhanced plastic” are designed and intended for use inmilitary/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use of TI componentswhich have not been so designated is solely at the Buyer's risk, and that Buyer is solely responsible for compliance with all legal andregulatory requirements in connection with such use.TI has specifically designated certain components as meeting ISO/TS16949 requirements, mainly for automotive use. In any case of use ofnon-designated products, TI will not be responsible for any failure to meet ISO/TS16949.

Products ApplicationsAudio www.ti.com/audio Automotive and Transportation www.ti.com/automotiveAmplifiers amplifier.ti.com Communications and Telecom www.ti.com/communicationsData Converters dataconverter.ti.com Computers and Peripherals www.ti.com/computersDLP® Products www.dlp.com Consumer Electronics www.ti.com/consumer-appsDSP dsp.ti.com Energy and Lighting www.ti.com/energyClocks and Timers www.ti.com/clocks Industrial www.ti.com/industrialInterface interface.ti.com Medical www.ti.com/medicalLogic logic.ti.com Security www.ti.com/securityPower Mgmt power.ti.com Space, Avionics and Defense www.ti.com/space-avionics-defenseMicrocontrollers microcontroller.ti.com Video and Imaging www.ti.com/videoRFID www.ti-rfid.comOMAP Applications Processors www.ti.com/omap TI E2E Community e2e.ti.comWireless Connectivity www.ti.com/wirelessconnectivity

Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265Copyright © 2015, Texas Instruments Incorporated

http://www.ti.com/audio

http://www.ti.com/automotive

http://amplifier.ti.com

http://www.ti.com/communications

http://dataconverter.ti.com

http://www.ti.com/computers

http://www.dlp.com

http://www.ti.com/consumer-apps

http://dsp.ti.com

http://www.ti.com/energy

http://www.ti.com/clocks

http://www.ti.com/industrial

http://interface.ti.com

http://www.ti.com/medical

http://logic.ti.com

http://www.ti.com/security

http://power.ti.com

http://www.ti.com/space-avionics-defense

http://microcontroller.ti.com

http://www.ti.com/video

http://www.ti-rfid.com

http://www.ti.com/omap

http://e2e.ti.com

http://www.ti.com/wirelessconnectivity

Documents

DLPC3439 Software Programmer s Guide - TI.com · DLPC3439 Software Programmer’s Guide User's Guide Literature Number: DLPU035 August 2015