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.

DLPC3478: Pattern file generation without GUI, compatible with DLPC firmware 9.0.1

Part Number: DLPC3478
Other Parts Discussed in Thread: DLPC-API

We are programatically generating pattern binary files with the DLPC-API, this works with the previous firmware 8.1.0, but there is no updated API for the new firmware 9.0.1. Looking at the binary files from the GUI generated files, something has changed. Can we please get the source code, specifically "dlpc347x_internal_patterns.c" used in DLPC GUI V3.2.0.6. or instructions on what has changed? 

  • Hello User,

    Can you please provide more details on the issue you're having when use the DLPC-API with the latest firmware version 9.0.1? 

    From my understanding TI does not offer source code of the DLP controllers to customers.

    Regards,

    Lori 

  • We are using the released software sourcecode from TI, https://www.ti.com/tool/DLPC-API  This piece of software does not run on the controller, but it can be used to generate the pattern binary file programmatically.  With the new 9.0.1 firmware TI also released a new version of the GUI, 3.2.0.6, which supports the new field for patternSetEntryIndex in the patternOrderTableEntries.  I assume the new GUI-version was to accomodate for this firmware change. We can successfully use the GUI to manually create a pattern-file, but the old API version (from 2019) does not generate the correct pattern binary, when given the same input as the GUI.  See hex-compare below. It starts to differe right after PATN+header.  We need a correct way to generate and merge this pattern-file with the 9.0.1 firmware-binary programmatically.

  • Hello Anders,

    Thank you for clarification!

    We will need to look into this more and get back to you by the end of next week.

    Regards,

    Lori 

  • Hi again! 

    We actually got it working now, we missed the changelog-notice where it says the newly introduced patternSetEntryIndex parameter is 1-indexed instead of 0-indexed. Just changed that, and it works!

  • Hi Anders,

    I'm glad you solve the problem!

    Please feel free to submit an E2E forum if you have further question about DLP Product.

    Regards,

    Lori