• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 717 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: Trouble connecting with Raspberry Pi Zero W

Simon Whalen
Prodigy 30 points
Part Number: DLPDLCR230NPEVM
Other Parts Discussed in Thread: DLPC3436

We have been able to successfully connect the evaluation module via a Raspberry Pi 3 a+ and have video play but have not been successful with connecting a Raspberry Pi Zero W.  Do to environmental restrictions, it is ideal that we are able to use the Raspberry Pi Zero W. 

When hooking up the Raspberry Pi Zero W and DLP evaluation module, the Raspberry Pi initially freezes and reboots itself. Once it has rebooted, the DLP evaluation module with first go to the splash screen then turn grey as the connection is being made.  What happens with the Raspberry Pi 3 a+ is that once the connection is done, the desktop is displayed.  This is not the case for the Zero W.  Instead the projector turns off.  

I then will try to connect with the DLP evaluation module by typing in the command python3 init_parallel_mode.py and get an error, which you can see via the attached image.

Please let me know if there is a way around  this or if the Raspberry Pi Zero W is not compatible with this DLP evaluation module.

  • 0
    TI__Mastermind 28005 points

    Simon,

    The Raspberry Pi Zero W and the Raspberry Pi 3 A+ appear to support same GPIO pin configuration and functions, so they should both work with this EVM assuming everything else is configured properly.

    That being said, it appears that you are unable to communicate with the EVM over I2C. Have you tried using the I2C Tools over command line to check if the DLP Controller (DLPC3436) is showing up on your selected I2C bus (using "i2cdetect")? On this note, you should also verify that the I2C Bus index for the Raspberry Pi Zero W is the same as the 3A+. If they are different, you would need to change the I2C bus index in the python code so that the Raspberry Pi will know what bus to access the DLPC3436 over.

    I hope this helps.


    Regards,
    Philippe

  • 0 in reply to Philippe Dollo
    Prodigy 30 points

    Philippe,

    Using sudo i2cdetect -y 1 , nothing showed up on the selected i2c bus.  I have been unable to find any information as to whether the Zero W and 3a+ have the same i2c bus index but I have inquired about that to raspberry pi to see if there is a difference.  I'll keep looking for now and see if I can find a solution.

  • 0 in reply to Simon Whalen
    TI__Mastermind 28005 points

    Simon,

    Thanks. Please keep us posted.

    Best Regards,

    Philippe

  • 0 in reply to Philippe Dollo
    TI__Mastermind 28005 points

    Simon,

    Any updates on the above?
    Regards,

    Philippe

  • 0 in reply to Philippe Dollo
    Prodigy 30 points

    Philippe,

    I was able to figure out the issue. 

    At first I was using a longer 40pin ribbon cable (125mm) and replaced it with the 50mm ribbon cable that came with the projector and it was connecting, albeit not consistently and it still would turn the screen black once the VNC was disconnected but I was able to detect the i2c connection by this point.  After a bit longer of trying different settings, I bricked one of the Zero W boards.  I tested another Zero W and it appeared that there was an over current problem with the Evaluation module pulling from the Zero W which luckily was on a fused circuit and blew a fuse rather than the EVM board.  I ended up cutting the 2x5V and 2X3.3V pins on the Zero W and have not had a problem since.  Signal is being sent and is working as should be.  It appears that the GPIO pins cannot send as strong of a signal as the other boards (only 50mm rather than 125mm) though this is not a problem.