VirtualBox Virtual Machine for TI AM3517 Linux SDK ReadMe ------------------------------------------------------------------------------ Texas Instruments SDK Version: ti-sdk-am3517-evm-05.05.00.00-Linux-x86-Install Date: February 2013 ------------------------------------------------------------------------------ --------------------------------- Table of Contents --------------------------------- 0 Scope of Document 1 Overview 2 Requirements 3 Installation 4 Build the Linux BSP 5 Create a Linux Bootable SD Card 6 General Info --------------------------------- 0) Scope of Document -------------------- The information contained within this ReadMe file may pertain only to this version of the Linux SDK and virtual machine (VM). Please refer to Logic PD's website for more information. 1) Overview ----------- The .ova file is a VM complete with Ubuntu operating system (OS) build tools and embedded Linux source code for this development kit. 2) Requirements --------------- --) VirtualBox --) VirtualBox Extention Pack for your OS. VirtualBox version 4.1.0 was used to create this VM. 3) Installation --------------- a) Install VirtualBox; see the VirtualBox website at: https://www.virtualbox.org b) Install the VirtualBox Extension Pack for your OS. See the VirtualBox website at: https://www.virtualbox.org c) In the "File" menu, select "Import Virtual Appliance." d) Select the .ova file included with this ReadMe file. e) Follow the prompts for installation. When complete, you'll see the VM in your VirtualBox control panel. f) Select the VM and click "Start" to launch it. 4) Build the Linux BSP ---------------------- a) Start the VM. b) When the VM is up and running, log in to Ubuntu with the following credentials: Ubuntu Username: logic Ubuntu Password: logic c) Set your environment. i) Open a command window and switch to the SDK directory: $ cd ti-sdk-am3517-evm-05.05.00.00 ii) Run the following environment script: $ source linux-devkit/environment-setup You should see your prompt change to "[linux-devkit]." d) Build the bootloaders. i) Switch to the U-Boot directory: $ cd board-support/u-boot-2011.09-psp04.06.00.08 ii) Clean the build: $ make CROSS_COMPILE=arm-arago-linux-gnueabi- ARCH=arm distclean $ rm -rf am3517 iii) Build the bootloaders: $ make O=am3517 CROSS_COMPILE=arm-arago-linux-gnueabi- ARCH=arm am3517_evm You will find the output here: am3517/MLO am3517/u-boot.img iv) Copy the files to the tftp directory for later use: $ cp am3517/MLO /tftpboot/. $ cp am3517/u-boot.img /tftpboot/. For additional information, see the following Texas Instruments (TI) wiki page: http://prprocessors.wiki.ti.com/index.php/AMSDK_u-boot_User%27s_Guide e) Build the kernel. i) Switch to the kernel directory: $ cd $HOME/ti-sdk-am3517-evm-05.05.00.00 $ cd board-support/linux-2.6.37-psp04.02.00.07.sdk ii) Clean the build: $ make CROSS_COMPILE=arm-arago-linux-gnueabi- ARCH=arm mrproper iii) Configure the build: $ make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- am3517_evm_defconfig iv) Build the kernel: $ make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- uImage You will find the output here: arch/arm/boot/uImage v) Copy the kernel to the tftp directory for later use: $ cp arch/arm/boot/uImage /tftpboot/. For additional information, see the following TI wiki page: http://processors.wiki.ti.com/index.php/AMSDK_Linux_User%27s_Guide 5) Create a Linux Bootable SD Card ---------------------------------- a) Insert an SD card into your host PC and then use the VirtualBox "Devices" menu to connect it to your PC. b) When the SD card is available in the VM, enter the following commands: $ cd $HOME/ti-sdk-am3517-evm-05.05.00.00/bin $ sudo ./create-sdcard.sh Many options will now be presented by this script. Below is an example of the output you will see and the options you should follow. TAKE GREAT CARE WHEN SELECTING THE DRIVE TO WHICH YOU WRITE THE IMAGE. Lines that require user input are noted below with two asterisks (**). NOTE: The "u-boot.bin file not found" message near the end of the script can be ignored. The old SDK used the "u-boot.bin" file and the new SDK uses the "u-boot.img" file instead. This script is set up to handle both "u-boot.bin" or "u-boot.img". **[sudo] password for logic: logic ############################################################################## This script will create a bootable SD card from custom or pre-built binaries. The script must be run with root permissions and from the bin directory of the SDK Example: $ sudo ./create-sdcard.sh Formatting can be skipped if the SD card is already formatted and partitioned properly. ############################################################################## Available Drives to write images to: # major minor size name 1: 8 16 247040 sdb **Enter Device Number: 1 sdb was selected Checking the device is unmounted unmounted /dev/sdb1 sdb1 sdb2 sdb3 247008 SD Card is not correctly partitioned ############################################################################## Select 2 partitions if only need boot and rootfs (most users) Select 3 partitions if need SDK & CCS on SD card. This is usually used by device manufacturers with access to partition tar balls. ****WARNING**** continuing will erase all data on sdb ############################################################################## **Number of partitions needed [2/3] : 2 Now partitioning sdb with 2 partitions... ############################################################################## Now making 2 partitions ############################################################################## 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB) copied, 3.73444 s, 281 kB/s Disk /dev/sdb doesn't contain a valid partition table DISK SIZE - 252968960 bytes Checking that no-one is using this disk right now ... OK Disk /dev/sdb: 30 cylinders, 255 heads, 63 sectors/track sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sdb: unrecognized partition table type Old situation: No partitions found New situation: Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/sdb1 * 0+ 8 9- 72261 c W95 FAT32 (LBA) /dev/sdb2 10 29 20 160650 83 Linux /dev/sdb3 0 - 0 0 0 Empty /dev/sdb4 0 - 0 0 0 Empty Successfully wrote the new partition table Re-reading the partition table ... If you created or changed a DOS partition, /dev/foo7, say, then use dd(1) to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1 (See fdisk(8).) ############################################################################## Partitioning Boot ############################################################################## mkfs.vfat 3.0.7 (24 Dec 2009) ############################################################################## Partitioning rootfs ############################################################################## mke2fs 1.41.11 (14-Mar-2010) Filesystem label=rootfs OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) Stride=0 blocks, Stripe width=0 blocks 40320 inodes, 160648 blocks 8032 blocks (5.00%) reserved for the super user First data block=1 Maximum filesystem blocks=67371008 20 block groups 8192 blocks per group, 8192 fragments per group 2016 inodes per group Superblock backups stored on blocks: 8193, 24577, 40961, 57345, 73729 Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 30 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. ############################################################################## Partitioning is now done Continue to install filesystem or select 'n' to safe exit Warning Continuing will erase files any files in the partitions ############################################################################## **Would you like to continue? [y/n] : y Mount the partitions Emptying partitions Syncing.... ############################################################################## Choose file path to install from 1 ) Install pre-built images from SDK 2 ) Enter in custom boot and rootfs file paths ############################################################################## **Choose now [1/2] : 2 ############################################################################## For Boot partition If files are located in tar ball write complete path including the file name. e.x. $: /home/user/MyCustomTars/boot.tar.gz If files are located in a directory write the directory path e.x. $: /ti-sdk/board-support/prebuilt-images/ and the beginning of the files should be labeled with MLO, u-boot, uImage i.e. test_MLO_image must be labeled as MLO_test_image NOTE: Not all platforms will have an MLO file and this file can be ignored for platforms that do not support an MLO ############################################################################## **Enter path for Boot Partition: /tftpboot Directory exists This directory contains: MLO rootfs.jffs2 u-boot.img uImage **Is this correct? [y/n] : y ############################################################################## For Rootfs partition If files are located in tar ball write complete path including the file name. e.x. $: /home/user/MyCustomTars/rootfs.tar.gz If files are located in a directory write the directory path e.x. $: /ti-sdk/targetNFS/ ############################################################################## **Enter path for Rootfs Partition : /home/logic/ti-sdk-am3517-evm-05.05.00.00/ filesystem/base-rootfs-am3517-evm.tar.gz File exists ############################################################################## Copying files now... will take minutes ############################################################################## Copying boot partition MLO copied u-boot.bin file not found u-boot.img copied uImage copied Copying rootfs System partition Written 100% Syncing... Un-mount the partitions Remove created temp directories Operation Finished $ ############################################################################## To boot the newly created SD card, following the steps in the "Zoom AM3517 Development Kit QuickStart Guide" and be sure DIP switches S7:1 and S7:4 are set to the ON position; all others should be set to the OFF position. For information on how to create an SD card with the Linux boot images, see the following TI wiki page: http://processors.wiki.ti.com/index.php/Sitara_Linux_SDK_create_SD_card_script 6) General Info --------------- --) If you have difficulty installing or running VirtualBox, please see the VirtualBox website at: https://www.virtualbox.org --) Make sure VT-x and VT-d/AMD-Vi flags are enabled in the host BIOS. --) VirtualBox versions 3.1.x and older may not work with this VM. --) Make sure the VirtualBox Extension Pack is installed. --) If using "Ubuntu Software Center" to install VirtualBox, consider instead going to: https://www.virtualbox.org to get the latest version of VirtualBox. 7) What’s New --------------- 2013-02-01 ---------- The following items have been added to the VM: --) Git --) Vim --) mtd-utils --) flex --) bison --) quilt --) Java SDK 1.7 ----------------------------------------------------------------------------- Copyright (c) 2013 Logic PD, Inc. www.logicpd.com