I2C communication between arduino and DLP LightCrafter Display 4710
Part Number: DLP3010EVM-LC
I'm planning a project to control six DLP3010EVM_LC at the same time by using Python (programming language).
There are some questions I'd like to inquire:
1. Is it possible that I hook up a Teensy LC - I2C to the main bus to send I2C commands to six DLPs, or do I need six teensy LC to control six DLPs? (Can each DLP has its individual address?)
2. How to bypass the cypress chip and msp430 chip, and only talk to DLPC3478? (Is there any pin to be toggled?)
3. Is the DLP3010EVM_LC project planning to have a long term service? (The DLP3000 was discontinued suddenly, my previous project is at risk of no replacement.)
Thanks very much.
Jiaqi Huang (Joseph)
1. The DLPC3478 only supports a single I2C address. Six Teensy devices will be needed to control six DLP devices.
I will work to get more feedback for you on items 2 and 3.
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 Andrew Wallace1:
Thanks very much for the quick reply, Andrew. Looking forward to seeing more information.
In reply to Jiaqi Huang:
2. We do not have a way to bypass the cypress chip and the MSP430, Any bypass would have to be done independently.
3. This is a mainstream device. There are no current plans to End Of Life this device in the foreseeable future.
Thanks for confirming the life of this device. Good to know it's a long term project.
You've mentioned there is no way of bypass cypress and MSP430, does that mean I do not need to toggle any pin to switch off cypress and MSP430, only need to connect the Teensy I2C to the DLP via socket J14 (3V3, Gnd, SDA, CLK) and sending the commands to address 0x1B directly? (as was mentioned in https://e2e.ti.com/support/dlp/f/94/t/565828?DLP3010-Write-Display-Image-Rotation )
If so, I'll have a try!~ (hope that's not going to damage anything. :-) )
Communication on the I2C bus directly may result in trying to communicate on a busy line. The MSP430 send I2C commands periodically. I think you may find that writing directly to the line may not be the most robust solution.
I have looked through more documentation and may have found a solution that may enable you to pausing the I2C communication of the MSP430. If you press the PB_LEFT1 and PB_RIGHT1 at the same time you should see the LED MSP2(D9) begin to blink repeatedly. This should place the MSP430 into a debug mode and clear the I2C bus. I have not confirmed this on a scope, but reading through the MSP430 software for this board that is my understanding.
Thanks for the information, Andrew.
You are correct, the I2C bus is quite busy, the Cypress chip and MSP430 are both chatty. :-)
I've pressed the two buttons and saw the blinking "MSP2" LED, and the I2C is quiet all of a sudden.
I got a response from the DLPC3478 chip from the bus too.
I think this is a good starting point for me, thanks very much for all the support.
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. 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.