• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 176 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DLPDLCR230NPEVM: with pi5, I2C communication problems

suyeon kang
Prodigy 10 points
Part Number: DLPDLCR230NPEVM
Other Parts Discussed in Thread: DLPC3436

Tool/software:

Hello, there

I am currently working with the DLPDLCR230NPEVM connected to a Raspberry Pi 5 (running Raspberry Pi OS Bookworm, 64-bit). The board powers on correctly, the fan is spinning, and the test pattern (rainbow bars) is projected as expected.

However, I cannot establish I²C communication with the DLPC3436 controller.

  • /dev/i2c-7 is created after adding the overlay (dtoverlay=i2c-gpio,sda=23,scl=22,bus=7,i2c_gpio_delay_us=20).

  • GPIO25 (MODE_SEL) is successfully held HIGH using gpioset, confirmed by gpioinfo.

  • Running i2cdetect -y 7 shows only -- (no device detected at 0x27).

  • I also tried increasing the I²C delay (20–100 µs), disabling DPI configuration, and verifying ribbon cable (pin1 Left right arrow pin1), but the issue persists.

  • On the TI forum, I found that Raspberry Pi 4 with Bullseye works correctly, but with Raspberry Pi 5 + Bookworm, it seems I²C is not responding.

Could you please confirm if the DLPDLCR230NPEVM has compatibility issues with Raspberry Pi 5 and Bookworm OS? Or is there an updated overlay / configuration recommended for Pi 5?

Any guidance on enabling I²C communication (address 0x27) would be greatly appreciated.

Thank you.

  • 0
    TI__Expert 7035 points

    Hello User,

    The EVM has not been tested with this version of the raspberry Pi and that OS.

    There is a I2C.py script that will likely need to be modified to match the address. It is included in the python support package. The default is 7 in this script, but this may have changed on the RPi side. Go to the /dev folder and look for some i2c-xx files. You will want to try either address found here in the i2c.py script. On the older OS this is a solution to most of these issues.

    Best,

    John