Rebuilding DVSDK target: gives compilation error in Blend.c linux/dm6467/Blend.c (1.40 Dvsdk for 6467)

Jawa,

In a post you made yesterday you were referring to DVSDK 2.0 and in this post you are referring to DVSDK 1.40.  Please note that you cannot mix and match components from one DVSDK version with other components from another DVSDK version.  There was a huge jump between DVSDK 1.40 (based on MV Pro 4.0 w/ linux kernel 2.6.10) and DVSDK 2.0 (based on MV Pro 5 w/ Linux kernel 2.6.18).  In conclusion, you need to install all the software components (including Linux kernel) from the same DVSDK release to ensure compatibility.  If you follow the GSG, it should take you thru the steps necessary to install all the required software components for a particular DVSDK release.  FYI, I have personally used DVSDK 1.40 in the past and am currently using DVSDK 2.0.

Juan,

Thanks for your response. Here is the scenario:

a) I have never installed DVSDK 2.0 at all. In my earlier post I was  asking specifically about all the updates  that go together in order to exactly avoid such a mix and match(before I do the switch to 2.0). I have a few questions open on that especially about not finding any update for:

mvl######_demo_target_setuplinux.bin
and
xdc_setuplinux####.bin
(even though I do see an "xdctools_setuplinux####.bin"

b) I have only DVSDK 1.40 installed.  and that is the one which is giving me the Blend.c error.  I wanted to give the system a test drive with basic stuff before i do any update to DVSDK.

===============================================

Given the above scenario and the fact that I am getting the compilation error asking for an include, do you have any suggestions ?
Thanks,

Jawa

did DVSDK 1.40 actually include dmai software component; I do not think dmai existed when DVSDK 1.40 came out, but I could be wrong.  The missing header files do appear in MV Pro 5 kernel included in DVSDK 2.0

Jawa Vythee said:

a) I have never installed DVSDK 2.0 at all. In my earlier post I was  asking specifically about all the updates  that go together in order to exactly avoid such a mix and match(before I do the switch to 2.0). I have a few questions open on that especially about not finding any update for:

mvl######_demo_target_setuplinux.bin
and
xdc_setuplinux####.bin
(even though I do see an "xdctools_setuplinux####.bin"

With regards to DVSDK 2.0, its GSG (spruf88e.pdf) refers to xdctools_setuplinux####.bin because this is the name of the binary in this particular release. (http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/S1SDKLNX/DVSDK_2_00/index_FDS.html)

With regards to DVSDK 1.40, its GSG (spruf88c.pdf) refers to xdc_setuplinux####.bin because this is the name of the binary in this particular release (http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/dvsdk/mv_dvsdk/v1_40/index.html)

GSGs do evolve with the software so please make sure you are using the GGS which corresponds to the DVSDK software.

Got it. Thanks.

Now, I am going through the process of getting the dm6467 codecs for 2_00####.

It is some officlal looking form which says it will mail me a link in 48 hours. 

Juan,

Would you know why this download insists on a company name and a url and a 24-48 hour delay for downloads ? What if I dont have  company and url ?

Would I need this version or will the DVSDK2.0 work with the version I got for the above programs with the 1.40 ?

Thanks,

Jawa

you would need this version.  If you do not have a company URL, I would contact www.ti.com/support to see if they may be able to enter your request manually.

I got the same question as yours. You just need to compile the monta vista linux kernel to solve the problem:

    make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm646x_defconfig

    make ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage