problem with video_copy example

jayakrishnan said:

The components selected during the interactive process is for both GPP & DSP, right?

Also , I remember,  I  read  somewhere that the matching components for both sides will  be selected automatically. (correct me , if wrong)

Can anyone clear me?

Also, how will  you select the components for a particular  application?

yes, you are correct that the conponents selected during the iterative process is for both GPP & DSP.  However, as you noted, there are two sides to DSPLINK.  On the ARM side, you will get a dsplink.ko Linux Kernel module which is typically loaded via loadmodules.sh script; on the DSP side, you will get a DSPLINK library which will be included in the final DSP image (normally with x64P extension).  As you may guess, if the version of DSPLINK included in your DSP image ( also known as DSP executable, DSP server, or codec engine server...) is not the same as the one loaded on your ARM, you are likely to get errors. 

Any particular reason why you are rebuilding DSPLINK?  If you are using all software from a single DVSDK, then your codec engine video copy example should work with the pre-built dsplinkk.ko included with the DVSDK.

Juan,

Thanks a lot for the reply.

I have decided to rebuild DSPlink when the video_copy application failed to execute, with the following errors.

App->Application started.

Version mismatch between GPP and DSP-side

GPP-side Version  [1.50]:

DSP-side version  [1.40.05_p3]:

I am using all  the  components  from dvsdk_2_10  and  CE  version is  codec_engine_2_10_01.

From the  error message it is to be  understood  that the DSP server is built  with dsplink version 1.40.05_p3. But when I checked  the  server package, it was built with the  dsplink version 1.50

(DSPLink according  to  xdcpaths.mak is dsplink_1_50)

Then why is the error  message  shows that the  dsplink used on DSP-side  is dsplink_1_40.05_p3?

Regards

Jayakrishnan

Juan,

Just an addition  to  my  previous reply....

I have  gone  through  the  following  wiki article

http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues

Problem: PROC_start failed with DSP_EVERSION error

Symptom: PROC_start failed with DSP_EVERSION error
Possible cause: The version of DSPLink used for building GPP-side and DSP-side is different. This is possible if GPP and DSP-sides are being built on different machines, or pre-built libraries are being shared directly. The version mismatch error also prints out information of the GPP and DSP-side versions found.

I could  not follow  this. I  understand  that DSP Link building procedure is the same  for both GPP and DSP and  it is  done simultaneously. (Using  the  interacive configuration)

Pls clarify

Regards

Jayakrishnan

Based on your last two posts, I would speculate that the DSP server included in this DVSDK may not have been re-built with the latest software components that are part of this DVSDK.  I believe DVSDK 2.10 is still an EA (Early Adoptor) release and has not been officially released thru our software update site (www.ti.com/davincisoftwareupdates ).  I have not played too much with it myself, but if the error is true, then the entire DSP image needs to be rebuilt to match the DVSDK software components, not only dsplink.

I want to highlight one misunderstanding on my part.  DVSDK 2.10 appears to be for DM365 only, it has not been tested for DM644X.  I was getting it confused with 2.00.01.15 wich is an EA release for DM644X (and other platforms).  I apologize for the confusion.

That said, please do not use DVSDK 2.10 w/ DM6446.

Jayakrishnan,

This is great news!  Thank you for sharing the solution back with the community.