Getting Started Guide for DM6446 EVM

From RidgeRun Developer Connection

Revision as of 20:42, 13 October 2011 by Dchaverri (Talk | contribs)
Jump to:navigation, search

Contents

Introduction

On this page you are going to find all the necessary information to start from scratch to use the RidgeRun SDK on your DM6446 evaluation module (EVM). In the following sections we assume that you have already downloaded the DVSDK version 4.01.00.09 for OMAP3X processor (this version is compatible with the DM6446) and that you have installed the toolchain 2009q1-203 from codesourcery as well as your DM6446 SDK following the steps on The RidgeRun installation guide.

Supported drivers

RidgeRun SDK's kernel has support for the following list of drivers for the DM6446 processor:

Basic preliminary work

Installing the DVSDK

1.   Set the DVSDK binary as executable and set the required permissions.

     sudo chmod 777 dvsdk_omap3530-evm_4_01_00_09_setuplinux

2.   Install the DVSDK. For ubuntu versions different than Ubuntu 10.04 LTS 32-bit you will need to add the --forcehost argument to install it:

     ./dvsdk_omap3530-evm_4_01_00_09_setuplinux --forcehost

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/

Setting up serial access to the Linux console

You use the serial port to control u-boot and Linux. The picocom terminal emulator work well for this purpose.

Setting up Picocom - Ubuntu

Setting up a TFTP server

If you are planning to use the SDK's installer to install images generated by the SDK in NAND, installing a TFTP server you will speed up downloads to the target hardware by using TFTP.

Setting Up A Tftp Service

Setting up an NFS server

For application development, it is convenient to use root NFS mount file system for the target hardware. This allows you to rebuild your application on the host and immediately run the application on the target hardware with no interveining steps. You host PC needs to be configured as a NFS server for this in order to work properly.

Setting Up A NFS Service

Recovery procedure

It is possible that during u-boot / UBL related tasks your board's bootloader becomes corrupted ( likely due to a write / erase operation of the address where u-boot / UBL is stored in NAND / NOR ). In such case, it is necessary to use the TI's Flash Utilities provided with your DM6446 SDK. It is assumed that you have already build the development directory by issuing a "make" command from the root of the directory.

1.  Turn OFF your board. Set the DM6446 EVM into UART boot mode by configuring the S3 dip switch as shown in Fig.1 (S3-1 and S3-2, ON position).

DM6446EVM BOOTMODE.JPG
Figure 1. DM6446 EVM UART boot mode configuration

2.   Proceed to load the binary image of u-boot into RAM, this task is accomplished by using the Serial Loader tool (slh) TI Flash Utility. The Serial Loader executable is located under the path shown below (please notice that the remaining recovery procedure commands will be given assuming that the user is located in this path).

$(DEVDIR)/bootloader/u-boot-2010.12-rc2-psp03.01.01.39/ti-flash-utils/src/DM644x/GNU$

3.   Turn ON your board and open your serial console, verify that you get a sequence of "BOOTME" messages on screen (This means that the board is currently in UART boot mode).

4.   Close the serial console.

5.   Issue the following command:

  
./slh_DM644x.exe -load2DDR ../../../../src/u-boot.bin -startAddr 0x82000000 -loadAddr 0x82000000 -v

note: The startAddr and loadAddr parameters have the same value and should match the U-boot RAM address specified under the Bootloader Configuration SDK menu.

       

Navigation
Toolbox