MCSDK OMAPL138 User Guide Getting Started

---

---

MCSDK User Guide for OMAP-L138: Getting Started with the MCSDK for OMAP-L138

Last updated: 12/18/2013

Overview

The Multicore Software Development Kit (MCSDK) provides foundational software for TI OMAP-L138 device platforms. It encapsulates a collection of software elements and tools intended to enable customer application development and migration.

This chapter provides information on installing the MCSDK, loading the EVM flash images via JTAG, and running the out-of-box demonstration application. It is expected the user has gone through the EVM Quick Start Guide provided with their EVM and have booted the out-of-box demonstration application flashed on the device.

By the end of this Getting Started chapter the user should have:

• Installed CCS
• Installed the MCSDK Software
• Update EVM flash with release images
• Executed the out-of-box demonstration application

Acronyms

The following acronyms are used throughout this chapter.

Acronym	Meaning
CCS	Texas Instruments Code Composer Studio
DHCP	Dynamic Host Configuration Protocol
DSP	Digital Signal Processor
EVM	Evaluation Module, hardware platform containing the Texas Instruments DSP
JTAG	Joint Test Action Group
MCSDK	Texas Instruments Multi-Core Software Development Kit
PDK	Texas Instruments Programmers Development Kit
TI	Texas Instruments

Supported Devices and Platforms

This release supports the following Texas Instrument devices:

Supported Devices	Supported EVM
OMAP-L138	OMAP-L138 LCDK

What's in this Kit?

The Multicore EVM kit Software DVD includes:

• Multicore Software Development Kit installer
• PDK installer
  
• cg_xml
• dsplib_c674x_<version>
• edma3_lld_<version>
• imglib_c64Px_<version>
• ipc_<version>
• mathlib_c694x_<version>
• syslink_<version>

Getting Started

Hardware Setup Guide

Follow instructions in the links below that correspond to the EVM that you are using.

• OMAP-L138 : Use L138/C6748_Development_Kit_(LCDK)

Installation

Installing Code Composer Studio

The MCSDK uses Code Composer Studio as the host tool for development and debug. Install the version of CCSv5 indicated in the MCSDK release notes; there is a link to it in the release notes itself. To install CCS, please refer to the instructions provided in the CCSv5 Getting Started Guide.

When installing CCS you can choose to control what is installed for processor architecture and components. The minimum required for MCSDK are

Processor Architecture option:

Component option:

Installing the Arago Toolchain

Untar the arago toolchain for ARMv5te (ARM9) (link to it is in the MCSDK release notes) to a Linux host PC. Add {tool chain install location}/arago-2011.09/armv5te/bin to the exported environment variable 'PATH'.

http://software-dl.ti.com/sdoemb/sdoemb_public_sw/arago_toolchain/2011_09/index_FDS.html

Installing the Multicore Software Development Kit

After installing CCS and arago toolchain, the next step is to install the MCSDK. See the Downloads chapter for information on how to get the latest version of this software. The release contents are delivered as installers. Some notes:

• To avoid manually updating file locations, it is recommended to install the MCSDK in the same directory as CCSv5
• For a Linux host, run the mcsdk_<build-id>_setuplinux.bin executable.
• For a Windows host, run the mcsdk_<build-id>_windows_setup.exe executable.
  
• Some of the components installed by CCS may be updated by the MCSDK installer (e.g., SYS/BIOS); see the MCSDK release notes for which installer each component is mapped to.
  

The pre-built binaries (u-boot, linux kernel, filesystem ...) are provided in the release under the folder mcsdk_linux_<version>.

The following is a more detailed listing of the contents of this folder:

release_folder
      mcsdk_<version>
      bin
      board-support
            linux-src (linux-x.x-psp<version>.sdk)
            uboot-src (u-boot--psp)
      docs
      filesystem
      host-tools
            aisgen
            OMAP-L138_FlashAndBootUtils_2.40
            pinmux_utils
      images 
      linux-devkit.sh
      setup.sh

Linux Host Setup

To set the development host for SDK, shell scripts are provided with mcsdk package.

The linux host side script is available at mcsdk_<version>\setup.sh . This top level script can be run which internally call the scripts from mcsdk_<version>\bin and set the different host settings for tftp,nfs,u-boot envirnment,linux-devkit etc.

some example host scripts console log is given below

x0089162@palin05:~/mcsdk_<version>$ sudo ./setup.sh
-------------------------------------------------------------------------------
TISDK setup script
This script will set up your development host for SDK development.
Parts of this script require administrator priviliges (sudo access).
-------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Verifying Linux host distribution
Ubuntu 10.04 LTS or Ubuntu 12.04 LTS is being used, continuing..
--------------------------------------------------------------------------------

Starting with Ubuntu 12.04 serial devices are only accessible by members of the 'dialout' group.
A user must be apart of this group to have the proper permissions to access a serial device.

Are you running this script using sudo? The detected username is 'root'.
Verify and enter your Linux username below
[ root ]

User 'root' is already apart of the 'dialout' group

-------------------------------------------------------------------------------
setup package script
This script will make sure you have the proper host support packages installed
This script requires administrator priviliges (sudo access) if packages are to be installed.
-------------------------------------------------------------------------------
System has required packages!
--------------------------------------------------------------------------------
Package verification and installation successfully completed
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
[ /home/x0089162/MCSDK/03-10-2013/mcsdk_1_01_00_02/targetNFS ]
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will extract the target filesystem to /home/x0089162/MCSDK/03-10-2013/mcsdk_1_01_00_02/targetNFS

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/x0089162/MCSDK/03-10-2013/mcsdk_1_01_00_02/targetNFS already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
[r] o
Old /home/x0089162/MCSDK/03-10-2013/mcsdk_1_01_00_02/targetNFS removed

Successfully extracted tisdk-rootfs-image-omapl138-lcdk.tar.gz to /home/x0089162/MCSDK/03-10-2013/mcsdk_1_01_00_02/targetNFS
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the SDK to install binaries in to:
    /home/x0089162/MCSDK/03-10-2013/mcsdk_1_01_00_02/targetNFS/home/root/omapl138-lcdk

The files will be available from /home/root/omapl138-lcdk on the target.

This setting can be changed later by editing Rules.make and changing the
EXEC_DIR or DESTDIR variable (depending on your SDK).

Press return to continue
Rules.make edited successfully..
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will export your target filesystem for NFS access.

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue

* Stopping NFS kernel daemon                                                                                       [ OK ]
* Unexporting directories for NFS kernel daemon...                                                                 [ OK ]
* Exporting directories for NFS kernel daemon...                                                                  

exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/home/a0132246/cl/target".
  Assuming default behaviour ('no_subtree_check').
  NOTE: this default has changed since nfs-utils version 1.0.x

                                                                                                                    [ OK ]
* Starting NFS kernel daemon                                                                                       [ OK ]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Which directory do you want to be your tftp root directory?(if this directory does not exist it will be created for you)
[ /tftpboot ]
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the tftp server in the /tftpboot directory.

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue

/tftpboot already exists, not creating..

/tftpboot/uImage-omapl138-lcdk.bin already exists. The existing installed file can be renamed and saved under the new name.
(r) rename (o) overwrite (s) skip copy
[r] o

Successfully overwritten uImage-omapl138-lcdk.bin in tftp root directory /tftpboot

/etc/xinetd.d/tftp already exists..
/tftpboot already exported for TFTP, skipping..

Restarting tftp server
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xinetd stop

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) utility, e.g. stop xinetd
xinetd stop/waiting
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xinetd start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start xinetd
xinetd start/running, process 18604
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------"
This step will set up minicom (serial communication application) for
SDK development

For boards that contain a USB-to-Serial converter on the board such as:
        * BeagleBone
        * AM335x EVM-SK
        * OMAP5 uEVM

the port used for minicom will be automatically detected. By default Ubuntu
will not recognize this device. Setup will add a udev rule to
/etc/udev/ so that from now on it will be recognized as soon as the board is
plugged in.

For other boards, the serial will defualt to /dev/ttyS0. Please update based
on your setup.

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

NOTE: For boards with a built-in USB to Serial adapter please press
      ENTER at the prompt below.  The correct port will be determined
      automatically at a later step.  For all other boards select
      the serial port that the board is connected to
Which serial port do you want to use with minicom?
[ /dev/ttyS0 ]

Copied existing /home/x0089162/.minirc.dfl to /home/x0089162/.minirc.dfl.old

Configuration saved to /home/x0089162/.minirc.dfl. You can change it further from inside
minicom, see the Software Development Guide for more information.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the u-boot variables for booting the EVM.
Autodetected the following ip address of your host, correct it if necessary
[ 172.24.191.34
192.168.122.1 ] 172.24.191.34

Select Linux kernel location:
1: TFTP
2: SD card
3: flash

[ 1 ] 1

Select root file system location:
1: NFS
2: SD card

[ 1 ] 1

Available kernel images in /tftpboot:
    uImage-omapl138-lcdk
    uImage-omapl138-lcdk.bin

Which kernel image do you want to boot from TFTP?
[ uImage-omapl138-lcdk.bin ]

Resulting u-boot variable settings:

setenv bootdelay 3
setenv baudrate 115200
setenv bootargs console=ttyS2,115200n8 rw noinitrd root=/dev/nfs

nfsroot=172.24.191.34:/home/x0089162/MCSDK/03-10-2013/mcsdk_1_01_00_02/targetNFS,nolock,rsize=1024,wsize=1024 ip=dhcp
setenv bootcmd 'dhcp;setenv serverip 172.24.191.34;tftpboot;bootm'
setenv autoload no
setenv serverip 172.24.191.34
setenv bootfile uImage-omapl138-lcdk.bin
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Would you like to create a minicom script with the above parameters (y/n)?
[ y ] n

--------------------------------------------------------------------------------
Installing Linux devkit
Enter target directory for SDK (default: /usr/local/arago-2013.05): ./linux-devkit
You are about to install the SDK to "/home/x0089162/MCSDK/03-10-2013/mcsdk_1_01_00_02/linux-devkit". Proceed[Y/n]?y
Extracting SDK...done
Setting it up...done
SDK has been successfully set up and is ready to be used.
-------------------------------------------------------------------------------
TISDK setup completed!
Please continue reading the Software Developer's Guide for more information on
how to develop software on the EVM
-------------------------------------------------------------------------------
x0089162@palin05:~/MCSDK/03-10-2013/mcsdk_1_01_00_02$

Host scripts will be available as part of  /mcsdk_<version>/bin

user@linux-host:~/mcsdk_<version>$/bin$ ls

add-to-group.sh

setup-minicom.sh

setup-targetfs-nfs.sh

setup-uboot-env.sh

common.sh

setup-host-check.sh

setup-package-install.sh

setup-tftp.sh

Program EVM

Details of programing EVM , ARM and DSP subsystem can be found at 'Exploring' Chapter of User Guide http://processors.wiki.ti.com/index.php/MCSDK_OMAPL138_User_Guide_Chapter_Exploring

Technical Support

For technical discussions and issues, please visit

• OMAPL138 forum: http://e2e.ti.com/support/dsp/omap_applications_processors/f/42.aspx
• OMAPL138 SW & HW Comparison
• BIOS Embedded Software forum: http://e2e.ti.com/support/embedded/f/355.aspx
• Linux Embedded Software forum: http://e2e.ti.com/support/embedded/linux/f/354.aspx
• Code Composer Studio forum: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/3131.aspx
• TI C/C++ Compiler forum: http://e2e.ti.com/support/development_tools/compiler/f/343/t/34317.aspx
• Embedded Processors wiki: http://processors.wiki.ti.com

For local support in China, please visit

• China Support forum: http://www.deyisupport.com

Note: When asking for help in the forum you should tag your posts in the Subject with “MCSDK”, the part number (e.g. “OMAP-L138”) and additionally the component (e.g. “MPM”).