It still looks like you're building a DSP-side executable/server. "configuring service.x64P" - a *.x64P is a DSP-side server.
Maybe sending the entire build log would help. When you say you only have server.x64P, do you mean "service.x64P"? Is your ARM-side cfg script using Engine.createFromServer()? If so, you'll need the Server _package_, not just the .x64P file. The Server package has details buried in it (like DSP-side memory map, codecs in the server and their names, etc.) that the ARM-side's Engine.createFromServer() will need. Chris > -----Original Message----- > From: Jaya krishnan [mailto:[email protected]] > Sent: Tuesday, June 09, 2009 9:51 PM > To: Ring, Chris; [email protected] > Subject: Re: ARM application build issue > > > Hi Chris, > > Thank you for the suggestion. > My application is ARM side only, but as you mentioned > the app.cfg file was wrongly configured as > osalGlobal.runtimeEnv = osalGlobal.DSPLINK_BIOS; So I > changed it to > osalGlobal.runtimeEnv = osalGlobal.DSPLINK_LINUX; > But now the following error occurs > > .............................................................. > ............................... > .............................................................. > ................................ > configuring service.x64P from package/cfg/service_x64P.cfg ... > OSAL-> Warning: DSKT2 NOT CONFIGURED BY THE APPLICATION! > Using default segment ('null') for all IALG segments > ti.xdais.dm.examples.stwenc1.close() ... > ti.sdo.ce.osal.close() ... > ti.sdo.ce.osal.validate() ... > prog.build.platform is undefined > will link with core:null > will link with ti.sdo.ce.video1:lib/viddec1.a64P;lib/videnc1.a64P > will link with ti.sdo.ce:lib/ce.a64P > will link with ti.sdo.ce.alg:lib/Algorithm_BIOS.a64P > js: > "/home/jayan/devel/dm6446/dvsdk_2_00/codec_engine_2_00/package > s/ti/sdo/ce/osal/package.xs", line 365: exception from > uncaught JavaScript throw: Error: ti.sdo.ce.osal does not > support target ti.targets.C64P with Global.runtimeEnv set to > 4 (lib lib/osal_dsplink_linux.a64P not found) > > "/home/jayan/devel/dm6446/dvsdk_2_00/xdc_3_00_02/packages/xdc/ > cfg/Main.xs", line 27 > > "/home/jayan/devel/dm6446/dvsdk_2_00/xdc_3_00_02/packages/xdc/ > cfg/Main.xs", line 173 > > "/home/jayan/devel/dm6446/dvsdk_2_00/xdc_3_00_02/packages/xdc/ > xs.js", line 144 > gmake[1]: *** [package/cfg/service_x64P.xdl] Error 1 > gmake[1]: *** Deleting file `package/cfg/service_x64P.xdl' > gmake[1]: *** [package/cfg/service_x64P.xdl] Deleting file > `package/cfg/service_x64P.h' > gmake[1]: *** [package/cfg/service_x64P.xdl] Deleting file > `package/cfg/service_x64P.c' > gmake: *** [/home/jayan/nftf.src/src/core,.executables] Error 2 > make: *** [all] Error 2 > > I have access to server.x64P only, but no server package. > Regards > Jayakrishnan > > > > ------- Original Message ------- > Sender : Ring, Chris<[email protected]> > Date : Jun 10, 2009 01:36 (GMT+09:00) > Title : RE: ARM application build issue > > You mention you're building an ARM application, but the > build looks like it's building a DSP-side server. > > If you _are_ building an ARM app, it's wrong that the > ti.sdo.ce.osal.bios package is coming into the picture at > all. You might double check that your ARM-side app's > config script is configuring the OSAL correctly. For a > multicore device like DM6467, it should be something like: > > ============================= > /* > * Example .cfg snippet for ARM-side Linux app with remote algs > * (OSAL = Linux, IPC = Link) > */ > var osalGlobal = xdc.useModule('ti.sdo.ce.osal.Global'); > osalGlobal.runtimeEnv = osalGlobal.DSPLINK_LINUX; > ============================= > > http://tiexpressdsp.com/index.php?title=CE_Config_Updates# Configuration_the_Operating_System_adaption_layer_.28OSAL.29> _and_Inter_Processor_Communication_.28IPC.29_layer > > Chris > > > -----Original Message----- > > From: > > [email protected] > p.com [mailto:davinci-linux-open-source-> > [email protected]] On Behalf Of Jaya krishnan > > Sent: Tuesday, June 09, 2009 2:56 AM > > To: [email protected] > > Subject: ARM application build issue > > > > > > Hi, > > > > I get the following errors while building my ARM application > > > > Initially I used codec_engine_2_10_00_08 > > Later I changed to codec_engine_2_10_02. but still the > > problem persists. > > Any clues? > > > > > > -------------------------------------------------------------- > > --------------- > > -------------------------------------------------------------- > > ------------- > > configuring service.x64P from package/cfg/service_x64P.cfg ... > > ti.xdais.dm.examples.stwenc1.close() ... > > js: > > "/home/jayan/devel/dm6467/dvsdk_2_10_00_08/codec_engine_2_10_0 > 2/packages/ti/sdo/ce/osal/bios/package.xs", line 25: > exception > from uncaught JavaScript throw: TypeError: Cannot > call method > > "instances" of undefined > > (/home/jayan/devel/dm6467/dvsdk_2_10_00_08/codec_engine_2_10_0 > 2/packages/ti/sdo/ce/osal/bios/package.xs#25) > > > > "/home/jayan/devel/dm6467/dvsdk_2_10_00_08/xdc_3_00/packages/x > dc/cfg/Main.xs", line 248 > > > > "/home/jayan/devel/dm6467/dvsdk_2_10_00_08/xdc_3_00/packages/x > dc/cfg/Main.xs", line 154 > > > > "/home/jayan/devel/dm6467/dvsdk_2_10_00_08/xdc_3_00/packages/x > dc/xs.js", line 137 > > gmake[1]: *** [package/cfg/service_x64P.xdl] Error 1 > > gmake: *** [/home/jayan/nftf.src/src/core,.executables] Error 2 > > make: *** [all] Error 2 > > > > Regards > > Jayakrishnan > > > > _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
