Rebuilding the DVSDK Software for the Target

Mahesh,

Our DVSDK is tested together as a whole; we do not test DVSDK against external packages as it would be impossible to predict and grab all that the open source community puts out there.  You can think of DVSDK as a tested distro; if you go out and grab other individual components and try to place them into an existing DVSDK, it is assumed that you have enough familiarity with the software to know what you are doing and that you are testing this modified distro.  If these external components are from TI website, we normally include release notes with our software components that specify compatibility requirements; if you grab this from non-TI Website, then we have less control over that software package.

That said, I see references to kernel 2.6.26 when our current DVSDK is based on 2.6.18.  What package are you updating and from where did you get it?  Do you really need to make this upgrade considering it has not been tested as part of DVSDK?  Are you doing your due diligence to test this modified DVSDK to ensure it is stable( Just something to think about)? 

Hi Juan,

I dowloaded form

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/S1SDKLNX/DVSDK_2_00/index_FDS.html

Mahesh,

I have installed this software and have been working with it for a while now; I am pretty certain that if you install software per the Getting Started Guide it should work.  In your previous message, I saw references to kernel 2.6.26, which seems odd.

If you continue to have problems, please send a listing of your DVSDK software components as installed in your system.  Also, please follow GSG in order, you cannot build to dvsdk tree without building linux kernel first

Hi Juan,

some Makefile problem in /dvsdk_2_00_00_22/linuxutils_2_23_01/packages/ti/sdo/linuxutils/cmem/src/module/Makefile

In Makefile Rules.mak is point different so made chnages according to my env...........

Now its working fine.

Thank you for giving your time.

Mahesh V Kalmeshwar

hi Juan,

I am intigarting "video copy program " i chnaged the codecs and copiled successfully..........

while compiling the dsp server am getting Error message likejs:

I worte some files and modified some file in dvsdk_2_00_00_22/codec_engine_2_23_01/packages/ti/sdo/ce/video

IVIDMPEG4DECODERConfig.xdc

 IVIDMPEG4DECODERConfig.xdt

vidmpeg4decoder_skel.c

vidmpeg4decoder_stub.c

vidmpeg4decoder.c

vidmpeg4decoder.h

_vidmpeg4decoder.h

package.xs

package.bld
package.xdc

while compiling the dsp server am getting Error message like:

XDCPATH="/media/hda2/home/mahesh/dvsdk_2_00_00_22/codec_engine_2_23_01/examples/ti/sdo/ce/examples/servers/Mpeg4_Lnt_decoder/evmDM6446/../../../../../../..;/media/hda2/home/mahesh/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;/media/hda2/home/mahesh/dvsdk_2_00_00_22/xdais_6_23/packages;/media/hda2/home/mahesh/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages;/media/hda2/home/mahesh/dvsdk_2_00_00_22/linuxutils_2_23_01/packages;/media/hda2/home/mahesh/dvsdk_2_00_00_22/framework_components_2_23_01/packages;/media/hda2/home/mahesh/dvsdk_2_00_00_22/biosutils_1_01_00/packages;/media/hda2/home/mahesh/dvsdk_2_00_00_22/bios_5_33_03/packages" /media/hda2/home/mahesh/dvsdk_2_00_00_22/xdctools_3_10_03/xs xdc.tools.configuro -c /media/hda2/home/mahesh/dvsdk_2_00_00_22/cg6x_6_0_21 -o Mpeg4_Lnt_decoder \
                -t ti.targets.C64P -p ti.platforms.evmDM6446 -b /media/hda2/home/mahesh/dvsdk_2_00_00_22/codec_engine_2_23_01/examples/ti/sdo/ce/examples/servers/Mpeg4_Lnt_decoder/evmDM6446/../../../../../../../config.bld \
                --tcf Mpeg4_Lnt_decoder.cfg
making package.mak (because of package.bld) ...
config.bld: Running the version from Codec Engine Examples.
config.bld: loading user build configuration file /media/hda2/home/mahesh/dvsdk_2_00_00_22/codec_engine_2_23_01/examples/user.bld
generating interfaces for package Mpeg4_Lnt_decoder (because package/package.xdc.inc is older than package.xdc) ...
configuring Mpeg4_Lnt_decoder.x64P from package/cfg/Mpeg4_Lnt_decoder_x64P.cfg ...
platform   = ti.platforms.evmDM6446
js: "/media/hda2/home/mahesh/dvsdk_2_00_00_22/xdctools_3_10_03/packages/xdc/xdc.tci", line 296: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: /media/hda2/home/mahesh/dvsdk_2_00_00_22/codec_engine_2_23_01/examples/ti/sdo/ce/examples/codecs/Mpeg4_Lnt_decoder/package.xdc found along the package path, but no schema file was found.  Ensure that the package 'ti.sdo.ce.examples.codecs.Mpeg4_Lnt_decoder' is completely built.
    "/media/hda2/home/mahesh/dvsdk_2_00_00_22/codec_engine_2_23_01/examples/ti/sdo/ce/examples/servers/Mpeg4_Lnt_decoder/evmDM6446/Mpeg4_Lnt_decoder.cfg", line 59
    "./package/cfg/Mpeg4_Lnt_decoder_x64P.cfg", line 758
    "./package/cfg/Mpeg4_Lnt_decoder_x64P.cfg", line 717
gmake: *** [package/cfg/Mpeg4_Lnt_decoder_x64P.c] Error 1
gmake: *** [package/cfg/Mpeg4_Lnt_decoder_x64P.c] Deleting file `package/cfg/Mpeg4_Lnt_decoder_x64Pcfg.cmd'
gmake: *** [package/cfg/Mpeg4_Lnt_decoder_x64P.c] Deleting file `package/cfg/Mpeg4_Lnt_decoder_x64Pcfg_c.c'
gmake: *** [package/cfg/Mpeg4_Lnt_decoder_x64P.c] Deleting file `package/cfg/Mpeg4_Lnt_decoder_x64Pcfg.s62'
js: "/media/hda2/home/mahesh/dvsdk_2_00_00_22/xdctools_3_10_03/packages/xdc/tools/Cmdr.xs", line 40: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake: *** [Mpeg4_Lnt_decoder/linker.cmd] Error 1

Thankyou

Mahesh

Mahesh,

Unfortunately, this is outside my area of expertise.  I know we have a couple of tools to help build codec and dsp servers (http://wiki.davincidsp.com/index.php/RTSC_Codec_And_Server_Package_Wizards), but cannot say I am very familiar with the process.  I will see if I can get someone to help answer your question.

mahesh kalmeshwar said:

js: "/media/hda2/home/mahesh/dvsdk_2_00_00_22/xdctools_3_10_03/packages/xdc/xdc.tci", line 296: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: /media/hda2/home/mahesh/dvsdk_2_00_00_22/codec_engine_2_23_01/examples/ti/sdo/ce/examples/codecs/Mpeg4_Lnt_decoder/package.xdc found along the package path, but no schema file was found.  Ensure that the package 'ti.sdo.ce.examples.codecs.Mpeg4_Lnt_decoder' is completely built.

This error condition is described here - http://rtsc.eclipse.org/docs-tip/XDCtools_Error_Codes#xdc.PACKAGE_NOT_FOUND

As the error describes, ensure your 'ti.sdo.ce.examples.codecs.Mpeg4_Lnt_decoder' _package_ is built using the XDC tools.  This step creates a package/ subdirectory with lots of metadata about your codec that's used during server integration (e.g. name, type, stack needs, IALG_Fxns, etc).  If you're basing your codec on the example codecs, this just means you need to run 'make' in the package directory - which will run xdc to generate the package/ directory.

Finally, be sure to review some of the documentation/tools available to codec producers described here:  http://tiexpressdsp.com/index.php/Codec_Engine_Roles#Algorithm_Creator

Chris

HI Chris,

now am getting Error like: can't resolve name.

js: "/media/hda2/home/mahesh/dvsdk_2_00_00_22/xdctools_3_10_03/include/utils.tci", line 748: xdc.services.spec.SessionRuntimeException: ti.sdo.ce.examples.codecs.Mpeg4_Lnt_decoder: can't resolve name ti.sdo.ce.video.IVIDMPEG4DECODER.serverFxns

Thanyou

Mahesh V Kalmeshwar

Mahesh,

I suspect this means that there are two versions of the ti.sdo.ce.video.IVIDMPEG4DECODER module in play -- one that has the serverFxns config param, and one that does not (for example, an older one). This error message means that the ti.sdo.ce.examples.codecs.Mpeg4_Lnt_decoder module was built against a version of IVIDMPEG4DECODER that had serverFxns, but the one currently on your package path does not.

Jon

hello everyone,

I am using  dm355,  MV4 & DVSDK_1_30_00_40.

I followed GSG & make appropriate changes in Rules.make file

but when I do "make" I got following error...I have tried reinstalling the whole dvsdk also.

***************************************************************************************************************************

.

.

.

======== Building decode ========
Configuring application using decode.cfg

XDCPATH="../g711;/home/digant/dvsdk_1_30_00_40/dm355_codecs_1_12_000/packages;/home/digant/dvsdk_1_30_00_40/codec_engine_2_00_01/packages;/home/digant/dvsdk_1_30_00_40/dsplink_140-05p1/packages;/home/digant/dvsdk_1_30_00_40/xdais_6_00_01/packages;/home/digant/dvsdk_1_30_00_40/cmem_2_00_01/packages;/home/digant/dvsdk_1_30_00_40/framework_components_2_00_01/packages" /home/digant/dvsdk_1_30_00_40/xdc_3_00_02/xs xdc.tools.configuro -c /opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le -o decode_config -t gnu.targets.MVArm9 -p ti.platforms.evmDM6446 decode.cfg
/bin/sh: /home/digant/dvsdk_1_30_00_40/xdc_3_00_02/xs: No such file or directory
make[2]: *** [decode_config] Error 127
make[2]: Leaving directory `/home/digant/dvsdk_1_30_00_40/demos/dm355/decode'
make[1]: *** [decode] Error 2
make[1]: Leaving directory `/home/digant/dvsdk_1_30_00_40/demos/dm355'
make: *** [demos/dm355] Error 2
root@digant-desktop:/home/digant/dvsdk_1_30_00_40#

***********************************************************************************************************************

PLZ help

Sorry , I  just didn't modify the XDC install path.....

I did it successfully.:)

Hello everyone,

I have also upgraded to dvsdk_2 _00_00_22 which is working fine. I have developed my DSP algorithm using IUNIVERSAL in the Codec Engine 2.23. I would like to test my algorithm / codec using the dvsdk_demos_2_00_00_07 which came with dvsdk_2 _00_00_22 package.

How can I modify the encodedecode demo to capture and display RAW VIDEO only? (without  encode/decoding the video)

Can you please tell me step by step on which files to modify?

Many thanks for your help.

Zoe

zoe said:

Can you please tell me step by step on which files to modify?

Zoe, unfortunately we do not have the resources to provide this level of detail.  The demos should not be too complicated to modify, but I am listing some hints below to help you get started.

1 ) remove calls to all engine APIs (CERuntime_init, Engine_open, Engine_close)

2) remove calls to VISA APIs (e.g. Venc1_xxx where xxx can be open, create, process and delete; similarly for Vdec2 )

FYI, VISA stands for Video, Image, Speech and Audio )the four classes of codecs we normally include).  Depending on the demo you are using, you may have video only or also some of the other types.  In the encodedecode case, we have video represented by Venc1 (video encode API version 1) and Vdec2 (video decode API version 2); normally all VISA APIs have four key functions (open, create, process, delete).

I hope this helps.

Hi Zoe,

Its bettre to follow video copy program and modify according to your requirement.

I followed the same thing and I am able to intigrate my own video-decoder and display on TV.

Regards.

Mahesh V  Kalmeshwar.

Hi Juan

    Can DVSDK be compiled for a linux 2.6.29 kernel?when can we expect DVSDK to integrated with the Android Kernel?

Thanks & Regards

Ananth

Ananth,

We are moving in this direction but we are not there yet.  What platform are you wirking with (DM6446?).  At present, what is provided and supported but our DVSDK 2.0 is kernel 2.6.18; we are porting all our drivers to open source GIT tree so that in the future we can take baselines from open source tree, test and release correspondingly.  When we get there, you will likely see more stability in our open source GIT tree; at present, we are in the porting process with some platforms being ported before others... hence you may experience some incompatibilities in GIT at the moment.  For this reason, we are not recommending customers move to GIT yet, but rather stick to DVSDK released kernel.

Hi Juan

    Thanks for your kind reply.I am working on an OMAP3530 eVM board running Android Kernel on top of it.Since integration of DVSDK with Android Kernel is in progress so it means that we cannot make use of DVSDK for writing applications that can communicate with DSP.Juan could you kindly give us an high level picture of how DVSDK interacts with the linux kernel for communicating with the DSP.I read the Getting Started Guide pdf but i could'nt get a clear notion of how DVSDK interaction takes place with the DSP.

Thanks & Regards

Ananth

I missed the part about Android in you previous message.  Depending on which hardware platform you are using, we have several Android projects. See http://wiki.davincidsp.com/index.php/Android

That said, I am not too familiar with Adroid or the various projects.  However, from a DVSDK persepctive the way Cortex-A8 (ARM) communicates with DSP is via dsplink.ko kernel module.  This module is exercised by our codec engine framework underneath the scenes, which is probrably why do not see much about it.  When you build your engine, you specify if the algorithms included in your engine or local to the ARM or remote and the framework takes care of the rest.  If you want to learn more about our codec engine framework or DSPLINK, you can find many great wiki articles at http://wiki.davincidsp.com/index.php/Main_Page