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.
Part Number: DLPC3439
We've been seeing this rare issue where after the DLPC3439 powers on, an image is sent to it, and it gets jumbled. This image:
When projected, looked like this:
Every image sent while it's in this state gets jumbled in a similar fashion. I believe the DLPC is in a bad at this point because I attempted to set the input source to be a test image instead of external video to see if the issue persisted. The test image was not jumbled like the previous images, but when I set the input source back to external video, the image being projected was also no longer jumbled.
It seems as if the DLPC was in a weird state, and changing the input source somehow reset it.
Is there anyway to detect this by querying the DLPC? Or is there anything we can do to avoid this issue?
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Philippe Dollo:
If I understand the result of the Read System Software Version command, the version is 1.3.2. The image size is 1920x1080.
In reply to Heather Rysenga:
This chipset actually features a curtain functionality for this sort of purpose. If you want to hide the image temporarily you can enable the curtain while switching display modes, and re-enable it when it is safe to do so. This command is detailed in the software programmer's guide (page 32):
Are you starting the system in external video mode by default while also sending parallel image data at the same time? Perhaps your particular frontend startup configuration is causing data to be sent the DLPC improperly. In this case having the system start up with a curtain is an easy fix.
Video data is being sent regardless of the projector being turned on. So if this has the potential to cause problems, then that's probably what's going on.
So what we should do is start with one of the internal image sources instead? That's what I was originally thinking about doing because I had noticed switching sources seemed to fix the problem, but I was worried that setting the source might be what caused the issue because I didn't know the source of the problem.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.