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.

TI-OMTB script vs TI-OMX C application [decode_scale_display] problem identified.

Just wanted to let the community know that the issue with not getting the OMTB "decode_scale_display.oms" script

to work under SDK 5.02 vs SDK 5.01 has now been resolved.

[Previous issue thread:  http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/132994.aspx ]

It seems that the TI-OMTB variant was drawing more power on our custom boards than the TI-OMX C application variant.

Why that would be the case I don't know since they both use the same VPSS subsystem.

[Well I have some theories but they're not relevant :-) ]

 

In any event, we had our H/W people take a closer look at the power circuits, they made some part changes and

now we have both the OMTB and the C application versions working.

Just a word to the wise on something to keep an eye out for as you develop your systems.

 

Juan.