Does the TMDXEVM3503 OMAP EVM include DVSDK?

 I tried to download DVSDK from the TI website. It seemed that the links to "OMAP 3530 DVSDK Top level Release Notes" and "OMAP 3530 DVSDK Beta 1 Software" are broken. Can someone@TI please fix them? Thanks.

This is something we found this morning, I believe the team who manages these files was alerted, unfortunately it may take some time to fix if it has not been already, particularly with the long weekend here.  

 I checked again today - hasn't been fixed yet. Thanks anyway for your info. I will try sending TI an email later.

You are correct, I followed up on this today and if I hear of any change in status I will make a post here, no need to email TI (at least support@ti.com) since that will come likely come through my team anyway.

Hi,

Is there further news on this lead? If not, is there any other way to download the package (dvsdk_setuplinux_3_00_00_13.bin)? Thx.

It is still down unfortunately, I will have to see if there is another way we can get it distributed, though that may be beyond my authority.

The download links should be working as of now (I just tried them and they appear to work for me). If you have further trouble with them let me know, thank you for your patience in retrieving these files.

horah... downloading now. Thanks a lot for your help.

Hi,

After unpacking the dvsdk that I downloaded from TI's site, it looked like that the prebuilt flash file system image (described in the getting started manual as <install_dir>/targetfs/...) is missing. I tried anther download and did untar getting the same result. Is the file image coming from other packages? Can I build the demos from the src? Thanks!

Assuming you are referencing DVSDK v1.0, the Getting Started Guide (SPRC655A - July 10, 2008) indicates the DVSDK contents in Section 1.4.  In the OMAP35x_SDK_1.0.0/bin directory you will find 4 pre-built filesystems.

nfs.tar.gz          : file system image for use with NFS
ramdisk-full.gz   : file system large ext2 ramdisk image with demos
ramdisk-min.gz  : file system minimal ext2 ramdisk image
rootfs.jffs2         : file system image for flash

Is this what you are referring to?

I just installed the dvsdk_setuplinix_3_00_00_13.bin file available in our software update site (www.ti.com/omapsoftwareupdates ) and can see the files underneath dvsdk_3_00_00_12/targetfs directory as suggested by the GSG.  Also, I agree with Brandon that the files under OMAP35x_SDK_1.0.0/bin are also probably a file system as well (maybe the same one).

Anyway, the files appear to be there in the DVSDK install.

The EVM I got was shipped with 3503 linux package (0.9.7). I would like to try out the new packages to see arm+dsp working, likely by firstly trying the demos (audio/video codecs).

I am refering to the OMAP35x DVEVM Getting Started Guide (SPRUFZ7, Aug. 2008), e.g., on page 16. in a textbox in the middle,

it's been mentioned that "If you already have a OMAP35x EVM with U-boot, kernel image and NAND flash file
system, make sure you update the kernel and NAND flash file system images, in the
NAND flash with the prebuilt kernel image available under the
OMAP35x_SDK_#.#.#/bin/OMAP35x folder on your Windows PC and prebuilt NAND
flash file system image available under the
/home/<useracct>/dvsdk_#_##_##_##/targetfs folder on your Linux PC. " this /home/<useracct>/dvesdk.../targetfs is the installation directory of  the dvsdk_setuplinux_#_##_##_##.bin from the download link TI has fixed. There're a few other places where the manual referred to this location as the file system image that contained the new demos (video/audio codecs). I didn't find that .../targetfs/... after I installed the download bin file.

I assume the file system image has all the demos software. Please correct me if I miss something there.

Thanks!

Hi Juan,

Thanks for your reply. I downloaded again from TI site the install file "dvsdk_setuplinux_3_00_00_13.bin" (size 445098100). I changed it to -x and executed it as a normal use, suggested in the GSG. After that, I got the following in my installation dir.

fc4:temp-dvsdk-install> ls dvsdk_3_00_00_13/
codec_engine_2_20_00_15  framework_components_2_20_00_15
data                     linuxlibs
dmai_1_20_00_00          Makefile
docs                     omap3530_3_00_00_13_release_notes.html
dsplink_1.51.00.08       Rules.make
dvsdk_demos_3_00_00_03   uninstall
dvtb_3_00_007

I didnt see a targetfs directory there, though I haven't gone to each of the sub-directories to look side.

Anyone has some HINTS???

BTW, Juan, I just noticed in your post that you mentioned "underneath dvsdk_3_00_00_12/targetfs", are you refering to 3.00.00.12 Version (as the version I downloaded is 3.00.00.13)?

strange, our bin files seem to be the same size (445098100), yet I get the following listing when I type ls:

armtoolchain
dvsdk_3_00_00_13
dvsdk_setuplinux_3_00_00_13.bin
dvsdk.txt
OMAP35x_SDK_1_0_0
codec_engine_2_20_00_15
data
dmai_1_20_00_00
docs
dsplink_1.51.00.08
dvsdk_demos_3_00_00_03
dvtb_3_00_007
framework_components_2_20_00_15
linuxlibs
linuxutils_2_20_00_05
local_power_manager_1_20_00_12
Makefile
omap3530_3_00_00_13_release_notes.html
omap3530_dvsdk_combos_3_11
quilt
Rules.make
targetfs
ti
uninstall
xdais_6_20_00_07

it seems like I get many more directories than you do.  I am downloading the bin file via my Windows machine and copying it over to my Linux Host, but I do not believe this should make a difference.

I just untarred the nfs.tar.gz file and it appears the demos are there.

If we are all getting the file from the same software update site and the files are the same size, can we compare Host OSes; which one are you using?  Also, are you sure there is enough free disk space available in your host OS?

I just checked the MD5sum of the file I downloaded - it showed the same key as listed here https://www-a.ti.com/extranet/cm/product/omapsw/dspswext/download/md5sum.list for ./dvsdk_setuplinux_3_00_00_13.bin

Space is no problem here - I am using a fedora core 4 Linux OS. I also downloaded the install file in Windows and copied the file to linux thru samba.

In case it matters, I am installing the bin as a normal user (not root).

I know the GSG suggests you do this as user, but can you try installing this as root (that is what I did); this may help expose permission problems.

OK, this has been solved on trying out on another OS - I did exactly the same thing on a Scientific Linux 5 box. And it gave me the following list in the installation dir, yes, targetfs is there! :)

---------

codec_engine_2_20_00_15
data
dmai_1_20_00_00
docs
dsplink_1.51.00.08
dvsdk_demos_3_00_00_03
dvtb_3_00_007
framework_components_2_20_00_15
linuxlibs
linuxutils_2_20_00_05
local_power_manager_1_20_00_12
Makefile
omap3530_3_00_00_13_release_notes.html
omap3530_dvsdk_combos_3_11
quilt
Rules.make
targetfs
ti
uninstall
xdais_6_20_00_07

-------------------

I compared the list to the one you posted earlier - your list has 5 extra in the beginning. but I guess they are not from this installtion part from the bin file, right?

Since we are on the topic of OS, I have another question: are all the tools supporting TI OMAP 35x EVM fine to run on 64bit OS (like SL5)?

Thanks a lot for the help!

Please disregard the first 5 listed at the beginning.  Also, my host OS is a 32-bit RHEL4, hence I do not believe that this issue is related to 64-bit vs 32-bit OSes.  I was hoping this was a 'root' vs 'user' permission related issue.  Did you try running the bin file as root before switching OSes?

I tested again - it doesn't seem to be a problem with root or normal user. It seemed to be a machine-specific problem that I was getting the wrong result from a vmware-linux, which I might have done something wrong with the user permissions. Anyways, I got the correct installation on a normal linux host. Thanks all the efforts from this forum on the problem! I appreicate.

We are glad we could help; please let us know if there is anything else we can assist you with.