• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 577 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

DLP300S: Evaluation Module for Lab Equipment Integration

DLP300S: DLP300S and DLPC1438 application sample

Scott Leatham
Prodigy 15 points
Part Number: DLP300S
Other Parts Discussed in Thread: DLPC1438

Hello,

We are using the reference H/W from eViewTek (EVT-D3 and optics controller board), however we need a sample application or driver to understand the SPI data format and better understand the I2C command set.

A generic reference application or driver for the DLPC1348 would really help us.  The TI documentation is too vague in some areas and verbose in others, with self inconsistencies.  A working piece of code would be of great help.

eViewTek doesn't seem to have an implementation kit, and simply points us to a H/W data sheet, a few snippets of an I2C command set, and the TI documentation.

They must be able to tell customers how to use their products.

And in theory TI should be able to tell/show developers how to use (or program) their parts.

Please point me to any working samples for the DLP300S and DLPC1438.

Thanks in advance!

  • 0
    Prodigy 15 points

    Specifically, I was hoping to get some information about the SPI data format. The documentation I have at hand doesn't give me enough detail about the dataflow format. I'm having trouble sending full frames at 2560x1440. Could this be a buffer issue? I see that data may need to be split into segment commands. Do you have sample frame data? Or any other information about the format of the individual pixel data? thank you very much for your help

  • 0 in reply to Scott Leatham
    TI__Genius 9971 points

    Hello Scott, 

    Our team will look into your query and will get back to you in a couple of days.

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    TI__Genius 9971 points

    In the meantime, can you please refer to the following FAQ and see if it helps in answering your queries? 

    https://e2e.ti.com/support/dlp-products-group/dlp/f/dlp-products-forum/1159336/faq-dlpc1438-python-script-example-for-dlpc1438-crc16-calculation

    Regards,

    Mayank

  • 0 in reply to Scott Leatham
    TI__Genius 12575 points

    Hello Scott,

    Please refer to Section 4, SPI Data Transmission, of the DLPC1438 Software Programmer's Guide. This contains in depth detail on the SPI data formatting for image transmission.

    With this information and the link to the CRC16 example script, is there any further uncertainty? If not, please click the resolved button below this post.

    Regards,

    Austin

  • 0
    Prodigy 15 points

    OK, thanks.  We did read those sections of the document regarding data transmission.  However more info is needed.  

    To cut to the chase... is there another reference controller board for the DLPC1438 rather than the eViewTek board (as listed in your 3rd party tools spread sheet)?

    The eViewTek may be using custom firmware that appears to be doing things differently from the documentation and doesn't appear to support all the IO options available on the DLPC1438.

    We have been in contact with eViewTek, they are VERY helpful, we go the H/W from an existing product on the market --- however they tell us to read the TI documentation for the most part; with a couple of exceptions that makes us wonder about variations in the firmware when compared to the TI documentations in the areas of CRC and SPI modes, plus there's no support for parallel image data input.

    Is there another reference board option other than eViewTek?

    Scott

  • 0 in reply to Mayank Khandelwal
    Prodigy 15 points

    Thanks, we did implement the code, converted to C++.  However it appears that the CRC is ignored by the reference system. But we will triple check.

  • 0 in reply to Scott Leatham
    TI__Expert 3425 points

    Scott,

    Our team will get back to you on the alternate board option if any exits.

    In the meantime, Could you please help us understand what do you mean by CRC being ignored by reference system. Are you facing issues to get the code compiled or runtime issues?

    Regards,
    Akhil

  • 0 in reply to Scott Leatham
    TI__Expert 7890 points

    Hi Scott,

    Unfortunately, there is no evaluation module for DLP300S + DLPC1438 + PMIC/LED driver available, but we are in the process of releasing a reference design of this chipset on TI.com soon. 

    Please let us know if you have any specific questions about sending the SPI data for CRC16 calculation on the DLPC1438 system.

    Also, as you mentioned in the private message that you may need a higher illumination power for your application. In that case, DLP301S can be capable of higher power output depending on the optical design and thermal solution. Please refer to [FAQ] DLP300S and DLP301S Benefits. However, if the user exceeding either the illumination power density limit or the thermal limit will void the warranty and may cause early failure of the device. 

    Regards,

    Lori

  • 0 in reply to Lori Wang
    Prodigy 15 points

    Fortunately we resolved it.  Turns out that the H/W we are using was not using documented SPI mode 0...  It used a different SPI mode.  It wasn't until we used a logic analyzer on our own that we were able to identify this.  If others run into such issues of not being able to get image data to appear, I might suggest you try a different SPI mode.  There are 4 SPI modes, 0, 1, 2, and "3".  I knew about 3 of them...  did I mention "3"?  No, of course I didn't.  ;-). I categorically did not mention "3".  That's my story and I'm sticking to "3", opps I mean "it".  Not "3".  OK now we've cleared that up.

  • 0 in reply to Lori Wang
    Prodigy 15 points

    Thanks, I'll check out the 301S in due time.  Hopefully it's pin compatible with 300S.

  • 0 in reply to Akhil Guntumadugu
    Prodigy 15 points

    Apparently it's possible to implement firmware for the DLPC1438 that doesn't return a CRC value.  In such cases there's no reason to calculate the CRC on the host side.  Albeit I would imagine extensive testing for SPI bus signal integrity and performance issues would be needed, like making sure the cable or traces aren't too long or influenced by nearby noise (induction, high frequency output etc).

  • 0 in reply to Scott Leatham
    TI__Genius 12575 points

    Hi Scott,

    We are glad to hear the issue is resolved. Please let us know if any further question arises in the future.

    Kind regards,

    Austin