Getting Started Guide for DM8168 EVM: Difference between revisions

From RidgeRun Developer Wiki
No edit summary
No edit summary
Line 6: Line 6:


On the rest of this document, we refer as $(DEVDIR) to the path where the RidgeRun SDK for DM8168 is installed
On the rest of this document, we refer as $(DEVDIR) to the path where the RidgeRun SDK for DM8168 is installed
= Basic preliminary work =
== Installing the EZSDK ==
# Set the ezsdk binary as executable and set correct permissions
<pre style="background:#d6e4f1">
sudo chmod 777 ezsdk_dm816x-evm_5_02_02_60_setuplinux
</pre>
# Install EZSDK. For ubuntu versions different than Ubuntu 10.04 LTS 32-bit you will need to add the --force-host argument to install it:
<pre style="background:#d6e4f1">
./ezsdk_dm816x-evm_5_02_02_60_setuplinux --force-host
</pre>
'''note:''' During the EZSDK installation process you will be asked for the toolchain's path, assuming that you installed it on /opt, the path that you need to provide is /opt/codesourcery/arm-2009q1/bin/


= Installation =
= Installation =

Revision as of 16:01, 4 October 2011

Page Under Construction

Introduction

On this page you are going to find all the necessary information to start from scratch to use the RidgeRun SDK on your DM8168 evaluation module (EVM). In the following sections we assume that you have already downloaded the EZSDK version 5.02.02.60 and that you have installed the toolchain toolchain 2009q1-203 from codesourcery.

The first section of this guide shows you how to install the EZSDK for DM8168 on your computer and how to configure a TFTP and NFS server. Subsequently, the second section contains instructions about how to configure the RidgeRun's SDK to create a SD with all software components (uboot, kernel and filesystem) needed to boot to Linux Shell in your EVM. Using this SD in the third and fourth section of this guide, you will be able to install on NAND images created by the SDK for kernel, uboot as well as your filesystem (JFFS2, UBI, NFS are available). Using the SD created on the second section to flash the SDK in your EVM is just an option because you could try to use the installer of the RidgeRun's SDK with the uboot version that is running by default in a new EVM, however, we cannot guaranty that it will work as we expect, hence, we recommend to use the SD instead. Finally, how to run opemax demos to encode and decode 1080p/h264 videos and some pipelines using gstreamer + openMax are shown.

On the rest of this document, we refer as $(DEVDIR) to the path where the RidgeRun SDK for DM8168 is installed

Basic preliminary work

Installing the EZSDK

  1. Set the ezsdk binary as executable and set correct permissions
 sudo chmod 777 ezsdk_dm816x-evm_5_02_02_60_setuplinux
  1. Install EZSDK. For ubuntu versions different than Ubuntu 10.04 LTS 32-bit you will need to add the --force-host argument to install it:
 ./ezsdk_dm816x-evm_5_02_02_60_setuplinux --force-host

note: During the EZSDK installation process you will be asked for the toolchain's path, assuming that you installed it on /opt, the path that you need to provide is /opt/codesourcery/arm-2009q1/bin/

Installation

In order to install your DM8168 EVM SDK 2011Q2 you can follow the steps described in the installation section of the RidgeRun 2011Q2 SDK User Guide.

Video initialization

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

echo 0 > /sys/devices/platform/vpss/graphics0/enabled 
echo 0 > /sys/devices/platform/vpss/graphics1/enabled
echo 0 > /sys/devices/platform/vpss/graphics2/enabled

Using Gstreamer

Some examples of use of GStreamer to implement basic multimedia pipelines can be found at DM81xx GStreamer Pipelines - SDK 2011Q2