Instruction for TI GLSDK

Note! All instructions in this guide are for Ubuntu 12.04. At this time, this is the only supported Linux host distribution for development.

Some commands are to be executed on the Linux development host, some on the Linux target and some on the u-boot (bootloader) prompt. The following conventions are used to distinguish the commands on a host and on the target:

host $ <this command is to be executed on the host> target # <this command is to be executed on the target> u-boot :> <this command is to be executed on the u-boot prompt>

Starting your software development

Setup up ARM linux development Environment on the host. Please refer to this link to see how to set one up.

Configuration of ARM Linux development Environment

Step 1: Install the GLSDK release on the host machine.

Download the GLSDK installer for your platform. If necessary make the installer executable manually by executing:

  host $ chmod +x ti-glsdk_omap5-uevm_6_03_00_01_linux-installer.bin

Execute the installer on the host and follow the instructions:

  host $ ./ti-glsdk_omap5-uevm_6_03_00_01_linux-installer.bin

Step 2: Setup the GLSDK environment variable to the location where the GLSDK is installed (the following assumes that GLSDK was installed at default location):

  host $ export GLSDK="${HOME}/ti-glsdk_omap5-uevm_6_03_00_01"

Step 3: Setup the GLSDK on host The GLSDK comes with a script for setting up your Ubuntu 12.04 LTS development host. It is an interactive script, but if you accept the defaults by pressing return you will use the recommended settings. This is recommended for first time users. Note that this script requires ethernet access as it will update your Ubuntu Linux development host with the packages required to develop using the GLSDK. Note: Please make sure that the proxy settings are done for http, https, git, ftp and wget before proceeding further. Execute the script in the GLSDK release directory using:

  host $ cd ${GLSDK}
  host $ ./setup.sh

The setup script would perform the following operations:

  1. Installs all the necessary package on the host for the SDK.

Prepares the UART terminal to communicate with the target over Debug USB on Minicom. If you want to use a windows host for connecting to the target instead, see the #Setting_up_Tera_Term section

  1. Setups the linaro cross compiler
  2. Installs the dependencies for the repo tool.
  3. Initialize the repo by pointing it to GLSDK release manifest location.
  4. Note: During this setup process, if the ducati tools are installed there is known issue as below
    1. XDC installation contains 64-bit version of gmake binary. Hence would not work with 32-bit Host m/c. Please download 32-bit binary from here and replace exiting gmake with the downloaded one if the installation is on a 32-bit Ubuntu host OS.

To start minicom on your Linux development host execute minicom -w (or Tera Term on Windows).

Step 4: Prepare SD card To install the release image, you need a µSD Card (at least 4GB) with 2 partitions:

  boot (vfat) partition.
  rootfs (ext4 or ext3) partition.

The following procedure prepares the sdcard: (however, the user can choose to do it manually as well)

Plug an SD card reader to your PC and insert a µSD card. It must be at least 4GB size. Identify which device corresponds to the SD card reader. sudo fdisk -l command can help you find out where the µSD Card is mapped. We will call it /dev/sdY here. Re-format your µSD card with this script mksdboot.sh from the bin directory in the GLSDK

  $ sudo ${GLSDK}/bin/mksdboot.sh --device /dev/sdY --sdk ${GLSDK}

The above script would prepare the SD card with the prebuilt images and yocto filesystem for SD boot.

Step 5: Booting the board To boot the board with the above created SD card, refer to the Quick Start Guide in docs/ folder in the GLSDK release to set the board. Then, power cycle the board and login with username as root.

Repo tool Usage Starting source code development using repo tool

The GLSDK release uses the repo tool to effectively manage the different components of the GLSDK.

NOTE :

1: The first step to the repo tool is the repo initialization and this is done as part of the $GLSDK/setup.sh script

2: The repo tool is downloaded into the bin folder in the GLSDK directory. Please ensure that this path is updated in the environment variable as shown below

  host $  export PATH=${GLSDK}/bin:$PATH

The GLSDK release contains a helper script that sets up the development environment. Run the script as shown below:

  host $ cd ${GLSDK}
  host $ ./bin/fetch-sources.sh

The script does the following:

  Check for the repo tool.
  Perform repo sync
  Create a branch called glsdk_dev
  Checkout the branch glsdk_dev

It is expected that the development is done on the glsdk_dev branch. How to get updates

If there are changes in the remote repositories, it could be fetched using the same script. However, please make note of these important points.

1. The script will fetch the latest changes, and switch back to the glsdk_dev branch. 2. The new updates from the remote, will be available in the master branch. 3. The decision on whether to merge the changes to the local branch or merge the local branch to the master is left to the developer

Building Yocto Filesystem

Before building the filesystem, please ensure that the svn, http, ftp and git proxies are set correctly. Refer to the following link for these settings https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy.

Add the Linaro cross-compile toolchain path in the PATH environment variable.

  host $ export PATH=<Path to Linaro cross-compile toolchain>/bin:$PATH

Run this command to as a one-time setup for the yocto build

  host $ cd $GLSDK 
  host $ ./bin/setup-yocto.sh

For building core sdk , run the build-core-sdk.sh passing machine name as an argument.

  host $ cd yocto-layers

A hack to prevent the build of 32-bit libpseudo.so is to set the variable NO32LIBS to 1 in sources/meta-arago/meta-arago-distro/conf/distro/arago.conf

  NO32LIBS = "1"

Create a downloads directory (if building using Yocto for the first time), where the Yocto build will place the downloads. Note the path of the directory.

  host $ mkdir downloads

NOTE: Please pass the same downloads directory path to the following build-script when prompted

  host $ ./build-core-sdk.sh omap5-evm

These scripts will build the arago-glsdk-multimedia-image.

After build is complete the generated images can be found in yocto-layers/build/arago-tmp-external-linaro-toolchain/deploy/images/

yocto.txt · Last modified: 2014/02/28 14:01 by bcousson
Recent changes RSS feed Creative Commons License Donate Minima Template by Wikidesign Driven by DokuWiki