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: SETUP TROUBLE

Part Number: DLPDLCR230NPEVM

Hello Support Team
I'm looking for support.
Initially, there was a problem that when the power was plugged in, the logo just flashed and didn't advance to the test chart.
In this regard, the problem was solved by plugging in a 6V 3A power supply, which was not what was indicated.
However, I set it up according to "[FAQ] DLPDLCR 230 NPEVM: DLPDLCR 230 NPEVM Quick-Start Tutorial," but an error occurs when I run the script "python init _ parallel _ mode.py."
What to do?

  • P.S.
     I use the default config.txt file provided in the 230NPEVM software package.

  • Hello Tokuji-san

    DLPDLCR 230 NPEVM expects a 5V 3-4A power supply to be connected to it and not a 6V one. Can you please check this out again and let us know what all problems you are facing after connecting the recommended power supply?

    Regards,

    Mayank

  • Hello Mayank

    I connected the 5V3A and 5V4A power supplies, but there was a problem.
    But First Graphic image (DLP logo)  is binking every second and not stayed on.

    The TI Japan Engineer already told customer;
    Try updating the firmware.

    So I tried to update the firmware, but things didn't change.

    I searched the forums for similar issues and found reports that it worked when the power supply was set to 6V4A.
    https://e2e.ti.com/support/dlp-products-group/dlp/f/dlp-products-forum/1027430/dlpdlcr230npevm-flashing-initial-logo-and-board-resetting?tisearch=e2e-sitesearch&keymatch=DLPDLCR230NPEVM#

    So I actually connected a 5.25 V 3 A power supply and this problem was solved.

    The problem that remains is the first question I asked.

    I set it up according to "[FAQ] DLPDLCR 230 NPEVM: DLPDLCR 230 NPEVM Quick-Start Tutorial," but an error occurs when I run the script "python init _ parallel _ mode.py."

    What should I do?

    Thank you for your reply.

  • Tokuji-san,

    Thanks for all the clarification. Our team will look into your query and will get back to you with an update by tomorrow. 

    Regards,

    Mayank

  • Hello Tokuji-san,

    We have found that some 5V supplies have a fluctuation on their voltage output. For example, some supplies listed as 5V are actually supplying 5.1 or 5.2 volts. Version 7.3.14 was uploaded to the EVM product page last year with a lowered initial LED current to ease the initial power demands. However, we find that a 5.2V supply works more consistently as you have found.

    Regarding the Python error that you are experiencing, it appears that the active I2C bus is not being found. Please trying running the following commands without including "sudo":

    i2cdetect -y 1

    i2cdetect -y 7

    i2cdetect -y 22

    One of these will likely return an active I2C bus. If not, it may be necessary to cycle through additional numbers. With the correct I2C bus, the printout should appear as:

    Once this is found, this number should be used for DEFAULT_I2C_BUS in the i2c.py module.

    Alternatively, this might be found in the /dev directory but should be confirmed with the i2cdetect -y command:

    Please let us know if this resolves your issue.

    Regards,

    Austin

  • Hello  Austin
    Thank you for your reply.

    I tried it and it doesn't seem to detect an active I2Cbus.

    I also checked the Dev directory and it seems that there is no directory other than "i2 c -22".

    Is the cause on the EVM side? Or is it on the side of Raspberry Pi?

    On the other hand, the script for "flash _ write _ fpga.py" seems to work, but what is the difference from "python init _ parallel _ mode.py"?

    Tokuji

  • Hello Tokuji,

    Thank you for the input. We will have to get back to you next week. Thank you for your patience.

    Regards,

    John

  • Hello Tokuji-san,

    It is difficult to pinpoint the issue to either the EVM or Pi. It appears that the communication between them is not properly established. The "flash_write_fpga.py" script primarily issues commands over the Raspberry Pi terminal while "init_parallel_mode.py" issues commands to put the DLPC into the proper configuration for video streaming using the I2C API.

    How are you certain that "flash_write_fpga.py" is properly writing? If you open this script you will see the following line:

            Summary = WriteDisplayImageCurtain(1,Color.Black)

    If you alter or comment out this code does your process change at all? It is possible that this script appears to execute properly because there is less feedback from the controller for the Pi to realize that its transmission is not being received.

    You have mentioned that you de-bugged the power supply issue for the EVM. Can you confirm that the EVM is powered (without turning off) and properly connected to the Pi with the ribbon cable?

    Regards,

    Austin 

  • Hello Austin,
    Thank you for your reply.

    I tried it as directed.
    As a result, the process doesn't seem to be different.

    The first time it was still the provided script and the second time it was partially commented out as instructed.

    Click here to play this videoClick here to play this video

  • Hello Tokuji-san,

    The last two attachments did not properly load onto the thread, but I assume that the behavior was more or less the same. Is that correct? Did the EVM display cut to black when the comment was in place and continue to project when it was not?

    Though the I2C bus appears active, it does not appear to be detecting the EVM. Can you confirm that the EVM is powered (without turning off) and properly connected to the Pi with the ribbon cable?

    Regards,

    Austin

  • Hello Austin,

    They all look exactly the same in action.

    original

    comment out

  • Hello Tokuji-san,

    Thank you for the new uploads. They appear this time.

    After some investigation, it appears that this issue is arising due to the recent Raspberry Pi update. The new update has the SPI and I2C interfaces disabled by default. Please try enabling these interfaces in the Raspberry Pi Configuration page or by entering 'sudo raspi-config' in the command line.

    After making this change, please reboot the Pi and try to detect the I2C bus as described in the Quick Start Tutorial.

    Please let us know if this corrects your issue.

    Regards,

    Austin

  • Hello Austin,
    Thank you for your reply.
    I followed the instructions and tried, but the situation did not change.

    So I borrowed a working EVM from a Japanese TI engineer to carve it out.

    The borrowed EVM has a return value in i2cdetect and the "init_parallel_mode.py" command now works correctly to project the raspberry pi screen.

    So the problem seems to be with the EVM I bought instead of the raspberry pi.

  • Hello Tokuji-san,

    Is this EVM connected to the same or different Raspberry Pi? If it is a different Raspberry Pi, please try connecting it to the Raspberry Pi with which you were finding difficulty to the working EVM. This will allow us to ensure that the issue lies in the EVM.

    Regards,

    Austin

  • Hello Audtin,

    Thank you for your reply.

    I use the same Raspberry Pi.
    I also tried it on a Raspberry Pi 3B that I borrowed additionally, and the results are the same as the previous Raspberry Pi 4.

  • Tokuji-san,

    I have sent you a friend request to collaborate about this issue off of the E2E thread. Please accept so that we might continue.

    Regards,

    Austin

  • Hello Tokuji-san,

    Please consider this post an approval for RMA of the failing DLP230NPEVM unit.

    Regards,

    Austin