• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 2613 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.

PC Communication with EVM4710

Jeff Hay
Prodigy 20 points

As part of a product feasibility study, I am attempting to communicate with the EVM4710 via custom PC software (i.e., not using the DLP LightCrafter Display software, but implementing some of the functionality of it).  Specifically, I wish to be able to turn the LEDs on and off via the custom software.

I have figured out to use the Cypress SDK to communicate over I2C on the USB virtual serial port.  My current procedure is:

1. Find the appropriate device and open it

2. Set GPIO 5 and 9, wait for 6 to go high (prepare for I2C)

3. Send the command bytes (for example, for LEDs On, send 0x52 0x07) to 0x36h

4. Clear GPIO 5 and 9 (close down I2C)

5. Close device communication

Step 3 doesn't appear to work - I always get a CY_ERROR_REQUEST_FAILED response when trying to write the data buffer (any command). 

Any ideas, or pointers on where I am going wrong? 

Thanks,

-Jeff

  • 0
    TI__Genius 10495 points

    Hello Jeff,

    For the Cypress chip the slave address is actually just the slave address without the read/write bit.  So the correct address would be 0x1B instead of 0x36h for both read/write.

    Can you please try if that resolves the problem?

    Furthermore I would recommend to set GPIO5 High wait for GPIO6 to get High and then set GPIO9 high.

    Best regards,

    Nadine

  • 0 in reply to Nadine Estermann
    Prodigy 20 points

    Hi Nadine.  Yup, 0x1B worked great!  Thanks for the help! (and I did change to setting GPIO9 after 6 goes high).

    Thanks,

    -Jeff

  • 0 in reply to Nadine Estermann
    Prodigy 95 points
    Hello Nadine,

    I also want to communicate with the LightCrafter DLPDLCR4710-CB. But I am having trouble getting Cypress to work at all. I downloaded the files provided here: www.cypress.com/.../usb-serial-software-development-kit
    The Serial Port Test Utility did not even detect the device even though I can see it in the Device Manager and can retreive information by typing
    mode COM1 into my console.
    Also I was not able to find information on how to get the functionality into my Visual Studio Project.
    Can you maybe clear that up for me?
    I might have overlooked something but I looked everywhere I could think of and did not find a solution to my problem.

    Thanks in advance,

    Tim
  • 0 in reply to Tim Elberfeld
    TI__Genius 10495 points

    Hello Tim,

    I am sorry to hear that you have issues with the cypress chip. In general is it possible for you to use our LightCrafter GUI without any communication issues ?

    I have a few question to be able to understand your problem better:

    • Have you tried to reinstall the windows driver ?
    • Have you also tried to reassign the com port ?
    • Can you please clarify what you would like to achieve ? Have you tried to implement the sample codes provided by cypress into visual studio ?

    Best regards,

    Nadine

     

     

     

  • 0 in reply to Nadine Estermann
    Prodigy 95 points
    Hello Nadine,

    I reinstalled the drivers multiple times, but unfortunately that didn't do anything. After your suggestion I changed the COM Port to COM2 and back but with both of those the test application provided by cypress could not detect the device. I can retreive information off the device using the GUI application of TI though. After trying the SerialPortTestTool.exe test application I tried to connect to the device directly using Visual Studio. With the example application I get the same problem:

    cyReturnStatus CY_ERROR_DEVICE_NOT_FOUND (10)

    This error code occured in the FindDeviceAtSCB0() function in the i2cmaster example using Visual Studio 2013 Professional.

    My goal is to build a 3D sensor using the TI projector as active light source. For that I need to be able to display different patterns on the projector from within my own application so that using the GUI is not possible. Unfortunately my expertise lies in image processing and not in hardware integration so I apologize for any obvious answers that I might have overlooked.

    Best regards,

    Tim
  • 0 in reply to Tim Elberfeld
    TI__Genius 10495 points

    Hello Tim,

    I think there is a misunderstanding regarding on how we use the cypress chip on our EVM. The cypress chip is a general-purpose bridge chip that can be used in several different configurations including: UART (e.g., Serial, or COM ports), SPI, I2C, JTag, etc.

    On our EVM we only use the I2C and SPI function of the chip. This means that the cypress chip will not connect to the SerialPortTestTool since we are not using the UART on the EVM.

    Please try to use the Cypress USB Serial Configuration Utility which can be  downloaded from the Cypress homepage. This tool should allow you to connect to the chip.  

    Cypress provides with the SDK sample code for the I2C communication. This would be a good starting point to start your communication to the chip.

    Please let me know if the USB Serial Configuration Utility tool works for you.

    Best regards,

    Nadine

  • 0 in reply to Nadine Estermann
    Prodigy 95 points

    Hello Nadine,

    yeah I misunderstood that. Sorry.
    I was able to use the Cypress USB Serial Configuration Utility with no problems now.
    But the i2cmaster example unfortunately still returns CY_ERROR_DEVICE_NOT_FOUND...
    Also the *.dll can not be found, when I try to use it in my own project. I copied the include and library paths from the example but it does not work.

    Is that something you can resolve or should I contact Cypress directly?

    I was able to resolve the problem with the  *.dll. I just placed it into my System folder and it worked. I guess that was described somewhere but I didnt find it. After some trial and error it worked though.



    Best regards,

    Tim