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.

  • Resolved

DLPDLCR2000EVM: Raspberry Pi access to the DLPDLCR2000EVM

Intellectual 495 points

Replies: 22

Views: 10796

Part Number: DLPDLCR2000EVM

Dear Forum,

Ia am having a harrd time getting a response when accessing the DLP2000 evm from my Rpi3, "Raspberry Pi". Ihave used I2cset and I2cget to interact with the EVM.

I2cdetect identifies the 0x1b for the 2607 and 0x57 for the EEprom. Reading from any of the preset registers returns 00 in all cases. Have tried to activate any of the test images, using reg 0x11 for test pattern generation, with no result, my commands were:

i2cset -y 1 0x1b 0x11 0x3 i   # This should show a green screen 

No change!!1

Has anybody been succesful with using an Rpi3 with the eval module?

Thanks for your assistance

regards

Samir Lehaff

  • Samir,

    Keep in mind that registers in the DLPC2607 are 32-bits wide. Hence you must write to them with zero padding. In my experience failing to do so causes the I2C transaction to fail.

    For instance I would write 0x00 0x00 0x00 0x03 instead of 0x3. Let me know if this helps

    Best Regards,
    Philippe Dollo
  • In reply to Philippe Dollo:

    Philippe,
    Thanks for the suggestion, it did raise my hopes, the outcome was still the same, cannot affect the evm in any way!
    I have downloaded the 2607 GUI interface, will have to wait for a usb to i2c plug, looking at the commands that the GUi issues, they do look similar to the ones that I composed based on hte programmer's guide.
    I will welcome any addditional suggestions.
    Best regards
    Samir
  • In reply to samir lehaff:

    With that approach you will be able to interface with the EVM without the use of the BeagleBone Black. Also, you are correct that the I2C commands issued by the GUI interface are the same as those issued using the BeagleBone's I2C bus.

    As an alternative to i2cset/i2cget, you can also employ the python library that helps facilitate some of the communication between the BeagleBone Black and the DLPDLCR2000EVM. In particular, I am referring to the "/opt/scripts/device/bone/capes/DLPDLCR2000" directory in the BeagleBone Black's disk.

    I am glad that, using either of these solutions, you have a means to reliably read data from the system. In the meanwhile, I will see if I can reproduce your issue and better document it for other users.

    Best Regards,
    Philippe Dollo
  • In reply to Philippe Dollo:

    Philippe,

    I have been looking for the above mentioned python code, could you point me to a link where I can access the python scripts that you refer to.

    Thanks in advance,

    Samir

  • In reply to samir lehaff:

    Samir,

    Now that you mention it, I forgot to mention that these scripts are supplied in with the BeagleBone Black disto featuring DLPDLCR2000EVM support.

    If you do not have the BeagleBone setup on hand, I can provide the scripts here for you to download. It may actually be convenient for other Raspberry Pi users who do not have access to a BeagleBone as well.
  • In reply to Philippe Dollo:

    Please see the attached software below. Note that the software exists under an open-source license.

    /cfs-file/__key/communityserver-discussions-components-files/94/7776.nhd_5F00_python_5F00_demo.zip

    /cfs-file/__key/communityserver-discussions-components-files/94/2402.README.txt

    I hope this helps.

    Best Regards,
    Philippe Dollo

  • In reply to Philippe Dollo:

    Thanks Philippe, will work on it first thing tomorrow.
    Will give you feed back such that others may benefit from it.

    Regards
    Samir
  • In reply to Philippe Dollo:

    The python package link is exactly what I needed, it will take me a couple of days to adjust it to my application and environement. It is a nice and complete interface to the 2607 that makes a sound basis for driving the DMD.
    I will keep you posted with my progress.
    Best Regards
    Samir
  • In reply to Philippe Dollo:

    I have installed the dlp_lightcrafter-1.0.19 on my Rpii3, changing the I2c bus address from 2 to 1, allowed me to test the 2607 I2c control interface successfully.
    Remainding task is to wire the paralell video bus to verify that part.

    Regards
    Samir
  • In reply to samir lehaff:

    As DPI on RPI disables both hardware I2C busses you need to use 18Bit RGB output for DPI and add in your /boot/config.txt following line to add a software I2C, which uses GPIO23/24 by default:

    Name:   i2c-gpio
    Info:   Adds support for software i2c controller on gpio pins
    Load:   dtoverlay=i2c-gpio,<param>=<val>
    Params: i2c_gpio_sda            GPIO used for I2C data (default "23")
    
            i2c_gpio_scl            GPIO used for I2C clock (default "24")
    
            i2c_gpio_delay_us       Clock delay in microseconds
                                    (default "2" = ~100kHz)

    Which gives you then:

    pi@raspberrypi:~ $ i2cdetect -r -y 3

         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

    00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 

    10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- -- 

    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

    50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 

    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

    70: -- -- -- -- -- -- -- --                         

    Remember to use pullups on those GPIO pins then...

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.