I received TI's port of gstreamer to it's DaVinci processors from http://focus.ti.com/dsp/docs/dspsplash.tsp?contentId=3100
I've tried to run the example (scripts) provided by TI and I've faced what seem to be two separate issues.
I've copied the stdout log below:
<linux prompt>:/opt/system_files_gstreamer# ./test_MP3.sh MP3_file.mp3
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
(gst-launch-0.10:1204): GStreamer-WARNING **: pad adecoder0:src returned caps which are not a real subset of its template caps
(gst-launch-0.10:1204): GStreamer-CRITICAL **: gst_caps_get_structure: assertion `index < caps->structs->len' failed
(gst-launch-0.10:1204): GStreamer-CRITICAL **: gst_structure_get_int: assertion `structure != NULL' failed

[program hangs here]
For most of you, who don't know about this script: All it does is after setting the gstreamer, plugin and library paths, it runs gst-launch with a pipeline, thus: gst-launch-0.10 filesrc location=$1 ! adecoder Codec=3 ! osssink

The two issues I'm facing:
(a) The *last* element in the gstreamer pipeline does not reply with a message to the app saying it has paused (This is ascertained with debug prints that I inserted in gst-launch.c. It's possible that for some reason, the element does not pause. I've faced this same issue with pipelines which have no decode/render elements as well.) Actually, I'm not sure if (a) it doesn't pause because it doesn't finish preroll or (b) it says it hasn't finished preroll because it doesn't send a pause signal! (I'm not sure which is the cause and which is the effect).

(b) The critical errors printed (seen above. I guess these are caused because of TI's mp3 decoder element plugin.) Could the adecoder capabilities be incompatible? Seems unlikely, since TI would have tested this first.

Would anyone know what the issue might be? Has anyone seen a similar issue with gstreamer?
I'd greatly appreciate any help.