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.

Engine Open Repeatability issue on DM8148

iUniversal based application on DM8148 runs for the first time but system hangs in Engine Open during second time. This is based of EZSDK_5.03.01.15 using codec engine 3.21.02.25 and syslink 2.0.05.85. Server.cfg, config.bld, debug trace attached.

CERuntime complete

[t=0x000a67dc] [tid=0x40030000] ti.sdo.ce.Engine: [+E] Engine_open> Enter('ti814

8', 0x0, 0xbe8c3bc4)

[t=0x000a683d] [tid=0x40030000] ti.sdo.ce.Engine: [+1] Engine_open> desc->memMap

[0x0], desc->useExtLoader [0]

[t=0x000a6891] [tid=0x40030000] ti.sdo.ce.Engine: [+E] rmsInit> Enter(engine=0x1

3a718, ec=0xbe8c3bc4)

[t=0x000a68d6] [tid=0x40030000] ti.sdo.ce.Engine: [+E] rmsInit> engine->desc = 0

x13a648

[t=0x000a6911] [tid=0x40030000] ti.sdo.ce.Engine: [+E] rmsInit> engine->desc->al

gTab = 0x101b70

[t=0x000a6951] [tid=0x40030000] ti.sdo.ce.Engine: [+E] rmsInit> found remote alg

c6accel

[t=0x000a698d] [tid=0x40030000] ti.sdo.ce.Engine: [+E] rmsInit> engine has serve

r!

[t=0x000a69c9] [tid=0x40030000] ti.sdo.ce.Engine: [+E] rmsInit> engine->procId =

DSP

[t=0x000a6a06] [tid=0x40030000] ti.sdo.ce.Engine: [+E] rmsInit> engine->coreId =

0

[t=0x000a6a42] [tid=0x40030000] ti.sdo.ce.Engine: [+E] rserverOpen('ti814x.xe674

'), count = 0

[t=0x000a6a97] [tid=0x40030000] ti.sdo.ce.Engine: [+E] rserverOpen >, memMap = 0

x0, useExtLoader = 0

[t=0x000a6add] [tid=0x40030000] ti.sdo.ce.ipc.Processor: [+E] Processor_create>

Enter(imageName='ti814x.xe674', memMap='(null)', attrs=0xbe8c3ba4)

[t=0x000f8fda] [tid=0x40030000] ti.sdo.ce.ipc.Processor: [+E] doCmd> Enter (cmdI

d=1, proc=0x13a760)

[t=0x000f9054] [tid=0x400c3490] ti.sdo.ce.ipc.Processor: [+X] getCmd_d> Exit (re

sult=1)

[t=0x000f9095] [tid=0x400c3490] ti.sdo.ce.ipc.Processor: [+E] Processor_create_d

> Enter(proc=0x13a760)

[t=0x000f90d9] [tid=0x400c3490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d

> Retrieving CPU ID for 'DSP'...

[t=0x000f9123] [tid=0x400c3490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d

> Opening DSP ProcMgr for cpuId 0...

[t=0x000f91c7] [tid=0x400c3490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d

> Attaching to DSP...

[t=0x000f94f5] [tid=0x400c3490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d

> Loading ti814x.xe674 on DSP (1 args)...

[t=0x0014eb58] [tid=0x400c3490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d

> calling Ipc_control(LOADCALLBACK)...

[t=0x0014ef82] [tid=0x400c3490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d

> Ipc_control(LOADCALLBACK) status: 0

[t=0x0014efe3] [tid=0x400c3490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d

> Starting DSP ...

 

http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/354/3704.config.bld1212.server.cfghttp://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/354/8713.Codec_5F00_engine_5F00_debug

Regards

Asheesh

  • Asheesh,

    From your trace, it looks like the app is hanging in the sylink start callback function.  It may be that something was left in a bad state after the first run.  Could you run the app with SysLink trace on?  You can do that by first insmod'ing syslink.ko with:

        insmod syslink.ko TRACE=1 TRACEFAILURE=1 TRACECLASS=3

    Thanks,

        Janet