Sitara PSP Test Setup

This page is currently under construction. The content of this page is due to change quite frequently and thus the quality and accuracy are not guaranteed until this message has been removed. Please feel free to contribute to this page while construction is in progress.

Document License

This work is licensed under the Creative Commons Attribution-Share Alike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/us/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.

Read This First

• TI81XX refer to TI816X/TI814X/TI813X.

About This Manual

This document provides an overview for Test Setup used for Sitara family of devices, OMAP35xEVM, AM3517EVM, AM/DM37xEVM, Beagle, BeagleXM, TI81XX/TI811X EVM, etc... Note that same setup is being used for performance measurements.

If You Need Assistance

For further information or to report any problems, contact http://community.ti.com/ or http://support.ti.com/

Trademarks

OMAP^TM is trademark of Texas Instruments Incorporated. All other trademarks are the property of the respective owner.

Test Setup

Audio

Ethernet

Video Display

Video Capture

Memory Technology Device (MTD - NAND, NOR, OneNAND Flash)

MMC/SD

Power Management

USB

MUSB Host MSC

The usb host msc setup consists of connecting the USB Mass storage hard disk or flash drive to usb port. In TI81XX/TI811X there are two usb ports, to get the performance data on one port, please connect the USB HDD to one of port. Please refer respective TI device data sheet for USB Host MSC performance numbers.

• If LFTB test suit used to take the performance, then use filesystem-test-suite module in LFTB. It supports functional, performance and stress test cases.
• If LTP-DDT is used to take performance measurement, then refer to LTP-DDT tools/procedure here

The host ports on EVM can be either musb otg controller port or Enhanced Host Controller Port (EHCI)(applicable for platform which has EHCI port), the setup for usb-host-msc is same any host controller.

Test Parameters

This section has basic setup information. This setup also depends on other variable parameters which are listed in the below table. For the exact values of these parameters, please refer the SATA section in the PSP software data sheet for that TI device.

Test Parameters

Silicon Revision

EVM Revision

PSP Software Revision

LFTB version

DDR Bandwidth

USB Hard Disk drive

HDD brand/model in each port

Setup Block Diagram

Please refer to below picture of USB test setup. The test results will be logged using the serial console.

MUSB HOST Setup

EHCI HOST Setup

Instruction to perform usb-msc-host performance test

Please refer to LFTB-Instruction to run the LFTB test script.

MUSB Device CDC/RNIDS

EVM act as CDC/RNDIS gadget device connected Linux/Windows Host respectively(PC or other EVM). The iperf tool used to get the performance figures for CDC/RNDIS gadget device. Please refer respective TI device data sheet for cdc/rndis performance figures.

Test Parameters

This section has basic setup information. This setup also depends on other variable parameters which are listed in the below table. For the exact values of these parameters, please refer the SATA section in the PSP software data sheet for that TI device.

Test Parameters

Silicon Revision

EVM Revision

PSP Software Revision

LFTB version

DDR Bandwidth

-

Setup Block Diagram

Please refer to below picture of USB test setup. The test results will be logged using the serial console.

Instructions

Setup : EVM as client and Linux/Windows Host PC as server
command at EVM: iperf -c <window/linux host ip_adr> -w <8|16|32|64|128>K -t 60 -d
command at Host: iperf -s

Linux CDC Setup

Windows RNDIS Setup

MUSB Device MSC

The EVM can act as mass storage device exposed as removable media over usb to Host (Linux/Windows). The storage media can be SATA/MMCSD etc.

Test Parameters

This section has basic setup information. This setup also depends on other variable parameters which are listed in the below table. For the exact values of these parameters, please refer the SATA section in the PSP software data sheet for that TI device.

Test Parameters

Silicon Revision

EVM Revision

PSP Software Revision

LFTB version

DDR Bandwidth

USB Hard Disk drive

HDD brand/model in each port

Setup Block Diagram

SATA

The setup uses SATA harddisks to test the SATA interface. The number of SATA ports could vary for different TI devices. Please refer respective TI device data sheet for number of SATA ports available in that device. SATA test uses filesystem-test-suite module in LFTB. It supports functional, performance and stress test cases.

Test Parameters

This section has basic setup information. This setup also depends on other variable parameters which are listed in the below table. For the exact values of these parameters, please refer the SATA section in the PSP software data sheet for that TI device.

Test Parameters

Silicon Revision

EVM Revision

PSP Software Revision

LFTB version

DDR Bandwidth

Number of SATA Ports

HDD brand/model in each port

Setup Block Diagram

Below picture has information on the SATA test setup. A PC SMPS is used to power the SATA HDD(s). The PC SMPS requires a loopback connection to power-up the devices. This is shown in the picture below. The test resulrs will be logged using the serial console. If a test case requires multiple sessions, a telnet session could also be used.

                                                                                                                                                  Figure: SATA Test Setup

Instructions

• Delete all the partitions in the device and create one partition of size 2GB. Refer fdisk tool section for help.
• In NFS path, change the current working directory to LFTB filesystem test suite.

  cd LFTB/filesystem_test_suite/scripts/common/

• Unmount the partition(s) if you have it already mounted.

  umount /dev/sda1

• Start the functional test and save the logs.

   root#./filesystem_tests_scripts.sh -plat <ti_device> -type func -device <hdd_device> -fs_type <ext2|vfat>

   Below example, starts functional test for ext2 filesystem on HDD device '/dev/sda1' on DM816x device (i.e. ti816x)
   root#./filesystem_tests_scripts.sh -plat ti816x -type func -device /dev/sda1 -fs_type ext2

• Start the performance test and save the logs.

   root#./filesystem_tests_scripts.sh -plat <ti_device> -type perf -device <hdd_device> -fs_type <ext2|vfat>

   Below example, starts performance test for ext2 filesystem on HDD device '/dev/sda1' on DM816x device (i.e. ti816x)
   root#./filesystem_tests_scripts.sh -plat ti816x -type perf -device /dev/sda1 -fs_type ext2

• Start the stress test and save the logs.

   root#./filesystem_tests_scripts.sh -plat <ti_device> -type stress -device <hdd_device> -fs_type <ext2|vfat>

   Below example, starts performance test for ext2 filesystem on HDD device '/dev/sda1' on DM816x device (i.e. ti816x)
   root#./filesystem_tests_scripts.sh -plat ti816x -type stress -device /dev/sda1 -fs_type ext2

Linux Tools

LFTB

Linux Functional Test Bench provides a framework to test drivers. Refer [LFTB Wiki] for architecture and tool usage help. LFTB releases could be downloaded from [arago LFTB git].

fdisk

fdisk tool is used to manage partition(s) in a storage device. This section has basic steps for listing/creating/deleting partition(s) on a storage device. For extensive list of commands and usage please refer the tool man page.

NOTE: Make sure the contents in the drive are backed-up, the below steps will completely erase the data in the drive.

The tool is invoked by passing the storage device node as the argument. To quit the 'fdisk' prompt use option 'q' and to save & exit use option 'w' and then 'q'.

  fdisk /dev/<device>

In the below examples it is assumed that the device currently managed is /dev/sda

List Partition(s)

Option 'p' is used to list the available partitions in a device.

root@ti8168-evm:~# fdisk /dev/sda

The number of cylinders for this disk is set to 60801.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Delete Partition(s)

• Option 'd' is used to delete a partition.
• If there are multiple partitions on the device then fdisk will request you to select the partition number.
• if there is only one partition then it will be deleted without prompting.
• Now write the new partition table to the HDD using option 'w'

Create Partition(s)

Option 'n' is used to delete a partition.

root@ti8168-evm:~# fdisk /dev/sda

The number of cylinders for this disk is set to 60801.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-60801, default 1): 1
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-60801, default 60801): +2G

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.

The above example creates a partition of size 2GB (i.e. +2G text in above example).