We have been struggling with getting any firmware newer than 3.1 to work reliably in our application. First we had the trigger glitch issue with 4.0.3 (see other thread on this forum), and now, testing 4.1 we have found another issue that is not present on the 3.1 firmware.
The configuration is as follows:
* trigger mode 1, sequence started by external trigger with start on falling edge on trig in 2.
* sequence defined with 22 patterns, mix of 1 bit and 8 bit, 4 flash indexes. (all exposure times long enough to allow buffer swap/flash load)
* first time the sequence is started, everything is ok. on subsequent starts, we get either wrong patterns displayed or half n half of two patterns
If we configure with only 2 flash indexes,11 pattern sequence, everything works as expected multiple times.
We configure and run everything over I2C from a microcontroller, so timing of trigger signal and I2C commands is very well defined and has been 100% stable on 3.1 firmware for a long time.
Same microcontroller firmware is used with both firmware version 4.1 and 3.1, we get problems only with 4.1. The TI changelog is very sparse with respect to what has changed, and no mention of anything related to this, but clearly something has changed between 3.1 and 4.1 causing this.
1. How should we proceed with getting help on this issue? we really don't want to change our microcontroller-code.
2. The only reason we need newer fw than 3.1 is the new DLP chip revision. This has caused a lot of trouble for us so far, almost 6 months of back and forth so far, and still not solved. Is it possible to just get a clean 3.1 firmware with one single hotfix introducing the correct waveform/park sequence for new DLP revision?
