• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 306 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

VIDDEC_process call failing with custom board

deepthi kiran
Intellectual 290 points

Hi

On our custom board we are using “TMS320DM6446AZWT” processor. We were doing video conference in our board. With this we are seeing sometimes DSP is not able to perform both encoding and decoding together, during this time one or two frames it decodes and stops. Some times decoded data is corrupted. Only decoder is working fine, the moment we start encoder, decoder is stopping. But same software setup is working fine with EVM. In the EVM chip version is TMS320DM6446ZWT. Will this causing any issue??

After putting the debug messages in plugins, I came to know that VIDDEC_process() is failing as soon as the encoder starts. If I do only video decode,there is no problem

Bleow is the some of the log messages that Iam geting withe CE_DEBUG=3

[DSP] @0,309,248tk: [+0 T:0x8b807f9c S:0x8bb7f544] ti.sdo.ce.video.VIDDEC - VIDDEC_process> Enter (handle=0x8fb84d10, inBufs=0x8bb7f5f4, outBufs=0x8bb7f600, inArgs=0x8fe06db8, outArgs=0x8fe06dc4)
[DSP] @0,309,376tk: [+5 T:0x8b807f9c S:0x8bb7f52c] CV - VISA_enter(visa=0x8fb84d10): algHandle = 0x8fb84d38
[DSP] @0,309,447tk: [+0 T:0x8b807f9c S:0x8bb7f50c] ti.sdo.ce.alg.Algorithm - Algorithm_activate> Enter(handle=0x8fb84d38)
[DSP] @0,309,523tk: [+0 T:0x8b807f9c S:0x8bb7f50c] ti.sdo.ce.alg.Algorithm - Algorithm_activate> return
[DSP] @0,309,715tk: [+5 T:0x8b807f9c S:0x8bb7f52c] CV - VISA_exit(visa=0x8fb84d10): algHandle = 0x8fb84d38
[DSP] @0,309,799tk: [+0 T:0x8b807f9c S:0x8bb7f50c] ti.sdo.ce.alg.Algorithm - Algorithm_deactivate> Enter(handle=0x8fb84d38)
[DSP] @0,309,875tk: [+0 T:0x8b807f9c S:0x8bb7f50c] ti.sdo.ce.alg.Algorithm - Algorithm_deactivate> return
[DSP] @0,309,941tk: [+0 T:0x8b807f9c S:0x8bb7f544] ti.sdo.ce.video.VIDDEC - VIDDEC_process> Exit (handle=0x8fb84d10, retVal=0xffffffff)
[DSP] @0,310,027tk: [+0 T:0x8b807f9c S:0x8bb7f584] OM - Memory_cacheWb> Enter(addr=0x88d35000, sizeInBytes=691202)
[DSP] @0,310,848tk: [+0 T:0x8b807f9c S:0x8bb7f584] OM - Memory_cacheWb> return
[DSP] @0,310,901tk: [+0 T:0x8b807f9c S:0x8bb7f584] OM - Memory_cacheWbInv> Enter(addr=0x88d35000, sizeInBytes=202752)
[DSP] @0,311,195tk: [+0 T:0x8b807f9c S:0x8bb7f584] OM - Memory_cacheWbInv> return
[DSP] @0,311,247tk: [+5 T:0x8b807f9c S:0x8bb7f5e4] CN - NODE> returned from call(algHandle=0x8fb84d10, msg=0x8fe06c80); messageId=0x000203ba
[DSP] @0,312,958tk: [+0 T:0x8b80006c S:0x8b804024] CR - processRmsCmd(0x8fe05ca8, 4056): cmd = 5
[DSP] @0,313,027tk: [+0 T:0x8b80006c S:0x8b804024] CR - remote time = 0x0, trace buffer size = 4032
@1,557,211us: [+0 T:0x464b0b60 S:0x464afa3c] CV - VISA_call Completed: messageId=0x000203ba, command=0x0, return(status=-1)
@1,557,584us: [+5 T:0x464b0b60 S:0x464afa54] CV - VISA_freeMsg(0x44008690, 0x4a4c2c80): Freeing message with messageId=0x000203ba
@1,557,798us: [+0 T:0x464b0b60 S:0x464afa9c] ti.sdo.ce.video.VIDDEC - VIDDEC_process> Exit (handle=0x44008690, retVal=0xffffffff)
VIDDEC_process failed: error (-1 ext-err: 0x1095)@1,558,781us: [+0 T:0x464b0b60 S:0x464afc74] OM - Memory_contigAlloc> Enter(size=202754, align=-1, cached=FALSE, heap=FALSE)

Please help us to resolve this issue

Thanks and Regards

Deepthi

 

  • 0
    TI__Genius 17205 points

    deepthi kiran said:
    VIDDEC_process failed: error (-1 ext-err: 0x1095)@1,558,781us: [+0 T:0x464b0b60 S:0x464afc74] OM - Memory_contigAlloc> Enter(size=202754, align=-1, cached=FALSE, heap=FALSE)

    Just to help you understand the internals, you can correlate the extended error (highlighted above in red), and this XDM FAQ:  http://processors.wiki.ti.com/index.php/XDM_FAQ#How_do_I_decode_extendedError.3F

    Decoding that extended error, it's returning "XDM_CORRUPTEDHEADER" (as you've reported), with an additional codec-specific error 0x95.  If you have the codec docs, you may be able to find what 0x95 is(?).

    If the decoder works fine until the encoder shows up, I might suspect one of them isn't cooperating with the other - maybe there's a resource collision.  Do you know which versions of the codecs are in your system?

    Chris

  • 0 in reply to Chris Ring
    Intellectual 290 points

    Hi Chris,

    Thanks for your reply.We are using XDM 0.9 version (dvsdk_1_30_01_41).

    If it can be a resouce issue are you doubting on CMEM, My worry is same software set up is working fine on the EVM with out anty issues. I tried even with the EVM which was having a TMS320DM6446BZWT since we were using TMS320DM6446AZWT,there also it is fine.

    Please help me out, I am not much aware of  Codecs and DSP.

    Thank  and Regards

    Deepthi