1. Codec datasheets/users guides should contain the codec-specific
extended error codes. (Unfortunately, the extended error codes vary
from codec to codec, so you'll have to consult the codec docs)
3. Which version of Codec Engine? If a recent release (2.00 or later),
you can set a CE_DEBUG env var to 1, 2, or 3 to easily get the trace.
If an older release, it's not quite as easy... but we can help you.
Section 4.8 has the [confusing] details:
http://www-s.ti.com/sc/techlit/sprue67
Exactly what you need to do will depend on how your app is written
(e.g., if it uses TraceUtils, the "how do I get DSP-side trace" answer
is different than if it doesn't). Please give that section a read, and
post a follow-up if you need further help.
[ Looking at your use case - if your app.cfg is configuring TraceUtils
attrs to "SOCRATES_TRACING", the refresh rate is initially set to zero,
meaning the ARM-side polling thread will never pull the DSP-side trace
contents off the DSP. Once the refresh rate is set to non-zero, the
TraceUtil thread will begin pulling trace data off - you may want to
look in that doc for the traceutils command pipe and issue a
"socrates=on" to it. Else, change the app.cfg script from
SOCRATES_TRACING to something more friendly like FULL_TRACING which has
an initial refresh period that's non-zero. ]
4. Often, we've found that the DSP Servers are configured way too
"close to the edge" WRT stack usage. Enabling trace has, on many
occasions, caused the stack to be blown. Might check this topic:
http://wiki.davincidsp.com/index.php?title=Stack_issues
Chris
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Ragas sag
Sent: Monday, April 14, 2008 9:36 PM
To: davinci-linux-open-source@linux.davincidsp.com
Subject: Re: MJPEG codec -> only 14 bytes after encoding ...
Hello Xperts,
1)
KIndly comment on the following mentioned error's from the TI
processor. How do i analyse or understand the cause ?
Error's:
a) VIDDEC_process() failed with a fatal error (-1
ext: 0x81d)
b) VIDDEC_process() failed with a fatal error (-1
ext: 0x201e)
2) The video decode code fails to run for a video that is more
than 10mnts. I tried to run two test vectors ( MPEG 2, *.m2v files) each
nearly
20mnts, And each time it hangs/stops at nearly 9 -11 minutes
time. Why ? Is their any limitation with the programme ?
3) I want to enable TI side CE trace util activity. I used
" CE_TRACE="*=01234567" TRACEUTIL_DSP0TRACEMASK="*=01234567"
TRACEUTIL_VERBOSE=1 <programme name & input file name>" only arm
side activity is written to a file. I want to collect dsp activity, what
do i need to change in the above configuration/setting , to trace /
write DSP activity to stdout / file ? Without the need of any *.cgf
file.
4) And when i enable the CE_TRACE above, my code crashes / hangs
in between why? Due to which what i started out to analyse, end's with
something to analyse again.
I am placing this question in this forum, hoping that i will get
some help to fix my problems.
Warm Regards,
Ragas
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
