problem about run Codec_Engine 3.22.01.06 examples

Hello xavier,

I'm trying to understand if you followed all the instructions in the build_instructions.html.

For instance:-

In your xdcpaths.mak what do you set for "DEVICES" environment variable:-

#
#DEVICE := OMAP3530 OMAPL138 OMAP4430 C6472 C6474 TI816X TI814X TI813X
DEVICE :=

Did you set your codegen and dependency tool locations in this same file ?

From the first error you get, it seems like it is not being able to access the sysbios libraries. Can you double check the permission on the directories etc and make sure this lib is accessible ?

From the other undefined symbols, it seems like it is unable to access the CE and FC installations as well. Can you confirm if you set all these paths in xdcpaths.mak ? (Maybe you can share a copy of that file here).

Gunjan.

Hi Gunjan,

thank you for your replay.

i have found  the answer. I develop on dm8168,It it the problem that I set the ti.target.C674 by mistake.

Now I changed the codegen tools setting with ti.target.elf.C674 instead. Then everything is OK.

but i still have some questions as I'm newbie to CE. Could  you give me some help ?

1. i found there lots of version of codec engine ,and other dependent components,

is there any limitation each codec engine has to use specified version dependent components then?

2. In ccs5.2.1 i found no codec engine include except some dependent components,

then if i want to build the codec engine example, i have to download codec engine together with all dependent components or i can use dependent components in ccs?

3.i see the instruction in codec engine packet, cgtools are used to build,

what is the different between using ccs and cgtools, is that cgtools is include in CCS5 ?

if so can it be updated with new versions in ccs5.1?

4. How to debug image process alg using ccs, as dsp has no video input?

first start arm -> load dsp progamme frome ccs->start linux app->debug?

best regards

xavier

Xavier,

If you have no other dependencies, then I would recommend you use the latest (and greatest) version of CE that supports your device. In your case that would be

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ce/3_23_00_07/index_FDS.html

In general, it is a good idea to install the versions of all the dependencies mentioned in the release notes. 

Codec Engine examples do not necessarily require CCS for building. After installing Codec Engine, you can navigate to the build instructions (also linked via the release notes) and see how to build the examples.

CGTools are just code generation tools that you will need to build/link your application. Typically CCS has these tools installed and when you build your Codec Engine example or applications you can simply point to the these.

If you have a pre-built application that you'd like to debug via CCS, you can look at some instructions here:- http://processors.wiki.ti.com/index.php/Debugging_the_DSP_side_of_a_CE_application_using_CCS

General information about using CCS :-

http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5

Gunjan.

Hi, Gunjan:

Thank you for your replay!

I have build the example code success, and i want to run the demo,

followed the build_instructions.html, i want to run the example,

i do not find universal_copy_local_.xv5T,only app_local.xe674 is found,

i also read the naming conventions in Codec Engine FAQ ,

• v5T - ARM v5 Thumb (GCC toolchain)
• e674 - C674 ELF
• em3 - ARM M3 ELF

it seems that the example is build as a dsp local run programm,

could you tell me how to set cfg for generate  xv5T file or xe674 file, i do not kown how to configure this,

i only  set follow params in xdcpaths.mak and products.mak

# Note, this is a space-delimited list.
PROGRAMS := APP_CLIENT DSP_SERVER APP_LOCAL

#
# Note, this is a space-delimited list.
#
#DEVICE := OMAP3530 OMAPL138 OMAP4430 C6472 C6474 TI816X TI814X TI813X
DEVICE := TI816X

best regards

xavier

Hi Xavier,

Since you are using Codec Engine 3.22.00.06, you will not have an executable named "universal_copy_local.xv5T".  That is for the newer
versions of Codec Engine (such as 3.23) that come with self contained examples.  It looks like you are following the right steps for building
the examples in CE 3.22.00.06.  Since you are not getting the Arm side executable built, maybe you don't have the path to the Arm code
gen tools set up in your products.mak file.  Here is how I set the CGTOOLS_V5T in my products.make file:

# Note that GCC targets are 'special' and require more than one var to be set.
#
# The CGTOOLS_* var points at the base of the toolchain.
# The CC_* var points at the gcc binary (e.g. bin/arm-none-linux-gnueabi-gcc)
#
CGTOOLS_V5T ?= $(VENDORS)/cs/arm/arm-2007q3
CC_V5T      ?= bin/arm-none-linux-gnueabi-gcc

Yours would be different, of course, since your Arm tools would be in a different location.

Then when you build, you should have an app_local.xv5T, app_remote.xv5T, app_local.xe674 in ti/sdo/ce/examples/apps/universal_copy/bin/ti_platforms_evmTI816X.

Best regards,

    Janet

Hi Janet:

you are right, i use CE 3.22.00.06, i just want  to use same software packages with dvrrdk 2.80 software packages for eg xdc ,

i set my the path to Arm code gen tools in follow way

# Note, the *_V5T vars are for Linux GCC tools, the *_BNC are for Android
CGTOOLS_V5T ?=
CC_V5T      ?= ${HOME}/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-gcc

CGTOOLS_BNC ?=
CC_BNC      ?=
LIBCDIR_BNC ?=
FSDIR_BNC   ?=

i search the whole example folder ,only one xv5t file was found , others are xe674files,

Should i only have to set the CC_V5T? no other configure then ?

best regards

xavier

Xavier,

Could you try changing your v5T tool variables to the following:

CGTOOLS_V5T ?= ${HOME}/CodeSourcery/Sourcery_G++_Lite
CC_V5T      ?= bin/arm-none-linux-gnueabi-gcc

I think because you don't have CGTOOLS_V5T set, the v5T programs will not be built (even if your CC_V5T is set to the full
path to the tools).  Other variables in products.mak depend on CGTOOLS_V5T, so if it is not set, the variable
gnu.targets.arm.GCArmv5T will not be set either, causing GCArmv5T targets not to be built.

Best regards,

    Janet

Hi all, 

I am working on DM8148 RDK 3.5

I also want to use Codec Engine for Audio Decode AAC, so I  have to compile Codec Engine for ARM (not for DSP or M3). Every body can approach me to resolve this issue. 

By the way anybody explain for me about some lines in products.mak (below)  and how to modify correct them. 

# Set location of various cgtools
ti.targets.C64P ?=
ti.targets.C674 ?=

ti.targets.elf.C64P ?=
ti.targets.elf.C64T ?=
ti.targets.elf.C66 ?=
ti.targets.elf.C674 ?=

ti.targets.arm.elf.M3 ?=

In my case I just need Codec Engine for  decoding Audio Decode AAC on ARM, So I don't need care about that, right?

Thanks!

quyendv

Hi quyendv,

Those variables in the products.mak file can be set to the toolchain locations.  If you are not building for a particular target, then you should leave the variable blank.  Since you are only building for ARM, and not the DSP or M3, you don't need to set any of the variables above.  However, you may need to set the path for your ARM GCC toolchain.  For example:

# Note that GCC targets are 'special' and require more than one var to be set.
#
# The CGTOOLS_* var points at the base of the toolchain.
# The CC_* var points at the gcc binary (e.g. bin/arm-none-linux-gnueabi-gcc)
#
CGTOOLS_V5T = $(VENDORS)/cs/arm/arm-2007q3
CC_V5T      = bin/arm-none-linux-gnueabi-gcc

Also, what version of Cocec Engine are you using?

Best regards,

    Janet

Hi Janet, 

Thanks for your response!

The version of Codec Engine : 3_22_01_06

I also set path for my ARM GCC toolchan like below

# The CGTOOLS_* var points at the base of the toolchain.
# The CC_* var points at the gcc binary (e.g. bin/arm-none-linux-gnueabi-gcc)
#

CGTOOLS_V5T ?= $(DEPOT)/linux_devkit

CC_V5T ?=bin/arm-arago-linux-gnueabi-gcc

But I still got some errors:

.........

#
# configuring bin/ti_platforms_evmTI814X/app_remote.xv5T from package/cfg/bin/ti_platforms_evmTI814X/app_remote_pv5T.cfg ...
/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdctools_3_24_03_33/xs -Dxdc.path="/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/examples/ti/sdo/ce/examples/apps/speech/../../../../../..;/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdctools_3_24_03_33/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdais_7_23_00_06/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/bios_6_33_05_46/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/linuxutils_3_23_00_01/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/syslink_2_20_02_20/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/osal_1_22_01_09/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/framework_components_3_22_03_09/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/edma3_lld_02_11_06_01/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/ipc_1_24_03_32/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdctools_3_24_03_33/packages;../../../../../.." -Dxdc.root=/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdctools_3_24_03_33 -Dxdc.hostOS=Linux -Dconfig.importPath=".;/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/examples/ti/sdo/ce/examples/apps/speech/../../../../../..;/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdctools_3_24_03_33/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdais_7_23_00_06/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/bios_6_33_05_46/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/linuxutils_3_23_00_01/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/syslink_2_20_02_20/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/osal_1_22_01_09/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/framework_components_3_22_03_09/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/edma3_lld_02_11_06_01/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/ipc_1_24_03_32/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/packages;/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdctools_3_24_03_33/packages;../../../../../..;/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdctools_3_24_03_33;/root/workdir/dm8127_35Board_ver2.2/ti_tools/xdctools_3_24_03_33/etc" -Dxdc.bld.targets="" -DTOOLS= xdc.cfg bin/ti_platforms_evmTI814X/app_remote.xv5T package/cfg/bin/ti_platforms_evmTI814X/app_remote_pv5T.cfg package/cfg/bin/ti_platforms_evmTI814X/app_remote_pv5T
js: "/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/packages/ti/sdo/ce/Engine.xs", line 262: Error: Server info file '/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/examples/ti/sdo/ce/examples/servers/all_codecs//package/info/bin/ti_platforms_evmTI814X/all_DSP.xe674.info.js' does not exist; specified serverExecutable='bin/ti_platforms_evmTI814X/all_DSP.xe674', serverPackage='ti.sdo.ce.examples.servers.all_codecs'; verify that your Server package has been properly built and released.
"/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/packages/ti/sdo/ce/Engine.xs", line 275
"/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/examples/ti/sdo/ce/examples/buildutils/remote.cfg", line 108
"./package/cfg/bin/ti_platforms_evmTI814X/app_remote_pv5T.cfg", line 216
"./package/cfg/bin/ti_platforms_evmTI814X/app_remote_pv5T.cfg", line 295
"./package/cfg/bin/ti_platforms_evmTI814X/app_remote_pv5T.cfg", line 203
gmake[1]: *** [package/cfg/bin/ti_platforms_evmTI814X/app_remote_pv5T.xdl] Error 1
gmake: *** [/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/examples/ti/sdo/ce/examples/apps/speech,.dlls] Error 2
make[2]: *** [all] Error 2
make[2]: Leaving directory `/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/examples/ti/sdo/ce/examples/apps/speech'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/examples/ti/sdo/ce/examples/apps'
make: *** [apps] Error 2

.......

From your error log, it looks like you are building a remote Codec Engine app for the ARM, that is expecting a server, all_DSP.xe674, running on the DSP:

262: Error: Server info file '/root/workdir/dm8127_35Board_ver2.2/ti_tools/codec_engine_3_22_01_06/examples/ti/sdo/ce/examples/servers/all_codecs//package/info/bin/ti_platforms_evmTI814X/all_DSP.xe674.info.js' does not exist; specified serverExecutable='bin/ti_platforms_evmTI814X/all_DSP.xe674',

Is this what you intended to do?  If so, it looks like your server has not been built.  If you want to just build local codec engine examples for the ARM, you should also modify the xdcpaths.mak file located at the root of the examples directory, and change the variable

PROGRAMS := APP_CLIENT DSP_SERVER APP_LOCAL

to

PROGRAMS := APP_LOCAL

Then try building the examples.

Best regards,

    Janet

Thanks Janet so much!

It compiled successfully.