Hi: TI's engineer:
I just want to modify the codecs.viddec_copy's name "decgzj" instead of "viddec_copy"
so I modified all the string "viddec_copy" to "decgzj" in the file: VIDDEC_COPY.xdc VIDDEC_COPY.xs package.xdc and so on;
then I also modified the file name (DEC_GZJ.xdc DEC_GZJ.xs) instead of (VIDDEC_COPY.xdc and VIDDEC_COPY.xs)
then I modify the server's file video_copy.cfg just as :
var DEC_GZJ =
xdc.useModule('codecs.decgzj.DEC_GZJ');
........
Server.algs = [
{
name: "decgzj", // C name for the of codec
mod: DEC_GZJ, // var VIDDEC_COPY defined above
threadAttrs: {
stackMemId: 0, // BIOS MEM seg. ID for task's stack
priority: Server.MINPRI + 1 // task priority
},
groupId : 0, // scratch group ID (see DSKT2 below)
},
{
name: "videnc_copy",
mod: VIDENC_COPY,
threadAttrs: {
stackMemId: 0,
priority: Server.MINPRI + 1
},
groupId : 0,
},
];
======================================================================================================
it can be generated the decgzj.a64P when build the codecs.decgzj
but when I build the server it always error: >> error: symbol referencing errors - 'video_copy.x64P' not built
this is the all information:
[root@localhost video_copy]# make
XDCPATH="/home/gzj/my_video_copy/server/video_copy/../..;
/home/gzj/dvsdk_2_00_00_22/codec_engine_2_23_01/cetools/packages;
/home/gzj/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;
/home/gzj/dvsdk_2_00_00_22/bios_5_33_03/packages"
/home/gzj/xdctools_3_10_03/xs xdc.tools.configuro -c /home/gzj/dvsdk_2_00_00_22/cg6x_6_0_16 -o video_copy \
-t ti.targets.C64P -p ti.platforms.evmDM6446 -b /home/gzj/my_video_copy/server/video_copy/../../config.bld \
--tcf video_copy.cfg
configuring video_copy.x64P from package/cfg/video_copy_x64P.cfg ...
platform = ti.platforms.evmDM6446
codecs.videnc_copy.close() ...
ti.sdo.ce.ipc.bios.close(): loading dsplink.dsp
NOTE: You can find the complete server data sheet in ./package/info/video_copy.x64P.DataSheet.html
--------------------------------------------------------------------------------------------------
will link with codecs.decgzj:lib/decgzj.a64P
will link with codecs.videnc_copy:lib/videnc_copy_dma.a64P
will link with ti.sdo.ce.video:lib/release/video.a64P
will link with ti.sdo.ce.bioslog:lib/release/bioslog.a64P
will link with ti.sdo.ce:lib/release/ce.a64P
will link with ti.sdo.ce.alg:lib/release/Algorithm_BIOS.a64P
will link with ti.sdo.ce.ipc.bios:lib/release/ipc_bios.a64P
will link with ti.sdo.ce.osal.bios:lib/osal_bios.a64P
will link with ti.sdo.ce.osal.bios:lib/osal_bios_load.a64P
will link with ti.bios.utils:lib/utils.a64P
will link with ti.sdo.fc.acpy3:lib/release/acpy3.a64P
will link with ti.sdo.fc.memutils:lib/release/memutils.a64P
will link with ti.sdo.fc.dskt2:lib/release/dskt2.a64P
will link with ti.sdo.ce.utils.xdm:lib/release/XdmUtils.a64P
will link with ti.sdo.utils.trace:lib/release/gt.a64P
will link with ti.sdo.ce.node:lib/release/node.a64P
will link with ti.sdo.fc.dman3:lib/release/dman3Cfg.a64P
cl64P package/cfg/video_copy_x64P.c ...
asm64P package/cfg/video_copy_x64Pcfg.s62 ...
cl64P package/cfg/video_copy_x64Pcfg_c.c ...
XDCPATH="/home/gzj/my_video_copy/server/video_copy/../..;
/home/gzj/dvsdk_2_00_00_22/codec_engine_2_23_01/cetools/packages;
/home/gzj/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;
/home/gzj/dvsdk_2_00_00_22/bios_5_33_03/packages"
/home/gzj/xdctools_3_10_03/xs xdc.tools.configuro -c /home/gzj/dvsdk_2_00_00_22/cg6x_6_0_16 -o video_copy \
-t ti.targets.C64P -p ti.platforms.evmDM6446 -b
/home/gzj/my_video_copy/server/video_copy/../../config.bld \
--tcf video_copy.cfg
/home/gzj/dvsdk_2_00_00_22/cg6x_6_0_16/bin/lnk6x -o video_copy.x64P -c main.obj video_copy/linker.cmd
undefined first referenced
symbol in file
--------- ----------------
_VIDDECCOPY_TI_VIDDECCOPY /home/gzj/my_video_copy/server/video_copy/video_copy/package/cfg/video_copy_x64P.o64P
>> error: symbol referencing errors - 'video_copy.x64P' not built
make: *** [video_copy.x64P] Error 1
==================================================================================================================
who I can modify the video_copy!! thank you !!
(note : I can run the video_copy in DVEVM DM6446)