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.

DLPC4422: 4K UHD High Brightness Display Reference Design using TI DLP® Technology / DDP4422 IIC

Part Number: DLPC4422
Other Parts Discussed in Thread: DLP660TE,

Hi TI

hardware platform:4K UHD High Brightness Display Reference Design using TI DLP® Technology

http://www.ti.com/product/DLPC4422/toolssoftware 

Firmware version :DLP660TE_Chipset_Firmware_v8.1 , Download from  http://www.ti.com/lit/zip/tidcd51a  

Functions currently implemented:
1、DLPC4422 GUI 1.0 + USB + Device  = OK ,Set and Get

Problems currently encountered

1、DLPC4422 GUI 1.0 + DeVaSys + Device = ERROR ,Set or Get

2、DeVaSys device connect UHD PCB board J10 \ J12 \ J13, but  The results are the same., ERROR !!!

3、I can confirm. DeVaSys  device is OK, EDID can be Programed by it

4、 iic0 iic1 iic2 , I suspect they all work in the slave mode.

1、DLPC4422 Software Programmer's Guide,There is no explanation for using which IIC interface

I assume that version 8.1 firmware does not support IIC slave control

Now,The function I need to implement is to control DLPC4422 through IIC interface of STM32 controller.

 

Please TI to determine whether firmware is a problem

 

Thanks

  • Hello,

    Thank you for using the DLP forums.

    I tested the software that is available on ti.com on our of our EVM boards and I did not have any issues communicating with I2C.

    Here are the following steps I took in order to test the I2C communication.

    1. Used USB communication to flash the given image file

    2. Verified the system was flashed correctly by observing if splash image is displayed on DMD

    3. then switched communication preferences to DeVaSys

    After these steps I was able to successfully communicate with I2C.

    The following images show the configuration of the DeVaSys board and the wiring of the I2C port. I had my DeVaSys connected to I2C0 (J13).


    As I was able communicate with the board using I2C, the firmware is not the issue. Please recheck your DeVaSys hardware and your setup.

    Regards,

    Oscar