• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 676 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DLPC900: I2C command sequence

Zhang Yutai
Prodigy 30 points
Part Number: DLPC900

Hello.

I’m trying to configure my LightCrafter 6500 using the I2C port. I've based my I2C command sequence on Table 5.2 (Pre-stored Pattern Mode Example) in the manual of “DLPC900 Programmer’s Guide” .  

 

It seems that everything is going well and finally i can get the images i want. But then I saw this notice in the chapter 2.4.4.3.4.(Pattern Display LUT Definition)

 

The words in bold show that I should send the command of LUT Configuration (0xF5) first and then send the command of LUT Definition (0xF8). So what does this sentence mean and which sequence of configuration should i respect?

Thank you very much.

 

  • 0
    TI__Genius 17370 points
    Hi user5640130,

    Thanks for your question, we are actively looking into this and planning to update this documentation to clarify this as it is a little confusing.

    There is likely somewhere else that the Pattern LUT is configured before your display definition executes. For now, if you are able to get working images then continue following the example in the Programmers Guide and we will get back to you on Wednesday with a clarification. Out of curiosity, did you try swapping the order in your code to see if you still get the correct images?

    Thanks,

    Taylor
  • 0 in reply to Taylor Vogt
    TI__Genius 17370 points
    Hi user5640130,

    After speaking with my team, we believe that you may continue following the above statement and ignore the bold text in section 2.4.4.3.4 as your code is executing correctly. Thank you for pointing this out to us and we will work on clarifying this in future documentation.

    Regards,

    Taylor