Digital Media Processors based on DaVinci™ Technology

Re: Where to Obtain Latest Tool Releases?

HyperGalaxy — Mon, 02 Feb 2009 23:12:34 GMT

Chris,

Here is the output with CE_DEBUG set to 1 (minimum):

Encode demo started.
@0,989,420us: [+6 T:0x4001ee50] CE - Engine_init> CE debugging on (CE_DEBUG=1; allowed CE_DEBUG levels: 1=min, 2=good, 3
=max)
TraceUtil_start> note: CE_DEBUG env. var is set, so TraceUtil is not active (unset CE_DEBUG if you need TraceUtil)
i2c_davinci i2c_davinci.1: controller timed out
@21,517,306us: [+7 T:0x40aeb490] OP - Processor_create_d> Loading and starting DSP server './encodeCombo.x64P' FAILED, s
tatus=[0x80008017] (look for error code 'DSP_EBASE + 0x17' in dsplink*/packages/dsplink/gpp/inc/usr/errbase.h)
@21,517,672us: [+6 T:0x40aeb490] OP - Processor_delete_d> Closing remote transport FAILED, status=0x80008000.
@21,517,885us: [+6 T:0x40aeb490] OP - Processor_delete_d> Stopping DSP FAILED, status=0x80008000
VIDIOC_QUERYSTD failed on /dev/video0. Video input connected?
@21,535,388us: [+6 T:0x42ce6490] CE - rserverOpen: can't start './encodeCombo.x64P'; Processor_create failed
Encode Error: Failed to open codec engine encode
@42,007,771us: [+7 T:0x40aeb490] OP - Processor_create_d> Loading and starting DSP server './encodeCombo.x64P' FAILED, s
tatus=[0x80008017] (look for error code 'DSP_EBASE + 0x17' in dsplink*/packages/dsplink/gpp/inc/usr/errbase.h)
@42,008,101us: [+6 T:0x40aeb490] OP - Processor_delete_d> Closing remote transport FAILED, status=0x80008000.
@42,008,314us: [+6 T:0x40aeb490] OP - Processor_delete_d> Stopping DSP FAILED, status=0x80008000
@42,018,726us: [+6 T:0x4001ee50] CE - rserverOpen: can't start './encodeCombo.x64P'; Processor_create failed
Encode Error: Failed to open codec engine encode

I still have no clue about how to circumvent this, but I would guess that it is DSP Link related from the output.

Do you have any ideas about what is causing this and how to resolve it?

Have a great day!

Take care,

Darwin

Re: Where to Obtain Latest Tool Releases?

Chris Ring — Mon, 02 Feb 2009 21:12:11 GMT

HyperGalaxy:

That looks fine, but here is what happens when I exectue ./encode -v out.mpeg4:

Encode demo started.
TraceUtil> Error: Failed to open codec engine "encode"
TraceUtil> Error: Aborting TraceUtil_start
i2c_davinci i2c_davinci.1: controller timed out
Encode Error: Failed to open codec engine encode
Capturing 720x480 video (cropped to 720x480)
Encode Error: Failed to open codec engine encode

Not sure what this is, but often you can gain more insight into what's failing by setting CE_DEBUG=1 (or 2?) in the environment (http://wiki.davincidsp.com/index.php?title=CE_DEBUG) before running the ./encode app.

Chris

Re: Where to Obtain Latest Tool Releases?

HyperGalaxy — Mon, 02 Feb 2009 21:03:23 GMT

Thanks, Brad.

That solved the installation issue. However, now none of the example applications are working.

For example, here is what happens when I execute ./loadmodules.sh:

ioremap_nocache(0x87800000, 8388608)=0xc9000000
allocated heap buffer 0xc9000000 of size 0xf7000
cmem initialized 4 pools between 0x87800000 and 0x88000000
dsplinkk: no version for "struct_module" found: kernel tainted.
DSPLINK Module (1.60) created on Date: Oct 24 2008 Time: 12:59:07

That looks fine, but here is what happens when I exectue ./encode -v out.mpeg4:

Encode demo started.
TraceUtil> Error: Failed to open codec engine "encode"
TraceUtil> Error: Aborting TraceUtil_start
i2c_davinci i2c_davinci.1: controller timed out
Encode Error: Failed to open codec engine encode
Capturing 720x480 video (cropped to 720x480)
Encode Error: Failed to open codec engine encode

Here are the files that the DVSDK installs:

-rw-rw-rw- 1 500 500   23438 Feb 2 2009 cmemk.ko
drwxr-xr-x 4 500 500    4096 Feb 2 2009 data
-rwxr-xr-x 1 500 500 319978 Feb 2 2009 decode
-r--r--r-- 1 500 500    4898 Feb 2 2009 decode.txt
-rw-rw-rw- 1 500 500 3645541 Feb 2 2009 decodeCombo.x64P
-rw-rw-rw- 1 500 500 123356 Feb 2 2009 dsplinkk.ko
-rwxrwxr-x 1 500 500     384 Mar 20 2008 dvevmdemo
-rwxr-xr-x 1 500 500 317524 Feb 2 2009 encode
-r--r--r-- 1 500 500    5283 Feb 2 2009 encode.txt
-rw-rw-rw- 1 500 500 1863279 Feb 2 2009 encodeCombo.x64P
-rwxr-xr-x 1 500 500 312143 Feb 2 2009 encodedecode
-r--r--r-- 1 500 500    4504 Feb 2 2009 encodedecode.txt
-rwxr-xr-x 1 500 500   60693 Feb 2 2009 interface
-rwxrwxrwx 1 500 500     372 Feb 2 2009 loadmodules.sh
-rw-rw-rw- 1 500 500 2550902 Feb 2 2009 loopbackCombo.x64P
drwxr-xr-x 2 500 500    4096 Feb 2 2009 thirdpartydemos
drwxrwxr-x 3 500 500    4096 Nov 5 2008 web

Can you please tell me how to resolve this?

Have a great day!

Take care,

Darwin

Brad Griffis:

The DVSDK 1.30 Makefile has this:

@install -m 666 $(LINK_INSTALL_DIR)/packages/dsplink/gpp/BUILD/EXPORT/RELEASE/dsplinkk.ko $(EXEC_DIR)

Better change that to:

@install -m 666 $(CE_INSTALL_DIR)/cetools/packages/dsplink/gpp/export/BIN/Linux/DAVINCI/RELEASE/dsplinkk.ko $(EXEC_DIR)

Re: Where to Obtain Latest Tool Releases?

Brad Griffis — Fri, 30 Jan 2009 16:28:14 GMT

The DVSDK 1.30 Makefile has this:

@install -m 666 $(LINK_INSTALL_DIR)/packages/dsplink/gpp/BUILD/EXPORT/RELEASE/dsplinkk.ko $(EXEC_DIR)

Better change that to:

@install -m 666 $(CE_INSTALL_DIR)/cetools/packages/dsplink/gpp/export/BIN/Linux/DAVINCI/RELEASE/dsplinkk.ko $(EXEC_DIR)

Re: Where to Obtain Latest Tool Releases?

HyperGalaxy — Wed, 28 Jan 2009 20:51:56 GMT

Brad, Juan, etc.,

Okay, I finally finish the client task that I swapped in while waiting for your assistance with this issue and am back on this.

I took a step back and tried to rebuild DVSDK 1.30.01.41 with CE 2.21, etc. This time, I noticed the following error when trying to make install:

install: cannot stat `/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/BUILD/EXPORT/RELEASE/dsplinkk.ko': No such file or directory

Do you have any idea what is causing this? (I am just trying to use the pre-built version of DSP Link that came with CE 2.21.)

Here are the different dsplinkk.ko kernel modules that I found in CE 2.21:

/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/pack
ages/dsplink/gpp/export/BIN/Linux/DAVINCI/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/pack
ages/dsplink/gpp/export/BIN/Linux/DAVINCI/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/Linux/DAVINCIHD/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/Linux/DAVINCIHD/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/Linux/DM357/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/Linux/DM357/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/Linux/OMAP2530/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/Linux/OMAP2530/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/Linux/OMAP3530/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/Linux/OMAP3530/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/DAVINCI/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/DAVINCI/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/DAVINCIHD/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/DAVINCIHD/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/DM357/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/DM357/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/OMAP2530/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/OMAP2530/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/OMAP3530/DEBUG/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/dsplink/gpp/export/BIN/ucLinux/OMAP3530/RELEASE/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/ti/bios/power/modules/dm357/dsplink/dsplinkk.ko

/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/ti/bios/power/modules/dm6446/dsplink/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/ti/bios/power/modules/omap2530/dsplink/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/cetools/packages/ti/bios/power/modules/omap3530/dsplink/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/examples/apps/system_files/DM6446/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/examples/apps/system_files/DM6467/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/examples/apps/system_files/OMAP2530/dsplinkk.ko
/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_21/examples/apps/system_files/OMAP3530/dsplinkk.ko

Thus, it appears that the pre-built version of DSP Link that is include with CE 2.21 does not have the version of the kernel module that the build system expects.

Have a great day!

Take care,

Darwin

Re: Where to Obtain Latest Tool Releases?

Brad Griffis — Tue, 20 Jan 2009 20:09:31 GMT

HyperGalaxy:

Yes, we have no problems building the kernel, and that is not even the point at which we are stuck. Can you please read the entire post and then help us to resolve the issue that we are stuck at?

Darwin,

If you're manually creating links then you have not built your kernel correctly. You need to back up a step and figure out why that link is not already created. Did you correctly configure your kernel? Perhaps there's a permissions error causing the config step to not be able to create the links?

Re: Where to Obtain Latest Tool Releases?

HyperGalaxy — Tue, 20 Jan 2009 20:00:05 GMT

Thanks, Mugdha.

Yes, we have no problems building the kernel, and that is not even the point at which we are stuck. Can you please read the entire post and then help us to resolve the issue that we are stuck at?

Have a great day!

Take care,

Darwin

MugdhaK:

Darwin,

You shouldn't have to manually make up the links to arch-omap in your kernel distribution. When you are building DSPLink (since it is a kernel-module), you need to make sure that you kernel distribution has been setup for the target device. i.e. you need to ensure that all the soft links are already in place in your kernel distribution.

You can do a build of your Linux kernel distribution for the target device before building DSPLink to get rid of this error.

Regards,
Mugdha

Re: Where to Obtain Latest Tool Releases?

HyperGalaxy — Tue, 20 Jan 2009 19:58:24 GMT

Chris,

The signature that it gives when we try to load the module is an MV4 signature. So, I wonder what is going on...

Have a great day!

Take care,

Darwin

ChrisRing:

Quick correction, the pre-built version of DSP Link that comes with CE 2.21 was built against an MVPro 5 kernel:

> strings codec_engine_2_21/examples/apps/system_files/DM6446/dsplinkk.ko | grep vermagic
vermagic=2.6.18_pro500-davinci_evm-arm_v5t_le preempt mod_unload ARMv5 gcc-4.2

It's true that if your MV5 distro has been reconfigured or patched, you should rebuild DSP Link's .ko modules (as well as CMEM and all other modules), so the pre-built modules may not load into your kernel. But it _is_ built against an MV5 Pro distro.

Chris

Re: Where to Obtain Latest Tool Releases?

MugdhaK — Tue, 20 Jan 2009 06:30:52 GMT

Darwin,

You shouldn't have to manually make up the links to arch-omap in your kernel distribution. When you are building DSPLink (since it is a kernel-module), you need to make sure that you kernel distribution has been setup for the target device. i.e. you need to ensure that all the soft links are already in place in your kernel distribution.

You can do a build of your Linux kernel distribution for the target device before building DSPLink to get rid of this error.

Regards,
Mugdha

Re: Where to Obtain Latest Tool Releases?

Chris Ring — Tue, 20 Jan 2009 03:33:31 GMT

Quick correction, the pre-built version of DSP Link that comes with CE 2.21 was built against an MVPro 5 kernel:

> strings codec_engine_2_21/examples/apps/system_files/DM6446/dsplinkk.ko | grep vermagic
vermagic=2.6.18_pro500-davinci_evm-arm_v5t_le preempt mod_unload ARMv5 gcc-4.2

It's true that if your MV5 distro has been reconfigured or patched, you should rebuild DSP Link's .ko modules (as well as CMEM and all other modules), so the pre-built modules may not load into your kernel. But it _is_ built against an MV5 Pro distro.

Chris

Re: Where to Obtain Latest Tool Releases?

HyperGalaxy — Tue, 20 Jan 2009 02:19:51 GMT

Thanks, Juan.

Juan> May I ask what your end goal is in moving to MV Pro 5.0 and DSPLINK 1.61

Because the prebuilt version of DSP Link that comes with CE 2.21 does load into MV Pro 5. (It is compiled for MV 4. Thus, when we try to load the module into the kernel, the kernel balks.) So, we need to build DSP Link 1.61 from scratch, unless you have a prebuilt version. (The issues that we are faced with are discussed in my previous, long post, in this thread.)

Can you please look at the problem mentioned in that previous long post (in this thread) and let me know how to circumvent that?

Have a great night!

Take care,

Darwin

Re: Where to Obtain Latest Tool Releases?

Juan Gonzales — Mon, 19 Jan 2009 23:57:18 GMT

Hi Darwin,

This thread is getting a bit long, so forgive me if I missed this. May I ask what your end goal is in moving to MV Pro 5.0 and DSPLINK 1.61? Do you just want to run codec examples (e.g. video_copy??) in this new environment ? If so, you do not need to rebuild DSPLINK at all, simply download MV Pro 5 LSP, Codec Egine 2.21, and BIOS 5.33. I believe you have all of these already.

Also, I am told DVSDK 2.0 should be releasing in early Feb, and it should have all these components integrated in a full software release.

Re: Where to Obtain Latest Tool Releases?

Juan Gonzales — Mon, 19 Jan 2009 23:05:50 GMT

Darwin,

I aplogize if you had already mentioned which GNU version you were using; I could not find it anywhere in this thread. The GNU make version is one of the more common problems we encounter; therefore it was worth mentioning it for the benefit of all the community. Especially since I could not readily find references to GNU make v3.81 in this thread.

With regards to your other questions, I am afraid I do not have an answer for them at this time; otherwise I would gladly have posted them.

Re: Where to Obtain Latest Tool Releases?

HyperGalaxy — Mon, 19 Jan 2009 22:28:48 GMT

Juan,

Yes, we have been using GNU make V3.81 for quite some time, now. I was pretty clear in my post about the issue that we are facing. Can you please respond to the issue in my previous post. (I think that my post was quite explicit, but if you do not agree, then please ask for clarification, so that we can get this resolved within a reasonable period of time.)

Have a great day!

Take care,

Darwin

Re: Where to Obtain Latest Tool Releases?

Juan Gonzales — Mon, 19 Jan 2009 21:28:01 GMT

Are you using GNU make 3.81 as specified in the DSPLINK 1.61 release notes: https://www-a.ti.com/downloads/sds_support/targetcontent/link/link_1_60/link_1_61_00/LinuxLinkReleaseNotes.pdf ?