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.

DLPC3479: The 8.3.0 firmware may have a display exception

Part Number: DLPC3479
Other Parts Discussed in Thread: DLP4710LC, , DLPA3005

Hello, TI expert

When we upgraded the 8.3.0 firmware, we found that when the pattern ready signal was set to high, the left and right sides could easily get out of sync when projecting the internal mode. When paused, the left pattern and right pattern may not come from the same pattern. This error occurs whether pattern ready is enabled or not. But it works well when the pattern ready signal is set to low. For firmware 8.1, there is no such exception.


Environment: dlpc3479+dlpa3005+dlp4710lc+pm1.

Thanks


  • Hello,

    Thank you for reporting this! Could you please attach your pattern set configurations so that we ma preproduce this issue? 

    Best,

    Maximus

  • Hello Maximus

    I failed to upload the attachment. First, we create two pattern sets of 8-bit pattern. Add 4 horizontal stripes to the first pattern set and 4 vertical stripes to the second pattern set. Next, the exposure time series is set to normal (as shown); Finally, click "Run continuously" and "Pause" and verify if there is a projection exception.

    Best,
    Jungle

  • Hello,

    Thank you for this, I have not yet been able to reproduce this issue. Could you attach a video of what you are seeing and anything else showing two controllers "out of sync"?

    Best,

    Maximus

  • Hi,

    1)update FWSel_DLPC3479_DLPA3005_pm1_i2c0x36_v8p3p0.img

    2)program and load pattern

    3)run

    but

    Thanks.

  • Hello,

    Are you using a TI EVM or a custom board? I have not been able to reproduce this on our system. How does the image look during normal run time? Can you setup a camera to take a photo during each pattern? I want to make sure this is an issue when you simply run once or continuously. We recommend only using the pause/step buttons for debugging as the behavior when using them is not guaranteed. 

    Best,

    Maximus

  • Hello,

    Did you still need help on this issue? For now I will close the ticket, feel free to respond in order to reopen it.

    Best,

    Maximus

  • Hi,

    We developed our own board. This phenomenon was not found on some boards. A board that has an exception with 8.3 firmware will not have this problem if 8.1 firmware is programmed. We haven't been able to find the root cause.

    Best,
    Jungle

  • Hello,

    What percentage of your boards do you see this issue? Have you been able to confirm this issue is only seen when using the "pause/step" buttons in the GUI or is it also seen during a run continuously? I mentioned before, but the best way to confirm this would be to setup a camera that captures each pattern. Because you are only seeing this on some of your boards, have you stepped back and verified your design with the TI reference design?

    Best,

    Maximus

  • Hi,

    When clicking "Run once" or "Run continuously", the difference between the left and right screens is too large. Therefore, we performed pause and step analysis observations. The problem with using camera grasping is the same. What might cause the left and right frames to get out of sync? If it's an individual issue, why doesn't this happen with the 8.1.0 firmware?

    Thanks.

    Jungle

  • Hello,

    Is it only one board or this problem is with multiple boards? What percentage of boards have this issue?

    regards,

    Vivek

  • Hi,

    We found similar issues on 3 ~ 4 boards and did not continue testing all boards. We plan to pause the firmware upgrade. We will wait for the release of the subsequent version from TI to verify this phenomenon.

    Thanks.

    Jungle

  • Hello, 

    I want to restate that the pause/step buttons are only meant for debugging and are not for production use. Visual artifacts are expected when using these functions, so we must verify you are seeing this issue during a regular "run once" or "run continuously". If you can verify the issue is still present when using the "run once" or "run continuously" functions then please probe/scope the trigger1, trigger 2, patternready, and seq_sync signals of both controllers to see if there are any anomalies during "run once" or "run continuously". We are unable to reproduce this issue on our hardware which indicates it may be related to your hardware configuration, is this affecting all of the boards you tested or just some? We currently do not have any planned maintenance releases for this firmware version. 

    Best,

    Maximus