DM8148开发记录 二

一个有用的解决不能找到 remote_copy_DSP  问题

examples speech1_copy and universal_copy from codec engine on EZSDK 5_02_02_60 for TI816x is not running

This question is answered

Posted by Gabi Gvili on Nov 24 2011 02:14 AM

Genius 3625 points

Hi TI experts,

 

I have followed the instructions in the document "Build/Run Instructions for Codec Engine Examples" attached to the codec engine.
After successfully building all the examples, servers etc.. i tried to run the examples speech_copy1 and universal_copy using remote server DSP according to the instructions.
The examples are not running, i recieve the following error message:

root@arago:~/codec_engine/speech1_copy#   ./app_remote.xv5T -p DSP -s xe674     

[t=0x0000192d] [tid=0x400f1000] xdc.runtime.Main: [+2] main> Welcome to app's main().

[t=0x00001ee8] [tid=0x400f1000] xdc.runtime.Main: [+1] App-> Application started, procId DSP engineName remote_copy_DSP input-file ./in.dat out.

./app_remote.xv5T: error: can't open engine remote_copy_DSP

[t=0x00002d64] [tid=0x400f1000] xdc.runtime.Main: [+1] app done.

 

Can anyone please help with this?

 

Thanks,
Gabi 

Codec Engine

Report Abuse

Reply

• Posted by wendelin klimann on Nov 24 2011 08:21 AM Verified Answer Verified by Gabi Gvili

  

  Prodigy 225 points

  Hy

   

  Try to run the

  root@arago:~/codec_engine/speech1_copy#   ./app_remote.xv5T -p DSP -s xe674    

   

  with CE_DEBUG=3 and make a .log file of the debug messages like:

  root@arago:~/codec_engine/speech1_copy#  CE_DEBUG=3  ./app_remote.xv5T -p DSP -s xe674 | tee FILENAME.log

  and post the .log file

   

  Regards

  Wendelin

     

  Report Abuse

  Reply

• Posted by Gabi Gvili on Nov 27 2011 10:08 AM Verified Answer Verified by Gabi Gvili

  

  Genius 3625 points

  Hi Wendelin,

  After running with CE_DEBUG=3 i saw that the DSP executable name should be all_DSP.xe674, the DSP executable file was created in a different name so i renamed it to all_DSP.xe674 and now the target stucks.

  Please see attached file. 

  6758.err1.log

   

  Thanks,
  Gabi 

  Report Abuse

  Reply

• Posted by janet on Nov 28 2011 11:52 AM Verified Answer Verified by Gabi Gvili

  

  Expert 4615 points

  Gabi,

  From your trace, it looks like SysLink's Ipc_control(LOADCALLBACK...) failed:

  [t=0x00150c73] [tid=0x400Assertion at Line no: 301 in /home/gabi/z3-DM8168/z3-netra-RPS-20111017/ezsdk/component-sources/syslink_2_00_02_80/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/Linux/IpcDrv.c: (status >= 0) : failed
  22490] ti.sdo.ce.ipc.Processor: [+E] Processor_create_d> Enter(proc=0xd8af0)
  [t=0x00150ca5] [tid=0x40022490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d> Retrieving CPU ID for 'DSP'...
  [t=0x00150cdd] [tid=0x40022490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d> Opening DSP ProcMgr for cpuId 0...
  [t=0x00150d5a] [tid=0x40022490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d> Attaching to DSP...
  [t=0x00151825] [tid=0x40022490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d> Loading all_DSP.xe674 on DSP (1 args)...
  [t=0x00172c6d] [tid=0x40022490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d> calling Ipc_control(LOADCALLBACK)...
  [t=0x00178845] [tid=0x40022490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d> Ipc_control(LOADCALLBACK) status: -1
  [t=0x001788a1] [tid=0x40022490] ti.sdo.ce.ipc.Processor: [+2] Processor_create_d> Starting DSP ...

  But, unfortunately, this trace doesn't indicate why the failure is occurring.  Could you please try enabling SysLink trace?  You can do this as follows:

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

  This will hopefully give us an idea as to why Ipc_control() is failing.

  Best regards,

      Janet

   

   

  Report Abuse

  Reply

• Posted by Gabi Gvili on Dec 01 2011 05:36 AM Verified Answer Verified by Gabi Gvili

  

  Genius 3625 points

  Janet,

  I have followed your instructions, attached please see log file.

  6082.err.log

  Thanks,
  Gabi

  Report Abuse

  Reply

• Posted by janet on Dec 01 2011 12:40 PM Verified Answer Verified by Gabi Gvili

  

  Expert 4615 points

  Gabi,

  According to your log, the symbol _Ipc_ResetVector could not be found:

  t=0x00153713] [tElfLoader_getSymbolAddress: symName [_Ipc_ResetVector]
  
  id=0x400f4000] t*** Loader_getSymbolAddress: Failed to get the symbol address!

  Could you check the map file for all_DSP.xe674 (in servers/all_codecs/package/cfg/bin/ti_platforms_evmTI816X), and verify that the symbol _Ipc_ResetVector exists?  Also could you provide a log without CE_DEBUG=3, so that just the SysLink trace is shown.  The Codec Engine trace is interspersed with the SysLink trace, making it harder to read, and I'd like to compare your trace with mine.

  Thanks,

      Janet

  Report Abuse

  Reply

• Posted by Gabi Gvili on Dec 04 2011 03:07 AM Verified Answer Verified by Gabi Gvili

  

  Genius 3625 points

  Hi Janet,

  _Ipc_ResetVector exists in the file all_DSP.xe674.map please see atached file.

  7433.all_DSP.xe674.map.txt
  

  Also i have attached log file without CE_DEBUG=3.

  3286.err.txt
  

  Thanks,
  Gabi 

  Codec Engine

  Report Abuse

  Reply

• Posted by janet on Dec 05 2011 14:46 PM Verified Answer Verified by Gabi Gvili

  

  Expert 4615 points

  Gabi,

  According to your map file, it looks like the DSP entry point is at the address 0x995d7800:

      ENTRY POINT SYMBOL: "ti_sysbios_family_c64p_Hwi0"  address: 995d7800

  But the error log indicates the address 0x8b033100 for the entry point:

      DLOAD: ELF file header entry point: 8b033100

  So it looks like the map file you sent does not correspond to the map file of the DSP executable that SysLink is attempting to load.

  Could you please check again for the correct map file?

  Best regards,

      Janet

   

  Report Abuse

  Reply

• Posted by Gabi Gvili on Dec 06 2011 07:15 AM Verified Answer Verified by Gabi Gvili

  

  Genius 3625 points

  Hi Janet,

  The example is working OK now, thankyou very much for your help, your answer helped me to find the correct DSP executable file, which its name is all_DSP.xe674 and it is found in

  ezsdk_xx_xx_xx/component-sources/codec_engine_xx_xx_xx/examples/ti/sdo/ce/examples/servers/all_codecs/bin/ti_platforms_evmTI816X/ 

  and not what i was doing mistakenly which was to take the DSP executable named app_local.xe674 from where the executables were created for the example speech1_copy and rename it to all_DSP.xe674. 

  Thanks,
  Gabi