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.

  • TI Thinks Resolved

DLPLCR9000EVM: DLPLCR9000EVM error: controller/dmd incompatible

Prodigy 180 points

Replies: 12

Views: 225

Part Number: DLPLCR9000EVM

Hello,

DLPLCR9000EVM product was tested recently and within the "DLP® LightCrafter 6500 and 9000 Firmware and Software Bundle", the error "controller/dmd incompatible" appeared.  

This error appeared suddenly and used to be functional.  The DMD chip was not replaced and everything is original hardware.  Firmware is up to date as well. 

I was recommended by TI to try buying new flex cables since the controller may not be communicating with the DMD board.  I was wondering if there were any diagnostics I can perform to ensure that it is in fact the flex cables?  (each flex cable is about $300).  I have a voltmeter to test various voltages on the board.  Can anyone suggest some things to check? 

Thanks!

Kevin

  • Hello Kevin,

    Welcome to the DLP section of the TI-E2E forums.

    Please look at the following threads to see if it helps:

    https://e2e.ti.com/support/dlp/f/94/t/742046?tisearch=e2e-sitesearch&keymatch=DMD%252520incompatible

    https://e2e.ti.com/support/dlp/f/94/t/608617?tisearch=e2e-sitesearch&keymatch=DMD%25252525252525252520incompatible

    It is fairly unusual to have a damaged flex cable.  It is possible to touch areas of the controller board near the controllers (and on the DMD board) that can cause the DMD to be damaged.  

    Try the procedure listed in the second thread first.  If that fixes it, then good.  If it does, then likely the firmware load got corrupted.

    If it does NOT fix it, then the another possibility is to have debris on the pads that the flex cable interfaces to one (or both) of the boards.  Disconnect and inspect for debris and clean.  Try the DMD end first, then the controller board end if it persists.

    If none of these help, then you may need to contact the distributor that you obtained it from if it has been less that the warranty period for your area of the world.

    Fizix

  • In reply to Fizix:

    Nah, that did not resolve the issue.  I updated the firmware and it was successful in updating with the boot mode jumper in.  But after power cycling it did not fix the issue. 

    Does TI provide older versions of the GUI and/or firmware.  The first link suggestion they had more luck with the older GUI. 

    I have also cleaned all the cables and it did not fix the issue. 

  • In reply to Kevin Freedman:

    Hi Kevin,

    Could you please send the debug log? This will tell us whether the communication with the DMD is the issue or the keying is incorrect.

    For getting the log, connect rx of your UART receiver to jumper J7 pin 2 and GND to pin  6

    Thanks

    Sachin

  • In reply to Bhatta:

    Hi Kevin,

    Were you able to get the information from the log?

    Thanks

    Sachin

  • In reply to Bhatta:

    Hi Sachin,

    I am working on getting it.  Had a order a new UART port connector.  Ill post the error as soon as I get it. 

    Thanks!

    Kevin

  • In reply to Kevin Freedman:

    Hi Kevin,

    Were you able to get the log with your new board?

    Could you please let me know if you need any assistance?

    Thanks

    Sachin

  • In reply to Bhatta:

    HI Sachin,

    Thanks for checking in.  I have not been able to get the log yet.  I have to fix another component first. 

    I hope to fix and let you know soon. 

    Thanks,

    K

  • In reply to Kevin Freedman:

    Hi Sachin,

    I got the error code but I need your help to know what it means.  The output was an array of number 1x455. 

    Best,

    Kevin

  • In reply to Kevin Freedman:

    Hi Sachin,

    Oops, my bad.  Here are the messages: 

    Bootloader Version 3.0

    Jumping to application ...

    Debug opened on URT0

    Memory test cc = 1

    API version: 05.00.01

    Configuration layout versions:

    Seq Map: 44.21.0100

    SW Map: 44.21.0000

    I2C Cmd Slave Address 34

    Slave ASIC is  Ready (0).

    DRAM memory pool 004025E8 200025E8

    ptn_seq.c (1014) >> Failed

    Illumination: Transition to operating mode

    DMD comm error in DMD_Power()

    Illumination: Transition to standby

  • In reply to Kevin Freedman:

    Kevin,

    Thanks for providing the information. Clearly from the log, there is DMD communication error. You need to verify these items

    1. Flex cable connection with DMD might be the root of the problem. Try a different one if you have. Or remove the flex, clean the pins and re insert the flex

    2. If the issue isn't solved, there is a chance that the DMD is faulty. It can be due to shorts while handling the board. Try replacing this and the problem should be solved

    Thanks

    Sachin

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.