This guide includes instructions and tips users should follow to get their DM365 Leopard Board to work with the RR Evaluation SDK.
For this guide different commands need to be executed on the host machine and the target. Commands to be run on the Ubuntu host have a yellow background. Commands to be run on the Ubuntu target have an aqua background.

Installation

The e-mail received with the evaluation SDK installation links should have:

The SVN repository link.

The toolchain download link.

An username and password in order to access the download link for the toolchain.

GNU Toolchain Installation

The LeopardBoard 365 Evaluation SDK uses the GNU toolchain for cross compilation. You need to download and install the toolchain before you can build the SDK.

Toolchain Download

The email you received when you requested the LeopardBoard 365 Evaluation SDK contained a link to the toolchain tarball, along with the user name and password to access the files available for download.

firefox http://support.ridgerun.com/leoparddm365sdk/downloads

I saved the toolchain to the default $HOME/Downloads directory.

Install Toolchain

Assuming the toolchain tarball is in the $HOME/Downloads directory, you can follow these steps to install the toolchain into the location expected by the SDK.

sudo tar -C / -xjf $HOME/Downloads/toolchain.tar.bz2

Verify your GNU toolchain is installed properly.

ls /opt/arm-linux-gnueabi/bin

and you should see around 35 tools in the directory.

Checkout SDK

With this SVN repository Linux from the email, check out a development directory from the repository:

mkdir -p ~/work
cd ~/work
svn co <repositoryLink> leo365

I put all my development directories in the work directory in my home folder. You can have more than one development directory installed, just remember to have the DEVDIR shell variable set properly.

Build SDK

Several packages are needed in order to compile the SDK. The SDK build process will let you know what packages are needed. While compiling you will be prompted to install them using sudo apt-get <packages>.

Configure the features you want to have in your board using:

make config

Set the PATH to include the toolchain and aslo set the DEVDIR shell variable

$(make env) # this is the same as using grave accents to execute the output from the command - `make env`

Compile the SDK:

make

Install bootloader, kernel, and target file system on LeopardBoard 365

Verify bootloader is active

First a minicom (or any other terminal emulator used) session must be opened in order to stop
the booting process at the bootloader prompt:

minicom

Reboot the board and stop the autoboot when

Hit any key to stop autoboot: ...

is displayed. Then close your minicom session.

Save bootloader to target hardware

The next step is to install the bootloader on the target. Typically you only install the SDK bootloader once.

Update target hardware with new images

Similar to the bootloader installation, to install the devdir on the target the booting process should be stopped at the bootloader prompt.

Updating your SDK

Since the SDK is in a SVN respository RidgeRun can periodically make updates to the contents. To have an up-to-date SDK the following command
must be executed on the SDK root directory

make update

If, for any reason, modifications to any files that are included in a patch were made, the make update process won't be able to finish successfully.
In order to override this the following command must be executed

make update FORCE_UP=1

Note that all changes previously made to these files will be lost.

Also, a debug functionality is implemented where all the executed commands will be displayed on the standard error (usually the same as standard output).
To activate it use

make update DEBUG_UP=1

Of course, a combination of both options can be used

make update FORCE_UP=1 DEBUG_UP=1

A brief help menu explaining these features can be displayed using

make help

SDK Hints

SD boot recover

If you brick your board, this can be recovered from an SD card. In order to make a bootable SD card you first need to have a successfully compiled SDK.

SD card preparation:

1. Insert the SD card to the host port

2. Find out the device mounting point (e.g. /dev/sdd)

3. On your devdir root directory type:

make sd_boot_recover device=/dev/sdX

where sdX is your device mounting point.

Install Boot recovery files on SD card

1. Remove SD card from host and reinsert the SD card into host. This will cause your host to mount the VFAT file system on the SD card.

2. Type

make install sd_boot_recover

3. Set switch 2 of DIPSW1 to ON, 1 and 3 to OFF. This is SD card boot mode.

When you use the SDK to set your video output and resolution, the SDK build process creates $DEVDIR/images/cmdline with different kernel command line parameter settings. The table below shows the various video output settings for three of the common settings

Video Output

DVI

Component

Composite

Resolution

720P-60

720P-60

NTSC

davinci_enc_mngr.ch0_output

DVI

COMPOSITE

COMPONENT

davinci_enc_mngr.ch0_mode

720P-60

720P-60

NTSC

davinci_display.cont2_bufsize

6291456

6291456

3145728

vpfe_capture.cont_bufoffset

6291456

6291456

3145728

vpfe_capture.cont_bufsize

6291456

6291456

6291456

Activation of video capture modules

While configuring the SDK go to Kernel configuration->Device drivers->Multimedia support->Video capture adapters and activate the devices you desire.

Video initialization

When you boot your board the RidgeRun logo will be displayed, in order to display video the following commands must be executed:

loadmodules.sh
fbset -disable

Component output initialization

There's a known bug with the component output initialization. Before you play or capture video using the component output this commands must be executed on the target:

You need to install the toolchain, follow the instructions Install here.

Unable to find the dvsdk

Error:

echo "Unable to find the file $DVSDK_DIR/Rules.make. Aborting" ; exit 1 ; \
fi \
fi
You need to install dvsdk_3_10_00_19 provided by Texas Instruments
You can abort now and install the dvsdk_3_10_00_19 binary package on the default path
at /home/work/dvsdk/dvsdk_3_10_00_19, so it will be automatically detected next time you try to build.
Otherwise you can enter the location where you installed the package below.
Please provide the path to dvsdk_3_10_00_19 installation location or press ctrl-c to abort