• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 797 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.

Simultaneous processing of multiple DLP chips

Seishin
Genius 4135 points
Other Parts Discussed in Thread: DLPC200

Hi,

I'm always thankful for the help.

For multiple DLP chip, Is it possible to simultaneously access?

Specifically, it generates a thread for each device connected on a single PC,

We would like to perform a simultaneous control.(0.55 XGA)

Current is

・Specifies the device to be controlled by the DLP_Misc_SetUSBDeviceNumber () method.

・Then I'm doing an API call such DLP_RegIO_WriteImageOrderLut () method.

However, the processing time increases in proportion to the increase in the number of DLP devices in these methods.

I'd like to reduce time by simultaneous processing of each device when using more API processing time such as

DLP_FlashProgram_ProgramParallelFlash () method.

Please give us your advice if you have any ideas.

Best regards,
Seishin

  • 0
    TI__Mastermind 30875 points
    Hello Seishin,

    Unfortunately there is no quick and easy solution available at this time to address your problem.

    On a different note,

    Option - 1 (USB):
    As you know, TI USB driver detect the DLPC200 controller chip with unique USB VID = 0x0451& PID = 0xAF35. Changing the ID # for each device is something that would make the PC to detect each DLPC200 as a different device and we can potentially communicate with copy of individual application. Now, whether to allow changing IDs and building Cypress EEPROM firmware for each Cypress USB device that connects to DLPC200 is something TI need to investigate and also business case justification.

    Option-2 (SPI):
    Another option is to use SPI interface of DLPC200 to receive the messages, as know SPI is slower than USB, idea would be to send SPI master broadcast messages, and all the DLPC200s on the bus would read the messages and take actions, for this type of architecture requires DLPC200 MCU firmware change to handle broadcast type messaging i.e., instead of command-response, it will be command and no response (adds risk that there is no way to detect if every DLPC200 device reading messages successfully and taking the action). This investigation also call for business justification for TI.

    Feel free to comment if there any further queries on this topic.

    Regards,
    Sanjeev