Getting Started with DaVinci

The links here are temporarily down, please check back on Tuesday, May 13.

Here are some good getting started links from a much older post:

DaVinci Technology Developers Wiki (great articles on DaVinci topics) -- http://wiki.davincidsp.com/index.php?title=Main_Page

Spectrum Digital Support Pages (low level hardware documentation on various Davinci EVM boards) -- http://support.spectrumdigital.com/

Linux Community for DaVinci Processors (open source software downloads) -- http://focus.ti.com/dsp/docs/dspsplash.tsp?contentId=3100

DaVinci Linux Open Source Mailing List -- http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

DaVinci Technology Page (links to device specific documentation) -- www.thedavincieffect.com

DaVinci EVM Registration Page (register your EVM and access software updates, applies to EVMs for DM6446, DM6437, DM648, DM355, and DM6467) -- www.ti.com/davinciregistration

If you have more useful links that could be added please make a post :)

EDIT: Adding in a link to the Davinci workshop which is now publicly posted on the Wiki - http://focus.ti.com/docs/training/catalog/events/event.jhtml?sku=4DW102644

A bit narrow, but very handy for sorting out uboot and bootargs: http://www.denx.de/wiki/DULG/Manual

DM6446 'encode' demo included in dvsdk should take input from a MIC and encoded in g.711; however, if you look at the demo source code, you have access to the audio buffer (stored in DDR2) and can choose to send it to g.711 encoder or write it to a file, ....

Linux DaVinci information catalog http://www.linux-davinci.info/

I can run encode, decode and interface demos. However, When I copy 'encodedecode' directory in the same folder renaming 'test1' and make changes to 'config' files  paths and 'make' file Istill get error like " make: *** No rule to make target `test1.cfg', needed by `test1_config/compiler.opt'.  Stop." What am I doing wrong?

some of the build scripts assume the same name as the directory for certain files (e.g. encodedecode_config, encodedecode.cfg), you will need to rename these as well.  What I normally do is copy the original demos into a different directory and make the original demo directory my working directory; this avoids many headaches such as the one you are running into.

Juan,

Thanks it worked out well! I tried both approaches

1. Renaming contents in the scripts and renaming the file names (there were several files and numerous script changes in replica of 'encodedecode' folder). Took me like 20 -25 minutes to do this. I wish I could get a good 'replace in files' program in Ubuntu (notepad++???). [:Y]

2. Easier approach of preserving demo's directory - 'acts like master / reference' directory. Then making replica directory 'working' directory without name/script content changes!

Juan,

Sorry, I am posting this question as a reply since I could not start a new thread.

I was trying to get started on building the DVSDK demo. The getting started guide that came with the kit (DM6467), mentions about editing the Rules.make file (in section 4.6 of the getting started guide) and modify certain env variables.e.g PLATFORM etc.

I found several of these already in place.

I found several discrepancies between what is stated on the guide and what is already there in this file.
for e.g. the guide says to point EXEC_DIR to "....."/$(platform)
but the rules.make already has en entry for this variable which does not end in the "$platform". Are we supposed to edit and add it at the end ?
Also a few other paths are different eg. the
LINUXKERNEL_INSTALL_DIR=/opt/mv_pro_4.0.1/montavista/pro/devkit/lsp/ti-davinci/linux-2.6.10_mvl401_LSP_01_30_00_082 in the rules.make
but the starting guide says it should be set to .... /<home/ useracct>/..... etc.

Is the starting guide (hard copy I got EVM) incorrect ?)

I also got the link
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_2_00/latest/index_FDS.html
 I am unsure as to what updates form here that I really need for a "basic" getting started and building the demos.

Any help/advice would be appreciated.

Thanks,

Jawa

start with this first

http://wiki.davincidsp.com/index.php/Before_the_Getting_Started_Guide

Then go to this page

http://tiexpressdsp.com/index.php/Category:Linux

Jawa,

The Rules.make that comes by default in DVSDK root directory has a few paths that are incorrect; this is why the GSG suggests you need to change some of them.  The real path that you need to put there depends on where you installed the software components, which means the directories pointed to by the paths need to exist.  The simplest way to ensure this is to follow the GSG steps; the GSG suggests where to install the various software components and if you followed those steps, then the suggestions made in section 4.6 should make sense.

One caveat, as DVSDKs evolve and new ones come out, so does the GSG.  Therefore, please make sure you use the GSG which corresponds to your DVSDK.  From the link you posted above

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_2_00/latest/index_FDS.html

you should be able to access the GSG for your platform directly; this GSG will tell you which of the various components you need to download and install from this site.

virgoptrex

I wish I could get a good 'replace in files' program in Ubuntu

add

myreplace()
{
        perl -i -pe "s[$1][$2]g"  `grep "$1" . -rl `
}

to your ~/.bashrc

and call it in from directory tree:

myreplace "old string" "new string"

also you my add options --exclude and --include to grep to filter files

Thanks Constantine,

For some reason this function doesn't seem to work. I tried other sample functions by adding them to .bashrc and they work! Is ' ` ' actually ' ' '?