DLPC3433: DLPC3433 I2C Address and Usage

Christopher Vollo

Part Number: DLPC3433
Other Parts Discussed in Thread: DLPA3000

Hello,

I have DLPC3433 and DLPA3000 both on an I2C bus, and I am not seeing the proper addresses when running an i2cdetect from the linux command line. Here is what I am seeing

[root@alarm ~]# i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- 32 -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- 4d -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Even after I set the PROJ_ON pin to HIGH, I do not see a change. What address should I expect to see for DLPC3433 and DLPA3000?

Thank you,

Chris

over 4 years ago

0 Philippe Dollo over 4 years ago

TI__Mastermind 28005 points

Christopher,

The DLPC3433 usually has an I2C address of 0x36 by default. You cannot talk to the DLPA3000 using I2C using the host processor in our typical system architecture.

I hope this helps.

Regards,

Philippe Dollo

0 Christopher Vollo over 4 years ago in reply to Philippe Dollo

Intellectual 335 points

Thank you,

Yes, I was wrong, the I2C is not connected to DLPA3000.

Is there anything else I need to do to get the DLPC3433 to show up on the I2C detect?

Thank you,

Chris

0 Philippe Dollo over 4 years ago in reply to Christopher Vollo

TI__Mastermind 28005 points

Chris,

In order for the host processor to detect your controller over I2C, the controller needs to be able to boot in the first place. Are you seeing a splash screen on your projector output? Typically, you won't be able to talk to the system over I2C until you see an image on the wall (or to be more specific, until the controller completes boot and HOST_IRQ goes low).

Regards,

Philippe Dollo

DLP®︎ products

DLP products forum

DLPC3433: DLPC3433 I2C Address and Usage