DLPC3479: PATTERN_READY signal is not going back from low to high in DLPC3479

Expert 2450 points

Replies: 27

Views: 432

Part Number: DLPC3479

Hello TI Team,

 

I have got a question from our customer about the Pattern Ready signal of DLPC3479.

Would you please check this question and give any comment?

 

[Phenomenon]

They are using the Trigger-in mode and if they keep displaying the pattern, they sometimes see the problem that the pattern displaying stops and the pattern ready signal is still low (active high) and it is not going high. (In the normal operation, PATTERN_READY becomes Low for 5ms and return to High.)

 

[Condition]

Operation Mode:Internal Pattern Streaming Mode

Trigger Out: Both 1 and 2 are Enable

Pattern Order: 8 order (Num of Disp:1)

Internal Pattern Control:Start with Repeat indefinitely

 

They checked that the PATTER_READY is High in the configuration above. Then, they are sending the trigger and display the pattern form their external MCU. Exposure time is 4.16ms and minimum period is 18ms.

 

On this procedure, if they keep running to display the pattern, they sometimes see the problem that the pattern displaying stops.

The time that the pattern displaying stops is some variation (from 10 minutes to 30 hours).

They do not know the reason why the pattern displaying stops.

If they display the last pattern, the PATTERN_READY becomes Low and it is keeping Low.

Internal Pattern Status is also 0 (Not Ready). If they send the Internal Pattern Control or external trigger signal, the phenomenon is not changed.

If they turn off the PROJ_ON signal and then, turn on it, it is going back to the normal operation.

 

[Question]

If you know the reason why the PATTERN_READY signal is still low, would you please tell us the reason or give any comment?

 

 

[Their additional request]

They think it may be related with the communication between SPI flash and DLPC3479.

They took a normal waveform of SPI communication between Flash and DLPC3479 while pattern data is read from SPI flash.

They think the timing requirement is matched to the datasheet specification. But they want you to check this waveform and want you to have a comment whether there is any problem or not.

 

Thank you very much for your comment.

 

Best Regards,

Nobu Arai

27 Replies

  • Arai-san,

    A couple initial questions from me on this issue:

    > What MCU is being used to drive the DLPC3479 system? 

    > Is this using a DLP EVM or a custom board design?

    > When the system enters a failure state, is any activity going on in the system (on either the MCU or DLP side)? Does the whole system stay idle for the entire 30 hours? Or is activity occuring?

    > If this is a custom board design, what SPI flash part is being used?

    Regards,

    Philippe Dollo

    --------------------------------------------------------------------------------------------------------

    If a post answers your question, please click the "Verify Answer" button.

    Have questions about DLP Pico Chipsets? Check out the DLP Pico Universal FAQ for quick answers: https://e2e.ti.com/support/dlp/f/94/t/946506 

  • In reply to Philippe Dollo:

    Philippe-san,

     

    Thank you for your comment.

    I am asking your questions to the customer, but I have not got it, yet.

    So, please let me answer partially below.

     

    > What MCU is being used to drive the DLPC3479 system?

    [Answer] Please wait for the feedback from the customer.

     

    > Is this using a DLP EVM or a custom board design?

    [Answer] This is happening on their custom board.

     

    > When the system enters a failure state, is any activity going on in the system (on either the MCU or DLP side)? Does the whole system stay idle for the entire 30 hours? Or is activity occuring?

    [Answer] I think that the entire system is working correctly when this problem happens. This problem happens after the system worked correctly for 30 hours and they sometimes see this problem after they keep displaying for only 10minutes. But I need to check.

     

    > If this is a custom board design, what SPI flash part is being used?

    [Answer] Please wait for the feedback from the customer.

     

    Anyway, if I get a feedback from the customer, I will let you know again.

     

    Best Regards,

    Nobu Arai

  • In reply to Nobuyoshi Arai44:

    Nobu-san,

    Thank you for your feedback. Please keep us informed on the same.

    Regards,

    Philippe Dollo

    --------------------------------------------------------------------------------------------------------

    If a post answers your question, please click the "Verify Answer" button.

    Have questions about DLP Pico Chipsets? Check out the DLP Pico Universal FAQ for quick answers: https://e2e.ti.com/support/dlp/f/94/t/946506 

  • In reply to Philippe Dollo:

    Philippe-san,

     

    I got some additional information from the customer. Please see below and if you have any advice or comment, it would be helpful.

     

     

    > What MCU is being used to drive the DLPC3479 system?

    [Answer] It is RX631(R5F5631EDDLJ) by Renesas.

     

    > Is this using a DLP EVM or a custom board design?

    [Answer] This is happening on their custom board.

     

    > When the system enters a failure state, is any activity going on in the system (on either the MCU or DLP side)? Does the whole system stay idle for the entire 30 hours? Or is activity occurring?

    [Answer] They are saying that they can be displaying the pattern just before entering a failure state.

    In the failure state, the system itself is working normally, the pattern displaying is just stopping on the DLP side.

    If they keep displaying the pattern repeatedly, the pattern display sometime stops after 10minues, sometimes stops after 30 hours.

    The time until the pattern displaying stops (PATTERN_READY is still Low) is various.

    - MCU(RX631) is normal status.

    - DLPC3479 can be communicate with MCU by I2C.

    - They do not know the status of DLPA3005 because MCU cannot communicate with DLPA3005 at this time.

    - After the pattern displaying stops, even if they set “0h:Start”, “1h:Stop” or “5h:Reset” by Internal Pattern Control(9Eh), the phenomenon is not changed (PATTERN_READY is still Low).

    - After the pattern displaying stops, if they turn on/off PROJ_ON, it becomes recovered.

    - After the pattern displaying stops, they can get the status information of DLPC3479 by communication between MCU and DLPC.

    Please see the attached file of this DLPC3479 status information. It looks Invalid command error is 1:Error, but there is no error other than this.

     

    > If this is a custom board design, what SPI flash part is being used?

    [Answer] It is W25Q64JVSSIQ by Winbond.

     

     DLPC3479_Status_after_stop.txt

    Best Regards,

    Nobu Arai

  • In reply to Nobuyoshi Arai44:

    Nobu-san,

    Thank you for this information.

    We will look it over and respond by the end of the week.

    Regards,

    Austin

    --------------------------------------------------------------------------------------------------------

    If a post answers your question, please click the "Verify Answer" button.

    Have questions about DLP Pico Chipsets? Check out the DLP Pico Universal FAQ for quick answers: https://e2e.ti.com/support/dlp/f/94/t/946506 

  • In reply to Austin Snyder:

    Austin-san,

    Thank you for your comment.

    We will wait for your feedback.

    Best Regards,

    Nobu Arai

  • In reply to Nobuyoshi Arai44:

    Arai-san,

    Thank you for your patience.

    regards,

    Vivek

    --------------------------------------------------------------------------------------------------------

    If a post answers your question, please click the "Verify Answer" button.

    Have questions about DLP Pico Chipsets? Check out the DLP Pico Universal FAQ for quick answers: https://e2e.ti.com/support/dlp/f/94/t/946506 

  • In reply to Vivek Thakur:

    Nobu-san,

    Kindly ask the customer to answer the following questions : 

    1. What is the Firmware version that they are using? If it is an older firmware version (not v8.1.0), kindly ask them to check the system behavior on the latest version as well.

    2. If the problem also seems to appear on firmware version v8.1.0, please ask them to check the behavior on the EVM also.

    3. Please ask them to log the status information more than 1 time, and check if they are still getting Invalid Command Error or not.

    Regards,

    Mayank

    If a post answers your question, please click on "Verify Answer" button

    Have any questions about DLP Pico Chipsets? Check out the DLP Pico Universal FAQ for quick answers: https://e2e.ti.com/support/dlp/f/94/t/946506 

  • In reply to Mayank Khandelwal:

    Hello Mayank-san,

     

    Thank you for the answer.

    Please let me add my comment below before asking to the customer.

     

    >1. What is the Firmware version that they are using? If it is an older firmware version (not v8.1.0), kindly ask them to check the system behavior on the latest version as well.

     

    I need to check their firmware version but their DMD is DLP4710A (not DLP4710LC). If V8.1.0 cannot work with DLP4710A, I do not think they can try the working with the latest version, V8.1.0. What do you think about this?

     

    >2. If the problem also seems to appear on firmware version v8.1.0, please ask them to check the behavior on the EVM also.

     

    I will ask them to try the same thing on the EVM.

     

    >3. Please ask them to log the status information more than 1 time, and check if they are still getting Invalid Command Error or not.

     

    I will ask them to try to log the status information more than 1 time.

     

    Best Regards,

    Nobu Arai

  • In reply to Nobuyoshi Arai44:

    Nobu-san,

    Thanks for the quick feedback.

    I need to check their firmware version but their DMD is DLP4710A (not DLP4710LC). If V8.1.0 cannot work with DLP4710A, I do not think they can try the working with the latest version, V8.1.0. What do you think about this?

    <Mayank> Yes, v8.1.0 will not work with their systems. Still, please let us know the firmware version that they are using. Also, ask them to see the behavior on the EVM with this firmware version.

    Regards,

    Mayank

    If a post answers your question, please click on "Verify Answer" button

    Have any questions about DLP Pico Chipsets? Check out the DLP Pico Universal FAQ for quick answers: https://e2e.ti.com/support/dlp/f/94/t/946506