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: DLPDLCR2000EVM
I am trying to interface the DLPDLCR2000EVM module to raspberry pi zero following the thread(http://e2e.ti.com/support/dlp__mems_micro-electro-mechanical_systems/video_and_data_display/f/947/t/651931) . I am able to detect the evm using i2cdetect . However I am unable to switch the input source using sudo i2cset -y 3 0x1b 0x0b 0x00 0x00 0x00 0x00 i , nothing happens when i send this command , I have tried to follow section 22.214.171.124 in the programmers guide to change the pixel data format to rgb666 using
sudo i2cset -y 3 0x1b 0x0d 0x00 0x00 0x00 0x01 i
but nothing happens still , could someone please help me locate my mistake , thanks
I am powering the pi with a 5v/2A external adapter and the evm with a external 5v/3a adapter .
here is my boot/config.txt
# Uncomment some or all of these to enable the optional hardware interfaces
# Uncomment this to enable the lirc-rpi module
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
# NOOBS Auto-generated Settings:
# Add support for software i2c on gpio pins
# DPI Video Setup
hdmi_timings=854 0 14 4 12 480 0 2 3 9 0 0 0 60 0 32000000 3
and here are my connections from evm to the raspberry pi zero pin numbers .
Thank you .
Hello, I updated my guide at https://e2e.ti.com/support/dlp__mems_micro-electro-mechanical_systems/video_and_data_display/f/947/t/651931 to add my full pinout from the Raspberry Pi to P1 and P2 of the EVM module. Note that you don't connect the 3.3V on P2. Also make sure you have the EXT_SDA and EXT_SCL the correct way around. For the I2C tests you should only need the 3 connections of GND, EXT_SDA and EXT_SCL which should enable you to switch to the internally generated graphics test mode on the DLPDLCR2000EVM. My connections are by 20cm Dupont connectors and I didn't use any pull-up resistors for the I2C . The original I2C pin mappings for hardware I2C on the Raspberry Pi has relevant pullups added to the circuitry and I'm not sure if they are configured using internal pull-ups or not on the new pin mapping. If you have a long wiring connection, it might be a reason your I2C is not communicating, either try short connections for I2C or add 1.8k pullup resistors on the Raspberry Pi for the physical Pins 16 and 18). Hopefully it's just a simple wiring issue.
In reply to Philip Hodgers:
In reply to sripathi pedaprolu:
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.