Ahh, that sounds reasonable.

 

I guess the way to test this is by just increasing the stack size? Or is there 
some other method to determine how much stack is currently being used?

 

Also, is there any way to test this if I do not have access to the DSP side 
codec? Currently, the server is delivered as the standrard *.x64P file.

 

I see this wiki, http://wiki.davincidsp.com/index.php?title=DDRALGHEAP. This 
looks like the best I can do from the Arm side.

 

Sam Hague
IPCBU

Cisco Systems, Inc.
7025 Kit Creek Road
RTP, NC 27709
Phone: 919 476-2794
Fax:   919 392-7065
[EMAIL PROTECTED]
www.cisco.com 

From: Ring, Chris [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 31, 2008 12:41 PM
To: Sam Hague (shague); [email protected]
Subject: Re: Codec Engine hangs when tracing is enabled

 

Check your DSP side codec stack config.  If you're right on the edge, enabling 
trace may blow it.

Chris


----- Original Message -----
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [email protected] 
<[email protected]>
Sent: Thu Jan 31 10:45:22 2008
Subject: Codec Engine hangs when tracing is enabled

Hi all,

does anyone have insight into why the DSP/ARM would hang when the
tracing collection thread is enabled?

I have a codec engine algorithm developed by someone else. I have
modified the decode demo to call this new algorithm after an h264 decode
of a frame has been completed. The decodeCombo server has been modified
to include this new algorithm

Everything works fine if I do not call "TraceUtil_start(ENGINE_NAME)" to
start the trace collection thread. In the decode.cfg file it does not
matter what "TraceUtil.attrs = TraceUtil.SOCRATES_TRACING" is set to.
Either SOCRATES_TRACING or FULL_TRACING.

If "TraceUtil_start(ENGINE_NAME)" is called, then the decode demo app
hangs when the VIDDEC_process(newAlg) all is made. The
VIDDEC_process(h264) call works fine and then the decoded frame is
passed into the VIDDEC_process(newAlg) call where it hangs. The
VIDDEC_create(newAlg) also returns successfully.

If "TraceUtil_start(ENGINE_NAME)" is not called then everything works
fine. Also if the TraceUtil.attrs = TraceUtil.FULL_TRACING, the newAlg
works fine and dumps the tracing messages to stdout.

My thinking is there is probably something in the new algorithm that has
not been implemented for supporting the trace collection. Or maybe some
build option for the server. So, I am looking for ideas to poke the
codec developer.

Thanks, Sam
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to