• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 277 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DLP4500: Board Stuck in Pattern Mode, GUI Does Not Detect Board

Abhijan Wasti
Prodigy 20 points
Part Number: DLP4500

Hi,

I am trying to configure my DLP4500 with the LightCrafter 4500 Control Software. I set up my pattern sequence, saved it as a solution, and created a new firmware with this solution so that I don't have to set my sequence again. I uploaded this firmware on the projector and now it automatically enters pattern mode and is projecting the pattern. The problem is that the LightCrafter 4500 Control Software can no longer detect the projector.

I have tried:

1) Resetting the projector (pressing the reset button on the board)

2) Restarting the projector (plugging it on and off again)

3) Putting the projector in Standby mode and back

4) Unplugging and replugging my USB connection

5) Closing the Control Software and opening it again.

Nothing has worked so far.

Here's my .ini file for reference:

APPCONFIG.VERSION.SUBMINOR 0x0 ;
APPCONFIG.VERSION.MINOR 0x0 ;
APPCONFIG.VERSION.MAJOR 0x3 ;
DEFAULT.FIRMWARE_TAG 0x0 ;
DEFAULT.AUTOSTART 0x0 ;
DEFAULT.DISPMODE 0x1 ;
DEFAULT.SHORT_FLIP 0x0 ;
DEFAULT.LONG_FLIP 0x0 ;
DEFAULT.TRIG_OUT_1.POL 0x0 ;
DEFAULT.TRIG_OUT_1.RDELAY 0xbb ;
DEFAULT.TRIG_OUT_1.FDELAY 0xbb ;
DEFAULT.TRIG_OUT_2.POL 0x0 ;
DEFAULT.TRIG_OUT_2.WIDTH 0xbb ;
DEFAULT.TRIG_IN_1.DELAY 0x1 ;
DEFAULT.TRIG_IN_2.POL 0x0 ;
DEFAULT.RED_STROBE.RDELAY 0xbb ;
DEFAULT.RED_STROBE.FDELAY 0xbb ;
DEFAULT.GRN_STROBE.RDELAY 0xbb ;
DEFAULT.GRN_STROBE.FDELAY 0xbb ;
DEFAULT.BLU_STROBE.RDELAY 0xbb ;
DEFAULT.BLU_STROBE.FDELAY 0xbb ;
DEFAULT.INVERTDATA 0x0 ;
DEFAULT.TESTPATTERN 0x1 ;
DEFAULT.LEDCURRENT_RED 0x97 ;
DEFAULT.LEDCURRENT_GRN 0x78 ;
DEFAULT.LEDCURRENT_BLU 0x7d ;
DEFAULT.PATTERNCONFIG.PAT_EXPOSURE 0x208d ;
DEFAULT.PATTERNCONFIG.PAT_PERIOD 0x208d ;
DEFAULT.PATTERNCONFIG.PAT_MODE 0x3 ;
DEFAULT.PATTERNCONFIG.TRIG_MODE 0x1 ;
DEFAULT.PATTERNCONFIG.PAT_REPEAT 0x1 ;
DEFAULT.PATTERNCONFIG.NUM_SPLASH 0x15 ;
DEFAULT.SPLASHLUT        0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xa 0xb 0xc 0xd 0xe 0xf 0x10 0x11 0x12 0x13 0x14 0x15 ;
DEFAULT.PATTERNCONFIG.NUM_LUT_ENTRIES 0x41 ;
DEFAULT.PATTERNCONFIG.NUM_PATTERNS 0x41 ;
DEFAULT.SEQPATLUT 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 0x62808 0x22800 0x22804 ;
DEFAULT.LED_ENABLE_MAN_MODE 0x0 ;
DEFAULT.MAN_ENABLE_RED_LED 0x0 ;
DEFAULT.MAN_ENABLE_GRN_LED 0x0 ;
DEFAULT.MAN_ENABLE_BLU_LED 0x0 ;
DEFAULT.PORTCONFIG.PORT 0x0 ;
DEFAULT.PORTCONFIG.BPP 0x1 ;
DEFAULT.PORTCONFIG.PIX_FMT 0x0 ;
DEFAULT.PORTCONFIG.PORT_CLK 0x0 ;
DEFAULT.PORTCONFIG.ABC_MUX 0x4 ;
DEFAULT.PORTCONFIG.PIX_MODE 0x1 ;
DEFAULT.PORTCONFIG.SWAP_POL 0x1 ;
DEFAULT.PORTCONFIG.FLD_SEL 0x0 ;
PERIPHERALS.I2CADDRESS[0] 0x34 ;
PERIPHERALS.I2CADDRESS[1] 0x3a ;
PERIPHERALS.I2CBUSYGPIO_ENABLE 0x0 ;
PERIPHERALS.I2CBUSYGPIO_SELECT 0x0 ;
DATAPATH.SPLASHSTARTUPTIMEOUT 0x1388 ;
DATAPATH.SPLASHATSTARTUPENABLE 0x0 ;
MACHINE_DATA.COLORPROFILE_0_BRILLIANTCOLORLOOK 0x0 ;


In case you want to try running it yourself to see if you can replicate the issue, you can find the firmware here: drive.google.com/.../1NReK4L5ij6NxpKnonPOWuN65_7C_ofqG

The only thing I think I might have done to break it is to automatically enter pattern mode. What could be the issue and how do I solve it?

  • 0
    TI__Expert 3905 points

    Hello Abhijan,

    Welcome back to the E2E forum. Thank you for your continued business!

    Can you reflash the original firmware onto your board? Can the GUI still not detect the board?

    Best,

    Maxine

  • 0 in reply to Maxine Cabrasawan
    Prodigy 20 points

    Hi Maxine!

    The computer could detect a USB connection, but the GUI could not find the projector. As a last-ditch effort, I shorted the J18 connectors on board (this enters bootloader mode), and reset the projector (by pressing the reset button on board). This finally worked and now the GUI can communicate with the projector. (After flashing, I removed the connection across J18 to resume normal function)

    I'm still not sure why it was not able to communicate with the computer while in pattern projection mode. After diff checking an original file and this file with the images, I was able to see that the following:

    1) Line:

    DEFAULT.DISPMODE 0x0 ;
DATAPATH.SPLASHATSTARTUPENABLE 0x1 ;

    were changed to
     

    DEFAULT.DISPMODE 0x1 ;
DATAPATH.SPLASHATSTARTUPENABLE 0x0 ;


    2) The following lines were added:
    PERIPHERALS.I2CBUSYGPIO_ENABLE 0x0 ;
PERIPHERALS.I2CBUSYGPIO_SELECT 0x0 ;


    My guess is unsetting the two I2CBUSYGPIO caused it to be irresponsive. Is that correct?

  • 0 in reply to Abhijan Wasti
    TI__Expert 3905 points

    Hello Abhijan,

    Yes, you are correct. These two registers should be set to 0x1 in order for I2C commands to be sent and received. Do you have any other questions I can help you with?

    Best,

    Maxine