This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLP471TEEVM: DMD Error (DMD not working)

Part Number: DLP471TEEVM
Other Parts Discussed in Thread: DLP471TE, DLPC7540

Dear TI support team,

I hope you are all doing great, as I need your assistance.
We have had a TI DLP471TE EVM with a DLPC7540 board for some time and they worked without any issues until recently.
Since two days ago the DMD has not displayed anything or even shown the start screen. I have tried to troubleshoot the issue and have undertaken the following steps thus far:
1. Exchanged all cables in different configurations to test if the cables work (different USB cable, different HDMI cable, also  since I have 3 jumpers I interchanged them)
2. Checked the power supply (it works fine and delivers the required amps and voltage)
3. Tried running not only on external display mode but also a pattern or an image
4. Reinstalled the firmware (following procedure according to the manual - moving the boot jumper and back again after restart)
5. Measured the test points on the DMD board (3.3V and DMD VDD) - both work
6. Checked the pins on the DMD itself - they are fine
The lights on the controller board that are on: D5, D7, D25 - constant green colour; D15 - blinking green; D6 - constant red colour. Furthermore, all the boards (DMD, Controller, HDMI) seem fine and have no signs of burned electronic components.

I have attached pictures of the Error being marked as checked in the GUI and the advanced GUI (no other checkmarks appear):


The DMD has been operational (until now) under broad wavelength illumination and in accordance with the specifications.

Could you please help me figure this out and fix the issue?
I am looking forward to your reply!

Thanks in advance!

  • You may try and check the connectivity of the lines from the controller board to the DMD board. Also try to make sure the two are firmly connected

  • Thank you for the reply and suggestion! I have checked the connecting cables for continuity and they both work. The two of them are pretty firmly connected - the pins have not been worn out and they are stable. Additionally, I think I would not have been able to read the voltages at the test points of the DMD board, have those cables been the problem. Does anything else come to mind? Thanks again!

  • Have you tied swapping out DMDs?

  • This is a great idea, but unfortunately, we have only this one :/ ...

  • Hello Dimitar,

    We're looking into this issue on our end and will get back to you within the next few days. Thank you for your patience.

    Best,

    Maxine

  • Please try looking at the serial output from J102 using USB to serial converter

  • Hello,

    sorry for the delayed reply but we had to wait for a USB to serial converter cable.
    I used Wireshark to detect some of the information exchanged between the devices over the Serial J102 port:

    To me, it looks like some configuration data is being sent. I have attached the captured package file here:

    https://drive.google.com/file/d/1DFmBmDQZjeqVvtYuhilHAhMqyax2Gj50/view?usp=sharing

    Looking forward to your reply!

  • Just requested access to those files

  • You need to open a COM port in a serial terminal, which should populate when you plug in the USB-Serial.

    I use Teraterm: https://ttssh2.osdn.jp/index.html.en for the serial terminal

  • Hello again! Okay, I will do that and report back asap. Thank you!

  • So the Serial J102 using TeraTerm just displays the commands that I send. Here is a snapshot from one session:


    And another session which I presume shows the errors (maybe DMD Power problem?):


    Command 0x0 execution took 52 us (greater than allowed 50 ms)
    Command 0x11 execution took 77 us (greater than allowed 50 ms)
    Command 0x0 execution took 56 us (greater than allowed 50 ms)
    Command 0x11 execution took 77 us (greater than allowed 50 ms)
    Command 0x22 execution took 205 us (greater than allowed 50 ms)
    Command 0x21 execution took 117 us (greater than allowed 50 ms)
    Command 0x26 execution took 65 us (greater than allowed 50 ms)
    Command 0x11 execution took 86 us (greater than allowed 50 ms)
    Command 0x22 execution took 189 us (greater than allowed 50 ms)
    Command 0x21 execution took 87 us (greater than allowed 50 ms)
    Command 0x26 execution took 56 us (greater than allowed 50 ms)
    gui: GUI event 2 (parm = 4)
    gui: GUI event 2 (parm = 0)
    Command 0x21 execution took 122 us (greater than allowed 50 ms)
    Command 0x11 execution took 82 us (greater than allowed 50 ms)
    Command 0x11 execution took 69 us (greater than allowed 50 ms)
    Command 0x900 execution took 182 us (greater than allowed 50 ms)
    Command 0x913 execution took 161 us (greater than allowed 50 ms)
    Command 0x11 execution took 77 us (greater than allowed 50 ms)
    Command 0x11 execution took 53 us (greater than allowed 50 ms)
    Command 0x11 execution took 82 us (greater than allowed 50 ms)
    Command 0x22 execution took 205 us (greater than allowed 50 ms)
    Command 0x21 execution took 105 us (greater than allowed 50 ms)
    Command 0x26 execution took 65 us (greater than allowed 50 ms)
    gui: GUI event 2 (parm = 4)
    dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
    dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
    dispfmt:apply_disp: activeSource = 3, dispSrc = 0
    dispfmt: DISP_SetDisplay failed (ret=-101)
             CroppedArea = { 0, 0, 3840, 2160 }
             DisplayArea = { 0, 0, 3840, 2160 }
    DISP_SetDisplay return value = 0
    Command 0x21 execution took 97701 us (greater than allowed 50 ms)
    Command 0x913 execution took 810 us (greater than allowed 50 ms)
    Command 0x11 execution took 103 us (greater than allowed 50 ms)
    Command 0x11 execution took 341 us (greater than allowed 50 ms)
    Command 0x11 execution took 187 us (greater than allowed 50 ms)
    Command 0x22 execution took 213 us (greater than allowed 50 ms)
    Command 0x21 execution took 113 us (greater than allowed 50 ms)
    Command 0x26 execution took 60 us (greater than allowed 50 ms)
    gui: GUI event 2 (parm = 4)
    dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
    dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
    dispfmt:apply_disp: activeSource = 3, dispSrc = 0
    dispfmt: DISP_SetDisplay failed (ret=-101)
             CroppedArea = { 0, 0, 3840, 2160 }
             DisplayArea = { 0, 0, 3840, 2160 }
    DISP_SetDisplay return value = 0
    Command 0x21 execution took 93902 us (greater than allowed 50 ms)
    Command 0x90E execution took 771 us (greater than allowed 50 ms)
    Command 0x11 execution took 94 us (greater than allowed 50 ms)
    Command 0x11 execution took 90 us (greater than allowed 50 ms)
    Command 0x11 execution took 69 us (greater than allowed 50 ms)
    Command 0x22 execution took 193 us (greater than allowed 50 ms)
    Command 0x21 execution took 83 us (greater than allowed 50 ms)
    Command 0x26 execution took 73 us (greater than allowed 50 ms)
    gui: GUI event 2 (parm = 4)
    dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
    dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
    dispfmt:apply_disp: activeSource = 3, dispSrc = 0
    dispfmt: DISP_SetDisplay failed (ret=-101)
             CroppedArea = { 0, 0, 3840, 2160 }
             DisplayArea = { 0, 0, 3840, 2160 }
    DISP_SetDisplay return value = 0
    Command 0x21 execution took 96484 us (greater than allowed 50 ms)
    Command 0x906 execution took 728 us (greater than allowed 50 ms)
    Command 0x11 execution took 94 us (greater than allowed 50 ms)
    Command 0x11 execution took 64 us (greater than allowed 50 ms)
    Command 0x11 execution took 86 us (greater than allowed 50 ms)
    Command 0x22 execution took 202 us (greater than allowed 50 ms)
    Command 0x21 execution took 105 us (greater than allowed 50 ms)
    Command 0x26 execution took 60 us (greater than allowed 50 ms)
    gui: GUI event 2 (parm = 4)
    dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
    dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
    dispfmt:apply_disp: activeSource = 3, dispSrc = 0
    dispfmt: DISP_SetDisplay failed (ret=-101)
             CroppedArea = { 0, 0, 3840, 2160 }
             DisplayArea = { 0, 0, 3840, 2160 }
    DISP_SetDisplay return value = 0
    Command 0x21 execution took 90877 us (greater than allowed 50 ms)
    Command 0x90C execution took 848 us (greater than allowed 50 ms)
    Command 0x11 execution took 103 us (greater than allowed 50 ms)
    Command 0x11 execution took 61 us (greater than allowed 50 ms)
    Command 0x11 execution took 82 us (greater than allowed 50 ms)
    Command 0x22 execution took 184 us (greater than allowed 50 ms)
    Command 0x21 execution took 96 us (greater than allowed 50 ms)
    Command 0x26 execution took 56 us (greater than allowed 50 ms)
    gui: GUI event 2 (parm = 4)
    dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
    dispfmt:apply_disp: activeSource = 3, dispSrc = 0
    dispfmt: DISP_SetDisplay failed (ret=-101)
             CroppedArea = { 0, 0, 3840, 2160 }
             DisplayArea = { 0, 0, 3840, 2160 }
    Command 0x11 execution took 54517 us (greater than allowed 50 ms)
    dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
    dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
    dispfmt:apply_disp: activeSource = 3, dispSrc = 0
    dispfmt: DISP_SetDisplay failed (ret=-101)
             CroppedArea = { 0, 0, 3840, 2160 }
             DisplayArea = { 0, 0, 3840, 2160 }
    DISP_SetDisplay return value = 0
    Command 0x21 execution took 95055 us (greater than allowed 50 ms)
    Command 0x907 execution took 713 us (greater than allowed 50 ms)
    Command 0x11 execution took 103 us (greater than allowed 50 ms)
    Command 0x11 execution took 52 us (greater than allowed 50 ms)
    Command 0x11 execution took 86 us (greater than allowed 50 ms)
    Command 0x22 execution took 193 us (greater than allowed 50 ms)
    Command 0x21 execution took 117 us (greater than allowed 50 ms)
    Command 0x26 execution took 56 us (greater than allowed 50 ms)
    Command 0x21 execution took 81 us (greater than allowed 50 ms)
    Command 0x1C execution took 56 us (greater than allowed 50 ms)
    Command 0x11 execution took 82 us (greater than allowed 50 ms)
    Command 0x11 execution took 53 us (greater than allowed 50 ms)
    Command 0x100B execution took 56 us (greater than allowed 50 ms)
    Command 0x1E execution took 74 us (greater than allowed 50 ms)
    Command 0x1F execution took 69 us (greater than allowed 50 ms)
    Command 0x11 execution took 69 us (greater than allowed 50 ms)
    Command 0x11 execution took 57 us (greater than allowed 50 ms)
    Command 0x6 execution took 140 us (greater than allowed 50 ms)
    Command 0x1 execution took 87 us (greater than allowed 50 ms)
    Command 0x0 execution took 73 us (greater than allowed 50 ms)
    Command 0x1 execution took 132 us (greater than allowed 50 ms)
    Command 0x11 execution took 69 us (greater than allowed 50 ms)
    
    ----------------------------------------
    Debug opened on URT0
    I2C Port 1 initialized as Master port
    I2C Port 2 initialized as Master port
    I2C Port 0 initialized as Slave port
    eeprom: Content validated
    Cal data block CWLamp not in EEPROM : Using data from flash
    Cal data block SSI present in EEPROM. Data version = 0
    Cal data block ADC not in EEPROM : Using data from flash
    Cal data block WpcSensor present in EEPROM. Data version = 4
    Cal data block WpcBrightness present in EEPROM. Data version = 4
    Cal data block XPR present in EEPROM. Data version = 4
    Cal data block XPRWaveform not in EEPROM : Using data from flash
    Cal data block EdgeBlend not in EEPROM : Using data from flash
    Cal data block SurfaceCorrection won't fit in EEPROM : Using data from flash
    Cal data block SurfaceCorrection not in EEPROM : Using data from flash
    Cal data block BlendMap won't fit in EEPROM : Using data from flash
    Cal data block BlendMap not in EEPROM : Using data from flash
    API version: 4.5.0.0.0.0
    App version: 4.5.0.0.0.0
    usbIO: Debug Messges added at interface 1
    usbIO: Keyboard Mouse added at interface 2
    usbIO: USBD_Start DONE
    usbIO: USBD_Listen started
    sysmon: URT Cmd Handlerfailed to start
    pca9539: Error - iox failure. APIcc = -7
    IT6807 - Configuring IT680x...
    digcontrol: Cfg complete
    digcontrol: Decoder 2 powerStandby complete
    digcontrol: Decoder 5 powerStandby complete
    datapath: PowerStandby Complete..
    sysmon: DLPA100 not present
    
    illumination: Starting SSI Initialization...
      Configured SSI Driver Type = 0.
      Configuring sensor failed : -6.
      Initializing WPC configuration...
      SSI initialization failed.
    illumination: Completed illum_Init
    Sysmon: Transition to normal operating mode
      Initializing WPC Failed: -6
      Initializing WPC calibration data Passed...
      Initializing WPC Brightness Table Failed: 0
    Environment:Temp Sensor Write Incomplete, returned fffffff9
    *** gui: OSD_Init failure ***
    datapath: autolock initialization passed
    digcontrol.c : line - 194 : digcontrol_powerNormal()
    iox_edid_init() failed
    digcontrol: powerNormal failed
    digcontrol.c : line - 194 : digcontrol_powerNormal()
    iox_edid_init() failed
    digcontrol: powerNormal failed
    digcontrol: powerNormal complete
    datapath: dig, adc, dec powerNormal
    source: SetUserSFGColor = 1
    9
     dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
    dispfmt:apply_disp: activeSource = 1, dispSrc = 1
    gui: GUI event 2 (parm = 4)
    source: SPLASH address:  0x10526880
    source: DisplaySplash size = 3840 x 2160
    Blank screen is set to splash
    dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
    dispfmt: minPan, pan, maxPan:0, 0, 0
             data = { 3840, 0, 3840 }
    dispfmt: minScan, scan, maxScan:0, 0, 0
             data = { 2160, 0, 2160 }
    dispfmt_CalculateCroppedArea:  X, Y, Width, Height = 0, 0, 3840, 2160
    dispfmt:apply_disp: activeSource = 2, dispSrc = 2
    
    datapath: Transition to IDLING on Vx1(ITE0)
    dispfmt_ConfigManualWarp(): LensCorrection enabled = 0
    dispfmt_ConfigManualWarp: Config warping failed with error code -16
    WarpValidateResult->InLinesPixOK = 1
    WarpValidateResult->HCtrlOK = 0
    WarpValidateResult->VCtrlOK = 1
    WarpValidateResult->WrpPointsOK = 1
    WarpValidateResult->FailRow = 0
    WarpValidateResult->FailCol = 1
     Actuator EEPROM size - 6 (where 0 = 0.125k,1 = 0.25k,2 = 0.5k,3 = 1k,4 = 2k,5 = 4k,6 = 8k)
    
     [Actuator Type]: 128   [AWC WG Auto-Offset]: 0
    
     Actuator Type: 128   Unipolar: 0
     XPR Param in EEPROM: MAtch Signature
    XPR 4 Way Orientation number: 22
    XPR: Act subframe order: 0 3 1 2
     XPR_4WAY_TIActGetActuatorData(): Read from EEPROM failed
     XPR_4WAY_TIActGetActuatorData(): Read from actuator failed!!!
    datapathf: XPR_4WAY_Init Failed
    Illumination: Transition to operating mode
    illumination: DMD LSIF comm error in DMD_Power()
    illumination: Can't set up DMD
    sysmon: Fault in illumination transition to operating mode
    sysmon: Sysmon can't transition to operating mode
    gui: GUI event 4 (parm = 0)
    gui: executing OnOSDClose
    illumination: Transition to standby
    illumination: Disabling SSI Illuminators.
    illumination: API WARNING - SEQ_POWER_DOWN_REFRESH_NOT_USED on Fusion DMD
    sysmon: _sysStandby - Transition
    omplete
    by
    sysmon.c : line - 741 : _sysReset()
    _sysNormalRun() failed
    sysmon: Init Complete
    Command 0x0 execution took 60 us (greater than allowed 50 ms)
    Command 0x11 execution took 90 us (greater than allowed 50 ms)
    Command 0x0 execution took 73 us (greater than allowed 50 ms)
    Command 0x11 execution took 86 us (greater than allowed 50 ms)
    Command 0x22 execution took 223 us (greater than allowed 50 ms)
    Command 0x21 execution took 108 us (greater than allowed 50 ms)
    Command 0x26 execution took 60 us (greater than allowed 50 ms)
    pctlCommands: switching to external source
    Command 0x11 execution took 7634 us (greater than allowed 50 ms)
    Command 0x21 execution took 100 us (greater than allowed 50 ms)
    Command 0x11 execution took 69 us (greater than allowed 50 ms)
    Command 0x11 execution took 52 us (greater than allowed 50 ms)
    Command 0x11 execution took 77 us (greater than allowed 50 ms)
    Command 0x22 execution took 172 us (greater than allowed 50 ms)
    Command 0x21 execution took 106 us (greater than allowed 50 ms)
    Command 0x26 execution took 60 us (greater than allowed 50 ms)

    Looking forward to your reply!

  • I'm a bit suspicious of this: "illumination: DMD LSIF comm error in DMD_Power()",

    which makes me believe there is a broken line or pin on the Low speed interface. Can you check these lines in particular to make sure the signals are getting through?

  • Hello once again. I used a Tektronix TBS2000 Series Digital Oscilloscope (70 MHz, 1GS/s) for the measurement (it is the only one we have). I am not sure if it can measure these signals at all or if I am measuring them wrongly. I definitely see some mV jumps (~150 to 200) from almost all the pins/lines you mentioned (LS_CLK_P - pin R9, LS_CLK_N - pin R10, LS_WDATA_P - pin T10, LS_WDATA_N - pin T11) besides LS_RDATA_A_BIST_A - pin T13. T13 is physically not on the back where I measured the others. Here are some pictures of the measurements and the DMD pins, as well as the missing T13 on the back. The blue cable connects to the GND of the board.

    Unfortunately, I am not sure it is easily fixable.
    We are doing research and our project has been on hold now for 14+ days.
    Our supplier (DigiKey) has been following this troubleshooting session and told us that to call the warranty into action we have to reach some sort of conclusion. Do you think this case qualifies for a replacement and is there anything else we can do to try to fix this one that does not take longer than 1-2 days because we can not afford to lose more time?
    Looking forward to Your reply and thanks for the kind help so far!