DSP stop at codec engine mechanic

puyol jiang

Hello everyone:
My platform is C6A8168, codec-engine version is 3_21_00_13.
I develop my own algorithm on DSP at codec engine mechanic. Unexpected, when I add my own algorithm, the DSP is stop, I doubt maybe the problem is wrong memory. the errors as fowlles:

[t=0x0067d612] [tid=0x40074000] ti.sdo.ce.video1.VIDENC1: [+E] VIDENC1_process> Enter (handle=0xb5088, inBufs=0xbeb01894, outBufs=0xbeb01b68, inArgs=0xbeb01b74, outArgs=0xbeb01)
[t=0x0067d676] [tid=0x40074000] ti.sdo.ce.VISA: [+4] VISA_getMaxMsgSize(0xb5088): returning 0x1000
[t=0x0067d6a1] [tid=0x40074000] ti.sdo.ce.VISA: [+5] VISA_allocMsg> Allocating message for messageId=0x00010006
[t=0x0067d6e9] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+E] Memory_getBufferPhysicalAddress> Enter(virtAddr=0x41d7a000, size=0x25200)
[t=0x0067d71e] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+1] Memory__getPhysicalAddress> Enter(virtAddr=0x41d7a000, size=0x25200)
[t=0x0067d750] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+1] Memory__getPhysicalAddress> found in cb(Sc=0x41d7a000, Ec=0x41d9f200, Ss=0x41d7a000, Es=0x41d9f200, PSc=0x94586000)
[t=0x0067d791] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+1] Memory__getPhysicalAddress> returning physAddr=0x94586000
[t=0x0067d7bf] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+X] Memory_getBufferPhysicalAddress> return (0x94586000)
[t=0x0067d7ee] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+E] Memory_getBufferPhysicalAddress> Enter(virtAddr=0x41e93000, size=0x25200)
[t=0x0067d821] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+1] Memory__getPhysicalAddress> Enter(virtAddr=0x41e93000, size=0x25200)
[t=0x0067d852] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+1] Memory__getPhysicalAddress> found in cb(Sc=0x41e93000, Ec=0x41eb8200, Ss=0x41e93000, Es=0x41eb8200, PSc=0x94560000)
[t=0x0067d893] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+1] Memory__getPhysicalAddress> returning physAddr=0x94560000
[t=0x006cf76a] [tid=0x40074000] ti.sdo.ce.osal.Memory: [+X] Memory_getBufferPhysicalAddress> return (0x94560000)
[t=0x006cf7a3] [tid=0x40074000] ti.sdo.ce.VISA: [+E5] VISA_call(visa=0xb5088, msg=0x422f1180): messageId=0x00010006, command=0x0
[t=0x006cf7db] [tid=0x40074000] ti.sdo.ce.ipc.Comm: [+E] Comm_put> Enter(msgqId=0x1, msg=0x422f1180)
[t=0x006cf833] [tid=0x40074000] ti.sdo.ce.ipc.Comm: [+X] Comm_put> return (0)
[t=0x006cf85c] [tid=0x40074000] ti.sdo.ce.ipc.Comm: [+E] Comm_get> Enter(comm=0xb5110, msg=0xbeb017e4, timeout=-1)

What reason?
Can anyone help me?
Thanks!

over 14 years ago

0 puyol jiang over 14 years ago

Intellectual 555 points

Nobody have the same question?

0 Rahul Prabhu over 14 years ago in reply to puyol jiang

TI__Guru** 116170 points

Jiang,

Can you check the main.c file of your codec server. Does the source code call IPC_start, if not I think you should add Ipc_start(); statement before CERuntime_init();

I remember there was an issue regarding IPC start in codec engine , where IPC_start was removed from the default codec engine initialization. Please try the fix and let us know if this fixed the issue that you are seeing.

Regards,

Rahul

0 Chris Ring over 14 years ago in reply to Rahul Prabhu

TI__Genius 17205 points

The fact that VIDENC1_create() was successful means the Server has started up and communication is going - so I don't think it's an issue calling IPC_start().

This looks like the classic case where the ARM tells the DSP to do something (in this case, encode a frame of video) and it's waiting for a reply. Often it's best to connect to the slave with a debugger and see what's going on. Sometimes you'll see an assert or crash, blown stack, etc.

Another thing to try might be setting CE_CHECK=1 - you might get lucky and catch an app/codec error.

Chris

0 puyol jiang over 14 years ago in reply to Chris Ring

Intellectual 555 points

I have checked main.c file, the IPC function is before CERuntime_init()function. I doubt the reason may be small stacksize, I want to know how to enlarge the stack size. Thanks!

0 Chris Ring over 14 years ago in reply to puyol jiang

TI__Genius 17205 points

This article describes some details on stack size:

http://processors.wiki.ti.com/index.php/Stack_issues

Chris

0 puyol jiang over 14 years ago in reply to Chris Ring

Intellectual 555 points

The problem as before, I do not know why.

When I use default data process function memcpy, the can work well, but when I chang memcpy to my own encode function, it have the problem.

I enlarge the stack size, but have the same problem.

I need help!

Thanks!

Processors

Processors forum

DSP stop at codec engine mechanic