• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 152 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.

DLPR410: DLPR410BYVA not initializing

Moshe Levy
Prodigy 220 points
Part Number: DLPR410
Other Parts Discussed in Thread: DLP9500UV

Hi,

re-opening this case

- Per previous question (sorry took time...was on vacation) here are our findings:

1. Until now on our products using the DLPR410AYVA we got the following readings:

    DMD_VERSION = 101 or 111

    DMD_TYPE = 000

2. on the boards we mounted the DLPR410BYVA we get

    DMD_VERSION = 000

    DMD_TYPE = 010

and thus, our SW indicates failures as it seeks the values of 5,7 for the version and 0 for the Type (i.e DLP9500UV)

Can you advise why? per the change notice the ID should not have changed

  • 0
    TI__Mastermind 38660 points

    Moshe,

    I believe per the update that DMD_VERSION is correct since there is only enough bit space for 0 - 7.  Therefore, the version was wrapped around and the version reports binary 000.  This is the version of the firmware.

    However, I am concerned about the DMD_TYPE.  Indeed for the 9500 I believe the DMD_TYPE should report 000.  Further investigation is needed on this.  

    Fizix

  • 0 in reply to Fizix
    TI__Mastermind 38660 points

    Moshe,

    As a point of clarification, this is the same DMD that was previously being used so that the DMD_TYPE is the same.  If I read your post correctly this is the DLP9500UV.

    I am sending a private message regarding this since I know that some of the information is proprietary to your project.

    Fizix

  • 0 in reply to Fizix
    TI__Mastermind 38660 points

    Moshe,

    Thank you for notifying me that adding version 0 as controller version solved this issue.  I am closing the thread.  THANKS again.

    Fizix