AR93xx ART2 Reference Guide MKG-15527

AR93xx
Atheros Radio Test 2

Reference Guide
December 2010
ATHEROS
2010 by Atheros Communications, Inc. All rights reserved.
Atheros, Atheros Driven, Align, Atheros XR, Driving the Wireless Future, lntellon, No New
Wll'es, Orion, PLC4Trucks, Powerpacket, Spread Spectrum Carrier, SSC, ROCm, Super A/G,
Super G, Super N, The Air is Cleaner at 5-GHz, Total 802.11, U-Nav, Wake on Wireless, Wireless
Future. Unleashed Now., and XSPAN, are registered by Atheros Communications, Inc. Atheros SST,
Signal-Sustain Technology, Ethos, Install N Go, IQUE, ROCm, amp, Simpli-Fi, There is
Here, U-Map, U-Tag, and 5-UPTM are trademarks of Atheros Communications, Inc. The Atheros logo
is a registered trademark of Atheros Communications, Inc. All other trademarks are the property of their
respective holders.
Subject to change without notice.
Notice
The information in this document has been carefully reviewed and is believed to be accurate. Nonetheless,
this document is subject to change without notice, and Atheros Communications, Inc. (Atheros) assumes no
responsibility for any inaccuracies that may be contained in this document, and makes no commitment to
update or to keep current the contained information, or to notify a person or organization of any updates.
Atheros reserves the right to make changes, at any time, in order to improve reliability, function or design
and to attempt to supply the best product possible. Atheros does not represent that products described
herein are free from patent infringement or from any other third party right.
No part of this document may be reproduced, adapted or transmitted in any form or by any means,
electronic or mechanical, for any purpose, except as expressly set forth in a written agreement signed by
Atheros. Atheros or its affiliates may have patents or pending patent applications, trademarks, copyrights,
maskwork rights or other intellectual property rights that apply to the ideas, material and information
expressed herein. No license to such rights is provided except as expressly set forth in a written agreement
signed by Atheros.
ATHEROS MAKES NO WARRANTIES OF ANY KIND WITT-I REGARD TO THE CONTENT OF THIS
DOCUMENT. IN NO EVENT SHALL ATHEROS BE LIABLE FOR DIRECT, INDIRECT, SPECIAL,
INCIDENTAL SPECULATORY OR CONSEQUENTIAL DAMAGES ARISING FROM THE USE OR
INABILITY TO USE THIS PRODUCT OR DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBLITY
OF SUCH DAMAGES. IN PARTICULAR, ATHEROS SHALL NOT HAVE LIABILITY FOR ANY
HARDWARE, SOFTWARE, OR DATA TRANSMITTED OR OTHERWISE USED WITH THE PRODUCT,
INCLUDING THE COSTS OF REPAIRING, REPLACING, INTEGRATING, INSTALLING OR
RECOVERING SUCH HARDWARE, SOFTWARE OR DATA. ATHEROS SPECIFICALLY DISCLAIMS THE
IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE AS
THEY MIGHT OTHERWISE APPLY TO THIS DOCUMENT AND TO THE IDEAS, MATERIAL AND
INFORMATION EXPRESSED HEREIN.
Document Number: MKG-15527 Ver. 1.0
ii
AR93xx ART Reference Guide

December 2010
Atheros Communications, Inc.

COMPANY CONFIDENTIAL
Revision History
Revision
Descrtptton of Changes
December 2010
Initial AR93xx document release

December 2010
iii
iv

December 2010

Contents
List of Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ix
Preface ... ...................................
xi
1 Overview .................................... 1-1

ART2 Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
2 Installing & Configuring ART2 ................... 2-1

ART2 Software Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Installing and Running ART2 for a STA Card . . . . . . . . . . . . . . . 2-2
Using ART2 with an AP . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
AP Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Network Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Loading and Running Software. . . . . . . . . . . . . . . . . . . . . 2-4
3 Using the ART2 GUI . ........................... 3-1

Initial Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
lfierarchical Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
ContTx Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Link Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
EEPROM Operations Screen . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Utilities Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Menu Bar Pull-Down Menus . . . . . . . . . . . . . . . . . . . . . . . . 3-9
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Clients Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Calibration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Advanced Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Window Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Contents
December 2010
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Usfng CART/NART Command Lfne Interfaces . . . . . . .
4-1
CART Command Line Control . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

CART /NART Startup Options . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
NART and CART Commands . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Command Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Results Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Record Type Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Field Name Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Computations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Report Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Getting Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
5 Interfacing a Custom Process to ART2 ............
5-1
Controlling CART using Custom/Vendor Software . . . . . . . . . . . . . 5-2

Controlling NART using Custom/Vendor Software. . . . . . . . . . . . . 5-4
6 Sample Manufacturing Test Flow. . . . . . . . . . . . . . . . .
6-1
Manufacturing Test System Requirements . . . . . . . . . . . . . . . . . . 6-1

Manufacturing Test System. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Set Up Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware Test Equipment Setup . . . . . . . . . . . . . . . . . . .
GPIB-ENET/100 from National Instruments . . . . . . . . . .
Power Meter E4416A from Agilent Technologies . . . . . . . .
Spectrum Analyzer E4404B from Agilent Technologies . . . .
Attenuator Switch Drivers 11713A from Agilent Technologies
.
.
.
.
.
.
.
.
.
.
.
.
6-3
6-3
6-3
6-5
6-5
6-5
Running the Sample Manufacturing Test Flow. . . . . . . . . . . . . . . . 6-6

Start.art . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
ProductList.ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
test_flow_flags.art . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Set this flag to 1 to disable the testing of the rx PER testing within the 2
GHz Rx unicast throughput test (default= 0) . . . . . . . . . . . . . . 6-14
$refID.ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
vi

December 2010

$refID_power.art . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Describing ctl_$refID.art . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
A Sample CART Command List . . . . . . . . . . . . . . . . . . . .
A-1
B Sample NART Command List .................... s-1
Sample Error Code List . . . . . . . . . . . . . . . . . . . . . . . .

Contents
December 2010
c-1
vii
viii

December 2010
List of Tables
Table 1-1.
ART2 Directory Structure . . . . . . . . . . . . . . . . . . . . . 1-2
Table 1-2.
ART2 Software Components . . . . . . . . . . . . . . . . . . . 1-3
Table 4-1.
CART Startup Options . . . . . . . . . . . . . . . . . . . . . . 4-4
Table 4-2.
NART Startup Options . . . . . . . . . . . . . . . . . . . . . . 4-4
Table 4-3.
Function Descriptions . . . . . . . . . . . . . . . . . . . . . . 4-10
Table 4-4.
Report Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Table 4-5.
Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Table 6-1.
Manufacturing Test System Requirements . . . . . . . . . . . 6-1
Table 6-2.
Files Used to Control Manufacturing Test Flow . . . . . . . . 6-7
Table 6-3.
Description of start.art Entries . . . . . . . . . . . . . . . . . . 6-9
Table 6-4.
Description of ProductList.ref Columns. . . . . . . . . . . . 6-10
Table 6-5.
Description of test_flow_flags.art . . . . . . . . . . . . . . . 6-13
Table 6-6.
Description of $refID.ref Commands . . . . . . . . . . . . . 6-18
Table 6-7.
Description of Target Power File Commands. . . . . . . . . 6-22
Table 6-8.
Description of CTL command File . . . . . . . . . . . . . . . 6-26

List of Tables ix
December 2010

December 2010

Preface
lbis document is intended to provide a description of the installation and
operation of the Atheros Radio Test (ART2) application.
ART2 is a manufacturing and radio evaluation tool that can be used with the
Atheros AR93xx family of devices.
About this Document

The document consists of these chapters:
Otapter 1
Overview-Gives a brief description of ART2 and its current feature

set.
Otapter 2
Installing & Configuring ART2-Describes how to set up ART2 using

the most common configuration: ART2 GUI controlling NART and
CART while testing a STA or an AP.
Chapter 3
Using the ART2 GUI-Describes the ART2 graphical user interface

and its menu functions.
Otapter4
Using CART/NART Command Line Interfaces-Describes the CART

and NART command conventions and options.
Chapter 5
Interfacing a Custom Process to ART2-Provides information on

using a custom or vendor solution to control CART and NART.
Otapter 6
Sample Manufacturing Test Flow-Provides an example of how a

manufacturing test flow may be implemented.
Appendix A
Sample CART Command List-A list of CART commands with full

descriptions for ART2 version 2.13.
AppendixB
Sample NART Command List-A list of NART commands with full

descriptions for ART2 version 2.13.
AppendixC
Sample Error Code List-A list of error codes for ART2 version 2.13.

Preface
December 2010
xi
Audience
lbis document is intended for users of ART2 who will be performing radio
evaluation or setting up a manufacturing flow with the Atheros AR93xx and
later.
Additional Resources
Atheros Reference Design hardware, software, and documentation contain
proprietary information of Atheros Commurrications, Inc., and are provided
under a license agreement containing restrictions on use and disclosure, and
are also protected by copyright law. Reverse engineering of this hardware,
software, or documentation is prohibited.
These resources should be referenced regarding topics that are not addressed
in this document:
xii
AR93xx Single-Chip 802.lln MAC/BB/Radio for 2.4/5 GHz WLANs data

sheets
AR93xx EEPROM Device Configuration Guides

December 2010
Chapter
II
1
Overview
The AR93xx Atheros Radio Test (ART2) is the next generation version of
Atheros Radio Test (ART). ART2 is a tool used for radio evaluation and
manufacturing tests. It performs various transmission tests, receive and link
tests, and calibrates and tests adapters during a manufacturing flow. It
supports all the same capabilities of ART with regards to the ability to test and
calibrate Atheros WLAN devices while providing more flexibility for how
these tests can be run. For example, tests can be created that run receive
sensitivity sweeps on the radio or comprehensive transmit power accuracy
tests can be performed in an automatic flow. While ART2 provides more
testing capabilities and flexibility than ART, the increased complexity may
require more time to learn all of its features. ART2 has both a command line
interface and a graphical user interface (GUI).
NOTE: All information related to EEPROM for Reference Designs is based on the AR93xx.
ART2 supports only AR93xx. Older versions of ART must be used for other adapters.
ART2 runs on the same three-chain calibration setups as ART, consisting of

one or more DUTs, Golden Unit, power meter, spectrum analyzer and threechain variable attenuators. It can also be used with one box testers, once the
appropriate software has been obtained from the tester manufacturer.

Overview
December 2010
1-1
Chapter
ART2 Structure
Table 1-1 descnbes the directory structure of the ART2 package.
Table 1-1. ART2 Dtrectory Structure

Contents
Directomy
Contains the components that should be run when the radio being tested
as an AP. This directory contains the source code needed to build nart.out
so that customers may port to their own AP p1atforms.
Contains the Wmdows driver files needed when the radio being tested is
a STA card within a PC.
Contains the ART2 executables and is the directory from which ARI2
software should be run.
Contains test flow files and reference design specific files needed for
testing Atheros WLAN radios.
Contains the Release Notes as well as the ART2 GUI support documents.
Contains the Microsoft Framework .NET Version 2 needed for the ART2
GUL Some systems may already have this installed. 1 while executing
the artGUl.bat an error message appears, the .NET framework must be
installed into the system before running the ART2 GUL
AP
art_driver
bin
command
docs
support
Figure 1-1 shows ART2 set up with various possible connections it may have
with other test components. The host PC system runs CART and optionally
NART on a local WiFi card, while additional PCs or APs run separate
instances of NART controlling other WiFi devices. CART and NART may be
controlled by other custom processes through their socket interfaces. See
Chapter 5, "Interfacing a Custom Process to ART2" on page 5-1 for more
information.
Test
Instruments
------------------------------------
CART
Optional 2 Radio
,. .......
t........~~~~....... .l
WiFi Device
Optional 511o Radio
NART
WiFi Device
PC1
PC1 may optionally run
NART. CART/NART may also
communicate though
sockets to other programs.
NART
Driver
WiFi Device
PC2/AP
Optional Multiple NART Setup:

The ART2 GUI supports up to 3 NART
setups. CART will support up to 5 NART
setups when the ART2 GUI is not being
used.
Figure 1-1. ART2 System Components
1-2

December 2010

Chapter
II
Table 1-2 describes the ART2 software components.

Table 1-2. ART2 Software Components
Component
Description
ART2GUI
Provides a graphical, easier-to-use interface to CART and NART. See "Using the ART2
GUI" on page 3-1. The GUI sends commands to CART.
CART
Contains the control software that runs all the test loops and controls the test
instrumentation. It sends radio-specific information over a socket to NART. Commands
can be sent to it directly via a terminal window, ART2 GUI, or a custom process. See
"Using CART/NART Command Line Interfaces" on page 4-1. CART sends NART
commands to NART.
NART
Contains the hardware specific code needed to control the Atheros radio. See "Using
CART/NART Command Line Interfaces" on page 4-1. NART runs in a slave mode and
takes its commands from a socket (which may be TCP /IP, USB, or other technology).
Commands can be sent to it directly via a terminal window, CART, or a custom process.
Driver
Driver used by ART2 to interface to one WiFi device. When using Windows, it is called
the ANWI driver.
If the radio under test is an AP, then NARI and the Linux version of the driver (called
art.ko) runs on the AP. In this scenario CART and the GUI run on a host PC.

Overview
December 2010
1-3
II Chapter
1-4

December 2010

Chapter
El
Installing & Configuring

ART2
This chapter provides information on connecting the test components and
installing the ART2 software applications in the most commonly used
configuration, which is using the ART2 GUI to control NART and CART
while testing a WiFi device, which may be either a STA or an AP.
NART and CART share the same method of parsing commands, regardless of
the configuration. NART and CART both report results using the conventions
described in "Results Output" on page 4-7.
After the hardware and software for the test setup have been installed, see
Chapter 3, "Using the ART2 GUI" for information on the features of the
GUI
Chapter 4, "Using CART /NART Command Line Interfaces" for

information on using CART and NART in a terminal window.
Chapter 5, "Interfacing a Custom Process to ART2" for information on

running ART2 using other configurations.

Installing & Configuring ART2

December 2010
2-1
lfJI Chapter
ART2 Software Setup
The following sections list the steps for setting up ART2 to run a STA card or
an AP.
InstalHng and Running ART2 for a STA Card

NOTE: The ANWI driver with the ART2 802.11n release must be used. If an ANWI
driver from a previous release is installed, it should be updated by running the

install batch file, installing the adapter, then rebooting the system before the new
ANWI driver takes effect.
To install ART2 on Windows 7, Vista, or XP:

1. Copy files from the release package to a directory on the system with the
the Atheros adapter. It is best to install ART2 before installing the adapter.
2. Refer to the ART2 driver release directory art_driver\bin. These
directories contain the Wmdows drivers as well as the batch files needed
to install the driver for the operating system.
Copy the following batch files to the indicated locations:
anwiwdm.sys to the directory %systemroot%\system.32\driverB.
anwi.inf to %system.root%\inp.
NOTE: The batch file assumes that Windows is instau.ed in C:\Windows. If it is not here,
change the batch file to copy to the system32\drlven and tnf OS directories.
3. Install the ANWI driver by running the OS-specific version of the
inst_new_drv_xxx.bat.
4. Insert the Atheros AR93xx reference design adapter into the host PC.
Scan for new hardware changes when Windows installs an instance of the
Atheros AR93xx ANWI Diagnostics Kernel Driver, as shown in Figure 2-1.
~ Device Manilger
f.ile
8dion
~-+
)!iew
~rg](8]
t!elp
IE~ @l!F.I
B~
B ~ AtherosMDK
"ii
18 Atheros AR9300 Anwi Diagnostic Kernel Driver
rB ~ Batteries
EB @!I Biometric
!1 Computer
EB .__ Disk drives
~ Display adapters
. _.J. Dl/D/CD-ROM drives

f+l ~ Human Interface Devices
~I
Figure 2-1. Successful Installation of ANWI driver in Device Manager
2-2

December 2010

Chapter
EJI
Using ART2 with an AP

The ART2 setup for an AP is similar as for a PC: the ART2 GUI and CART
execute on the host PC and communicate with NART on the AP, as shown in
Figure2-2.
Test
Instruments
CART
NART
WiFi Device
AP
PCl
Figure 2-2. ART2 Setup for AP

After NART executes on the AP, it waits for the commands from CART
rwuting on the PC. The AP bootup sequence can be modified such that the
NART runs automatically when the AP boots up. The CART program on the
PC communicates with NART on the AP through a standard TCP /IP socket.
This configuration is sllnilar to that of a STA card, except that NART runs on
the AP instead of a PC.
NOTE: Access point (AP) refers to Atheros AP Reference Designs.

AP Setup
Bringing up the ARI'2 utility on an AP requires:
1. An AP board with appropriate RF module. For example, a PB92 with an
AR93xx board.
2. A serial port module for the RS232 connector.
3. A terminal system with terminal emulation software, such as
HyperTerminal or Minicom.
4. A straight through serial cable, male to female.
5. An Ethernet cable.
6. A server system with a TFfP server to download ART2 client application.
Connect the Ethernet ports of the PC and AP WAN with the Ethernet cable.
Connect the serial cable between the Terminal system and the AP. Set the
serial port properties to: baud rate=115200, data bits=8, parity=none, stop
bits=1, flow control=none.

Installing & Configuring ART2 2-3
December 2010
El Chapter
Network Addresses
NART running on the AP communicates with CART running on a host PC
using TCP /IP sockets. The default Ethernet MAC address that comes with the
software release is 00:03:7F:FF:FF:FE or 00:03:7F:FF:FF:FF. It may be necessary
to change the default address if another device is connected with same
address in the network. The MAC address can be modified at the bootloader
prompt using a command provided with the BSP.
The default Ethernet IP address is 192.168.1.2. Change it using the ifconfig
utility at the Llnux prompt. By default, the WAN interface is bridged with the
LAN and WLAN interfaces. This example command changes the Ethernet IP
address to 10.10.12.242:
> ifconfig brO 10.10.12.242
Loading and Running Software

AP software release notes contain instructions of loading the boot loader,
kernel and file system. ART2 software has two components: a kernel module
and an application. ART2 module (art.ko) comes along with kernel image and
it is located in the nib/modules/2.6.15/net folder. The ART2 client application
(nart.out) is part of the ART2 software distribution. Users may setup a TFTP
server to download it on to the board. The steps to run the art client
application are:
1. Place art_driver\Linux\art.ko and ap \bin \nart.out on the TFTP server.
2. Log into the Atheros-based AP and set the Ethernet IP address:
ifconfig bro <IP_Address>
3. Change to the tmp directory:

cd /tmp
4. TFTP art.ko to the /tmp directory with the command:

tftp -r art.ko -g <tftp_server_ip_address>
5. Start the driver:

inamod art.ko
6. TFTP the nart.out file:

tftp -r nart.out -g <server_ip>
7. Change the mode of the file to be executable:

chmod +x nart.out
8. Create a device handler for the radio:

:mknod /dev/dkO c 63 O
9. Start nart.out:
./Dart.out
At this point the application sits in a loop waiting for a connection from an
ART2 host station.
2-4

December 2010

Chapter
EJ
Using the ART2 GUI

The ART2 GUI is a front-end, graphical user interface that interacts with the
CART/NART console application and provides easy access to its features.
Figure 3-1 shows the ART2 software components, including the ART2 GUI
and its relationship to the CARI/NART application executables.
Test
I Instruments
..................................................
CART
"lo
Optional 2 Radio
Optional 3"' Radio
NART
i::::::::~~~~:::::J
'--
NART
Driver
WiFi Device
Wifi Device
PC1
PC1 may optionally run
NART. CART/NART may also
communicate though
sockets to other programs.
WiFi Device
PC2/ AP

Up to 3 NART setups ore allowed
Figure 3-1. ART2 Software Components
Users interact with the GUI. CART and NART executables sit below the GUI
and are transparent to the user. Messages propagate from the GUI to the
NART via CART, which controls the WiFi card. The appropriate responses
will be propagated up to the GUI from below. Responses may originate
anywhere below the GUI.

Using the ART2 GUI

December 2010
3-1
El Chapter
ART2 GUI requirements include:
The ART2 GUI is designed for use on AR93xx designs only
The Microsoft .NET Framework Version 2 must be installed on the

computer running the GUI. H .NET Framework Version 2 is not already
installed, run the executable dotnetfx.exe provided in the ARI'2 GUI
package to install the .NET framework.
To Run the ART2 GUI:

1. Start the GUI by executing artGUI.exe in the \bin directory.
2. Plug in one of the three WiFi cards: OUT, golden unit, or Client2.
3. On the GUI sc~ choose the corresponding Load Card.
NOTE: Prior to running the NART GUI, ensure that there are no CART or NART
console windows opened. During initialization, the NART GUI opens these windows
and minimizes them. Upon exiting, these windows close automatically. However,
after abnormal terminations, some console windows may remain. Any windows left
over must be closed manually before starting the NART GUI.
Jn;tial Screen
Upon execution of the artGUI.exe file, the initial screen is shown:
l.OOY~
CIO
IMlTI ALIZArlOll 111'
~ Pl.MS&.
*11'
&103 1111'0 ComMGWCI w ooot.rol prooe11a on

loaalboat ~318
6102' nao Producu.J a t.. ref bui been la.dmd
1002 UDO cc-and flle " at.art art. opened t
315,968
1'7002 nao ca...nc1 f lle
\ \OOllmillnd
\ta.t. f109 n...,a . art opeaecl e t. Jest968
1000
lwo Cc-.acl tu. \ .
\OWllMDd
\teat f109 u_,a . art QIDlllP14t.ed e t l9WH

a.i..p.ec1 t.1- . . . H . .
11000 l lll'D ec-ud flle a t.a.rt . art OOl!pl~
a t 315CH . Slap_. U.. . . . l6 4048 lllPO 111UDone .
IWITIALllArlOlll DCllS Pl.&ASS , CCllllNU&
WfkC11t toART?!
Figure 3-2. Initial ART2 GUI Screen
3-2

December 2010

Chapter
EJ
The initial screen is divided into:

Controls for Loading Cards The application supports up to three clients. The middle of the saeen lists the three
(gray-shaded area)
supported NART clients. The heading IP Addresses lists the three combo boxes that
c.an input the IP address of every client. Each has a Load Card button to press to
load the card after it has been plugged in and before any tests can be run.
LogWmdow
(green-shaded area)
The log window displays important data and/or messages for the user. The log
window always remains visible no matter where the user navigates to within the
GUI.
Controls for Choosing Tests 1\vo main controls select operations and for navigating the GUI. One is the
and Operati.ons (left side hierarchical window shown on the left hand side of the screen (see Figure 3-3). The
and top of the screen)
other is the menu bar at the top of the window. See "Hieran:hical Screen".
Hierarchical Screen
The hierarchical screen is laid out to show: Home, Tests, EEPROM, and
Registers. Click on each to open a new set of controls in the middle of the
screen, named to describe what type of operation it makes available to the
user. For example, Load Cards allows users to load cards. Opening a page
displays a new set of controls to allow users to execute operations such as
tests, read/writes, etc. Users can navigate between pages to reach more
functionality. Figure 3-3 displays the categories of the hierarchical screen.
rnrEJ
.if Alh uo1 Radio lcs l 2 (A.IU:l-C.iUI)
...
..'''"'""'
_
T"-'
r"""cm
lltQstetS
t
...................................
. . ........
ttT1U.UATIOS
PaOOU SS .
.Pt.EASE . tT
5 103 llll'O COllP9oted to paat.rol proo -
on
local.hon 2')99 .
6 102 uro rocluou.J.ait Z" :f bu ~002
nro c - . . t illo start . u:t
loaded
opened at
1~2JUO .
3001 Dl'O 11Hded c,.W.,-Dt coat&:ol llbruy J.m

~ohdeesc-a...ri 11RP- r11 rrcm nrpdt . d.11
3009 l FO fomad. p1M9r - t r R.ohde&Sct.Mr2
u -111.
1001 lllFO Laded .,..tw-nt dOntral library fm
Aqilant: 11111& f'r- lt1tJ. .
1010 1wro rouml attenuator &qillent 111 llA for
~o.
J010 uro round att.....tor &C)ilent 1.171.lA
~ar
~1 .
'3010 UFO FOWMI ttonuator &p.lcnt 1111la f ar

........ 2
~oo? nm c..-.nd Ul
. \ ,. \oa-..ntl\t- t flaw flap . rt opened t
~2621101> .
:iooo imro comuml file

\ .. \oOlmtlncl\t-t n .. n .,.. ast
'174128011 . u . ...... u - 16 -
1000 uro c......t l i l start art
:i26280f.6. &J.ap ed u- ...... 905 ~172 Ul'O l n1U.aliuUon cOllpleto
ooeplld t
oollpl.eted at
We.J.U.n9 tor
~-
Figure 3-3. lntttal ART2 GUI Screen, wtth Hterarchtcal Screen Displayed

Using the ART2 GUI

December 2010
3-3
EJ Chapter
Menu Bar
The menu bar is the set of options available to the user at the top of the screen
via pull-down menus in Figure 3-3, including these options:
Menu Bar Option
File
Setup
Test setup or card setup operations
Clients
NART client-specific operations
Tools
Operations related to calibrating a card
Equipment
Equipment related operations
Advanced
Advanced feature, usually password protected.
Help
Tools available to the user
Calibration
Wmdow
3-4
Description
File operations

December 2010
Operations related to the log window

Help options
Chapter
EJ
ContTx Screen
Open the ContTx screen by choosing Tests > ContTx from the hierarchical
window. The ContTx screen provides the controls to put the WlFi card in
continuous transmission mode. Figure 3-4 shows the ContTx control screen.
~-
Ocrts lcds 'ibfaitb'!.
3 1bneo
~ Test~:J C~m!s
COfltTX
Lril:
r:.:=:
---
f~~re &c!v~ 't{pc!Ot.'1 ~
1t.$1PAA./..~rfl't5(LCCllON
f.recency
llZ<il~ .,]
11..lte:
@ txQ.l'i'l:
l:!.._______:::
l.tQl)('f
O txpows:
:.tn,F f~'1.1tlt ,-,...Cr!()H
0'r:-..aerO"""" Q o.,;a
"'
l rWdfl'IOdt
0(0.o~ 0'6-IQ"ec.crr~
b~dl~N
(l'Jc7;(t.1J1d\l ,d'\2
G!Se~
Pk.et~
~ y
~erfrtr"<O~
O nar~
:ir
lswrt T14f'Ofll l
0 Cl.99
Ot.<100
FAAN'IETER COOTP..
NO TRANSMISSION JN PROGRESS
I
hr
Rat:t:
I
:?412!+!:
1Tx?\o.r: L___,
lfG-S- MbpsOft+1 1rxGs,...- ~
Figure 3-4. ContTx Control Screen

To retrieve the latest full description of the transmit command, type help
transmit at the CART comm.and line.
To start transmission, press the Start Transmit button. The controls provided
on th.is screen include:
Control Set
Description
Parameters (e.g., frequency, rate) that can be selected for testing

These controls provide users the ability to set the frequency, rate, Tx gain, or Tx power the
card can transmit at. These paramete!s can be changed while the card is transmitting. To
become effective, they must be committed by pressing the Commit button. Note that default
parameters are aJready set up and are shown in the Status box at the bottom of the screen.
Setup Parameters Card and setup configuration parameters such as chain mask, ifs, etc.
These controls allow the user to set up card parameters. The user can also choose the
transmitter card.
Parameter Control Access to test parameters during transmission
These controls allow the user to change the test parameters dynamically while the card is
transmitting. This means that the user doesn't need to do anything to make them effective.
Status
Cummt test parameters set
The status controls change automatically to display the current test parameters.
Test Parameters
The ContTx window shows three buttons: Commit, Start Transmit, and Stop
Transmit Only the buttons that are relevant are available to the user.

Using the ART2 GUI

December 2010
3-5
El Chapter
Link Screen
Open the link page by choosing Tests > Link from the hierarchical window.
This page provides the controls to run a link test. The link test requires two
NART clients to be set up.
--
...
-- --
Corfll)I
~~~~~~~~~~
...-
...
....., .....
!Cl
f'll""'9r.
'""
.........
........
ltpom
"~ ~
b: Ox'1dl0,d\l.dll
!!bi; 0,.7'; d'(l,ch1.o12 ..
.. .
""""""'
"''"'
NO UNK TEST IN PROGRESS
Figure 3-5. Link Test Control Screen

Figure 3-6 shows the link command.
';: fQ][>c"
.if Athero1. Radio Tesl 7 (ART7-GlllJ

~ ~ti.o~
"' ......
""""'"'
""""'
""
"'""""
""""""'
loc;b,
~~lien
tq,,pn-, t
$.:lv~ed
tieb
2"1UPP~W
{lSIPAAAl'CIW
ftt'1'""Y' ~vj
.....
~ feits
--!"'
l~t
fk f'OIMt:
IJ ~g.xy
:j
lo
Al.let~:
.......
8 Recbtert
0 """' O"''
0 W1
O""" O Oi:nt>
a.,..,
UN< Tai IN PROGRESS
Ulll
gef,'.edc
0 ' -v
Q lff ~
Q H12G,'liMO Q Kl <\O
fu~k.c diS!t
Tic l O;lc1: d'f.l,-:M,cha ..,

lb ~
STATUS
rransmtteir
0 W1
0.:7. d(l,.c;M,(fl2
0 1\.:.""sk
?tt.-;,iotcf't!o~
~l't Ccut
0 Atun.itt ~ <Olltll
~v
"""'
o0 ""'"""'"'''
........
I AOt-~ l*~sl
'
....................
"" -
IH
....,..,i...t-
Llg TElr UPORT
Ha
2U2
6
100
USI
1100 tllf'O
2U2
9
100
SI
2U2
12
100
c~ ln
2U2
18
100
,.
prOll,P"
2U2 2U2
21
l6
100
100
SI
Try pu.a
,.
2 1.12
18
100
H
,.
,.
21.12
100
C'Dftttiw.
prot" lng.
2 1.12
11
100
12
or
21.12
2J.
100
op
H.12
2S
100
2 1 .12 2U2 2U2 2U2

H
SS
111
us
100
100
100
100
n
52
52
SJ
SJ
report c,-, . _ . . i tp.1eu9d for ltr
Figure 3-6. Running a Lfnk Test

To retrieve the current full description for the link command, type help link
at the CART command line.
3-6

December 2010

Chapter
EJ
Figure 3-7 shows a throughput test.
.....
lodCttdl
~ '""'-''
....
11!:!!1
r;J feprom
....,..,,
Opttlbon~
............
rtST>AIW1"fRS
FrtOAnCY:
~;
~tmO
O tll.~!
XI
tllpo.;
~OC1t1:
"""' ......
nc: OIO:d'IO.chLd'l2
....
30
L f9t(Y
a,,,.,
'"
"""
"
" J_
_.....,.
o HTlO
..... HT20,Hf4J
AX! 01r1:dl),di1,ct.2
.... ...... ... ...... ....

....
-..
..
-1--..........................
_:: ..::
..,._
-. -......
"
---- . ... _
.........................
..::.. - .. .....
......
-...-.. ,.,.
-:; ::: ::::
....
-;: ..:!
Kr4J
R.ltlf ....
""""""""
,... .
HH
11
HU
.._,. ,,._,
~:
,,_
._
...
..........
--
STA'IUS
H lJ
H I
U
II
.a
" .,..
'"
""
itet
_..,.
.........................
TPUT TEST IN PROGRESS
-:! :--:r:
... ., ...
.
-::!! :: ......
- ..... .,,
-==
.........................
-n-
........ .. ...... ... ....
--....
... ......
::::: .... .. ...
--
I 11111
HU
HU
"
..
":
Hilt
. .H I-
i:
H U
"~
7J
"' "
HU
Figure 3-7. Throughput Test

Figure 3-8 shows the link controls advanced parameters screen.
Other parameters
Log window display preferences
Rate interleaving
0
0
0
Stats
0
0
0
no rate interleaving
interleave rates
single rates
GI Settings
@ long (BOOns)
collect Rx stats only

collect Tx stats only
collect Rx and Tx stats
Raw data logging

O short (400ns)
OK
] [
disable
enable
Cancel
Figure 3-8. Advanced Parameters Screen

Using the ART2 GUI

December 2010
3-7
El Chapter
EEPROM Operations Screen
Open the EEPROM operations screen by choosing EEPROM > Operations on
the hierarchical window. This page provides the controls to read from and
write to the EEPROM.
...
~ NotwAtheros Radio Tt:i.t(HART--Gl.IQ

~
s....
,...,., ,
<llbr.thOr'I
......
Hom<
Ii' '""CGtith
.,_,
arr
"""
,...
....,,
~,.~.Mi
e t19rom
"""'
....,..,. .,...
ftesCl;ifftP'Oll.
~@~@
....m>U-
"'
,>D'.lilol.Qil
..,_
,,.
.
1- -..- - 1
1- ............ 1
v-..:
E::Zl!::I
Jtcgt.ttcrs
Ollw ooer'W
lte.st.\'t1l:e OpiHbors
l oadCrd'
.........
~Med
q...Pft'ltnl
"'9'1Pl"-
....,,
. L """"==i
YM:
~@
Figure 3-9. EEPROM Operations Control Screen
Figure 3-10 shows the EEPROM contents.

GJQ
A1Jy.~ ro.R.dd10 lnl l(JIN I J-tilll)
,.
IOI 1UO nro

JOI J\10 ID"O
(OJ JHO lnl)
101 1sa nrro
(01 1510 Hf'O
I CAL Vllrldomi
101 1no urro
101 1 510 ..,,
I MarAddre
0.00 OJ Jr U
IDJ 1\10 IUO

101 .,510 ln'O
'IX1!419k
Oprh. . .
..
101 1'110 lff'O

101 JUO IUO
111.-ie Se n20
101 1uo nrro

IOI 7510 UIFO
101 rno 1uo
101 1510 llfnl
101 1no nrro

(01 1510 Hl"'O
101
ruo ,..,..,
IOI JUO llfnl
''"'
101 7"10
101 1510 llrrO
101 JUO IUO
101 JUO 10'0

JOI 7UO tlr'F'O
101 1uo urro
qnnnH~n~~NnM~nu
10 urn
101 1uo nrro

IOI l'UO 1..-0
101 JUO llSR
IOI JUO 1..-0
101 1uo nrro

(01 1!110 IU'O
IOI UlO IUV
101 1UO IH'O
..
------------------------------------------------------------------....., .,
etDOMtn
,
"""'
.....
1
'"'OM
1
Pia.bl SCI ft410
l
lndin
.,. sia..
1
PeiH C p
Tt.uft9 ca.. co, l) 1
....
.....
0
0
- .
--
91fD-.&D 7
lnt.arnal ret'llatM'
Ant Chain 0
Ant C'baln t
-u-
a.att..,. DI dtO 1.ow

x.tt- 1111 C'h2 Law
UI C'hl
- - D C'hO 91...
x.&U.. . lI C'h2 hi. .
-.u.. 1Har'191nO LDlil
ten 1Henji.n2 LUM
(00 . 00)
1>.1.W. 20 r20
01....1. :zg Jl1'40
tllli;e oa Ni.rele9
ah1l-U1
__ _....
-tt-
....--
GPIO eeptfrite ltnbleo

PIO Mlen N lll
101 JUO 10'0
101
r..plau ._.al.on
l'J to
....
l'CU
lnbl c ......-auon
OP lO r d.... teleeottcm
eHO "'1an UD
....-r..weou....
0.00000000
Odd
......
our
Sftz Nodal
.....,.
........,.
19
19
....
....
0x00041HH
0.0010
lat. . . C - 1 '
a.t C'tNJ. 1
aau. . Im ch1 i.ow

lD9 CbO
1119 Ch2
sat t - 1J)li C'h1 Ml...
a.ti-
-u-
lltu'...1
sat - llkrqlnO
a....
...
...
19
19
lt
Figure 3-10. EEPROM Contents
3-8

December 2010

Chapter
EJ
Utilities Screen
Open the Utilities screen by choosing Registers > Utilities in the hierarchical
menu.
t~fgj~
..if Athcrcn Radio TK1 "J (ART? CUI)
.. -..
.... <Nd<
tl l ftl:',it'i
0M
tjf~Ctl\
fil P.elW.erS
!tZll
LogWadorr'
RMl#Wrtt ODt'tKltlt
1t:t ...-SWl ~t;lrQ1\'io~ lTt
Adcten:
v ]
y.,_,,,
llohdeSlc hwart DP S11 lraa ~ll dll

f009 l FO F ound pQIWm' - lr Rohdd.Sdmarz
RP Zlt
~~ 1 .,....00.,1
JOOl llf'O LNdecl llC(W.p-L control

AqUent 11713A f'r 117Ua
3010 HIFO r ound ttenuat.or Agilent
chain 0
3010 1 ro r ound att...at.or A9ilen~
chaa 1
3010 t ro r ound tt. . . . tor ap.lmat
1:h&.ln 7
1007 tro c_.nd Ul
. \ . . \o~\t-t flaw flve rt
1 l0t 6UO.
7000 Jlll'O c - o d Jla
, \ \o-.nd\t t. Daw Oeqa. art
13144781 l..-4 u - ... ll -
1000 uro c - . d ft.1 tut . .rt
73tt6l96 ll.p edl u ........ 781 1112 IllFO JnlU.a UaaUon oomp.l.ota
fll0.()91,fi\Of.1,,A,l l t
v1
fllltld:
C\l
5103 1ro Cannltl't ... la ttant.rol 1Rtt no

l.ooa.lho t t 2lt8 .
6102 Jlll'O Prodactl..lac r d b.11 Ileen l.aact.d
1002 Jllf'O C'-...cli ti.lo t.u-t . u t opened t
1JH60U
3001 i ro l.Ncled. eqW.p-t c:ontrol l.J.bzary for
Q G<ldon Q ci.,..>
v""' I
I
~~ l -oo., I
USt of s-Ud(y liQkls: and n:igiSters:
.-.
lJJuary for
11113& far
llll.3& foe
11113& f ar
optmnll l
CG911"lttl t
~td
at:
WUUDg tor
..........................................
IWITIALI ZATJ08 DOllE , , PLEASE
C'OHHIB
l ~UO
HFO c..-tYrlan. 2. ll , cuuuildl>.te.

~101.lllr C aa:tau.l.lcrn.. 133000
Figure 3-11. Utilities Screen
Menu Bar Pull-Down Menus

File Menu
~~ Now All>c
rt (
Equipm nt
Home
Cortlonbon
Nut locatton
Client
ourcoi
Advanced
IP Address
loc.lllos1
Golde1 (tl
0en12 m
I Loodcard
I Loodcard
I Lood card
NM cmd conrole
togwr.dow
Gui aerver llabtning'
Figure 3-12. File Menu Options

Option
Description
Home
Returns the user to the Load Cards page
Cmd C011SOle
Exit Application

Spawns a command console

Exits the ART2 GUI application
Using the ART2 GUI

December 2010
3-9
El Chapter
Setup Menu
. I
Loodc..d
[~]
I l.oldc..d l
* INITIALllATIOll IN PllOm&q
Figure 3-13. Setup Menu Options

Option
Description
Pathloss
Enter setup path losses (overwrites defaults from start.art)
Change Startup
Script
Pushes a new startup script (similar to stut.art) into CART

without exiting the application
Client.s Menu
~ New Athetos Radio Test (NART-GUI)
File S~up
CliM~
e Home
Tcols
lood
Unload
qi-Tests
dJ-~cprom
I Rtgisttrs
Info
Catibratic.n
Equipm"'t
nt
{O)
Advanc~
IP Address
lo<atlost
(I)
Hello
Window
H!lp
I LoodCNd I
I LoodCNd I
I LoodCord I
lOQWtndaw
I NIT IALIZATION IN
Storage
Figure 3-14. CHent Menu Options
Option
Load
Unload
Info
Hello
Storage
Description
Loads the card
Attaches the host to the card, reads the bus to discover the card device
ID, then loads the appropriate software. Load must be performed prior
to using a card.
Unloads the card
Detaches the currently attached card. Unload must be run before
removing the card.
Provides basic information about a plugged and loaded card
Pings all clients
Sets the storage type on the card before loading it
auto
Enables an automatic detection algorithm
EEPROM
Indicates that the storage device is the EEPROM
Flash
Indicates that the storage device is the fl.ash
OTP
Indicates that storage device is the one-time
programmable (OTP) ROM
To retrieve the current full description for the any of the commands on the
Clients menu, type help [CommandNameJ at the CARI command line. The GUI
Help menu will access the command help descriptions in a future revision of
the software.
3-10

December 2010

EJ
Chapter
Tools Menu
File
Setup
Clients - - - ' ' - - - - - - ' - ' -..--.
9 Hom
r&
Run script
mm
r ..
1.
Sondcmd
I& Eeprom
- Registers
toowmow
I toad card
I toad Gord
I toadeord
Open script
WnteoS<npt
JlflTIALI ZA%JON Jlf
Gui -rver liatening' .
Error display priority

CntlMsgsON
5103 INFO Connected
Show Cmd Lin
Figure 3-15. Tools Menu Options

Option
Description
Allows the user to select a script to run; enter script name

Allows the user to select and open a script for editing; enter script
name. Refer to Chapter 6, "Sample Manufacturing Test Flow" for script
examples.
Opens a text box for commands, similar to a command line interface.
SendCmd
Whatever the user types will be sent to CART, unmodified, as a string.
Error Display Manage errors displayed on the log window. See Figure 3-16 for the
options on this dialog box.
Show Cmd Llne Shows the command that was sent to CART
Run Script
Open Script
P. Enor O.SplayS.oct1on
n.. dalog ..rom you ID manoge tho cls?<rY of"""' type, and codes.
AU orror message t"ypes ond code; ore cisplayed "'1ess olllenYise ildi"'ted here
Gcncrol
General Error Display Options
~ IJlsPay all error messages
~ Dis?aY default error mes.sage~
~ Q;si:lay yo<o
selected <nor messages
i:.J Display ro emJt me<soQ1!$
Error Types
Error Codes
Che<k 1110 Olll>"oe>ile error type lo keep me$$090S

of dial cype from displaying en the log wiidow:
O>eck the ..,.,,opriote error CJ>de lo

d<Sable Its cisplay on the log window:
INFO
WARNING
1002 Paiseloot"liW'ly
1003 P~cgotivc!nocment
ERROR
1001
P.r-~osrtivclncrcmcnt
1005 Par.:~1il'Wnu'n0ednal
1006 ParseMaxllTU'TlDecinal
1007 Porsel>IUWnunllex
1008 ParseMaxmvrliex
1009 ParseM'*'111nDcuble
1010 ParseMaxinvnOoWle
!Oil ParseError
1012 Pr..eH""
1n11
OK
II
r.w
CMcel
Figure 3-16. Error Display Dialog

Using the ART2 GUI

December 2010
3-11
El Chapter
Calibration Menu
IJ-l' New Athetos Radio Test (NART-GUI)
Homm
File Setup Clients Tools
1-------'...:..----..,
Strt
Trns
E<prom
- Rogistors
Stop
Loadc.td
P1u~
load Cord
Continue
load Cord
I N IT IALIZATION I N PJUJGRBS
Ttst seltttions
./
Show script dilog
./
Show crd ID dialog
OU1 erver lleteldaq
5103 JNIO Coaneatecl to con
Figure 3-17. caHbration Options
Option
Description
Start
Selects a calibration script to run
Stop
Stops a cah"bration script
Pause
Pauses a calibration script
Continue
Continues a cah"bration script
Test Selections
Sel.eds/unseled:s tests to run

When checked, this option prompts users to run a script.
When unchecked, the application runs the last script that was run.
Show Script
Dialog
Show Card ID
Dialog
When checked. prompts the user to enter a card ID (SSID, RBFname,

etc.). When unchecked, the application does not prompt the user.
See "Sample Manufacturing Test Flow" on page 6-1.
Figure 3-18 shows the cahbration running in the log window.
CUll UTT09 l I U
l . . . .. . . . . . . . . . .
l _ . .rimD l lll'O LoMffl ctU'
20 . ....
M>14
M>H
f or aart lJ
lln9I'
~
er..i .... -
l - . it
911uKRm
en9r
t014.
l . . . .1 . . . . _ -=r'm' Wl14
001 IDO GCMMI UM t ttOI
OOJ l90 . ._ _ ttaleot t.t Joy
OOJ lm'O
1 H ID
J l m'O
l
re fllt
OOJ lm"O
'J U......_ 1. - i
20) 1111'0 PIM . . . .ly a val
fei HiUJ D...l'CID'l'Jp9
(li-..:dllrl'yp9)
20\ 190 n.llk yau f K' ....aP-1 ta. n 1 - 2 fm: wad ..abl l oardllny . . ..
201 1..0 P I N -..iv ...... ror rtdal u Mra.1. 1191
( a t .......L411Ml)
H S . . . ,,...... ,... f'..: ...... Fl-I ~ n~OJO 00001 fur
rt
lm"O k f ...... . - D U2
aua.r-1.. ....
to, _.,.,.
l .O .....f_lll. . . . - D 1ll
.,.._._...... tot
, ...... .-.- ....... 'u
1.-0 .... u.. , .._, ro1

cont ta: t . .t t.rt cid u 813H U8,
l1 19"0
H
1. . 0
C'ont t t st u .a.._. t e1 111091

t t ...., ... t. e 1111H o
t.t. f lai..._. t H lltl211
Jl I DO C'Clllt tit
l l m'O C-t u
OO J 1. 0
........12
............12
.........
H17
Ht2
He?
.,,,,.,
1 1 1. 0
c-t
aa . ._ . u -
- nn -
. . . ._ . t . i - -
fl? -
_.... -. ......_,
" -
.'
..... ... ....
... ..
"" ...
u
111
20 . 0
1S
.."
-t trt_. . t a111e no
11
.
13
1J, )
ll
WIDJ.t gll
-..... ...
111
............
m
Figure 3-18. cat;bration Being Run
3-12

December 2010

Chapter
EJ
Figure 3-19 shows the panel that appears when Test Se1.ecti.ons is chosen from
the Cahbration menu. This panel modifies the options set in the
test_flow_flags.art file. For more inform.ati~ see "tesLflow_flags.art'' on
page6-11.
~ Test selections
rn~
ALL TESTS AAE ENABLED BY DEFAULT.
Select those tests you wish to disable or modify:
L~~:~~f.~jjSG TESTS iiPOWERCALIBRATION 1

Tx Power Chains Option
Tx EllM (Litepoint)
0 Sin~echilln
0 enable
0 disable
O AI chains
Tx Mask
Tx Channel Accuracy
enable
enable
0 disable
0 disable
Pock.et type
Unicast
0 Broadcast
Rx Sensitivity
0 enable
Tx PER
Tx Throughput
enable
0 disable
enatle(no p/f J
RxPER
Rx Throughput
0 enobl6'
O c!isable
Q disable
QK
enable
0 disable
enable(no p/f)
J [
0 enable
Q disable
~ancel
Figure 3-19. Test Selections Dialog
Advanced Menu
IJ.:' New Alheros Radio T.st (NART-OUI)
Fil
Setup
Clients Tools
fHoimm
+Tests
Etprom
- R<gistm
Golden ( I)
Clont2(2)
Oi.. ble advanced test>

Beam Forming
Test
Figure 3-20. Advanced Options

Option
Description
Enable
Prompts for a password to access advanced features
Advanced Tests
Disable
Password protects access to advanced features
Advanced Tests
Beam Forming Beam forming feedback for regulatory testing pwposes
Using the ART2 GUI

December 2010
3-13
EJ Chapter
Window Menu
File Setup
Clients Tools
Hoiim
Save- log window to file.
losts
Colden (I)
Eeprom
Cl<nt2(2)
- Rogistcr>
Figure 3-21. Wtndow Opttons
Option
Description
Clear Log
Cl.ears the log window
Wmdow
Save Log
Saves the log to a designated file
Window to File
Help Menu
~ Now Athe<o Radio Test (NART-GUI)
Filo
Setup
Clients
Tools
t;i- Hom
~
dJ
mm
locahost
Tosts
Goldon (I)
Eprom
Cliont2 (2)
._ Rcgistm
Boords Supportod
About ART
loadG!wd
INIT IALIZATIOll I N
5103 INFO Conneoted to oon
Figure 3-22. Help Optfons
Option
3-14
Description
Boards
Supported
Displays a list on the log window of the boards supportEd by the

application
About ART
Information about the application version and build date

December 2010

Chapter
Using CART/NART Command
Line Interfaces
This chapter provides information on using CART and NART in a command
line interface environment, and discusses the following:
CART Command Line Control
CART /NART Startup Options
NART and CART Commands
Reporting
Getting Online Help

Using CART/NART Command Line Interfaces

December 2010
4-1
D Chapter
CART Command Line Control
Figure 4-1 shows a configuration in which NART is controlled through the
CART command line interface. 1his configuration allows up to five NART
instances running on either PCs or APs. See the sections "CART/NART
Startup Options" on page 4-4 and "NART and CART Commands" on page 45 for information on using the CART command line interface. 1his
configuration is used when access to commands and parameters not
supported by the ART2 GUI are required.
.................................................................
Test
Instruments
.....,
Optional 5111 Radio
Optional 2d Radio
NART
' +.
NART
WiFi Device
Driver
WiFi Device
WiFi Device
PC2/AP
PC1
Up to 5 NART setups ore ollowed
Figure 4-1. CART Command Line Control

CART accepts typed commands from the user, interprets these commands,
and then sends the appropriate commands to multiple NART processes to
perform the requested tests. Normally, CART runs in a command window
and accepts user entered commands from the keyboard and displays the
results in the window.
The NART processes may be run on the same PC as CART or on a different

PC. Because CART and NART communicate using a socket, the remote PC
can be any place in the world accessible through the internet. The typical
setup runs one instance of NART on the same PC as CART to control one WI.Fi
card and a second instance on an adjacent PC to control a second WiFi card.
NART may also be run on APs to control the WiFi card in that device. On PCs
with multiple interfaces or APs that support multiple WiFi cards, multiple
NARTs must be run, one for each radio. CART can control all of these
configurations.
NART must be started on every PC or AP where a W:iFi card is installed that is

ready for testing, and CART must be started on the PC through which input is
entered.
4-2

December 2010

Chapter
See "Installing and Running ART2 for a STA Card" on page 2-2 for
instructions on how to start NART on a PC. See "Using ART2 with an AP" on
page 2-3for instructions on how to start NART on an AP.
The PC system used may have been configured with a CART icon that runs
the file [ART2 release directory]\bin\CART.bat. If this is the case, double
click on that icon to start CART. If not, start a new command window. Change
the directory to [ART2 release directory]\bin and then start CART.
If the local directory contains a file called start.art, CART reads that file and
executes the commands contained in it. Any CART command can be included
in the file start.art. The ART2 release contains an example start.art command
file. Typically this file contains instructions on how to configure the test
equipment and the software. An example start.art file is described in
"Start.art" on page 6-8.
CART must know where to find the NARTs to use. The command that
performs this is connect. One connection for each NART or WiFi card is
required to be used in tests. The command connect accepts three parameters
as described in the following:
help connect
connect: establishes a network connection to the nart process
instance, device: which nart
dut [OJ
golden[l]
blocker[2]
host, computer: the name or ip address of the computer running nart
type=text; default=localhost;
port: the port number used by nart
type=unsigned; minimum=lOOO; maximum=65535; default=2390;
The simple command connect connects to the NART on the same PC as CART
and designates this NART as the device under test (OUT). The command
connect instance=golden; host=l0.10.13.20; connects to the NART on the host
using IP address 10.10.13.20 and designates this NART as the golden unit. The
command line arguments -dut [host]:[port] and -golden [host]:[port] may
also be used to make the same connections.
Online documentation on all of the commands and parameters is available
using the help command.


December 2010
4-3
Chapter
CART/NART Startup Options

The options shown in Table 4-1 may be appended to the cart command when
initiating the program.The options shown in Table 4-2 may be appended to
the nart command when initiating the program.
Table 4-1. CART Startup Options
Option
Description
-blocker [host :port]
Connects to NART on the specified host and port for the blocker unit. This
command line option is equivalent to issuing the command connect
instance=2; host=[host:port];
-command
Prints commands received by NART, followed by the normal output from NART
-console
Tums the console window output off
-dut [host :port],

-local [host :port]
Connects to NART on the specified host and port for the DUT or local machine. The
host can be any available host name or IP address on the network. If :port is not
specified, NART uses a default port. This command line option is equivalent to
issuing the command connect instance=O; host= [host: port] ;
-golden [host :port),

-remote [host :port)
Connects to NART on the specified host and port for the golden unit or remote
machine. The host can be any available host name or IP address on the network.
If :port is not specified, NART uses a default port. This command line option is
equivalent to issuing the command connect instance=l; host= [host :port] ;
-gui [host : port1
Connects to a user interface process (console input and output is disabled)
-help
Prints the command line help message
-log [log file name]
Directs console output to both to screen and a specified file
-port [port number]
Opens the specified listen port and waits for connections from a control process
-start [command file]
Executes commands from the specified command file. If none is specified, uses the
default file start.art.
Table 4-2. NART Startup Options

Option
Description
-console
Enables logging of information on the console
-help
Prints the command line help message
-instance [device index]
Opens this device on a system with more than one WtFi radio
-log [log file name)
Enables logging of information to the specified file
-port [port number]
If NART is started with narl -port 0, it accept commands from the console.
Otherwise, specifies a port and waits for a connection from a control process.
The default value for port is 2390.
-start [command file]
Executes commands from the specified command file. The default file is
nut.art).
4-4 AR93xx ART Reference Guide

December 2010

Chapter
NART and CART Commands

This section describes the format of NART and CART command input and
output.
Command Conventions
All CART and NART commands start with a unique command word. This
word may be followed by a variable number of parameters and values
specified with a name followed by an equal sign, the values, and finally
ended with a semicolon.
The syntax for a command followed by two parameters and their values
is:
command parameter=value; parameter=value;
A list of parameter values are allowed for some parameters. Values are
separated with commas, as in:
3. 4, 5, 6
Ranges of parameter values are allowed for some parameters. Ranges are
specified as low:high:increment, as in:
30:40:1
Mixing single values with ranges of values is allowed, such as:

f=2412,2452:2472:5;
Increments can be negative, such as for ISS sweeps, which are generally
performed as:
iss=-50:-100:-1;
Every parameter expects a value of a certain type. The expected type is

listed in the online help documentation. The value supplied is interpreted
as a value of this type.
There are three types of integer parameters values: signed decimal,

unsigned decimal, and hexadecimal. The expected type may be
overridden by supplying a type code in front of the values:
x or Ox forces the parser to interpret the supplied value as
hexadecimal.
-
u forces the interpretation to be unsigned decimal.

leading + or - forces the interpretation to be signed decimal.
No code is interpreted as the default type
For example, x10, +16, and u16 all result in the integer value 16 being
stored, no matter which input type is preferred. But the input 16 will
result in the value 22 being stored if the preferred input type is
hexadecimal or 16 if the preferred input type is decimal.
Some parameters may have a default value that is used if none is specified
on the command line. The default values are shown in the online help
documentation.


December 2010
4-5
Chapter
Some parameters may enforce a minimum or maximum allowed value. If

a value that violates these limits, an error message is printed and the
command is not executed. The minimum and maximum values are
shown in the online help documentation.
CART maintains a set of local variables. (NART does not have this
capability.) Some of these local variables are created automatically when
CART begins execution. Others are created when a set or get command is
executed. Additional local variables may be created with the assign or
prom pt commands. The values of local variables may be used in any
command by preceding the local variable name with a$. For example, the
command tx frequency=$x; executes the tx command with the parameter
frequency set to the current value of the local variable x.
CART is capable of reading files containing commands, which may

include branch statements. (NART does not have this capability.)
CART treats any command it does not recognize as a potential file name.
It opens the specified file and then attempts to execute commands in the
file.
Two additional commands allow the creation of conditional branches in

command files. The command label name=[name]; specifies a name for a
particular line in the file. It does not take any other action. The command
branch condition=[equation]; name=[name]; transfers control to the
specified line if the condition is true and proceeds to the next line in the
file if it is not true. The standard manufacturing test flow described in
Chapter 6, "Sample Manufacturing Test Flow" makes extensive use of
these two flow control commands.
Some parameters allow special named values in addition to numeric

values. Either the named or numeric value may be used. The special
named values and their numeric equivalents are described in the online
help documentation. See Appendix A and Appendix B for examples.
Consider the following, which lists one parameter for the connect
command:
dut [OJ
golden [1]
blocker[2]
For this parameter (which incidentally has two synonyms), typing

connect instnce=blocker is the same as typing connect device=.2, and
sets the device to blocker.
4-6
Command names and parameter names may be specified by giving the

minimum number of letters that define a unique command and/ or
parameter. Some commands and parameter names contain multiple
words delimited by periods. When typing these names enough characters
to distinguish each individual word must be furnished. For example the
input 2.t.p is sufficient to identify the parameter with the full name
2GHz.Target.Power. In addition, a few commands have short
abbreviations that violate this rule. For example, 1 (lower case letter L)

December 2010

Chapter
means link even though both link and load start with that letter. The full
descriptions in the online help contain both the abbreviation and the fully
spelled versions of each command.
Some commands have synonyms, as shown (for example, load, card,

attach). All synonyms are functionally equivalent to each other.
Results Output
CART and NART typically responds to commands with messages. All
messages have a 4-digit error code, a type or severity, followed by the
message contents.
Usually, all of these fields are shown in a single line of text. The error
command can change how messages are displayed. It is also possible to
enable a warning sound or force CART or NART to pause and wait for the
user to read and acknowledge the message before proceeding. See the online
help documentation for more information on the error command.
The 4-digit code identifies the message, which can be helpful when
investigating errors. The following indicates the error severity:
ERROR messages report fatal errors, which indicates that the requested
command has not been performed.
WARNING messages are less severe. The requested command is

performed, but it may not do exactly what is expected.
INFO messages provide information that was either requested or deemed

useful by the program.
CONTROL messages, which are not normally shown, provide additional

useful information about the state of CART and NART.
DEBUG messages, which are not usually shown, provide even more
information about CART and NART. Viewing the DEBUG messages is not
recommended for most users, as the meaning of messages in this raw data
stream is not always clear.
If a command produces data, data messages are returned. There are two kinds
of data messages: headers and records. The header message indicates the
names of all of the fields in the data records. CART & NART output one of
these for each type of data the command produces. The data records contain
the actual data values. The number of data records may be quite large,
depending upon the complexity of the command. For example, if the
command instructs NART to transmit at multiple rates, NART outputs one
header and then a data record for each rate.
Data messages are a single line of text representing a data record. A special
character demarcates the fields in the record. This character is the first
character in the line. Currently, NART returns data messages using a vertical
bar (I) as the field demarcation character, but this is not guaranteed. The
parsing rule of using the first character on the line must be followed.


December 2010
4-7
Chapter
The following are two sample data messages, the first is a data header and the
second is a data record:
7505 INFO
ltxlfrequencyltpltxchainlisslattlpdgainltxgainlratelpllpclaggl Icorrect
lthroughputlerrorlfifolexcesslretryldretrylrssilrssiOOlrssiOllrssi02lr
ssilOlrssilllrssil2ltxgildacglbyteldurationltemplvoltl
7504 INFO
ltxl51ao10.0111011ol3l30lf2ll1500l204Bl32I l204Bl29639Blolololo.o:64IO.
o:64lo.010.010.010.010.010.010.01-11-1130101521ao2051143IOI
The first field in the data header and in the data records is the type of the
record. These will match exactly; in the example the record type is tx. The
requested command sent to CART or NART may return several types of data.
This data type allows the association of data records with the proper header.
The data header is always returned before any data record of the same type.
Data records may be returned in any order. Types may be interleaved or not.
The order of the data fields is not guaranteed between different versions of
NART. The data header must be parsed to understand the order of the fields
in the data records.
Sometimes data messages are shown on the screen as they are returned and
sometimes they are not. CART and NART are inconsistent in this regard.
Some commands show the data messages, some do not, and some include a
parameter that allows the user to specify whether the messages are shown or
not. Regardless of whether data messages are shown on screen, all of them are
put into an internal database that can be used to produce formatted data
reports with the report command, or can be displayed in raw form with the
dump command.

December 2010

Chapter
Reporting
CART allows users to generate formatted reports based on the collected data.
As data is collected, it is written into a small in-memory database as a
collection of records with field names.
Multiple records may be collected with a single command; for example, if
multiple frequencies or multiple rates are specified, one record will exist for
each combination of the input parameters. Multiple record types exist; for
example, a link command returns records from both the transmitter and
receiver (labeled tx and rx, respectively). Normally, each record translates into
a line in the resulting report or a point on a graph.
Field names are normally given by a record type followed by the specific field
name. For example, rx.rate refers to the field rate in the data records returned
by the receiver and tx.rate refers to the field rate in the records returned by the
transmitter.
Record Type Shortcut

For convenience and to simplify the amount of typing, CART remembers the
last record type specified and applies it automatically to subsequent fields
specified with the field parameter. Thus, in the line:
f=rx.rate;f=success
the word "success" refers to the field rx.success.
Field Name Discovery

To discover all of the field names, type the command dump after running an
operation. The dump command displays a header line of text with the names
of all of the fields, and then subsequent lines with the individual data records.
The first word in each line is the record type.
Display the values of the data fields directly by citing their name, for example:
dump f=rx.success.
Computations
Computations on the data fields may be performed before displaying them.
Computations can use any field, predefined variables, constants, arithmetic
operators(+, - , *, /, ... ), logical operators(&, I, ! ), comparison operators
(<, <=, =, >, >=, ! =, or <>),and some built-in functions. For example,
f=O.OOtrx.bytes would display the value in kilobytes as opposed to bytes.


December 2010
4-9
Chapter
Functions
The functions listed in Table 4-3 assist in analyzing the data collected by
ART2. They are intended to be used in conjunction with reports to evaluate
the performance of a DUT. For examples of reports and functions in scripts,
see Chapter 6, "Sample Manufacturing Test Flow".
ART2 functions have the following characteristics:
Variables with $ in front of them are passed by value

Variables with in front of them are passed by reference.
@ is used when the variable is an array or when it may be changed by the
function.
If no $ or is shown, the variable is presumed to be a field in the data
collected by the last operation.
Table 4-3. Function Descriptions

Function
Format
Description
lookup
lookup(value,@x,@y)
The array @x is searched for the element equal to value. The

corresponding element of the array @y is returned.
For example, if x=4, 2, a, 10 and y=l, 17, 4, so then lookup (8, x,@y)
returns 4.
dip
dip(x,y,$threshold)
Looks at the data presented in x and y as a graph. Starting on the right

side of the graph (high values of x), it searches backwards (toward low
values of x) for the first y value less than threshold. It returns the
corresponding x value. Typically used to find the board sensitivity point.
ndip
ndip(x,y,$threshold) Looks at the data presented in x and y as a graph. Starting on the left side
of the graph (low values of x), it searches forward (toward high values of
x) for the first y value less than threshold. It returns the corresponding x
value. 'fypically used to find the maximum input point for the board.
fit
fit(x,y,$low,$high)
nfit
nfit(x,y,$low,$high) Looks at the data presented in x and y as a graph. It attempts to find the
steepest negatively sloped part of the graph that transitions from below
the low threshold to above the high threshold. It then fits a straight line to
this section of the curve to compute then return the x value corresponding
to the point where the straight line crosses the line y = high. Can be used
to compute a more accurate maximum input point for sparse data.
test
test(condition,
$passtext,
$failtext,
passcount,
@failcount)
Evaluates the specified condition. The condition may be any equation

made up of other variables, functions, and arithmetic, logical, or
conditional operators. If the condition is true, the value of pas scoun t is
incremented and the value of $passtext is returned. If the condition is
false, the value of@failcount is incremented and the value of
$fail text is returned. If either passcount or @failcount are 0, they
are not used.
min
min(x)
Returns the minimum value of the field x across all collected data records.
max
max(x)
Returns the maximum value of the field x across all collected data
records.
mean
mean(x)
Returns the mean value of the field x across all collected data records.
4-10
Looks at the data presented in x and y as a graph to find the steepest

positively sloped part of the graph that transitions from below the low
threshold to above the high threshold. It then fits a straight line to this
section of the curve to compute then return the x value corresponding to
the point where the straight line crosses the line y = high. Can be used to
compute a more accurate sensitivity point for sparse data.

December 2010

Chapter
Table 4-3. Function Descriptions (continued)

Function
Format
Description
sum
sum(x)
Returns the sum of the values of the field x across all collected data
records.
count
count(x)
Returns the number of data records containing the field x.
first
first (x)
Returns the value of the field x from the first data record.
last
last (x)
Returns the value of the field x from the last data record.
Report Types
Table 4-4 describes the standard report types.
Table 4-4. Report Types
Report Type
Column
Descrtption
Produces a column-formatted set of data, up to 10 columns:

rep r='c f=pm.pcdac,tx.dacg,pm.power'
pm.pcdac tx.dacg pm.power
2.0
3.0
4.0
5.0
6.0
7.0
Row
2.0
1.0
0.0
3.0
2.0
1.0
-24.1
-23.7
-23.2
-22.9
-22.4
-21.9
Produces a row-formatted set of data.

report r='row field=pm.rate,tx.tp,pm.power,tx.tp-pm.power;
label=rate,target power,actual power,difference;'
rate
target power
actual power
difference
Table
6
19.0
18.9
0.1
54
17.0
16.4
0.6
to
18.0
18.0
0.0
t7
17.0
17.1
-0.1
t12
17.0
17.1
-0.1
t23
13.0
13.0
0.0
Produces a table of data, like a spreadsheet, field z as a function of field x and field y. It is
permissible to have more than one z.
rep r='t f=pm.pcdac,tx.dacg,pm.power'
2.0
2.0
-24.l
l. 0
0.0
3.0

3.0
4.0
5.0
-23.7
6.0
-22.4
7.0
-21. 9
-23.2
-22.9

December 2010
4-11
Chapter
Table 4-4. Report Types (continued)

Report Type
Graph
Description
Produces a graph of the second field as a function of the first. Multiple secondary fields
may be graphed on the same plot. The graph is a column-formatted set of data, up to 10
columns.
rep r='g f=pm.pcdac,pm.power'
-20.0
-20.5
-21.0
-21.5
-22.0
-22.5
-23.0
-23.5
-24.0
-24.5
-25.0
*
*
0.0
Histogram
5.0
10.0
Produces a histogram of the specified field.

rep r='h f=tx.dacg;inc=l'
* tx.dacg: mean=l.5 sd=O.O min=O.O max=3.0 count=12 outlier=O
1. 0
0.9
0.8
0.7
0.6
0.5
0.4
0.3
0.2
0.1
0.0
**
**
****
****
0.0
4-12

December 2010
10.0

Chapter
Report Parameters
Table 4-5 describes the report parameters.
Table 4-5. Report Parameters
Parameter
Description
key, sort
Field names that are used to sort the data. CART provides one chart for each combination
of key fields values. For example, "sort=frequency,rate;" splits the data into different
charts based on frequency and rate. The specific combination is printed at the top of each
chart.
field
Gives the displayed field names in the form "class.field". Class is tx, rx, pm, etc. The
report command requires at least one field specified for each report. Field names are the
names used by CART/NART in the header message.
x
Shorthand for setting field[O]
Shorthand for setting field[l]
Shorthand for setting field[2]
minimum
Minimum value on the chart axis. Autoscaling is the default.
maximum
Maximum value on the chart axis. Autoscaling is the default.
increment
size
Increment on the chart axis and bin size for histograms

Size of the chart
label
Provides an alternative label for the display of the field (Default= Field name)
units
Optional field that display units along with the label (Default = None)
type
width
decimal
Data type: f, d, x, or s (Default = f)

Width of the data fields (Default = 10)
Number of decimal places shown (Default= 1 on f type; none on s, d, and x)


December 2010
4-13
Chapter
Getting Online Help

CART and NART provide online documentation for every command. The
online help documentation can provide guidance in writing an ART2
application since it most accurately represents the commands and parameters
that CART or NART accepts. See for Appendix A and Appendix B for
command lists applicable to ART2 version 2.13.
To retrieve a list of current commands, issue the help command. CART or
NART responds with the complete list of commands and includes a short
description for each one. For example, NART responds to the help command
with:
7508 CONTROL BEGIN help
1012 INFO exit: exits the program
1012 INFO help, ?: supplies information about the commands and
parameters
1012 INFO error: allows you to control how error messages are
displayed
1012 INFO version: retrieve version information
7506 CONTROL DONE help
To facilitate easier reading in a temUnal window, tum off the INFO error code
and type by issuing the command error code=1012; response=message. Also
consider widening the terminal window to minimize line wrap.
To view more detailed documentation about a specific command, issue the
help command followed by the command name. For example, issuing the
command
help rr
to NART results in the messages

7508
1012
1012
1012
1012
7506
4-14
CONTROL BEGIN help rr

INFO rr: reads a device register
INFO
address: the address
INFO
type=hexadecimal;
INFO Reads a device register.
CONTROL DONE help rr

December 2010

Chapter
To view more detailed information about a particular parameter, enter the

help command followed by the command name and then the parameter
name. For example, issuing the command
help tx duration
to NART results in the messages

1012 INFO
1012 INFO
1012 INFO
duration: the maximum duration of the operation

type=decimal; minimum=-1; maximum=2147483647;
default=60000; units=ms;
forever [-1]
This response lists the type of parameter value NART expects, the allowed
range of values, and any special values.


December 2010
4-15
Chapter
4-16

December 2010

Chapter
Interfacing a Custom
Process to ART2
This chapter provides information on configuring ART2 for use with custom
or vendor software, which can control NART, CART, and test equipment
through socket connections.
NART and CART share the same method of parsing commands, regardless of
the configuration. NART and CART both report results using the conventions
described in "Results Output" on page 4-7.

Interfacing a Custom Process to ART2

December 2010
5-1
D Chapter
Controlling CART using Custom/Vendor Software
Titls section is intended for software developers, and describes how ARI'2
software and test equipment can be controlled directly by a custom process
through the CART socket interface as shown in Figure 5-1. This configuration
allows up to five NART instances running on either PCs or APs, and is
intended for use with an application such as a custom manufacturing control
process.
Custom
Process
................................................................,
Test
Instruments
CART
......
Optional 5111 Radio
Optional 2d Radio
NART
NART
WiFi Device
WiFi Device
WiFi Device
PC1
Driver
PC5/ AP..
PC2/AP

Up to 5 NART setups are allowed
Figure 5-1. Custom or Vendor Software Controlling CART and NART

Normally, CART accepts commands from a command window, interprets
these commands, and then sends the appropriate commands to one or
multiple NART processes to perform the requested tests.
1he custom process can instruct CART to divert these commands and
responses to a standard TCP socket, using optional command line arguments.
1he custom software can connect to this socket and have direct control of
CART with immediate feedback. Every command that a user can type to
CART can be sent over this socket. Every response that CARI' normally prints
in the command window is returned over this socket.
CART may be active or passive in setting up the socket. H the custom
application opens a listen port, start CARI' with the command
cart -gui [ip address] : [port number]
Replace [ip addressI and [port numberI with the IP address and port number
of the application that is listening. H the application is running on the same
computer as CART, slln.ply supply a port number. When CART starts, it
actively connects to that port.
H CART is to open the listen port, start CART with the command
5-2

December 2010

Chapter
cart -port [port number]
CART opens a listen socket and the application may connect to it.
When a connection is established through a socket, CART enables the printing
of the CONTROL messages in addition to the usual INFO, WARNING, and
ERROR messages. These additional CONTROL messages may be used by an
application to help understand the state of CART. It is possible to enable or
disable any message with the error command.
All responses from CART are given in a standard format consisting of a 4digit error code, a severity, and a message. It may be desirable to use the error
code to control branching within a custom application. Here is a sample
response:
2012 CONTROL Link test started at 798456.
With the exception of enabling the CONTROL messages, the rest of CART
behavior is the same as when a user types directly to CART in a window. The
commands and responses are the same.
While CART accepts shortened command and parameter names for the
convenience of the user, fully spelled names are recommended for custom
application programs, to avoid confusion with commands and parameters
that may be added in the future.
To explore the socket interface with a telnet product, such as HyperTerminal,
start CART in listen mode and then connect to it with HyperTerminal. Type
commands to HyperTerminal and observe how CART responds with
messages that are displayed by HyperTerminal. Set the following options in
the ASCII Setup window:
Send line feeds with line ends
Echo typed characters locally
For further information on NART and CART, see Chapter 4.


December 2010
5-3
Chapter
Controlling NART using Custom/Vendor Software

This section is intended for software developers, and describes how NART
can be controlled directly by a custom process through the NART socket
interface as shown in Figure 5-2. This configuration is used when a test
equipment manufacturer has supplied special code to control the test flow.
Customer/
Vendor SW
Customer/vendor softwore controls

test flow, equipment, ond sends
commonds to NART to control WiFi
device in test modes.
WiFi
Device
Figura 5-2. Custom or Vendor Software Control of NART

NAKI' controls the operation of a single radio card or device. It can be used
under the control of any other application program.
NART accepts commands and sends data and status responses with text
messages over a socket. All messages are lines of text ending with a new line
character, \n.
Normally, NART opens TCP port 2390 and listens for connection requests
from clients. This port can be changed to any other port using the command
line argument -port [port number] when starting NART. The custom
application must initiate the connection to NART.
NART can be controlled with any telnet type program, such as
HyperTerminal on a PC. It may be useful to do this to see exactly how NAKI'
reacts as a custom interface is developed. When using HyperTerminal, set the
following options in the File>Properti.es>Settings>ASCII Setup menu:
Send line ends with line feeds
Echo typed characters locally
If NART is started with the argument -console, it prints debug information to

the screen as it runs. This debug information includes every requested
command sent to NART and every response NART sends back.
If NART is started with the command line argument -port 0, control is
transferred directly to the command window. Commands may be typed on
the keyboard and results are displayed in the command window.
5-4

December 2010

Chapter
These two NART starting options may be useful for debugging a custom
process.
NOTE: The NART console mode argument should not be used when trying to run
high performance tests. The additional information printed on the screen may
degrade the performance.
When the interface program connects to NART, NART responds with these
data messages:
7504
7504
7504
7504
7504
INFO
INFO
INFO
INFO
INFO
lsetlNartVersionll.OI
isetiNartBuildDateil00428173000I
lsetldevidl I
lsetlmacl I
lsetlcustomerl I
The first two responses contain the NART version number and build date.
The next three responses describe the card that is currently loaded. In the case
shown, there is no card, as all of the data fields are blank. These responses are
formatted as data messages.
After this step, NART is ready to accept commands. NART accepts
commands in the standard format described in "Using CART/NART
Command Line Interfaces" on page 4-1.
NART typically responds to commands with data, error, and done messages.
All messages from NART begin with a 4-digit error code, a type or severity,
and then the message contents. C language header files are available that
define the response codes and the format of the messages to assist in parsing
and understanding the error response.
When NART receives a command, it responds by acknowledging the
command with a BEGIN message. The BEGIN message starts with code 7508,
followed by the type CONTROL, and then an exact copy of the command sent
to NART. These messages can be seen in the help examples provided above.
Consider the following example:
tx f=5500; r=tO
nart responds with the message:
7508 CONTROL BEGIN tx f=5500; r=tO
When the command is finished, NART returns a DONE message, which is

always sent whether the command is successful or unsuccessful. DONE
messages begin with the code 7506, the type CONTROL, and then an exact
copy of the command sent to NART. The DONE message for the command
used in the above example is:
7506 CONTROL DONE tx f=5500; r=tO
All other message are sent between the BEGIN and the DONE messages.
NART sends an ERROR message if something is wrong. ERROR messages
start with a standard 4-digit error code, then the word ERROR followed by a
brief explanation of the problem. For example, the following ERROR message
may appear in response to a load, tx, or rx command:


December 2010
5-5
l1I Chapter
6003 ERROR No card loaded.
If the command produces data, NART sends DATA messages before the
DONE message. See "Results Output" on page 4-7 for a description and
example.
The easiest command to try is hello. It is used to check the link between an
application and NART. After the command is sent:
hello
NART responds with the same messages as it sends upon connection:

7508
7504
7504
7506
CONTROL BEGIN hello

INFO lhellolmajorlminorldateltimel
INFO ihellolllOl10042Bl173000I
CONTROL DONE hello
If the process sends a bad command such as

crud
NART responds with

7508 CONTROL BEGIN crud
1026 ERROR Unknown command "crud".
7506 CONTROL DONE crud
tx and rx commands implement a two-step initiation process. When the

command is issued, NART first processes the request and sets up (but does
not start the operation). If there are any errors in the request, NART will
respond with an ERROR message and a DONE message. If the request is
acceptable, NART responds with
7500 CONTROL OK
and then waits for the START command.

This two-step process allows users to coordinate the activities of the
transmitter and receiver. To cancel a tx or rx operation while it is in progress,
send the STOP command at any time.
After the tx or rx command terminates, either because the specified packet
count or duration was reached or because a STOP command was issued,
NART sends the collected statistics in DATA messages and then finishes by
sending the DONE message.
5-6

December 2010
Chapter
Sample Manufacturing
Test Flow
This document describes a sample manufacturing test flow for station (STA) and
access point (AP) implementations using the Atheros AR93xx chip sets. Atheros
partners should develop a complete manufacturing test suite to meet their
manufacturing test requirements.
Manufacturing Test System Requirements

Table 6-1 shows the equipment required to run the standard calibration and
test flow for manufacturing.
Table 6-1. Manufacturing Test System Requirements

Part
Requirement
ARTI
ART2 SW release package for Wmdows; this package generally includes a Linux image for
AP calibration as well as other third part libraries as required by instruments
Attenuator
HP 8496H 110dB, HP 8495H 70dB, HP 8494H lldB attenuators with a switch driver or
HP 11713A Attenuator /Switch Driver. Three sets are required to support up to three Tx/Rx
chains of the AR93xx.
Cables
DUT
Ethernet Switch
GPIBRouter
Appropriate cables for instrument attachment

A device under test (DUT)
Any standard ethernet switch
National Instruments GPIB-ENET /100
GU
A golden unit (GU) is required
PCs
One or two PCs with Windows VISta/XP OS (only one is needed if the GU is an AP)
Power Meter
Power Splitter
Agilent E4416A, Peak and Average Power Sensor, Rhodes & Schwarz NRP Zll power
meter
Mini-Circuits ZN2PD-9G-S+; To combine the Tx/Rx chains for AR93xx-based products,
such as the XB112, HB116, etc.
Spectrum Analyzer Agilent 4404B, Agilent 4405B or Rodhe & Schwarz FSL

Sample Manufacturing Test Flow

December 2010
6-1
[J
Chapter
Manufacturing Test System

Figure 6-1 provides a diagrammatic view of the manufacturing test system
that the sample manufacturing test flow uses.
Device Under
Test (DUT)
=== =--.
Attenuator
HP 8495H 70 dB+
HP 8494H 11 dB x3
Ethernet
RF Cable
Golden Unit
Attenuator
Connection
HP 11713A
Attenuator/
Switch Driver x3
RF Cable
Ethernet Router
HP 4404B
HP E4416A
Spectrum
Power
Meter
_ _ _ _ _ _ _ _ _ _ _ _ Analyzer
f---,-,-~- io---1G
PI
_
B
National Inst ruments

GPIB-ENET/100
Figure 6-1. System Requtrements for Sample Manufacturing Test Flow

NOTE: This setup differs from previous reference design setups in two ways: three RF
paths come from the DUTs three chain connectors through three separate
attenuators to the GU; the power meter and spectrum analyzer are now placed after
the attenuators before the GU (previously they were between the DUT and the
attenuators). Combiners are required to combine the three chains into single inputs
to the power meter and spectrum analyzer.
Atheros customers who use different instruments in their manufacturing test
suite must develop appropriate instrument control dynamic linkable libraries
(DLLs) that can be included in the ART2 package with the command
equipment.
Users must also gather some calibrated data from a GU and cable/splitter loss
that used in the manufacturing test software before starting the
manufacturing test flow. Therefore, a GU should be fully calibrated having
known output power, receive sensitivity, and reference oscillator, with cable
and splitter loss specifications obtained. The initial software setup uses these
known data in the manufacturing test program through the file start.art With
these known values, users can calculate the settings for the attenuator to be
used for the packet error rate (PER) and receive sensitivity tests in the
manufacturing test program.
NOTE: Make sure that the attenuator switch drivers are all set to Owhen measuring
the path losses between instruments/golden and the DUT.
6-2

December 2010

Chapter
Set Up Test Equipment

This section describes the test equipment and software setup used for
cahbration of the Atheros chip sets in a Card.Bus, Mini PCT, PCT Express, or
access point (AP) design. It assumes the test equipment used is listed in the
Atheros-recommended list. If the test equipment used differs from the
suggested list, software additions to ART2 may be required.
Hardware Test Equipment Setup

Set up according to the appropriate procedure.
GPIB-ENET/100 from National Instruments

To set up GPIB-ENET/100:
1. Install the National Instruments software.
2. Configure the PC's Ethernet controller with the same IP address subnet of
the GPIB-ENET /100 (that is, 192.168.1.1).
3. Configure GPIB-ENET/100 from Start> Programs> NI-488.2M for
Wmdows NT> GPIB-ENETlOO Utilities> Device Configuration.
A dialog box similar to Figure 6-2 appears.
Cfrct~*!rci
IP eddc.ssAlostneme
p 1pyij:M1i
00.9!l:2f-Ool:Cf:32
Scrio!w rrbCI' ,
OOCB7865
GPIBENET/100
ft"""'... I
!lefreh
Rgure 6-2. GPIB Device Configuration Dialog

4. Select the Property box and as.sign the IP address (i.e., 192.168.1.200) and
.subnet mask for the GPIB-ENET /100.
:,; GrIB E/\ET/ lOO rropcrhcs
Network Settings
Se<ial nurb...
OOC87!165
Elhemet addre,.
oo:9J:2t:0.:11:32
Firmmwe versicn:
8.9
!fostname: j i i iil:fj:ti
(' .QbtaO> .,.. 1p oddreos outomotic~ (DHCP)
U}e tile following IP settings.
JP address:
192 . 169 . 1
S1rbnet mask:
255 . 255 . 255 . 0
. 200
g afeway:
QNS server:
!;onwnenl (Olltional)
OK
Cancel
Rgure 6-3. GPIB Device Conflguratlon Properties Dialog

Sample Manufacturing Test Row

December 2010
6-3
[J
Chapter
5. Open a DOS window and Ping 192.168.1.200 to make sure the PC can
communicate with the GPIB-ENET/100. If it sees no responses, make sure
it is using a crossover Ethernet cable if connecting the PC straight to the
GPIB-ENET/100, or a straight Ethernet cable for a hub configuration.
6. Configure the GPIB-ENET /100 interface to ART2 software. The steps
involved vary depending on whether ART2 is run within Windows or
Llnux.
Configuring for Windows

a. Jn the Control Panel, select the GPIB icon.
liji;J1ICdi;j @lit4!I!M
Hardware Settings ------~
Hosl Name
I5mlsec ::::J Bus Timing
.QK
.Cancel
]::!elp
~ollware
Figure 6-4. GPIB Software Interface Configuration

b. Select Board Type as shown in Figure 6-5 and click OK.
21
Board Type
BoardJype
GPIB !!oard
:I
GPIBl
GPIB2
GPIB3
.-.. t
..=..!
.QK
.Cancel
l::!elp
Figure 6-5. GPIB Board Type Configuration

c. Select Configure and enter the same IP address that was assigned to
the GPIB-ENET /100 and click OK.
liji;J1ICdi;j @lit4!I!M
Hardware Settings ------~
Hosl Name
j5mlsec ::::J Bus Timing
.QK
.Cancel
]::!elp
~ollware
Figure 6-6. GPIB IP Address Configuration
6-4

December 2010

Chapter
Power Meter E4416A from Agilent Technologies

To set up the power meter E4416A:
1. Make sure Self Calibration and Zeroing is complete.

2. Connect Senor to the Power Ref connector and press the Zero/Cal button
(first make sure that Power Ref is in the Off state).
3. Assign a GPIB address for the power meter by choosing System > Remote
Interface > Configure Interface > GPIB. Enter 13 for the GPIB address.
Spectrum Analyzer 44048 from Agilent Technologies

Assign the GPIB address for spectrum analyzer by choosing System > Remote
Port from the menu. Enter 18 for the GPIB address.
Attenuator Switch Drivers 11713A from Agilent Technologies
To set up switch drivers 11713A:
NOTE: Make sure that the antennuators on each chain are connected to a single
switch driver. It is recommended using GPIB address 1 for chain 0, GPIB address 2 for
chain 1, and GPIB 3 for chain 2.
1. Assign different GPIB addresses for each of the three attenuator switches
by adjusting the dip switches behind the instrument. Enter 1, 2 and 3 for
the GPIB address.
2. Connect the 1 dB increment Attenuator 8494H to the X Atten connectors
behind each of the instruments.
3. Connect the 10 dB increment Attenuator 8496H to the Y Atten connector
behind each of the instruments
NOTE: Ensure that the GPIB address assigned to the test equipment matches the
GPIB address in the ART2 software (in the file start.art).


December 2010
6-5
Chapter
Running the Sample Manufacturing Test Flow

The sample manufacturing test flow can perform calibration and testing of
AR93xx-based radios. Available tests include calibration, target power,
spectral mask, channel accuracy, EVM, sensitivity sweeping, and throughput.
Most tests are on by default and require a OUT and a Golden Radio as well as
the standard ART2 based calibration setup. Tests can be turned on and off
using the flags in command\ test_flow_flags.art.
To run the sample manufacturing test flow:

1. Start NART and CART as shown in "Installing and Running ART2 for a
STA Card".
2. In the CART window, run the command:
test flow
3. At the Please supply a value for BoardIDType: prompt, enter:

- 0 to identify the card via subsystem.ID or
- 1 to enter it by refID
Available choices are:
reflD
SSID
refName
Ox3112
Ox3113
Ox3113
Ox3114
OxAlll
Ox3116
Ox3110
XB112-035
XB113-024
XB113B-112
XB114-235
APlll
HB116-041
HB112-241
XB112
XB113
XB113
XB114
APlll
HB116
HB112
Because two designs use the same subsystem!D, select 1 to enter via refID.
4. Enter the refID at the next prompt (for example, hb116-041).
5. Enter the MAC address when prompted at the next prompt (for example,
11:22:33:44:55:66).
6-6

December 2010

Chapter
Table 6-2 shows files used for controlling the manufacturing test flow:
Table 6-2. Files Used to Control Manufacturing Test Flow
File
Description
bin\start.art
bin \ProductList.ref
command\ test_flow_flags.art
$refName \$refID.ref
$refName \$refID _power.art

$refName\ctl_$refID.art
Parsed at CART startup time, typically

Specifies path loss of the manufacturing setup. Path loss for frequency
ranges of chain 0, chain 1 and chain2 can be specified (see the path
command for more information).
Multiple frequency ranges can be used, for example, to span the 5-GHz
band.
Specifies the directory for where command files can be found and where
log and report files should be saved. The default start.art points to the
appropriate paths within the ART2 package.
Parsed at CART startup time
Contains the lookup table for reference design specific files. Identifies a
reference by subsystem ID (SSID) or by a descriptive reference design
specific name (reflD), where reJName is the directory where the reference
design specific files are.
Called from start.art, thus it is called at CART startup time
Contains the flags to disable tests within the manufacturing test flow
Called from the manufacturing test_flow run from within CART for
manufacturing calibration
Contains the reference design specific information that will typically get
stored on the EEPROM/OTP/flash during calibration
Called from the refID.ref file called during manufacturing calibration
Sets the reference design specific target powers
Called from the refID.ref file called during manufacturing calibration
Sets the reference design specific Conformance Test Limits (CTL)
Each of these files are described in more detail in the following sections.


December 2010
6-7
Chapter
Start.art
Start.art is parsed automatically at CART startup time. It must be in the same
directory as cart.exe, so the start.art that is released with ART2 is found in the
bin directory of the package. The following is a sample of the start.art file that
is released with the art2 package.
#---------------------------------------------------------------#Pathlosses
#---------------------------------------------------------------#Dut
path
path
path
to golden
device=go1den;f=2442,5240,SSOO,SBOS;chain=l;loss=7.6,9.9,10.3,10.6;
device=go1den;f=2442,5240,5500,5805;chain=2;1oss=7.6,9.9,10.2,10.6;
device=golden;f=2442,5240,5500,5805;chain=4;loss=7.S,9.9,10.3,10.6;
path device=pm;f=2442,5240,SS00,5805;chain=l;loss=17.2,19.1,19.1,19.6;
path device=pm;f=2442,5240,5500,5805;chain=2;1oss=17.5,19.1,19.5,19.9;
path device=pm;f=2442,5240,5500,5805;chain=4;1oss=17.2,19.l,19.2,19.5;
#---------------------------------------------------------------#equipment models and types
#---------------------------------------------------------------equipment model=nrpzll;
equipment model=ll713a; arg=l,2,3; delay=SO;#agilent
#equipment model=E4404B; arg=18;
#---------------------------------------------------------------# command file and log/report file paths
#---------------------------------------------------------------assign artcommand=.\ .. \command;

assign artlog=.\ . \log;
assign artreport=.\ .. \report;
# default test flow selection setting flags

#xb113b\test_flow_flags_ab113b.art
test_flow_flags.art
Table 6-3 describes each of the setting used within the start.art.

December 2010

Chapter
Table 6-3. Description of start.art Entries

Entries
path
Description
Specifies the path loss between the DUT and one of the components within the
manufacturing setup, on a per chain basis. The equipment component is specified
via the device argument, that is, golden or pm or sa. Multiple frequencies can be
entered using the f argument, for example =2442,5240,5500,5805. The chain for
which this path loss applies should be entered via the chain command, where the
chain is specified as a bit mask, bit 0 being chain 0 (Oxl), bit 1 being chain 1 (Ox2) and
bit 2 being chain 2 (Ox4). The loss itself is entered with the loss argument, and the
number of values entered should match the number of frequencies specified. For
example:
path device=golden;f=2442,5240,5500,5805;chain=1;loss=7.6,9.9,10.3,10.6;
equipment
Specifies the equipment types that will be part of the manufacturing setup. The
equipment type is entered via the model command, for example model=e4416a for
the Agilent power meter model e4416a. The argument arg is used to specify the GPIB
address of the equipment. If the equipment needs settling time then the delay
argument can be used to enter the amount of delay in milliseconds that is needed
after issuing a command to the equipment.
assign artcommand
Specifies the directory where the ART2 commands reside. By default it is set to point
to the command directory within the ART2 package:
assign artcommand=. \ . \command;
assign artlog
Specifies the directory where the CART-created logs should be stored. By default it is
set to point to the log directory within the ART2 package:
assign artlog=. \ .\log;
assign artreport
Specifies the directory where the cart created logs should be stored. By default it is
set to point to the report directory within the ART2 package:
assign artreport=. \ ..\report;
test_flow_flags.art
Calls the test_flow_flags.art file (see the "test_flow_flags.art" section) to setup all
the manufacturing test flags within the ART2 environment.


December 2010
6-9
Chapter
Productlist.ref
ProductList.ref is parsed automatically at CART startup time. It must be in
the same directory as cart.exe, so the Productlist.ref that is released with
ART2 is found in the bin directory of the package. It contains a list of the valid
reference designs that are supported in the ART2 package. It also provides a
pointer to the board specific .ref file that needs to be called to setup the board
properly in the absence of calibration data being stored on the adapter. A
sample productList.ref is shown below
ref ID
SSID
refName
prodID
---------------------------------------------Ox3112
Ox3113
Ox3113
Ox3114
Oxalll
Ox3116
Ox3110
XB112-035
XB113-024
XB113B-112
XB114-235
APlll
HB116-041
HB112-241
XB112
XB113
XB113
XB114
APlll
HB116
HB112
200
203
203
204
206
209
205
Table 6-4 describes the meaning of the columns within this file.
Table 6-4. Description of Productlist.ref Columns

Column
Description
SSID
Subsystem ID that should be assigned to the card. This should match the subsystem
ID that is set in the adapter specific .ref file by the command set ssid=.
refID
File name of the board-specific .ref file but without the .ref extension.
refName
Folder name within the ART2 command directory that contains the reference design
specific files used the calibration and test of that reference design.
prodID
This is an Atheros internally-defined ID that is used with the Atheros internal label
scheme. Customers do not need to assign a unique prodID; existing values can be
used.
NOTE: The contents of the .ref file are currently very sensitive to layout and syntax
-requiring tabs rather than spaces between the columns. While it is planed to
improve this in a future version of ART2, for now it is recommended that to add a
new line item to this file, an existing entry be copied and modified with updated
values as needed.
6-10

December 2010

Chapter
test_flow_flags.art
Test_flow_flags.art is called from the start.art file. It contams the flags for
which calibration and test items should be performed in a manufacturing
flow. Below is an example of the current contents of test_flow_flags.art.
##----------------------------------------------------------------# manufAuto: 1 For manufacture auto test, no user enter required

#
refID need to be setup correctly, BoardIDType=l
#
For manufacture test with user selection

refID and SSID will be entered by user
for atheros internal
BoardIDType, refID need to be entered by user
#
##-----------------------------------------------------------------
assign manufAuto=2
assign BoardIDType=l
assign refID=hb116-041
##----------------------------------------------------------------## default test selection 0: run the test,
1: disable the test
##-----------------------------------------------------------------
##
Select TP, FT test
##----------------------------------------------------------------assign ptTestDisable=O
assign ftTestDisable=O
##-----------------------------------------------------------------
# LitepointDisable=O
using LitePoint for EVM/mask and as vsg for Rx sens

assign LitepointDisable=l
##
##----------------------------------------------------------------assign isFlashCal=O
##----------------------------------------------------------------## For calibration

##-----------------------------------------------------------------
assign
assign
assign
assign
txCalDisable2g=O
txCalDisable5g=O
rxca1Disable2g=l
rxCalDisable5g=l
##----------------------------------------------------------------## For EEPROM Write Operation
##----------------------------------------------------------------assign saveEEPTxCalDisable=O
assign saveEEPRxCalDisable=l
assign savePCieDisable=O
assign eepCheckDisable=O
# noEEPSaveOnFail: O saveEEP based on above flag
# noEEPSaveOnFail: 1 saveEEP based on above flag and when all pass
assign noEEPSaveOnFail=l


December 2010
6-11
Chapter
##----------------------------------------------------------------## For Tx Test

##----------------------------------------------------------------assign
assign
assign
assign
assign
assign
assign
assign
assign
assign
txPwrDisable2g=O
txPwrDisableSg=O
txPwrA11ChainDisable2g=l
txPwrA11ChainDisable5g=l
maskDisable2g=l
maskDisableSg=l
txEVMDisable2g=l
txEVMDisableSg=l
channAccDisable2g=l
channAccDisable5g=l
##----------------------------------------------------------------## For Rx Test

##----------------------------------------------------------------assign
assign
assign
assign
rxsensDisable2g=O
rxsensDisable5g=O
rxPerDisable2g=0
rxPerDisableSg=O
##----------------------------------------------------------------## For TX unicast Throughput Test

##----------------------------------------------------------------assign
assign
assign
assign
txPerDisable2g=O
txPerDisable5g=0
tputTx2gDisable=O
tputTxSgDisable=O
##----------------------------------------------------------------## For TX broadcast Throughput Test

## O: enable test,1: disable test
## 2: enable test, but pass/fail results don't count at final summary
##----------------------------------------------------------------assign
assign
assign
assign
btxPerDisable2g=l
btxPerDisableSg=l
btputTx2gDisable=l
btputTx5gDisable=l
##----------------------------------------------------------------## For rx Throughput Test

##----------------------------------------------------------------assign tputRx2gDisable=O
assign tputRxSgDisable=O
##----------------------------------------------------------------## For current measurement

##----------------------------------------------------------------assign rxcurrentDisable=l
assign txCurrentDisable=l
##----------------------------------------------------------------# if LitepointDisable=O, litepoint box is used

# the following setting will overwrite previous settings
branch name=SETTING_DONE; action=goto; condition='$LitepointDisable=l'
assign txEVMDisable2g=O
assign txEVMDisableSg=O
assign channAccDisable2g=0
assign channAccDisable5g=O
assign maskDisable2g=O
assign rnaskDisableSg=O
branch name=SETTING_DONE; action=start;
##----------------------------------------------------------------## End of test default test selection
6-12

December 2010

Chapter
Table 6-5 explains the available flags that enable and disable tests. lhis table
also provides the name of the reference design-specific flow files that are run
for each of the tests described. These flow files can be found in each of the
reference design specific command directories.
NOTE: All of the flags in test_flow_flags.art are set with the assign command. In
the command description of Table 6-5, the assign statement has been omitted for
simplicity. Note however that each of these flags needs to be set using the CART
assign command.
Table 6-5. Description of test_flow_flags.art

Command
manufAuto
BoardID'fype
refID
Description
Can be set to control the automatic flow of the manufacturing test so that the user is
not prompted to enter reference design specific identifiers at the manufacturing
test_flow runs. It has the following options:
0
User will be prompted to enter refID or SSID at the start of the test flow
User will not be prompted, refID I ssid will be set in test_flow_flags
Reserved for atheros internal use
Only applies when manufAuto is set to 1. Specifies whether boards will be identified
by refID (1) or SSID (0) (reflD is currently recommended)
This is the refID field from the ProductList.ref file, that is used to identify which
board should be run when the manufAuto flag is set to 1.
ptTestDisable
Set this flag to 1 to disable all the power test type functions which includes: Tx
Calibration, power accuracy and spectral mask testing. This flag is intended for use
by manufacturers who have divided manufacturing test stations into power test
(those tests that are performed with a power meter and spectrum analyzer) and
function test (those link type tests that are performed against a golden radio)
ftTestDisable
Set this flag to 1 to disable all the functional test type functions which includes: RX
sensitivity, TX PER, TX/RX Throughput. This flag is intended for use by
manufacturers who have divided manufacturing test stations into power test (those
tests that are performed with a power meter and spectrum analyzer) and function
test (those link type tests that are performed against a golden radio)
LitepointDisable
Set this flag to 0 if using LitePoint test for EVM/mask and Rx sensitivity, set it to 1 if
using golden radio based setup (with power meter spectrum analyzer and golden
radio)
isFlashCal
Set to 1 if the calibration data should be stored in flash. Typically used for APs
txCalDisable2g
Set this flag to 1 to disable the 2 GHz tx calibration. (default 0)
txCa1Disable5g
Set this flag to 1 to disable the 5 GHz tx calibration (default 0)
rxCa1Disable2g
Set this flag to 1 to disable the 2 GHz rx RSSI calibration. This feature is only being
used for specific customer application and is recommended to be set to 1 for most
customers. (defaultl)
rx.Ca1Disable5g
Set this flag to 1 to disable the 5 GHz rx RSSI calibration. This feature is only being
used for specific customer application and is recommended to be set to 1 for most
customers. (defaultl)
saveEEPTxCalDisable
Set this flag to 1 to disable the writing of the tx calibration/ref file/ Target power/
CTL data to the EEPROM/OTP /Flash

Sample Manufacturing Test Flow 6-13

December 2010
Chapter
Table 6-5. Description of test_flow_flags.art (continued)

Command
saveEEPRxCalDisable
Description
Set this flag to 1 to disable the writing of the rx RSSI calibration data to EEPROM/
OTP /Flash. It is recommended that this be set to 1 for most customers (default 1)
savePCieDisable
Set this flag to 1 to disable the writing of the PCie auto configuration data to
EEPROM/OTP. (default= 0)
eepCheckDisable
Set this flag to 1 to disable the test that ART2 performs to verify the contents of the
EEPROM/OTP/FLASH
noEEPSaveOnFail
Set this flag to 1 if the calibration data should not be saved to EEPROM/OTP/Flash
if any of the power tests fail. In this case, the data will only be saved if the tests pass
and the saveEEPTxCalDisable flag has not been set.
Set this flag to 0 to save the calibration data even if tests fail (and the
saveEEPTxCalDisable flag has not been set).
It is recommended that this flag be set to 1 if the reference design uses OTP to save
the calibration data

txPwrDisable2g
Set this flag to 1 to disable the 2 GHz per chain tx power accuracy test. (default= 0)
This test gets performed by target_test_2g.art
txPwrDisableSg
Set this flag to 1 to disable the 5 GHz per chain tx power accuracy test. (default= O)
This test gets performed by target_test_5g.art
txPwrAllChainDisable2g Set this flag to 1 to disable the 2 GHz combined chain be. power accuracy test. (default
= 1) This test gets performed by target_test_2g_combined.art
txPwrAllChainDisable5g Set this flag tol to disable the 5 GHz combined chain be. power accuracy test. (default
= 1) This test gets performed by target_test_Sg_combined.art
maskDisable2g
Set this flag to 1 to disable the 2 GHz mask test (default = 0). This test gets performed
by xmask_cal_flow_2g.art
maskDisableSg
Set this flag to 1 to disable the 5 GHz mask test (default = O). This test gets performed
by xmask_cal_flow_Sg.art
channA.ccDisable2g
Set this flag to 1 to disable the 2 GHz channel accuracy test, performed against
spectrum analyzer (default= 1). This test gets performed by
xfrequency_accuracy_cal_flow_2g.art
channA.ccDisableSg
Set this flag to 1 to disable the 5 GHz channel accuracy test, performed against
spectrum analyzer (default= 1). This test gets performed by
xfrequency_accuracy_cal_flow_Sg.art
rxsensDisable2g
Set this flag to 1 to disable the 2 GHz rx sensitivity tests performed against a golden
radio (default= 0). This test gets performed by sens_2g.art (and sens_2g_vsg if
LltePoint tester is being used)
rxsensDisableSg
Set this flag to 1 to disable the 5 GHz rx sensitivity tests performed against a golden
radio (default= O). This test gets performed by sens_Sg.art (and sens_5g_vsg if
LltePoint test is being used)
rxPerDisable2g
Set this flag to 1 to disable the testing of the rx PER testing within the 2 GHz Rx
unicast throughput test (default= 0)
rxPerDisable5g
Set this flag to 1 to disable the testing of the rx PER testing within the 5 GHz Rx
unicast throughput test (default= O)
tputTx2gDisable
Set this flag to 1 to disable the 2 GHz tx unicast throughput test performed against a
golden radio (default= 0). This test gets performed by unicast_tput_2g_tx.art
tputTxSgDisable
Set this flag to 1 to disable the 5 GHz tx unicast throughput test performed against a
golden radio (default = O). This test gets performed by unicast_tput_Sg_tx.art
6-14

December 2010

Chapter
Table 6-5. Description of test_flow_flags.art (continued)

Command
Description
txPerDisable2g
Set this flag to 1 to disable the testing of the tx PER testing within the 2 GHz Tx
txPerDisable5g
Set this flag to 1 to disable the testing of the tx PER testing within the 5 GHz Tx
tputRx2gDisable
Set this flag to 1 to disable the 2 GHz rx throughput test performed against a golden
radio (default= 0). This test gets performed by unicast_tput_2g_rx.art
tputRxSgDisable
Set this flag to 1 to disable the 5 GHz rx throughput test performed against a golden
radio (default = 0). This test gets performed by unicast_tput_Sg_rx.art
btputTx2gDisable
Set this flag to 1todisablethe2 GHz tx broadcast throughput test. (default= 1). This
test gets performed by bcasLtput_2g_tx.art
btputTxSgDisable
Set this flag to 1 to disable the 5 GHz tx broadcast throughput test. (default = 1). This
test gets performed by bcasLtput_Sg_tx.art
btxPerDisable2g
Set this flag to 1 to disable the 2 GHz tx PER testing within the 2 GHz Tx broadcast
throughput test (default= 1)
btxPerDisable5g
Set this flag to 1 to disable the 5 GHz tx PER testing within the 5 GHz Tx broadcast
throughput test (default= 1)
rxCurrentDisable
Set this flag to 1 to disable the rx current test (default 1). This test is currently not
supported
txCurrentDisable
Set this flag to 1 to disable the tx current test (default 1). This test is currently not
supported
txEVMDisable2g
Set this flag to 1 to disable the 2 GHz EVM test. This test is only valid when using
LitePoint tester. It is currently set to 1 by default if testing with regular power meter
setup, otherwise it is default to 0 when using LitePoint test. This test gets performed
by evm_2g.art
txEVMDisableSg
Set this flag to 1 to disable the 5 GHz EVM test. This test is only valid when using
LitePoint tester. It is currently set to 1 by default if testing with regular power meter
setup, otherwise it is default to 0 when using LitePoint test. This test gets performed
by evm_Sg.art


December 2010
6-15
Chapter
$refID.ref
The $refID.ref file contains reference design-specific flags that get saved to
EEPROM/OTP/Flash during manufacturing calibration. These files are
found in the reference design specific directories. The following is a sample of
one of these file.
#specify the best template to use to result in less information stored in OTP or eeprom
#select template types from
#
OspreyGeneric=2,
#
HB112=3,
#
HB116=4,
#
XB112=5,
#
XB113=6,
template prefer=3; allow=3,2; install=yes;
#subsystem and subverdor !D's
set ssid=3110;
set svid=l68c;
# set device type
# l=>Cardbus, 2=>PCI, 3=>miniPCI, 4=>AP, 5=>PCie mini, 6=>pcie express, 7=>pcie desktop
set devicetype=5;
# set Reg domain
# customers can set regulatory domain index here
set regdmn=O;
#tx and rx chain mask: bitO
#
bitl
bit2
#
Set txmask=7;
Set rxmask=7;
chaino enable,
chainl enable,
chain2 enable
#configure modes:
#
bitO = enable SGHz
#
bitl
enable 2GHz
#
bit2
disable SG HT40
bit3
disable 2G HT40
#
bit4
disable 5G HT20
#
bits
disable 2G HT20
#
#Note: these flags will be given individual commands in subsequent release
set opflags=3;
#antenna switch table control
#2GHz
set antctrlcommon2g=110;
set antCtrlChain2g=10, 10, 10;
#SGHz
set antCtrlChain5g=10, 10, 10;
#strong signal parameters
set xatten1Margin2g=b,b,b;
set xattenlMarginSg=b,b,b;
set xattenlMarginlowSg=l0,10,10;
set xattenlMarginhighSg=b,b,b;
6-16

December 2010

Chapter
set
set
set
set
xatten1db2g=18,18,18;
xatten1db5g=1e,le,1e;
xatten1dblow5g=lb,1b,lb;
xattenldbhighSg=le,le,le;
set
set
set
set
set
miscellaneous.quickdropenable=l;
quickdrop2g=-44;
quickdropSg=-34;
quickdroplow=-34;
quickdrophigh=-34;
# tx gain table
#
O - for client based designs containing an XPA
#
1 - for no xpa design
#
2 - for AP based (or modules that will be used in an AP) designs containing an XPA
#
3 - not currently used
set txgainTable=1;
# rxgainTab1e
#
0: xlna
#
1: no xlna
set rxgainTable=O;
#Temperature compensation
set temperatureCompensation=1
set tempSlope2g=25
set tempSlope5g=70
set tempSlopelow=35
set tempSlopehigh=SO
#force chainX thermometer at all times
set thermometer=1;
#GPIO for EEPROM protect
set eepromwriteEnable=6;
#enable spur mitigation
set spurchans2g=2464;
#enable PA Pre-Distortion for enhanced tx EVM on FEMless design
set papdenable=l;
#set to 1 to enable Adapter power management
set ChainMaskReduce=O;
#set rfSilent by calling this file if needed
#common\rfkill.art
#set wake-on-wireless by calling this file if needed
#common\wow.art
#target power files
hb112\hb112_trg_pwr_v2.art
#CTL Files
#common\ctl_generic.art
Table 6-6 describes the flags that set within these files.


December 2010
6-17
Chapter
NOTE: Many of the .ref file arguments are further described in the AR93xx EEPROM
Device Configuration Gujde. Refer to that document for a more detailed explanation of
these variables.
Table 6-6. Description of SrefID.ref Commands

Command
template
Descrfptton
Set a list of templates from which to do calibration structure diff against. Software
holds templates for different reference designs. Using a template that matches the
reference design results in a smaller compressed footprint when saving to OTP.
Available template selections are listed below.
The Atheros drivers include templates which are default representations of the
possible configuration and calibration information stored in the device memory.
Different drivers may be configured with different templates depending upon the
expected use. Usually NART only stores the difference between the actual
information and the specified template for the device. The template command
specifies which templates are available in the intended driver and thus which
templates can be compared against the actual values before storage. The allow
parameter specifies the list of available templates. The prefer parameter specifies
which template is preferred, although NART always chooses to use whichever
available template produces the smallest data size for storage. If the install
parameter is set, NART initializes the configuration and calibration structure with
the preferred template when the command is processed. This process replaces any
data on the device with the contents of the template.
No data is ever written to the device by this command. Writing to the device is
done with the command commit
Generic
HB112
HB116
XB112
XB113
ssid
Set the PCIE subsystem ID that should be set in the adapter
svid
Set the PCIE subvendor ID that should be set in the adapter
devicetype
regdmn
6-18
Set the device type of the adapter. Available choices are:
CardBus
PCI
MiniPCI
AP
PCieMini
PCIExpress
PCIE Desktop
Set the regulatory domain code that should be written to EEPROM/OTP /Flash.
Refer to Table 2-8 of the AR93xx EEPROM Guide

December 2010

Chapter

Command
Descrf ptton
txmask
Set the tx chain mask of the adapter. Refer to Table 2-8 of the AR93xx EEPROM
Guide
rxm.ask
Set the rx chain mask of the adapter. Refer to Table 2-8 of the AR93xx EEPROM
Guide
opflags
Set the supported options of the adapter. Refer to Table 2-8 of the AR93xx
EEPROM Guide
antctrlcommon2g
Set 2 GHz Antenna control options. Refer to Table 2-9 of the AR93xx EEPROM
Guide
antctrlcommon22g
Guide
antCtrlChain2g
Guide
antctrlcommon5g
Guide
antctrlcommon25g
Guide
antCtrlChainSg
Guide
xatten1Margin2g
Set 2 GHz Strong Signal Parameters. Refer to Table 2-9 of the AR93xx EEPROM
Guide
xatten1Margin5g
Guide
xatten1Marginlow5g
Guide
xatten1Marginhigh5g
Set 5 GHz Strong Signal Parameters. Refer to table 2-11 of the AR93xx EEPROM
Guide
xattenldb2g
Guide
xattenldb5g
Guide
xattenldblow5g
Guide
xattenldbhigh5g
Guide
quickdrop2g
Guide
quickdrop5g
Guide
quickdroplow
Guide
quickdrophigh
Guide
txgainTable
Set tx gain table selection. Refer to table 2-8 of the AR93xx EEPROM Guide
rxgainTable
Set the rx gain table selection. Refer to table 2-8 of the AR93xx EEPROM Guide


December 2010
6-19
Chapter

Command
Descrfptton
temperatureCompensation Enable temperature compensation. Refer to table 2-8 of the AR93xx EEPROM
Guide
tempSlope2g
Set 2Ghz temperature slope value. Refer to table 2-8 of the AR93xx EEPROM
Guide
tempSlope5g
Set 5 GHz temperature slope value. Refer to table 2-8 of the AR93xx EEPROM
Guide
tempSlopelow
Guide
tempSlopehigh
Guide
thermometer
Set which chain's thermometer should be used. Refer to table 2-8 of the AR93xx
EEPROM Guide
eepromWriteEnable
Set GPIO for EEPROM protection. Refer to table 2-8 of the AR93xx EEPROM Guide
spurchans2g
Set 2 GHz channels for spur mitigation. Refer to table 2-9 of the AR93xx EEPROM
Guide
papdenable
Enable PA predistortion. Refer to table 2-8 of the AR93xx EEPROM Guide
ChainMaskReduce
Enable adapter power management. Refer to table 2-8 of the AR93xx EEPROM
Guide
common\rfkill.art
Enable calling of this file to correctly configure the reference design for RF silent
mode of operation.
common\wow.art
Call this file to correctly configure the reference design for Wake On Wireless mode
of operation.
hbl12\
hb 112..Jrg_pwr_v2.art
Each reference design has its own version of this file. It is called to set the target
power values of the reference design. Refer to "$reflD_power.art'' that further
describes this file
hb116\ctl_hb116Jtotxbf.art Each reference design will have its own version of this file. It is called to set the
CTL values of the reference design. Refer to "Describing ctl_$refID.art" that further
describes this file.
$reflD_power.art
lbis file contains reference design-specific target power values. Target power
values describe the power values that can be set in the reference design for
each rate and still meet EVM and Spectral Mask limitations. These powers are
not necessarily CTL compliant (these powers get set in the CTL file). This file
is called by the reference design $refld.ref file and can be found in the
reference design specific directories. Below is an example of one of the target
power files:
# Target power freq piers for CCK, Max 2 piers, in order of fO, fl, f2
set caltgtfreqcck=2412,2472;
# Target power for each pier defined in caltgtfreqcck
# 4 values represent the target power in dBm for the following data rate
# lL_SL,SS,llL,llS
set caltgtpwrcck=v. (17,17,17,17),f.O;
set caltgtpwrcck=v. (17,17,17,17),f.1;
6-20

December 2010

Chapter
# Target power freq piers for OFDM legacy 2G, Max 3 piers, in order of fO, fl, f2
set caltgtfreq2g=2412,2437,2472;
# Target power for each pier defined in caltgtfreq2g
# r6_24,r36,r48,r54
set caltgtpwr2g=v. (17,17,16,16),f.O;
set caltgtpwr2g=v. (17,17,16,16),f.l;
set caltgtpwr2g=v. (17,17,16,16),f.2;
#Target power freq piers for OFDM legacy 5G, Max 8 piers, in order of fO, fl,
set caltgtfreq5g=5180,5240,5320,5400,5500,5600,5700,5825;
... f7
# Target power for each pier defined in caltgtfreq5g

# r6_24,r36,r48,r54
set caltgtpwr5g=v. (15,15,14,12),f.O;
# Target power freq piers for HT20 2G, Max 3 piers, in order of fO, fl, f2
set caltgtfreqht202g=2412,2437,2472;
# Target power for each pier defined in caltgtfreqht202g
#
MCSO 8 16,MCSl 3 9 11_17_19,MCS4,MCSS,MCS6,MCS7,MCS12,MCS13,MCS14,MCS15,MCS20,MCS21,MCS2
2,MCS23
set caltgtpwrht202g=v. (16,16,16,16,16,15,16,16,15,14,14,14,14,13),f.O;
set caltgtpwrht202g=v. (16,16,16,16,16,15,16,16,15,14,14,14,14,13),f.1;
#Target power freq piers for HT20 5G, Max 8 piers, in order of fO, fl,
set caltgtfreqht205g=5180,5240,5320,5400,5500,5700,5745,5825;
... f7

#
MCS0_8_16,MCS1_3_9_11_17_19,MCS4,MCS5,MCS6,MCS7,MCS12,MCS13,MCS14,MCS15,MCS20,MCS21,MCS2
2,MCS23
set caltgtpwrht205g=v. (15,15,15,14,13,12,15,14,13,12,11,11,11,9),f.O;
set caltgtpwrht205g=v. (15,15,15,14,13,12,15,14,13,12,11,11,11,9),f.l;
set caltgtpwrht205g=v. (15,15,15,14,12,ll,15,13,12,11,10,10,10,B),f.3;
# Target power freq piers for HT40 2G, Max 3 piers, in order of fO, fl, f2
set caltgtfreqht402g=2412,2437, 2472;


December 2010
6-21
Chapter

#
MCS0_8_16,MCS1_3_9_11_17_19,MCS4,MCSS,MCS6,MCS7,MCS12,MCS13,MCS14,MCS15,MCS20,MCS21,MCS2
2,MCS23
set caltgtpwrht402g=v. {15,15,15,15,15,14,15,15,14,13,13,13,13,12),f.O;
set caltgtpwrht402g=v. {15,15,15,15,15,14,15,15,14,13,13,13,13,12),f.l;
set caltgtpwrht402g=v. {15,15,15,15,15,14,15,15,14,13,13,13,13,12),f.2;
#Target power freq piers for HT40 5G, Max 8 piers, in order of fO, fl,
set caltgtfreqht405g=5180,5240,5320,5400,5500,5700,5745,5825;
... f7

#
MCS0_8_16,MCS1_3_9_11_17_19,MCS4,MCS5,MCS6,MCS7,MCS12,MCS13,MCS14,MCS15,MCS20,MCS21,MCS2
2,MCS23
set caltgtpwrht405g=v. {14,14,14,13,12,11,14,13,12,11,10,10,10,8),f.O;
Table 6-7 describes the commands used in this file
NOTE: There are two variable name types used to set the target power table
arguments. The document uses the names from the .art file and makes cross
reference to the tables of the AR93xx EEPROM Device Configuration Gujde which uses
the alternative names. Both names are valid and either one can be used to achieve
the same result.
Table 6-7. Description of Target Power File Commands

Command
caltgtfreqcck
caltgtpwrcck
Description
Set the Frequency piers for 2 GHz CCK rates. Refer to Table 2-14 of the AR93xx
EEPROM Guide
Used to set the per rate powers for each frequency pier of the 2 GHz CCK rates. Refer
to Table 2-16 of the AR93xx EEPROM Guide
6-22
caltgtfreq2g
Set the Frequency piers for 2 GHz OFDM rates. Refer to Table 2-14 of the AR93xx
EEPROM Guide
caltgtpwr2g
Used to set the per rate powers for each frequency pier of the 2 GHz OFDM rates.
caltgtfreq5g
Set the Frequency piers for 5 GHz OFDM rates. Refer to Table 2-14 of the AR93xx
EEPROM Guide

December 2010

Chapter
Table 6-7. Description of Target Power File Commands (continued)

Command
caltgtpwr5g
Description
Used to set the per rate powers for each frequency pier of the 5 GHz OFDM rates.
caltgtfreqht202g
Set the Frequency piers for 2 GHz HT20 rates. Refer to Table 2-14 of the AR93xx
EEPROM Guide
caltgtpwrht202g
Used to set the per rate powers for each frequency pier of the 2 GHz HT20 rates.
caltgtfreqht205g
EEPROM Guide
caltgtpwrht205g
caltgtfreqht402g
EEPROM Guide
caltgtpwrht402g
Refer to table 2-19 of the AR93xx EEPROM Guide
caltgtfreqht405g
Set the Frequency piers for 5 GHz HT40 rates. Refer to table 2-14 of the AR93xx
EEPROM Guide
caltgtpwrht405g
Refer to table 2-19 of the AR93xx EEPROM Guide
Describing ctl_SreflD.art
Contains reference design-specific Conformance Test Llmited powers that
must be applied in order for the reference design still to be compliant with the
regulatory domains in which the card will operate. When setting rate-specific
powers, software drivers take the lowest of the target power and CTL limited
power at the current channel of operation. Below is an example of one of the
CTL files:
#Note: Official Regulatory power for US/ETSI/JP on Oct212010.
#Note: US Power are the same with or without TXBF.
#Note: JP/ETSI Power is affected by TXBF for lln. Below Tables are for no TXBF for JP/
ETSI
#Note: General information. B Frequency points for 5Ghz, 4 Frequency points for 2Ghz
#Note: Taiwan Power numbers added on Oct282010. It affects FCC Unii2 band lla and
llna HT20.
#Note: Korea Power numbers are not included yet
##2GHz CTL List
# Test Group Oxll: US and CANADA (FCC) 802.llb mode CTL
set 2GHz.ctl.Index[O]=Oxll;
set 2GHz.ctl.Frequency[0]=2412,2417,2422,2462;
set 2GHz.ctl.Power[O]=
17 ,17 ,17 ,16.5;
set 2GHz.ctl.BandEdge[O]= 1
,1
,1
,O;
#Test Group Oxl2: US and CANADA (FCC) 802.llg mode CTL
set 2GHz.ctl.Index[l]=Dx12;
set 2GHz.ctl.Power[l]=
10.5,16.5,16.5 ,10;
set 2GHz.ctl.BandEdge[l]= 1
,1
,1
,0;


December 2010
6-23
Chapter
#Test Group Oxl5: us and CANADA (FCC) 802.lln HT20 2GHz mode CTL
set 2GHz.ctl.Index[2]=0xl5;
set 2GHz.ctl.Power[2]=
11 ,16 ,16 ,10;
set 2GHz.ctl.BandEdge[2]= l
,1
,1
, 0;
#Test Group Ox17: us and CANADA (FCC) 802.lln HT40 2GHz mode CTL
set 2GHz.ctl.Index[3]=0xl7;
9.5 ,13 ,13 ,9.5;
set 2GHz.ctl.BandEdge[3]= 1
,1
,1
,O;
# Test Group Ox41: Japan (MKK) 802.llb mode CTL
set 2GHz.ctl.Index[4]=0x41;
15.5,15.5,14.5,16;
,1
,O
,O;
#Test Group Ox42: Japan (MKK) 802.llg mode CTL
17.5,17.5,17.5,17;
,1
,1
,O;
#Test Group Ox45: Japan (MKK) 802.lln HT20 2GHz mode CTL
17.5,17.5,17.5,17;
,1
,1
,O;
15 ,17.5,17.5,17.5;
,1
,1
,O;
# Test Group Ox31: Europe (ETSI) 802.llb mode CTL
12.5,12.5,12.5,12.5;
,1
,1
,O;
#Test Group Ox32: Europe (ETSI) 802.llg mode CTL
12.5,13 ,12.5,12.5;
,1
,1
,O;
#Test Group Ox35: Europe (ETSI) 802.lln HT20 2GHz mode CTL
set 2GHz.ctl.Index[lO]=Ox35;
set 2GHz.ctl.Frequency[l0]=2412,2417,2442,2472;
12.5,13 ,12.5,12.5;
,1
,1
IO;
set 2GHz.ctl.Index[ll]=Ox37;
set 2GHz.ctl.Frequency[lll=2422,2427,2432,2462;
set 2GHz.ctl.Power[ll]=
13 ,13 ,13 ,12.5;
set 2GHz.ctl.BandEdge[lll= 1
,1
,1
,O;
6-24

December 2010
Chapter
##5GHz CTL List

#Test Group OxlO: US and CANADA (FCC) 802.lla mode CTL
set 5GHz.ctl.Index[O]=OX10;
set SGHz.ctl.Frequency[0]=5180,5260,5320,5500,5520,5700,5745,5765;
set 5GHz.ctl.Power[O]=
12 ,11.5,12 ,14.5,14 ,13.5,15 ,14.5;
,1
,1
,1
,1
,1
,1
,O;
#Test Group Ox16: us and CANADA (FCC) 802.lln HT20 5GHz mode CTL
set SGHz.ctl.Index[l]=Oxl6;
set 5GHz.ctl.Frequency[1]=5180,5240,5260,5500,5520,5700,5745,5825;
set 5GHz.ctl.Power[l]=
12 ,12.5,11.5,15 ,14 ,13.5,15 ,14.5;
set 5GHz.ctl.BandEdge[l]= 1
,1
,1
,1
,1
,1
,1
,O;
#Test Group Ox18: us and CANADA (FCC) 802.lln HT40 SGHz mode CTL
set 5GHz.ctl.Index[2]=0xlB;
11 ,13.5,12 ,8.5 ,14 ,14.5,15.5,15;
,1
,1
,1
,1
,1
,1
,O;
#Test Group Ox40: Japan (MKK) 802.lla mode CTL
set SGHz.ctl.Index[3]=0x40;
14.5,15 ,15 ,15 ,15 ,15 ,14 ,14;
,1
,1
,1
,1
,1
,1
,O;
15 ,15 ,15 ,15 ,15 ,15.5,15.5,14.5;
,1
,1
,1
,1
,1
,1
,O;
14.5,14 ,14.5,14.5,14.5,14 ,14 ,14.5;
,1
,1
,1
,1
,1
,1
,O;
#Test Group Ox30: Europe (ETSI) 802.lla mode CTL
16.5,16.5,16.5,16.5,16.5,16.5,13.5,13.5;
,1
,1
,1
,1
,1
,1
,O;
set SGHz.ctl.Index[7]=0x36;
16.5,16.5,16.5,16.5,16.5,13.5,13.5,14;
,1
,1
,1
,1
,1
,1
,O;
#Test Group Ox38: Europe (ETSI) 802.lln HT40 SGHz mode CTL
15.5,15.5,15.5,15.5,14 ,14 ,14 ,14;
,1
,1
,1
,1
,1
,1
,O;
Table 6-8 describes the commands used in this file.


December 2010
6-25
Chapter
Table 6-8. Description of CTL command File

Command
2GHz.ctl.Index
2GHz.ctl.Frequency
2GHz.ctl.Power
2GHz.ctl.BandEdge
SGHz.ctl.Index
5GHz.ctl.Frequency
SGHz.ctl.Power
5GHz.ctl.BandEdge
6-26
Description
Set the 2 GHz regulatory domain Index. Refer to Table 2-21 of the AR93xx EEPROM
Guide
Set the 2 GHz band edge frequencies. Refer to Table 2-22 of the AR93xx EEPROM
Guide
Set the 2 GHz band edge power values. Refer to Table 2-22 of the AR93xx EEPROM
Guide
Set the 2 GHz band edge flags values. Refer to Table 2-22 of the AR93xx EEPROM
Guide
Set the 5 GHz regulatory domain Index. Refer to Table 2-21 of the AR93xx EEPROM
Guide
Set the 5 GHz band edge frequencies. Refer to Table 2-22 of the AR93xx EEPROM
Guide
Set the 5 GHz band edge power values. Refer to Table 2-22 of the AR93xx EEPROM
Guide
Set the 5 GHz band edge flags values. Refer to Table 2-22 of the AR93xx EEPROM
Guide

December 2010

Chapter
Sample CART Command List

The command list presented in this chapter represents the commands
available in CART or NART for ART2 version 2.13. To obtam the applicable
list of commands for another version, use the help command within that
version of NART/CART (help level=2 for detailed descriptions; help for
short descriptions).
When using the help command in a terminal window, there are two
adjustments that may increase readability of the command descriptions:
Adjust the width of the terminal window so that line wraps do not occur.
For version 2.13, a width of 150 characters is sufficient.
Tum off the printing of the message code and severity in the help output
by using the command: error code=1012; response=message.
When CART and NART both implement the same command, CART also
accepts all of the NART parameters listed in Appendix B, "Sample NART
Command List"
. For example, the CART command rr accepts the parameter address listed in
the NART section as well as the parameters instance and screen listed in this
section.


December 2010
A-1
EJ Chapter
exit: exits the program
help, ?: supplies information about the commands and parameters
topic, name: the command name, parameter name, or topic
type=text; dimension=[1 O];
show: what do you want to see?
all[O]
synopsis[1]
parameters[2]
desaiption[3]
depth, level: the numbers of levels of documentation shown
type=decimal; minimum=O; maximum=2; default=2;
index: show an index of topics?
no[O]
yes[1]
connect: establishes a network connection to the nart process
dut[O]
golden[1]
blocker[2]
host, computer: the name or ip address of the computer running nart
type=text: default=localhost:
port: the port number used by nart
type=unsigned; minimum=1000; maximum=65535; default=2390;
hello: checks that the network link to nart is working, synchronizes commands and responses
prompt: asks the user to supply a value for the specified variable
name: the name of the variable
type= text;
help: a short description
type= text;
type: the type of the variable
mac, address[109]
decimal, integer[100]
unsigned[117]
hexadecimal, x[120]
float, real[102]
text, sbing[116]
dimension: the maximum dimension
type=decimal;
minimum: the minimum value of the variable
type= text;
maximum: the maximum value ofthe variable
type= text;
units: units
type= text;
default: default value
type= text;
assign: sets the specified variable to the specified value
deassign: deletes the variable
show: displays the value of the variable
load, card, attach: loads the card
unload, remove, detach: unloads the card
path, loss: sets the path loss between the various pieces of test equipment
device, path: the path to the test equipment
golden, path[O]: dut to golden
PowerMeter, pm[1 ]: dut to power meter
SpectrumAnalyzer, sa[2]: dut to spectrum analyzer
blocker[3]: dut to blocker
gpm[4]: golden to power meter
A-2

December 2010

Chapter
gsa[5]: golden to spectrum analyzer

gblocke~6]: golden to blocker
frequency: lhe frequency at which the loss value is measured
type=unsigned; minimum=2000; maximum=6000; units=MHz; dimension=[20];
chain: lhe chain mask for which lhe loss value is measured
type=hexadecimal; minimum=1; maximum=7; default=7; dimension=[3];
loss, value: the path loss value
type=decimal; minimum=O; maximum=1000; unlts=dB; dimension=[20];
gu2: obsolete parameter
type=decimal:
gu5: obsolete parameter
type=decimal:
bu2: obsolete parameter
type=decimal:
bu5: obsolete parameter
type=decimal;
sa2: obsolete parameter
type=decimal;
sa5: obsolete parameter
type=decimal;
pm2: obsolete parameter
type=decimal;
pm5: obsolete parameter
type=decimal:
transmi~ tx, t: causes the specified device to transmit
rx: which device is the receiver
type=decimal; minimum=-1; maximum=2; default=O;
none[-1]
dut[O]
golden[1]
blocke~2]
be: which device is the transmitter

type=decimal; minimum=-1: maximum=2; default=1:
none[-1]
dut[O]
golden[1]
blocke~2]
blocker: which device is the blocker

type=decimal: minimum=-1: maximum=2; default=-1;
none[-1]
dut[O]
golden[1]
blocke~2]
frequency, t the channel carrier frequency

type=unsigned; minimum=2400; maximum=6000; default=2412; unils=M Hz; dimension=[200];
rate, r: the data rates used
6[0]
9[1]
12[2]
18[3]
24[4]
36[5]
48[6]
54[7]
11[8]
21[9]
2s[10]
51[11]


December 2010
A-3
EJ Chapter
5s[12]
111[13]
11s[14]
to, mcs0[32]
t1 , mcs1 [33]
t2, mcs2[34]
t3, mcs3[35]
t4, mcs4[36]
t5, mcs5[37]
t6, mcs6[38]
t7, mcs7[39]
t8, mcs8[40]
t9, mcs9[41]
t10, mcs10[42]
t11, mcs11[43]
t12, mcs12[44]
t13, mcs13[45]
t14, mcs14[46]
t15, mcs15[47]
t16, mcs16[48]
t17, mcs17[49]
t18, mcs18[50]
t19, mcs19[51]
t20, mcs20[52]
t21, mcs21 [53]
t22, mcs22[54]
t23, mcs23[55]
fO, mcs0/40[64]
f1, mcs1/40[65]
f2, mcs2/40[66]
f3, mcs3/40[67]
f4, mcs4/40[68]
f5, mcs5/40[69]
16, mcs6/40[70]
f7, mcs7/40[71]
f8, mcs8/40[72]
f9, mcs9/40[73]
f10, mcs10/40[74]
f11, mcs11/40[75]
f12, mcs12/40[76]
f13, mcs13/40[77]
f14, mcs14/40[78]
f15, mcs15/40[79]
f16, mcs16/40[80]
f17, mcs17/40[81]
f18, mcs18/40[82]
f19, mcs19/40[83]
f20, mcs20/40[84]
f21, mcs21/40[85]
f22, mcs22/40[86]
f23, mcs23/40[87]
all[1000]
legacy[1001]
ht20[1002]
ht40[1003]
interleaveRates, ir: interleave packets from different rates?
no[O]
yes[1]
A-4

December 2010

Chapter
CART[2]
packetCount, pc, np: the number of packets sent
type=decimal; minimum=-1: maximum=2147483647; default=100; dimension=[200];
infinite[O]
packetLength, pl: the length of the packets
type=unsigned; minimum=30; maximum=4000; default=1000; units=Byte; dimension=[200];
chain, ch: the chain mask used for both transmit and receive
txehain: the chain mask used for transmit
type=hexadecimal; minimum=1: maximum=7; default=7; dimension=[200];
rxChain: the chain mask used for receive
type=hexadecimal; minimum=1: maximum=7; default=7;
transmitPower, tp, txp: the transmit power used
type=ftoat: minimum=-100; maximum=31.5; default=-100; units=dBm; dimension=[200];
target[-1 00]
pcdac, txgain, txg: the tx gain used by the transmitter
type=decimal; minimum=O; maximum=100; default=30; dimension=[200];
delay: delay between receiver ready and transmitter start
type=decimal: minimum=O; maximum=10000; default=O: units=ms;
temperature: the temperature at which the test is run
type=decimal; minimum=-1: maximum=100; default=-1; units=deg C; dimension=[200];
none[-1]
attenuation: the attenuation between the golden unit and the dut
type=decimal; minimum=O: maximum=110; default=O; unils=dB; dimension=[200];
inputSignalStrength, iss: the expected input signal strength at the dut
type=decimal; minimum=-120; maximum=O; default=O; units=dB; dimension=[200];
aggregate: the number of aggregated packets
powerMeter, pm: measure power
none[O]: nothing is measured
combined[1]: the combined output signal is measured
isolated[2]: attenuators are used to isolate and measure each chain separately
evm: measure evm
spectralMask, mask: measure spectral mask
fa, ppm: measure frequency accuracy
current, cm: measure current consumption
rxvsg: measure rxvsg
average, avg: number of measurements taken and averaged
type=decimal; minimum=-1; maximum=1000; default=-1;
automatic[-1]
delta: frequency delta for blocker unit
type=decimal; minimum=-1000; maximum=1000; default=25; units=MHz; dimension=[200];
bfrequency, bfreq, bf: frequency for blocker unit


December 2010
A-5
EJ Chapter
type=decimal; minimum=2000; maximum=8000; default=2437; units=MHz; dimension=[200];
biss: input signal strength from blocker unit
blp: transmit power for blocker unit
type=ftoat; minimum=O; maximum=31.5; default=-1; units=dBm; dimension=[200];
target[-100]
log: log data
no[O]
yes[1]
logFile, If: log file name
type=text; default=$LogFileName;
retry: the number of times a packet is retransmitted
type=unsigned; minimum=O; maximum=15; default=O;
broadcast, be: if set to 1the packets are broadcast, if set to 0 the packets are unicast
no[O]
yes[1]
type=decimal; minimum=-1; maximum=2147483647; default=60000; units=ms;
foreverf-1]
dump: the number of bytes of each packet displayed in the nart log
promiscuous: if set to 1, all packet types are received
no[O]
yes[1]
bssid: the bssid used by the transmitter and receiver
type=mac address; default=50:55:55:55:55:05;
mactx: the mac address used by the transmitter
macrx: the mac address used by the receiver
type=mac address; default=10:11 :11 :11 :11 :01;
calibrate: calibrate transmit power
iterate-combined, ic[3]: the combined output signal is measured with iteration to reach the power goal
iterate-isolated, ii[4]: attenuators are used to isolate and measure each chain separately with iteration to reach the power goal
nf: noise floor value
current[O]
calculate[1]
rssical: measure and calibrate rssi
no[O]
yes[1]
reset: reset device before operation
no[O]
yes[1]
automatic[-1]
statistic: statistic
ht40: use 40MHz channel
none[O]
low[-1]
high[1]
automatic[2]
gi, sgi: use short guard interval
no[O]
yes[1]
tx99: use tx.99 mode, small, constant interframe spacing
A-15

December 2010

Chapter
no[O]
yes[1]
tx100: use tx100 mode, continuous data transmission
no[O]
yes[1]
interFrameSpacing, ifs, fs: spacing between frames
regularf-1]
tx.100[0]
tx.99[1]
deafMode: disable receiver during transmission
no[O]
yes[1]
pattern: data pattern
type=hexadecimal; minimum=O; maximum=ff; default=O; dimension=[100];
chipTemperature: wait for chip temperature to exceed this value
receive, rx, r: causes the specified device to receive
none[-1]
dut[O]
golden[1]
blockerf2]
tx: which device is the transmitter
type=decimal; minimum=-1; maximum=2; default=1;
none[-1]
dut[O]
golden[1]
blockerf2]
none[-1]
dut[O]
golden[1]
blockerf2]
frequency, f: the channel carrier frequency
type=unsigned; minimum=2400; maximum=6000; default=2412; units=M Hz; dimension=[200];
6[0]
9[1]
12[2]
18[3]
24[4]
36[5]
48[6]
54[7]
11[8]
21[9]
2s[10]
51[11]
5s[12]
111[13]
11s[14]
tO, mcs0[32]
t1 , mcs1 [33]
t2, mcs2[34]
t3, mcs3[35]


December 2010
A-7
EJ Chapter
t4, mcs4[36]
ts, mcs5(37]
t6, mcs6[38]
t7, mcs7[39]
t8, mcs8[40]
t9, mcs9[41]
t10, mcs10[42]
t11, mcs11[43]
t12, mcs12[44]
t13, mcs13[45]
t14, mcs14[46]
t15, mcs15[47]
t16, mcs16[48]
t17, mcs17[49]
t18, mcs18[50]
t19, mcs19[51]
t20, mcs20[52]
t21, mcs21 [53]
t22, mcs22[54]
t23, mcs23[55]
fO, mcs0/40[64]
f1, mcs1/40[65]
f2, mcs2/40[66]
f3, mcs3/40[67]
f4, mcs4/40[68]
f5, mcs5/40[69]
16, mcs6/40[70]
f7, mcs7/40[71]
f8, mcs8/40[72]
f9, mcs9/40[73]
f10, mcs10/40[74]
f11, mcs11/40[75]
f12, mcs12/40[76]
f13, mcs13/40[77]
f14, mcs14/40[78]
f15, mcs15/40[79]
f16, mcs16/40[80]
f17, mcs17/40[81]
f18, mcs18/40[82]
f19, mcs19/40[83]
f20, mcs20/40[84]
f21, mcs21/40[85]
f22, mcs22/40[86]
f23, mcs23/40[87]
all[1000]
legacy[1001]
ht20[1002]
ht40[1003]
no[O]
yes[1]
CART[2]
infinile[O]
packetlength, pl: the length of the packets
A-8

December 2010
Chapter
type=hexadecimal; minimum=1; maximum=?; default=?; dimension=[200];

txChain: the chain mask used for transmit
type=hexadecimal; minimum=1; maximum=?; default=?; dimension=[200];
type=hexadecimal; minimum=1; maximum=?; default=?;
type=ftoat; minimum=-100; maximum=31.5; default=-100; units=dBm; dimension=[200];
target[-1 00]
type=decimal; minimum=O; maximum=10000; default=O; units=ms;
type=decimal; minimum=-1; maximum=100; default=-1; units=deg C; dimension=[200];
none[-1]
type=decimal; minimum=O; maximum=110; default=O; unils=dB; dimension=[200];
combined(1]: the combined output signal is measured
evm: measure evm
isolated(2]: attenuators are used to isolate and measure each chain separately
automatic[-1]
btp: transmit power for blocker unit
target[-1 00]
log: log data


December 2010
A-9
EJ Chapter
no[O]
yes[1]
no[O]
yes[1]
type=decimal; minimum=-1; maximum=2147483647; default=60000; untts=ms;
forever[-1]
no[O]
yes[1]
type=mac address: default=20:22:22:22:22:02;
calibrate: calibrate transmtt power
isola1ed[2]: attenuators are used to isolate and measure each chain separately
iterate-<::ombined, ic[3]: the combined output signal is measured with tteration to reach the power goal
iterate-isolated, ii[4]: attenuators are used to isolate and measure each chain separately wtth iteration to reach the power goal
current[O]
calculate[1]
no[O]
yes[1]
no[O]
yes[1]
automatic[-1]
none[O]
low[-1]
high[1]
automatic[2]
no[O]
yes[1]
no[O]
yes[1]
tx.100: use tx100 mode, continuous data transmission
no[O]
yes[1]
A-10

December 2010

Chapter
regularf-1]
tx.100[0]
tx.99[1]
no[O]
yes[1]
type=unsigned; minimum=O: maximum=255; default=O;
link, rxl, I: causes one device to receive while another is transmitting
none[-1]
dut[O]
golden[1]
blockerf2]
type=decimal; minimum=-1: maximum=2; default=1;
none[-1]
dut[O]
golden[1]
blocker12]
none[-1]
dut[O]
golden[1]
blockerf2]
type=unsigned; minimum=2400; maximum=6000; default=2412; units=MHz; dimension=[200];
6[0]
9[1]
12[2]
18[3]
24[4]
36[5)
48[6)
54[7]
11[8]
21[9]
2s[10]
51[11]
5s[12]
111[13]
11s[14]
to, mcs0[32J
t1 , mcs1 [33]
t2, mcs2[34]
t3, mcs3[35]
t4, mcs4[36)
ts, mcs5[37]
t6, mcs6[38]
t7, mcs7[39]
ts, mcs8[40]
t9, mcs9[41)
t10, mcs10[42]


December 2010
A-11
EJ Chapter
t11, mcs11[43]
t12, mcs12[44]
t13, mcs13[45]
t14, mcs14[46]
t15, mcs15[47]
t16, mcs16[48]
t17, mcs17[49]
t18, mcs18[50]
t19, mcs19[51]
t20, mcs20[52]
t21, mcs21 [53]
t22, mcs22[54]
t23, mcs23[55]
fO, mcs0/40[64]
f1, mcs1/40[65]
f2, mcs2/40[66]
f3, mcs3/40[67]
f4, mcs4/40[68]
f5, mcs5/40[69]
16, mcs6/40[70]
f7, mcs7/40[71]
f8, mcs8/40[72]
f9, mcs9/40[73]
f10, mcs10/40[74]
f11, mcs11/40[75]
f12, mcs12/40[76]
f13, mcs13140[77]
f14, mcs14/40[78]
f15, mcs15/40[79]
f16, mcs16/40[80]
f17, mcs17/40[81]
f18, mcs18/40[82]
f19, mcs19/40[83]
f20, mcs20/40[84]
f21, mcs21/40[85]
f22, mcs22/40[86]
f23, mcs23/40[87]
all[1000]
legacy[1001]
ht20[1002]
ht40[1003]
inter1eaveRates, ir: inter1eave packets from different rates?
no[O]
yes[1]
CART[2]
packetCount, pc, np: lhe number of packets sent
infinile[O]
type=unsigned: minimum=30; maximum=4000; default=1000; units=Byte; dimension=[200];
chain, ch: lhe chain mask used for both transmit and receive
type=hexadecimal; minimum=1: maximum=7; default=7; dimension=[200];
type=hexadecimal; minimum=1: maximum=7; default=7: dimension=[200];
type=hexadecimal; minimum=1: maximum=7; default=7;
A-12

December 2010

Chapter
target[-1 00]
type=decimal: minimum=O; maximum=100; default=30; dimension=[200];
type=decimal: minimum=O; maximum=10000; default=O; units=ms;
type=decimal; minimum=-1: maximum=100; default=-1; units=deg C; dimension=[200];
none[-1]
type=decimal; minimum=O; maximum=110; default=O; units=dB; dimension=[200];
evm: measure evm
combined[1): the combined output signal is measured
speclralMask, mask: measure spectral mask
isolated[2): attenuators are used to isolate and measure each chain separately
isolated[2): attenuators are used to isolate and measure each chain separately
type=decimal; minimum=-1: maximum=1000; default=-1:
automatic[-1]
type=decimal; minimum=-1000; maximum=1000; default=25; units=MHz: dimension=[200];
type=decimal; minimum=2000; maximum=BOOO; default=2437; units=MHz; dimension=[200];
type=decimal; minimum=-120; maximum=O: default=O; units=dB; dimension=[200];
blp: transmit power for blocker unit
target[-1 00]
log: log data
no[O)
yes[1]
type=text: default=$LogFileName;
type=unsigned; minimum=O: maximum=15; default=O;


December 2010
A-13
EJ Chapter
no[O]
yes[1]
type=decimal; minimum=-1; maximum=2147483647; default=60000; unlts=ms;
foreverf-1]
no[O]
yes[1]
type=mac address; default=10:11:11 :11 :11 :01;
iterate-combined, ic[3]: the combined output signal is measured with Iteration to reach the power goal
current[O]
calculate[1]
no[O]
yes[1]
no[O]
yes[1]
automatic[-1]
none[O]
low[-1]
high[1)
automalic[2]
no[O]
yes[1]
no[O]
yes[1]
tx.100: use tx.100 mode, continuous data transmission
no[O]
yes[1]
interframeSpacing, ifs, fs: spacing between frames
type=decimal; minimum=-1; maximum=1: default=-1;
regularf-1)
tx.100[0]
tx.99[1]
no[O]
yes[1)
A-14

December 2010

Chapter

txl: causes one device lo transmit while another is receiving
none[-1]
dut[O]
golden[1]
blocker12]
none[-1]
dut[O]
golden[1]
blockert2]
none[-1]
dut[O]
golden[1]
blocker12]
6[0]
9[1]
12[2]
18[3]
24[4]
36[5]
48[6]
54[7]
11[8]
21[9]
2s[10]
51[11]
5s[12]
111[13]
11s[14]
tO, mcs0[32]
t1 , mcs1 [33]
t2, mcs2[34]
t3, mcs3[35]
t4, mcs4[36]
t5, mcs5[37]
t6, mcs6[38]
t7, mcs7[39]
t8, mcs8[40]
t9, mcs9[41]
t10, mcs10[42]
t11, mcs11[43]
t12, mcs12[44]
t13, mcs13[45]
t14, mcs14[46]
t15, mcs15[47]
t16, mcs16[48]
t17, mcs17[49]


December 2010
A-15
EJ Chapter
t18, mcs18[50]
t19, mcs19[51]
t20, mcs20[52]
t21, mcs21[53]
t22, mcs22[54]
t23, mcs23[55]
fO, mcs0/40[64]
f1, mcs1/40[65]
f2, mcs2/40[66]
f3, mcs3/40[67]
f4, mcs4/40[68]
f5, mcs5/40[69]
f6, mcs6/40[70]
f7, mcs7/40[71]
f8, mcs8/40[72]
f9, mcs9/40[73]
f10, mcs10/40[74]
f11, mcs11/40[75]
f12, mcs12/40[76]
f13, mcs13/40[77]
f14, mcs14/40[78]
f15, mcs15/40[79]
f16, mcs16/40[80]
f17, mcs17/40[81]
f18, mcs18/40[82]
f19, mcs19/40[83]
f20, mcs20/40[84]
f21, mcs21/40[85]
f22, mcs22/40[86]
f23, mcs23/40[87]
all[1000]
legacy[1001]
ht20[1002]
ht40[1003]
no[O]
yes[1]
CART[2]
type=decimal; minimum=-1; maximum=2147483647; default=100; dimension=[200];
infinile[O]
type=hexadecimal; minimum=1; maximum=7; default=7;
target[-1 00]
type=decimal; minimum=O; maximum=10000; default=O; units=ms;
temperature: the tempera1ure at which the test is run
type=decimal; minimum=-1; maximum=100; default=-1; units=deg C; dimension=[200];
A-16

December 2010
Chapter
none[-1]
type=decimal; minimum=O; maximum=110; default=O; units=dB; dimension=[200];
evm: measure evm
automatic[-1]
btp: transmit power for blocker unit
target[-1 00]
log: log data
no[O]
yes[1]
retry: the number o1 times a packet is retransmitted
no[O]
yes[1]
duration: the maximum duration o1 the operation
type=decimal; minimum=-1; maximum=2147483647; default=60000; unils=ms;
forever[-1]


December 2010
A-17
EJ Chapter
no[O]
yes[1]
iterate-<::ombined, ic[3]: the combined output signal is measured with iteration to reach the power goal
current[O]
calculate[1]
no[O]
yes[1]
no[O]
yes[1]
automatic[-1]
none[O]
low[-1]
high[1]
automatic[2]
no[O]
yes[1]
no[O]
yes[1]
no[O]
yes[1]
regular[-1]
tx.100[0]
tx99[1]
no[O]
yes[1]
chipTemperab.Jre: wait for chip temperature to exceed this value
carrier: causes the device to transmit the carrier tone
tx, device[O]
temperab.Jre[1]
frequency, 1[2]
A-18
December 2010

Chapter
txChain, chain[3]
txgain, pcdac[4]
duration[5]
log[6]
powerMeter, pm[8]
speclralMask, mask[9]
sleep: pauses program execution for the specified number of milliseconds
report, status: produces a formatted report
test, if, calculate: evaluates an equation and prints the result
test, condition[O]
data: restores the data from a log file
filename, name, f: the name of the log file to read
screen: show the data on the screen as it is read
no[O]
yes[1]
filter, type: data type to read from the file, default is to use all data types
type=text; default=;
dump: dumps the data to a log file
filename, name, f: the name of the log file to write
screen: show the dala on the screen
no[O]
yes[1]
tiUe: an additional comment added to the file
filter, type: data type to write to the file, default is to use all data types
reset: resets the device
instance: which device
dut[O]
golden[1]
blocker[2]
screen: show results on the screen
no[O]
yes[1]
rr: reads a device register
dut[O]
golden[1]
blocker[2]
no[O]
yes[1]
rw: writes a device register with the specified value
dut[O]
golden[1]
blocker[2]
no[O]
yes[1]
sr, sl: prints the current list of sticky writes


December 2010
A-19
EJ Chapter
dut[O]
golden[1]
blocker12]
no[O]
yes[1]
sw: sticky write of a device field/register, sticky writes are perfonned after every device reset
dut[O]
golden[1]
blockert2]
no[O]
yes[1]
sc: clear sticky field/register from list, last-0n, first-0ff order
dut[O]
golden[1]
blockert2]
no[O]
yes[1]
fr: field read
dut[O]
golden[1]
blockert2]
no[O]
yes[1]
fw: field write
dut[O]
golden[1]
blockert2]
no[O]
yes[1]
fl: list all the matching fields
dut[O]
golden[1]
blockert2]
no[O]
yes[1]
mr: memory read
dut[O]
golden[1]
blockert2]
A-20

December 2010

Chapter
no[O]
yes[1]
mw: memory write
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
er: EEPROM read
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
ew: EEPROM write
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
or: OTP read
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
ow: OTP write
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
er: PCI config read
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
cw: PCI config write


December 2010
A-21
EJ Chapter
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
tgr: transmit gain table read
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
tgw: transmit gain table write
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
pl: tum on packet logging
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
set: set a configuration parameter on the card
get: get a configuration parameter from the card
clear: clear data records
commit, save: write configuration and calibration data to the device
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
pcie, boot: write pcie inililization data to the device
dut[O]
golden[1]
blockerf2]
no[O]
yes[1]
check: check calibration data on device
A-22

December 2010
Chapter
dut[O]
golden[1]
blocker12]
no[O]
yes[1]
backup: backup the configuration and calibration data from the device to a file
dut[O]
golden[1]
blockert2]
filename, name: the name of the backup file to write
type=text; default=$customer.backup;
equipment, powerMeter: select and install test equipment
type: type of the equipment
type=decimal; default=-1;
automatic[-1]
PowerMeter, pm[O]
Attenuatort11
Spectl'\JmAnalyzer, sa[2]
Supply, ps[3]
MultiMeter, mm[4]
Oven, Temperature[5]
model: equipment model number
type=decimal; default=O;
automatic[-1]
NRPZ11, Z11, RohdeAndSchwarz[O]
HP436A, 436A[1]
HPE4416A,E4416A(2]
HP4531, 4531[3]
IQV, IQF[4]
argument: arguments passed to the test equipment load function
delay[3]: set equipment settling time
comment: add a comment to a report
stop, cancel: cancel the current operation
branch, goto, loop: evaluate an equation and branch to the specified label if it is true
action: obsolete parameter
start, begin[O]
repeat, skip, goto[1]
condition, test, if: if this expression is true, control transfers to the specified label
type= text;
name, label: the target label
type= text;
label: create a target for a branch instruction
name, label: the target label
type= text;
log: tum on/off the log file
file: the name of the log file
type=text; minimum=none;
channel: retrieve and display a list of the valid channels
dut[O]
golden[1]
blockert2]


December 2010
A-23
EJ Chapter
no[O]
yes[1]
nolsefloor, nf: compute the noise floor
dut[O]
golden[1]
blocker[2]
no[O]
yes[1]
nfg: retrieve and display the calibrated noise floor measurements
dut[O]
golden[1]
blocker[2]
no[O]
yes[1]
targetPower, tp: retrieve and display the target power values
dut[O]
golden[1]
blocker[2]
no[O]
yes[1]
reference, refDeslgn: display the list of reference designs
error: allows you to control how error messages are displayed
code, number[O]: the individual message code or number
type: the message type
DEBUG[O]
CONTROL[1]
INF0[2]
WARNING[3]
ERROR[4]
response: the response
code[O]: show the 4 digit message code
type[1]: show the message type severity
message[2]: show the actual message
pause[3]: pause and wait for user response
bell[4]: ring the bell
log, file[5]: append message to the current log file
all[100]: same as code+type+message
none[101]: ignore error message
normal[102]: do the normal response
list: list all of the matching error messages
no[O]
yes[1]
short: use short format?
no[O]
yes[1]
version: retrieve CART version information
measure: measure power, evm without nart
template: controls the use of calibration templates
A-24

December 2010
Chapter

dut[O]
golden[1]
blockerf2]
no[O]
yes[1]


December 2010
A-25
EJ Chapter
A-26

December 2010

Chapter
ll
Sample NART Command List

The following provides the command descriptions contained in the NART
application for ART2, version 2.13.
exit: exits the program

help, ?: supplies information about the commands and parameters
topic, name: the command name, parameter name, or topic
type=text; dimension=[1 OJ;
show: what do you want to see?
all[O]
synopsis[1]
parameters[2]
desaiption[3]
depth, level: the numbers of levels of documentation shown
index: show an index of topics?
no[O]
yes[1]
hello: checks that the network link to nart is working, synchronizes commands and responses
transml~ tx, t: causes the specified device to transmit
type=unsigned; minimum=2400; maximum=6000; default=2412; units=M Hz;
6[0]
9[1]
12[2]
18[3]
24[4]
36[5]
48[6]
54[7]
11[8]
21[9]
2s[10]
51[11]
5s[12]
111[13]
11s[14]
to, mcs0[32]
t1 , mcs1 [33]


December 2010
B-1
ll Chapter
t2, mcs2[34]
t3, mcs3[35]
t4, mcs4[36]
t5, mcs5[37]
t6, mcs6[38]
t7, mcs7[39]
ts, mcs8[40]
t9, mcs9[41]
t10, mcs10[42]
t11, mcs11[43]
t12, mcs12[44]
t13, mcs13[45]
t14, mcs14[46]
t15, mcs15[47]
t16, mcs16[48]
t17, mcs17[49]
t18, mcs18[50]
t19, mcs19[51]
t20, mcs20[52]
t21, mcs21 [53]
t22, mcs22[54]
t23, mcs23[55]
fO, mcs0/40[64]
f1, mcs1/40[65]
f2, mcs2/40[66]
f3, mcs3/40[67]
f4, mcs4/40[68]
f5, mcs5/40[69]
f6, mcs6/40[70]
f7, mcs7/40[71]
f8, mcs8/40[72]
f9, mcs9/40[73]
f10, mcs10/40[74]
f11, mcs11/40[75]
f12, mcs12140[76]
f13, mcs13/40[77]
f14, mcs14/40[78]
f15, mcs15/40[79]
f16, mcs16/40[80]
f17, mcs17/40[81]
f18, mcs18/40[82]
f19, mcs19/40[83]
f20, mcs20/40[84]
f21, mcs21/40[85]
f22, mcs22/40[86]
f23, mcs23/40[87]
all[1000]
legacy[1001]
ht20[1002]
ht40[1003]
inter1eaveRates, ir: inter1eave packets from different rates?
no(O]
yes[1]
none[O]
low(-1]
high[1]
automalic[2]
B-2

December 2010
Chapter
ll

infinite[O]
foreverf-1]
type=unsigned; minimum=30; maximum=4000; default=1000; units=Byte;
type=ftoat; minimum=-100; maximum=31.5; default=-100; units=dBm;
target[-1 00]
no[O]
yes[1]
tx99: use tx99 mode, small, constant interframe spacing
no[O]
yes[1]
no[O]
yes[1]
carrier: transmit carrier only
no[O]
yes[1]
type=hexadecimal; minimum=1 ; maximum=?; default=?;
no[O]
yes[1]
type=decimal; minimum=O; maximum=110; default=O; units=dB;
type=decimal; minimum=-120; maximum=O; default=O; units=dB;
combined[1): the combined output signal is measured
iterate-<:ombined, ic[3]: the combined output signal is measured with iteration to reach the power goal
iterate-isolated, ii[4): attenuators are used to isolate and measure each chain separately with iteration to reach the power goal
goal: target output power for calibration


December 2010
B-3
ll Chapter
mean[-100]
[OJ
[O]
txgminimum: minimum txgain for calibration search
type=decimal; minimum=O; maximum=100; default=O;
txgmaximum: maximum txgain for calibration search
current[O]
calculate[1]
no[O]
yes[1]
rxiqcal, iqcal: perform rx iq calibration
no[O]
yes[1]
automatic[-1]
no[O]
yes[1]
automatic[-1]
pdgain: pdgain
no[O]
yes[1]
interframeSpacing, ifs, fs: spacing between frames
regular[-1]
tx100[0]
tx99[1]
no[O]
yes[1]
type=hexadecimal; minimum=O; maximum=ff; default=O;
chipTemperab.Jre: wait for chip temperature to exceed this value
receive, rx, r: causes the specified device to receive
type=unsigned; minimum=2400; maximum=6000; default=2412; units=M Hz;
rate, r. the data rates used
6[0]
9[1]
12[2]
18[3]
24[4]
36[5]
48[6]
54[7]
11[8]
21[9]
2s[10]
B-4

December 2010
Chapter
ll
51[11]
5s[12]
111[13]
11s[14]
tO, mcs0[32]
t1 , mcs1 [33]
t2, mcs2[34]
t3, mcs3[35]
t4, mcs4[36]
t5, mcs5[37]
t6, mcs6[38]
t7, mcs7[39]
t8, mcs8[40]
t9, mcs9[41]
t10, mcs10[42]
t11, mcs11[43]
t12, mcs12[44]
t13, mcs13[45]
t14, mcs14[46]
t15, mcs15[47]
t16, mcs16[48]
t17, mcs17[49]
t18, mcs18[50]
t19, mcs19[51]
t20, mcs20[52]
t21, mcs21[53]
t22, mcs22[54]
t23, mcs23[55]
fO, mcs0/40[64]
f1, mcs1/40[65]
12, mcs2/40[66]
f3, mcs3/40[67]
f4, mcs4/40[68]
f5, mcs5/40[69]
f6, mcs6/40[70]
f7, mcs7/40[71]
f8, mcs8/40[72]
f9, mcs9/40[73]
f10, mcs10/40[74]
f11, mcs11/40[75]
f12, mcs12/40[76]
f13, mcs13/40[77]
f14, mcs14/40[78]
f15, mcs15/40[79]
f16, mcs16/40[80]
f17, mcs17/40[81]
f18, mcs18/40[82]
f19, mcs19/40[83]
120, mcs20/40[84]
121, mcs21/40[85]
122, mcs22/40[86]
123, mcs23/40[87]
all[1000]
legacy[1001]
ht20[1002]
ht40[1003]
no[O]


December 2010
B-5
ll Chapter
yes[1]
none[O]
low[-1]
high[1]
automatic[2]
infinile[O]
forevert-1]
packetLength, pl: the length of the packets
type=unsigned; minimum=30; maximum=4000; default=1000; units=Byte;
type=ftoat; minimum=-100; maximum=31.5; default=-100; units=dBm;
target[-1 00]
no[O]
yes[1]
tx99: use tx99 mode, small, constant interframe spacing
no[O]
yes[1]
no[O]
yes[1]
carrier: transmit carrier only
no[O]
yes[1]
no[O]
yes[1]
type=decimal; minimum=O; maximum=110; default=O; units=dB;
type=decimal; minimum=-120; maximum=O; default=O; units=dB;
B-6

December 2010
Chapter
ll
combined[1J: the combined output signal is measured

isola1ed[2J: attenuators are used to isolate and measure each chain separately
iterate-<::ombined, ic[3J: the combined output signal is measured with iteration to reach the power goal
iterate-isolated, ii[4J: attenuators are used to isolate and measure each chain separately with iteration to reach the power goal
goal: target output power for calibration
mean[-100J
[OJ
[OJ
txgminimum: minimum txgain for calibration search
txgmaximum: maximum txgain for calibration search
current[OJ
calculate[1J
no[OJ
yes[1]
rxiqcal, iqcal: perform rx iq calibration
no[OJ
yes[1J
automatic[1J
no[OJ
yes[1]
automatic[-1]
pdgain: pdgain
no[OJ
yes[1]
regularf1J
tx.100[0]
tx99[1J
no[OJ
yes[1]
carrier: causes the device to transmit the carrier tone
sleep: pauses program execution for the specified number of milliseconds
load, card, attach: loads the card
devid: device type
type=hexadecimal; default=mmlf;
osprey[48J
wasp[49]
preference, default: the prefered starting template
type=decimal; minimum=2; default=2;


December 2010
B-7
ll Chapter
ar938x[2]
ar939x[2]
hb112[3]
hb116[4]
xb112[5]
xb113[6]
xb114[7]
tb417[8]
ap111[9]
ap121[10]
ar9330[11]
memory, caldata: memory type used for calibration data
none[4]
automatic[O]
flash[1]
eeprom[2]
olp[3]
size: memory size used for calibration data
automatic[O]
1K[1024]
2K[2048]
4K[4096]
8K[8192]
unload, remove, detach: unloads the card
reset: resets the device
frequency: channel carrier frequency
type=unsigned; minimum=2400; maximum=6000; default=2412; units=MHz;
chain: chain mask
txChain: transmit chain mask
rxChain: receive chain mask
type=hexadecimal; minimum=1 ; maximum=7; default=7;
ht40: use ht40 mode
no[O]
high[1]
low[-1]
automatic[2]
reset: force reset
no[O]
yes[1]
automatic[-1]
rr. reads a device register
type=hexadecimal;
rw: writes a device register with the specified value
type=hexadecimal;
value: the value
type=hexadecimal;
sr, sl: prints the current list of sticky wriites
sw: sticky write of a device field/register, sticky writes are performed after every device reset
address, name: the field name or address
type= text;
value: the value
type=hexadecimal;
sc: dear sticky field/register from list, last-on, first-off order
B-8

December 2010
Chapter
ll
type= text;
fr: field read
type= text;
fw: field write
type= text;
value: the value
type=hexadecimal;
n: list all the matching fields
type= text;
mr: memory read
size, bytes: the number of bytes
type=decimal;
type=hexadecimal;
mw: memory write
type=decimal;
type=hexadecimal;
value: the value
type=hexadecimal;
er: eeprom read
type=decimal;
type=hexadecimal;
ew: eeprom write
type=decimal;
type=hexadecimal;
value: the value
type=hexadecimal;
or: otp read
type=decimal;
type=hexadecimal;
ow: otp write
type=decimal;
type=hexadecimal;
value: the value
type=hexadecimal;
er: pci config read
type=decimal;
type=hexadecimal;
cw: pci config write
type=decimal;
type=hexadecimal;


December 2010
B-9
ll Chapter
value: the value
type=hexadecimal;
rd: enable register read/write debug mode
debug: tum register debug log on or off
no[O]
yes[1]
response: the response to rx commands
verbose[O]
split[1]
simple[2]
tgr: transmit gain table read
tgw: transmit gain table write
restore: restores calibration information from card
ar938x[2]
ar939x[2]
hb112[3]
hb116[4]
xb112[5]
xb113[6]
xb114[7]
tb417[8]
ap111[9]
ap121[10]
ar9330[11]
none[4]
automatic[O]
flash[1]
eeprom[2]
otp[3]
automatic[O]
1K[1024]
21<[2048]
41<[4096]
8K[8192]
comml~ save: finalize calibration and write data to device
allow: which templates may be used
type=decimal; minimum=2; default=2; dimension=[100];
ar938x[2]
ar939x[2]
hb112[3]
hb116[4]
xb112[5]
xb113[6]
xb114[7]
tb417[8]
ap111[9]
ap121[10]
ar9330[11]
none[4]
automatic[O]
flash[1]
eeprom[2]
otp[3]
B-10

December 2010

Chapter
ll

automatic[O]
11<[1024]
21<[2048]
41<[4096]
81<[8192]
compress: use compression?
no[O]
yes[1]
overwrite: overwrite existing data?
no[O]
yes[1]
pcie, boot: write pcie configuration data to chip
memory, caldata: memory type used for pcie initilization data
none[4]
automatic[O]
flash[1]
eeprom[2]
otp[3]
action: action to be performed
commit, save: save the (register, value) pairs in the power on initialization space
read: read the (register, value) pairs in the power on inltialization space
list, print: list the (register, value) pair to the power on initialization space
add: add a (register, value) pair to the power on initialization space
delete: delete a (register, value) pair from the power on initialization space
register: register address
type=hexadecimal;
value: register value
type=hexadecimal;
check: check calibration data on device
none[4]
automatic[O]
flash[1]
eeprom[2]
otp[3]
automatic[O]
11<[1024]
21<[2048]
41<[4096]
81<[8192]
all: include unchanged fields?
no[O]
yes[1]
set: se1 a configuration parameter on the card
Version, eepversion, version: the calibration structure version number
Template: the template number
Mac, mac: the mac address of the device
type=mac address;
Customer, customer: any text, usually used for device serial number
type= text;
RegulatoryDomain, regDmn: the regulatory domain
type=hexadecimal; minimum=O; maximum=lflf; default=O; dimension=[2];
Mask, txrxMask: the transmit and receive chain masks


December 2010
B-11
ll Chapter
Mask.Tx, TxMask: the maximum chain mask used for transmit
Mask.Rx, RxMask: the maximum chain mask used for receive
OpFlags, opFlags: flags that control operating modes
EepMisc, eepMisc: some miscellaneous control flags
RfSilent: rf silent mode control word
RfSilent.HardwareEnable, rfSilenlBO: implement rf silent mode in hardware
no[O]
yes[1]
RfSilent.Polarity, rfSilentB1: polarity of the rf silent control line
no[O]
yes[1]
RfSilent.Gpio, rfSilentGpio: the chip gpio line used for rf silent
type=hexadecimal; minimum=O; maximum=3f; default=O;
BlueToothOptions: bluetooth options
DeviceCapability, DeviceGap: device capabillties
DeviceType, DeviceType: devicetype
PowerTableOffset, PwrTableOffset: power level of the first entry in the power table
type=decimal; minimum=-10; maximum=35; default=O; units=dBm;
Tuningcaps: capacitors for tuning frequency accuracy
FeatureEnable, featureEnable: feature enable control word
FeatureEnable.TemperatureCompensation, TemperatureCompensationEnable, TempCompEnable: enables temperature compensation
on transmit power control
no[O]
yes[1]
FeatureEnable.VoltageCompensation, VoltageCompensationEnable, VoltCompEnable: enables voltage compensation on transmit
power control
no[O]
yes[1]
FeatureEnable. FastClock, FastelockEnable: enables fast clock mode
no[O]
yes[1]
FeatureEnable.Doubling, DoublingEnable: enables doubling mode
no[O]
yes[1]
FeatureEnable.SwltchingRegulator, swregenable: enables the internal switching regulator
no[O]
yes[1]
FeatureEnable.PaPredistortion, papdenable: enables pa predistortion
no[O]
yes[1]
FeatureEnable.TuningCsps, TuningGapsEnable: enables use of tuning capacitors
no[O]
yes[1]
Miscellaneous: miscellaneous parameters
Miscellaneous.DriveStrength, DriveStrengthReconfigure, DriveStrength: enables drive strength reconfiguration
no[O]
yes[1]
B-12

December 2010

Chapter
ll
Miscellaneous.Thennometer, Thennometer: forces use of the specified chip thennometer

Miscellaneous.Dynamic2x3, ChainMaskReduce: enables dynamic 2x3 mode to reduce power draw
no[O]
yes[1]
Miscellaneous.QuickDropEnable, quickDrop: enables quick drop mode for improved strong signal response
no[O]
yes[1]
EepromWriteEnableGpio: gpio line used to enable the eeprom
WlanDisableGpio:
WlanledGpio:
Rx:BandSelectGpio:
GainTable: transmit and receive gain table control word
GainTable.Tx, TxGain, TxGainTable: transmit gain table used
type=hexadecimal; minimum=O; maximum=f; default=O;
GainTable.Rx, Rx:Gain, RxGainTable: receive gain table used
SwltchingRegulator, SWREG, intemalregulator: the internal switching regulator control word
type=hexadecimal; minimum=O; maximum=llllH!f; default=O;
AntennaDiversltyControl, antDivCtrl: antenna diversity control
Future: reserved words, should be set to 0
type=hexadecimal; minimum=O; maximum=ff; default=O; dimension=[11 ];
2GHz.AntennaControlCommon, AntCtrlCommon2g: antenna switch control word 1
2GHz.AntennaControlCommon2, Antctr1Common22g: antenna switch control word 2
2GHz.AntennaControlChain, antCtrlChain2g: per chain antenna switch control word
type=hexadecimal; minimum=O; maximum=fllf; default=O; dimension=[3];
2GHz.Attenuation.Db, xatten1 DB2g: attenuation value
2GHz.Attenuation .Margin, xatten1 margin2g: attenuation margin
2GHz.TemperatureSlope, tempSlope2g, TemperatureSlope2g: slope used in temperature compensation algorithm
2GHz.VoltageSlope, voltSlope2g, VoltageSlope2g: slope used in voltage compensation algorithm
2GHz.Spur, SpurChans2g: spur frequencies
type=unsigned; minimum=O; maximum=2600; default=2412; unils=MHz; dimension=[5];
2GHz. NoiseFloorThreshold, NoiseFloorThreshCh2g: noise floor threshold
type=decimal; minimum=-127; maximum=127; default=O; dimension=[3];
2GHz.Reserved, Reserved2g: reserved words, should be set to 0
2GHz.QuickDrop, quickDrop2g: quick drop value
2GHz.XpaBiaslevel, XpaBiaslvl2g: external pa bias level
2GHz.TxFrameToDataStart, TxFrameToDataStart2g:
2GHz.TxFrameToPaOn, TxFrameToPaOn2g:
2GHz.TxFrameToXpaOn, TxFrameToXpaOn2g:


December 2010
B-13
ll Chapter
2GHz.TxEndToXpaOff, TxEndToXpaOff2g:
2GHz.TxEndToRxOn, TxEndToRxOn2g:
2GHz.TxClip, TxClip2g:
2GHz. DacScaleCCK, DacScaleCCK:
2GHz.AntennaGain, AntennaGain2g, AntGain2g:
2GHz.SwitchSetuing, SwitchSettling2g:
2GHz.AdcSize, AdcDesiredSize2g:
2GHz.Thresh62, Thresh622g:
2GHz. PaPredistortion.Ht20, papd2gRateMaskHt20: pa predistortion mask for HT20 rates
type=hexadecimal; minimum=O; maximum=flfflfff; default=O;
type=hexadecimal; minimum=O; maximum=flfflfff; default=O;
2GHz.Future, future2g: reserved words, should be set to 0
type=hexadecimal; minimum=O; maximum=ff; default=O; dimension=[1 O];
2GHz. PowerCalibration.Frequency, ca1Pierfreq2g: frequencies at which calibration is performed
2GHz.TransmitCalibration.PowerCorrection, CalPierRefPower2g: transmit power calibration correction values
type=decimal; minimum=-127; maximum=127; default=O; dimension=[3][3];
2GHz.TransmitGalibration.Voltage, CalPierVoltMeas2g: voltage measured during transmit power calibration
type=unsigned; minimum=O; maximum=255; default=O; dimension=[3][3];
2GHz.TransmitCslibration.Temperature, CslPierTempMeas2g: temperature measured during transmit power calibration
2GHz. ReceiveCslibration .NoiseFloor, GalPierRxNoiseftoorCal2g: noise floor measured during receive calibration
2GHz.ReceiveCslibration.Power, CalPierRxNoiseftoorPower2g: power measured during receive calibration
2GHz.ReceiveCslibration.Temperature, GalPierRxTempMeas2g: temperature measured during receive calibration
2GHz.Target.Frequency.Cck, calTGTFreqcck: frequencies at which target powers for eek rates are specified
2GHz.Target.Power.Cck, calTGTpwrCCK: target powers for eek rates
type=ftoat; minimum=O; maximum=35; default= 1O; units=dBm; dimension=[2][4];
2GHz.Target.Frequency.Legacy, calTGTFreq2g: frequencies at which target powers for legacy rates are specified
2GHz.Target.Power.Legacy, calTGTpwr2g: target powers for legacy rates
2GHz.Target.Frequency.Ht20, calTGTFreqht202g: frequencies at which target powers for ht20 rates are specified
2GHz.Target.Power.Ht20, calTGTpwrht202g: target powers for ht20 rates
type=ftoat; minimum=O; maximum=35; default=10; units=dBm; dimension=[3][14];
2GHz.Ctl.lndex, Ctllndex2g: ctl indexes, see eeprom guide for explanation
2GHz.Ctl.Frequency, Ct1Freq2g: frequencies at which maximum transmit powers are specified
type=unsigned; minimum=O; maximum=2600; default=2412; units=MHz; dimension=[12][4];
2GHz.Ctl.Power, CUPower2g, Ct1Pwr2g: maximum allowed transmit powers
B-14

December 2010

Chapter
ll
2GHz.Ctl.BandEdge, CdBandEdge2g, ctlflag2g: band edge ftag

type=hexadecimal; minimum=O; maximum=3; default=O; dimension=[12][4];
5GHz.Antenna.Common, AntCtrlCommon5g: antenna switch control word 1
type=hexadecimal; minimum=O; maximum=ffllfflf; default=O;
5GHz.Antenna.Common2, AntClr1Common25g: antenna switch control word 2
type=hexadecimal; minimum=O; maximum=ffllfflf; default=O;
5GHz.Antenna.Chain, antCtrlChain5g: per chain antenna swttch control word
type=hexadecimal; minimum=O; maximum=flff; default=O; dimension=[3];
5GHz.Attenuation.Db.Low, xatten1 DBLow5g, xatten1DBLow: attenuation value at 5180 MHz
5GHz.Attenuation.Db.Middle, xatten1DB5g: attenuation value at 5500 MHz
5GHz.Attenuation.Db.High, xatten1DBHigh5g, xatten1DBHigh: attenuation value at 5785 MHz
5GHz.Attenuation.Margin.Low, xatten1Marginlow, xatten1 Marginlow5g: attenuation margin at 5180 MHz
5GHz.Attenuation.Margin.Middle, xatten1Margin5g: attenuation margin at 5500 MHz
5GHz.Attenuation.Margin.High, xatten1MarginHigh, xatten1MarginHigh5g: attenuation margin at 5785 MHz
5GHz.TemperatureSlope.Low, tempSlopeLow5g, TemperatureSlopeLow5g: slope used at 5180 MHz in temperature compensation
algorithm
5GHz.TemperatureSlope.Middle, tempSlope5g, TemperatureSlope5g: slope used at 5500 MHz in temperature compensation algorithm
5GHz.TemperatureSlope.High, tempSlopeHigh5g, TemperatureSlopeHigh5g: slope used at 5785 MHz in temperature compensation
algorithm
5GHz.VoltageSlope.Middle, voltSlope5g, VoltageSlope5g: slope used in voltage compensation algorithm
type=unsigned; minimum=O; maximum=7000; default=5180; untts=MHz; dimension=[5];
5GHz.NoiseFloorThreshold, NoiseFloorThreshCh5g: noise floor threshold
5GHz.QuickDrop.Low, quickDroplow5g: quick drop value used at 5180 MHz
5GHz.QuickDrop.Middle, quickDrop5g: quick drop value used at 5500 MHz
5GHz.QuickDrop.High, quickDropHigh5g: quick drop value used at 5785 MHz
5GHz.TxFrameToPaOn, TxFrameToPaOn5g:
5GHz.TxEndToXpaOff, TxEndToXpaOff5g:


December 2010
B-15
ll Chapter
5GHz.SwltchSettling, SwltchSettling5g:
type=hexadecimal; minimum=O; maximum=flfllflf; default=O;
5GHz.Transmitcalibration.Frequency, calPierFreq5g: frequencies at which calibration is performed
5GHz.Transmitcalibration.PowerConection, CalPierRefPower5g: transmit power calibration correction values
5GHz.TransmitCalibration.Voltage, CalPierVoltMeas5g: voltage measured during transmit power calibration
5GHz.TransmitCalibration.Temperature, CalPierTempMeas5g: temperature measured during transmit power calibration
5GHz. ReceiveCalibration .NoiseFloor, CalPierRxNoiseftoorCal5g: noise floor measured during receive calibration
5GHz.ReceiveCalibration.Power, CalPierRxNoiseftoorPower5g: power measured during receive calibration
5GHz.ReceiveCalibration.Temperature, CalPierRxTempMeas5g: temperature measured during receive calibration
type=unsigned; minimum=4000; maximum=7000; default=5180; units=MHz; dimension=[B];
5GHz.Target.Power.Ht20, calTGTpwrtrt205g: target powers for ht20 rates
type=float; minimum=O; maximum=35; default= 1O; units=dBm; dimension=[8][14];
type=float; minimum=O; maximum=35; default= 1O; units=dBm; dimension=[8][14];
5GHz.Ctl.Power, CUPower5g, Ct1Pwr5g: maximum allowed transmit powers
type=float; minimum=O; maximum=35; default=10; units=dBm; dimension=[9][8];
5GHz.Ctl.BandEdge, CUBandEdge5g, ctlflag5g: band edge ftag
Config:
ConfigPCle:
DevicelD, devid: the device id
type=hexadecimal; minimum=O; maximum=fllf; default=O;
SSID, subSystemld: the subsystem id
VID, vendorld: the vendor id
SVID, subVendorld: the subvendor id
B-U

December 2010

Chapter
ll
get: get a configuration parameter from the card

ALL: formatted display of all configuration and calibration data
type= text:
Version, eepversion, version: the calibration structure version number
type=unsigned; minimum=2: maximum=255; default=2;
Template: the template number
type=unsigned: minimum=2: maximum=255: default=2:
Mac, mac: the mac address of the device
type=mac address:
Customer, customer. any text, usually used for device serial number
type= text:
RegulatoryDomain, regDmn: the regulatory domain
type=hexadecimal; minimum=O: maximum=fllf; default=O; dimension=[2];
Mask, txrxMask: the transmit and receive chain masks
type=hexadecimal: minimum=O; maximum=ff; default=O;
Mask.TX, TxMask: the maximum chain mask used for transmit
Mask.Rx, RxMask: the maximum chain mask used for receive
type=hexadecimal: minimum=1: maximum=7; default=7;
OpFlags, opFlags: flags that control operating modes
type=hexadecimal; minimum=O: maximum=ff; default=O;
EepMisc, eepMisc: some miscellaneous control flags
type=hexadecimal: minimum=O: maximum=ff; default=O:
RfSilent: rf silent mode control word
RfSilent.HardwareEnable, rfSilenlBO: implement rf silent mode in hardware
no[O]
yes[1]
RfSilent.Polarity, rfSilentB1: polarity of the rf silent control line
no[O]
yes[1]
RfSilent.Gpio, rfSilentGpio: the chip gpio line used for rf silent
type=hexadecimal; minimum=O; maximum=3f; default=O;
BlueToothOptions: bluetooth options
DeviceCapability, DeviceCep: device capabiltties
type=hexadecimal: minimum=O: maximum=ff; default=O:
DeviceType, DeviceType: devicetype
type=hexadecimal; minimum=O: maximum=ff; default=O;
PowerTableOffset, PwrTableOffset: power level of the first entry in the power table
type=decimal; minimum=-10; maximum=35; default=O; units=dBm:
TuningCeps: capacitors for tuning frequency accuracy
FeatureEnable, featureEnable: feature enable control word
FeatureEnable.TemperatureCompensation, TemperatureCompensationEnable, TempCompEnable: enables temperature compensation
on transmtt power control
no[O]
yes[1]
FeatureEnable.VoltageCompensation, VoltageCompensationEnable, VoltCompEnable: enables voltage compensation on transmit
power control
no[O]
yes[1]
FeatureEnable. FastClock, FastclockEnable: enables fast clock mode
no[O]
yes[1]
FeatureEnable.Doubling, DoublingEnable: enables doubling mode
no[O]


December 2010
B-17
ll Chapter
yes[1]
FeatureEnable.SwttchingRegulator, swregenable: enables the internal swttching regulator
no[O]
yes[1]
FeatureEnable.PaPredistorlion, papdenable: enables pa predistorlion
no[O]
yes[1]
FeatureEnable.TuningCaps, TuningCapsEnable: enables use of tuning capacitors
no[O]
yes[1]
Miscellaneous: miscellaneous parameters
Miscellaneous.DriveStrength, DriveStrengthReconfigure, DriveStrength: enables drive strength reconfiguration
no[O]
yes[1]
Miscellaneous.Thermometer, Thermometer: forces use of the specified chip thermometer
Miscellaneous.Dynamic2x3, ChainMaskReduce: enables dynamic 2x3 mode to reduce power draw
no[O]
yes[1]
Miscellaneous.QuickDropEnable, quickDrop: enables quick drop mode for improved strong signal response
no[O]
yes[1]
EepromWriteEnableGpio: gpio line used to enable the eeprom
WlanDisableGpio:
WlanledGpio:
RxBandSelectGpio:
GainTable: transmit and receive gain table control word
GainTable.Tx, TxGain, TxGainTable: transmit gain table used
GainTable.Rx, RxGain, RxGainTable: receive gain table used
SwttchingRegulator, SWREG, intemalregulator: the internal switching regulator control word
type=hexadecimal; minimum=O; maximum=ffllfllf; default=O;
AnlennaDiversityControl, antDivCtrl: antenna diversity control
Future: reserved words, should be set to 0
2GHz.AntennaControlCommon, AntCtrlCommon2g: antenna switch control word 1
2GHz.AntennaControlCommon2, AntCtrlCommon22g: antenna switch control word 2
2GHz.AntennaControlChain, antCtrlChain2g: per chain antenna switch control word
type=hexadecimal; minimum=O; maximum=fllf; default=O; dimension=[3];
2GHz.Attenuation.Db, xatten1 DB2g: attenuation value
2GHz.Attenuation .Margin, xatten1 margin2g: attenuation margin
2GHz.TemperatureSlope, tempSlope2g, TemperatureSlope2g: slope used in temperature compensation algorithm
2GHz.VoltageSlope, voltSlope2g, VoltageSlope2g: slope used in voltage compensation algorithm
B-18

December 2010

Chapter
ll
type=unsigned; minimum=O; maximum=2600; default=2412; unils=MHz; dimension=[5];

2GHz. NoiseFloorThreshold, NoiseFloorlhreshCh2g: noise floor threshold
2GHz.QuickDrop, quickDrop2g: quick drop value
2GHz.XpaBiasLevel, XpaBiasLvl2g: external pa bias level
2GHz.TxFrameToPa0n, TxFrameToPa0n2g:
2GHz.TxEndToXpaOff, TxEndToXpaOfl2g:
2GHz.DacScaleCCK, DacScaleCCK:
2GHz.SwltchSetuing, SwltchSettling2g:
2GHz. PaPredistortion.Ht20, papd2gRateMaskHt20: pa predistorlion mask for HT20 rates
type=hexadecimal; minimum=O; maximum=ffllftlf; default=O;
2GHz. PaPredistortion.Ht40, papd2gRateMaskHt40: pa predistorlion mask for HT40 rates
type=hexadecimal; minimum=O; maximum=ffllftlf; default=O;
type=hexadecimal; minimum=O; maximum=ff; default=O; dimension=[1 OJ;
2GHz. PowerCalibration.Frequency, calPierFreq2g: frequencies at which calibration is perfonned
2GHz.Transmitcalibration.PowerCorrection, CalPierRefPower2g: transmit power calibration correction values
2GHz.TransmltCalibration.Voltage, CalPierVoltMeas2g: voltage measured during transmit power calibration
2GHz.TransmltCalibration.Temperature, CalPierTempMeas2g: temperature measured during transmit power calibration
2GHz. ReceiveCalibration .NoiseFloor, CalPierRxNoisefloorCal2g: noise floor measured during receive calibration
2GHz.ReceiveCalibration.Power, CalPierRxNoiseftoorPower2g: power measured during receive calibration
2GHz.ReceiveCalibration.Temperature, CalPierRxTempMeas2g: temperature measured during receive calibration
2GHz.Target.Frequency.Cck, calTGTFreqeek: frequencies at which target powers for eek rates are specified
2GHz.Target.Power.Cck, calTGTpwrCCK: target powers for eek rates


December 2010
B-19
ll Chapter
2GHz.Target.Frequency.Hl20, calTGTFreqhl202g: frequencies at which target powers for hl20 rates are specified
2GHz.Target.Power.Ht20, calTGTpwrtrt202g: target powers for hl20 rates
2GHz.Target.Power.Ht40, calTGTpwrtrt402g: target powers for ht40 rates
2GHz.Ctl.Power, CHPower2g, Ct1Pwr2g: maximum allowed transmit powers
2GHz.Ctl.BandEdge, CHBandEdge2g, ctlflag2g: band edge flag
5GHz.Antenna.Common, AntCtr1Common5g: antenna switch control word 1
type=hexadecimal; minimum=O; maximum=flfllfff; default=O;
5GHz.Antenna.Common2, AntCb1Common25g: antenna switch control word 2
type=hexadecimal; minimum=O; maximum=flfllfff; default=O;
5GHz.Antenna.Chain, antCtr1Chain5g: per chain antenna switch control word
type=hexadecimal; minimum=O; maximum=fflf; default=O; dimension=[3];
5GHz.Attenuation.Db.Low, xatten1 DBLOYl5g, xatten1DBLow: attenuation value at 5180 MHz
5GHz.Attenuation.Db.Middle, xatten1DB5g: attenuation value at 5500 MHz
type=hexadecimal; minimum=O; maximum=lf; default=O; dimension=[3];
5GHz.Attenuation.Db.High, xatten1DBHigh5g, xatten1DBHigh: attenuation value at 5785 MHz
5GHz.Attenuation.Margin.Low, xatten1Marginlow, xatten1 Marginlow5g: attenuation margin at 5180 MHz
5GHz.Attenuation.Margin.Middle, xatten1Margin5g: attenuation margin at 5500 MHz
5GHz.Attenuation.Margin.High, xatten1MarginHigh, xatten1MarginHigh5g: attenuation margin at 5785 MHz
5GHz.TemperatureSlope.Low, tempSlopelow5g, TemperatureSlopeLOYl5g: slope used at 5180 MHz in temperature compensation
algorithm
5GHz.TemperatureSlope.Middle, tempSlope5g, TemperatureSlope5g: slope used at 5500 MHz in temperature compensation algorithm
5GHz.TemperatureSlope.High, tempSlopeHigh5g, TemperatureSlopeHigh5g: slope used at 5785 MHz in temperature compensation
algorithm
5GHz.VoltageSlope.Middle, voltslope5g, VoltageSlope5g: slope used in voltage compensation algorithm
type=unsigned; minimum=O; maximum=7000; default=5180; units=MHz; dimension=[5];
5GHz.NoiseFloorThreshold, NoiseFloorThreshCh5g: noise floor threshold
5GHz.QuickDrop.Low, quickDroplow5g: quick drop value used at 5180 MHz
5GHz.QuickDrop.Middle, quickDrop5g: quick drop value used at 5500 MHz
5GHz.QuickDrop.High, quickDropHigh5g: quick drop value used at 5785 MHz
B-20

December 2010

Chapter
ll

5GHz.TxFrameToPa0n, TxFrameToPa0n5g:
5GHz.TxEndToXpaOlf, TxEndToXpaOfffig:
5GHz.SwitchSetuing, SwitchSettling5g:
type=hexadecimal; minimum=O; maximum=fflllfff; default=O;
5GHz.PaPredistortion.Ht40, papd5gRateMaskHt40: pa predistortion mask for HT40 rates
type=hexadecimal; minimum=O; maximum=fflllfff; default=O;
type=hexadecimal; minimum=O; maximum=ff; default=O; dimension=[1 O];
5GHz.TransmitCalibration.Frequency, calPierFreq5g: frequencies at which calibration is performed
5GHz.TransmitCalibration.PowerCorrection, CalPierRefPower5g: transmit power calibration correction values
5GHz.TransmitGalibration.Voltage, GalPierVoltMeas5g: voltage measured during transmit power calibration
5GHz.TransmitGalibration.Temperature, GalPierTempMeas5g: temperature measured during transmit power calibration
5GHz. ReceiveGalibration .NoiseFloor, GalPierRxNoisefloorCal5g: noise floor measured during receive calibration
5GHz.ReceiveGalibration.Power, GalPierRxNoisefloorPower5g: power measured during receive calibration
5GHz.ReceiveGalibration.Temperature, GalPierRxTempMeas5g: temperature measured during receive calibration
type=ftoat; minimum=O; maximum=35; default=1 O; units=d Bm; dimension=[8][4];
5GHz.Target.Power.Ht20, calTGTpwrhl205g: target powers for ht20 rates
5GHz.ctl.lndex, ctllndex5g: ctl indexes, see eeprom guide for explanation
5GHz.ctl.Frequency, ct1Freq5g: frequencies at which maximum transmit powers are specified
5GHz.ctl.Power, CUPower5g, ct1Pwr5g: maximum allowed transmit powers


December 2010
B-21
ll Chapter
5GHz.Ctl.BandEdge, CUBandEdge5g, ctlflag5g: band edge flag
Config:
type=hexadecimal; minimum=O; maximum=fflllftf; default=O;
ConfigPCle:
type=hexadecimal; minimum=O; maximum=fflllftf; default=O;
DevicelD, devid: the device id
type=hexadecimal; minimum=O; maximum=lflf; default=O;
SSID, subSystemld: the subsystem id
VID, vendorld: the vendor id
SVID, subVendorld: the subvendor id
setTP: set target power configuration parameter on the card
getTP: get target power configuration parameter from the card
pl: tum on packet logging
channel: retrieve and display a list of the valid channels
noisafloor, nf: compute the noise floor
nfg: retrieve and display the calibrated noise floor measurements
targetPower, tp: retrieve and display the target power values
rate, r. the data rates used
6[0]
9[1]
12[2]
18[3]
24[4]
36[5]
48[6]
54[7]
11[8]
21[9]
2s[10]
51[11]
5s[12]
111[13]
11s[14]
to, mcs0[32]
t1 , mcs1 [33]
t2, mcs2[34]
t3, mcs3[35]
t4, mcs4[36]
t5, mcs5[37]
t6, mcs6[38]
t7, mcs7[39]
t8, mcs8[40]
t9, mcs9[41]
t10, mcs10[42]
t11, mcs11[43]
t12, mcs12[44]
t13, mcs13[45]
B-22

December 2010
Chapter
ll
t14, mcs14[46]
t15, mcs15[47]
t16, mcs16[48]
t17, mcs17[49]
t18, mcs18[50]
t19, mcs19[51]
t20, mcs20[52]
t21, mcs21[53]
t22, mcs22[54]
t23, mcs23[55]
to, mcs0/40[64]
f1, mcs1/40[65]
f2, mcs2/40[66]
f3, mcs3/40[67]
f4, mcs4/40[68]
f5, mcs5/40[69]
f6, mcs6/40[70]
f7, mcs7/40[71]
f8, mcs8/40[72]
f9, mcs9/40[73]
f10, mcs10/40[74]
f11, mcs11/40[75]
f12, mcs12/40[76]
f13, mcs13/40[77]
f14, mcs14/40[78]
f15, mcs15/40[79]
f16, mcs16/40[80]
f17, mcs17/40[81]
f18, mcs18/40[82]
f19, mcs19/40[83]
f20, mcs20/40[84]
f21, mcs21/40[85]
f22, mcs22/40[86]
f23, mcs23/40[87]
all[1000]
legacy[1001]
ht20[1002]
ht40[1003]
start: start the current command
stop: stop the current command
template: Manipulates the configuration and calibration template
ar938x[2]
ar939x[2]
hb112[3]
hb116[4]
xb112[5]
xb113[6]
xb114[7]
tb417[8]
ap111[9]
ap121[10]
ar9330[11]
allow: which templates may be used
type=decimal; minimum=2; default=2; dimension=[100];
ar938x[2]
ar939x[2]


December 2010
B-23
ll Chapter
hb112[3]
hb116[4]
xb112[5]
xb113[6]
xb114[7]
tb417[8]
ap111[9]
ap121[10]
ar9330[11]
none[4]
automatic[O]
flash[1]
eeprom[2]
otp[3]
automatic[O]
1K[1024]
2K[2048]
4K[4096]
BK[8192]
compress: use compression?
no[O]
yes[1]
overwrite: overwrite existing data?
no[O]
yes[1]
install: install tempatle?
no[O]: never install the tempalte
yes[1]: always install the template
blank[2]: install on a blank card
error: allows you to control how error messages are displayed
code, number[O]: the individual message code or number
type: the message type
DEBUG[O]
CONTROL[1]
INF0[2]
WARNING[3]
ERROR[4]
response: the response
code[O]: show the 4 digit message code
type[1]: show the message type severity
message[2]: show the actual message
pause[3]: pause and wait for user response
bell[4]: ring the bell
log, file[5]: append message to the current log file
all[100]: same as code+type+message
none[101]: ignore error message
normal[102]: do the normal response
list: list all of the matching error messages
no[O]
yes[1]
short: use short format?
no[O]
yes[1]
version: retrieve version information
B-24

December 2010
Chapter


December 2010
ll
B-25
ll Chapter
B-26

December 2010

Chapter
II
Sample Error Code List

The list of error codes in this section are valid for version 2.13 of ART2
software. The current list of error codes can be obtained by entering the
command error list=yes at the CART or NART command line.
C language header files are available that define the response codes and the
format of the messages.
0000 DEBUG %s
0001 WARNING Unknown error%d.
1000 ERROR Unknown parameter "%s".
1001 ERROR Bad value "%s" for parameter "%s".
1002 ERROR Too many values for parameter "%s". Maximum is %d.
1003 ERROR End value must be smaller than start value for parameter "%s".
1004 ERROR End value must be larger than start value for parameter "%s".
1005 ERROR Value %d is smaller than the minimum value of %d for parameter "%s".
1006 ERROR Value %d is greater than the maximum value of %d for parameter "%s".
1007 ERROR Value Ox%x is smaller than the minimum value of Ox%x for parameter "%s".
1008 ERROR Value Ox%x is greater than the maximum value of Ox%x for parameter "%s".
1009 ERROR Value %lg is smaller than the minimum value of %lg for parameter "%s".
101 OERROR Value %lg is greater than the maximum value of %lg for parameter "%s".
1012 INFO %s
1011 ERROR Command parsing error. Command not started.
1013 CONTROL Help start.
1014 CONTROL Help end.
1015 ERROR Value %u is smaller than the minimum value of %u for parameter "%s".
1016 ERROR Value %u is greater than the maximum value of %u for parameter "%s".
1017 ERROR Value %02x:%02x:%02x:%02x:%02x:%02x is smaller than the minimum value of %02x:%02x:%02x:%02x:%02x:%02x
for parameter "%s".
1018 ERROR Value %02x:%02x:%02x:%02x:%02x:%02x is greater than the maximum value of %02x:%02x:%02x:%02x:%02x:%02x
for parameter "%s".
1019 CONTROL Synopsis:
1020 CONTROL
1021 CONTROL Parameters:
1022 CONTROL
1023 CONTROL Description:
1024 CONTROL
1025 INFO I don't know.
1026 ERROR Unknown command "%s".
1027 ERROR Bad array index "%s".
1028 ERROR Array index [%d] is less than zero or greater than maximum [%d].
1029 ERROR Array index [%d, %d] is less than zero or greater than maximum [%d, %d].


December 2010
C-1
II Chapter
1030 ERROR Array index [%d, %d, %d] is less than zero or greater than maximum [%d, %d, %d].
2000 ERROR Too many reports. Maximum is %d.
2001 ERROR Input signal strength requires use of Ix power control.
2003 ERROR Calibration requires use of Ix gain setting.
2004 WARNING Transmit forever requires rate inter1eaving. pc<O => ir-1.
2005 ERROR No connection to receiver %d.
2006 ERROR No connection to transmitter %d.
2007 ERROR No connection to blocker %d.
2008 ERROR No attenuators.
2002 ERROR You must specify a transmitter or a receiver device.
2009 ERROR No power meter.
2010 ERROR No spectrum analyzer.
2011 ERROR No VSG.
2012 ERROR No multimeter.
2013 ERROR No EVM analyzer.
2014 CONTROL Link test started at %d
2015 CONTROL Link test finished at %d. Elapsed time was %d ms.
2016 ERROR The transmitter and receiver must be different.
2017 ERROR Link test not started.
2018 INFO Data log is in file "%s".
2019 CONTROL Link iteration started at %d
2020 CONTROL Link iteration finished at %d. Elapsed time was %d ms.
2021 WARNING Attenuation %d is out of range [%d, %d] for chain %d.
2022 CONTROL Frequency is %d MHz.
2023 CONTROL Rate is %s.
2024 CONTROL Attenuation is %d dB.
2025 CONTROL Input signal strength is %d dBm.
2026 CONTROL Packet count is %d.
2027 CONTROL Packet length is %d.
2028 CONTROL Temperature is %d C.
2029 CONTROL Transmit gain is %d.
2030 CONTROL Transmit power is %.1 If dBm.
2031 CONTROL Transmit power is target power.
2032 CONTROL Blocker frequency delta is %d MHz.
2033 CONTROL Blocker transmit power is %d dBm.
2034 CONTROL Blocker input signal strength is %d dBm.
2035 CONTROL Transmit chain is Ox%x. Receive chain is Ox%x.
2036 CONTROL Aggregation is %d.
2037 CONTROL Transmit test started a1 %d.
2038 CONTROL Transmit test finished at %d. Elapsed time was %d ms.
2039 INFO Transmit operation canceled.
2040 ERROR Can't setup transmit operation.
2041 INFO Receive operation canceled.
2042 ERROR Can't setup receive operation.
2043 INFO Carrier operation canceled.
2044 ERROR Can't setup carrier operation.
2045 ERROR Calibration failed for chain %d. txgain=%d, power-%.1 If.
2046 INFO Removed rate %s because 118 rates are not allowed at 5GHz.
2047 INFO Removed rate %s because HT40 rates are not allowed.
2048 CONTROL Blocker frequency is %d MHz.
3000 ERROR No free equipment control library slots. Maximum is %d.
3001 INFO Loaded equipment control library for %s from %s.
3002 ERROR Can't load equipment control library from %s
3003 ERROR Can't find EquipmentName function in %s.
3100 ERROR Too many path loss measurements. Maximum is %d.
3101 ERROR Bad chain value Ox%x.
3102 ERROR Bad frequency value %d.
3103 ERROR Bad loss value %.11f.
C-2
December 2010

Chapter
II
3104 ERROR Bad device value %d.

3004 ERROR Can't find EquipmentSetup function in %s.
3005 ERROR Trouble with equipment setup is %d.
3006 ERROR No known equipment control library for %s.
3007 ERROR Unknown equipment type in %s.
3008 ERROR No code library specified.
3009 INFO Found power meter %s.
3010 INFO Found attenuator %s for chain %d.
3011 INFO Found spectrum analyzer %s.
3012 INFO Found power supply %s.
3013 INFO Found multimeter%s.
3014 INFO Found oven %s.
3105 ERROR You must specify a frequency before the loss value.
3106 ERROR You must specify a device and a frequency before the loss value.
3200 ERROR Bad chain mask Ox%x on evm mesaurement.Bad chain mask Ox%x on evm mesaurement.
4000 CONTROL Report start.
4001 INFO %s
4002 INFO %s
4003 INFO %s
4004 INFO %s
4005 CONTROL Report end.
4006 INFO Report is in file "%s".
4007 ERROR Can't open report file "%s" "%s".
4008 ERROR Too many keys. Maximum is %d.
4009 ERROR Too many fields. Maximum is %d.
4010 ERROR Too many minimums. Maximum is %d.
4011 ERROR Too many maximums. Maximum is %d.
4012 ERROR Too many increments. Maximum is %d.
4013 ERROR Too many sizes. Maximum is %d.
4014 ERROR Too many labels. Maximum is %d.
4015 ERROR Too many units. Maximum is %d.
4016 ERROR Too many types. Maximum is %d.
4017 ERROR Too many widths. Maximum is %d.
4018 ERROR Too many decimals. Maximum is %d.
4019 ERROR Can't find field "%s".
4020 ERROR Can't find field "%s.%s".
4021 ERROR No value for field "%s".
4022 ERROR No value for field "%s.%s".
4023 ERROR Can't find variable "%s".
4024 ERROR Argument %d must be value.
4025 ERROR Argument %d must be field.
4026 ERROR Argument %d must be field.
4027 ERROR Argument %d must be variable.
4028 ERROR No fields.
4029 ERROR Report format requires at least %d fields.
4030 ERROR Report format requires %d fields.
4031 ERROR Too many x values. Maximum is %d. "%s" discarded.
4032 ERROR Too many y values. Maximum is %d. "%s" discarded.
4033 ERROR Trouble evaluating equation: "%s".
4034 WARNING Unevaluated conditional expression.
4035 ERROR Function requires %d arguments.
4036 WARNING Cani parse value for %s[%d]
4037 WARNING Field name "%s" begins with digit.
4038 WARNING Too many records. Maximum is %d.
4039 ERROR Opened input data log file "%s".
4040 ERROR Opened output data log file "%s".
4041 ERROR Can't open input data log file "%s".
4042 ERROR Can't open output data log file "%s" "%s".


December 2010
C-3
II Chapter
4043 WARNING Misparsed data header column=%d of%d, word="%s"
4044 INFO Loaded %d headers and %d records from file "%s".
4045 INFO Data acquisition command was "%s".
4046 ERROR Can't parse equation: "%s".
4047 INFO %s
4048 INFO %s
4049 INFO %s
5000 INFO Trying to connect to nart[%d] on %s:%d.
5001 INFO Connected to nart(%d] on %s:%d.
5002 ERROR Can't connect to nart[%d] on %s:%d.
5003 ERROR No response from nart[%d].
5004 INFO Good link to nart[%d].
5005 ERROR Read error from nart[%d].
5006 ERROR Write error to nart[%d].
5007 ERROR Closed connection to nart[%d].
5008 CONTROL Command "%s" to nar1[%d].
5009 CONTROL Response "%s" from nart[%d].
5010 ERROR Error "%s"from nart[%d].
5011 CONTROL Done "%s" from nart[%d].
5012 ERROR Bad nart[%d].
5013 ERROR No connection to nart[%d].
5014 CONTROL Data "%s" from nart[%d].
5100 INFO Listening for control process connections on %d.
5101 INFO Can't open control process listen port %d.
5102 INFO Trying to connect to control process on %s:%d.
5103 INFO Connected to control process on %s:%d.
5104 ERROR Can't connect to control process on %s:%d.
5105 ERROR Read error from control process.
5106 ERROR Write error to control process.
5107 ERROR Closed connection to control process.
5108 INFO Waiting for connection from control process.
6000 INFO Loaded carcl
6001 ERROR Can't load card.
6002 INFO Unloaded card.
6003 ERROR No card loaded.
6004 CONTROL Device reset successfully. frequency=%d, ht40=%d, Ix chain=%d, rx chain=%d.
6005 ERROR Device reset error %d. frequency=%d, ht40=%d, Ix chain=%d, rx chain=%d.
6006 ERROR Anwi driver load error.
6007 ERROR HAL load error.
6008 ERROR Device attach error %d.
6009 ERROR No legal channels.
6010 INFO No calibration information found.
6011 INFO Calibration infromatin read from flash.
6012 INFO Calibration information read from eeprom at Ox%x.
6013 INFO Calibration information read from otp at Ox%x.
6014 ERROR Can't load pcie inltilization space.
6015 ERROR No support for device type Ox%x.
6016 ERROR Device not loaded or not reset.
6017 WARNING Bad noise floor value: (%d, %d) (%d, %d) (%d,%d).
6018 WARNING Device reset error %d. frequency=%d, ht40=%d, Ix chain=%d, rx chain=%d. Retrying.
6019 ERROR Unknown chip. Please specify devid.
6020 INFO Chip initialization space saved in %d bytes.
6021 ERROR Chip initialization space save error.
6022 INFO Calibration structure saved in %d bytes.
6023 ERROR Calibration structure save error.
6024 INFO Free memory for initialization and calibration is %d (%d - %d) bytes.
6100 INFO %s
6101 INFO Last reference design
C-4 AR93xx ART Reference Guide

December 2010

Chapter
II
6102 INFO %s has been loaded

7000 INFO Command file "%s" completed at %u. Elapsed time was %d ms.
7001 WARNING Command file changed while processing loop.
7002 INFO Command file "%s" opened at %u.
7003 INFO %s:%d %s
7004 ERROR Can't open file "%s" "%s".
7005 ERROR Too many open files. Maximum is %d.
7006 ERROR Label command is only valid in files.
7007 ERROR Branch command is only valid in files.
7008 ERROR Can't evaluate condition: "%s".
7009 ERROR Can't find label "%s".
7010 INFO Backup saved in file "%s".
7011 ERROR Error saving backup in file "%s".
7100 INFO Can't open log file "%s".
7101 INFO Opened log file "%s".
7102 INFO Closed log file.
7170 INFO CartVersion: %d.%d;CartBuildDate: %06d; CartBuildlime: %06d 7202 INFO %sis undefined.
7171 INFO %s
7172 INFO Initialization complete. Waiting for commands.
7200 INFO %s= %s
7201 ERROR No value specified.
7203 INFO Please supply a value for variable "%s":
7204 WARNING Possible substitution loop at position %d of variable %s.
7205 INFO Thank you for supplying the value "%s" for variable %s.
7206 INFO Using default value "%s" for variable %s.
7207 INFO %s
7208 INFO Please supply a value for variable %s [%s]:
7300 INFO Command in progress. Try "pause", "continue", or "stop". "%s" command queued for later processing.
7301 INFO Command paused.
7302 INFO Command continued.
7303 INFO Command stopped.
7500 CONTROL OK
7501 CONTROL ON
7502 CONTROL OFF
7503 INFO %s
7504 INFO %s
7505 ERROR ERROR %s
7506 CONTROL DONE %s
7507 DEBUG %s
7508 CONTROL BEGIN %s
7509 INFO Please look for another active nart.
7510 INFO %s
7511 INFO %s
8000 ERROR Compressed block is too big.
8001 ERROR Calibration memory verify error at Ox%x: Ox%x != Ox%x.
8002 INFO Writing calibration memory using algorithm=%d reference=%d size=%d address=Ox%x.
8100 ERROR Chip initialization space verify error at Ox%x: Ox%x != Ox%x.
8101 ERROR Too many chip initilization space write errors.
8102 ERROR Can't write chip initialization memory.
8003 ERROR Too many calibration memory write errors.
8004 ERROR Can't write calibration memory.
8005 ERROR Fatal calibration mmory error. Bad chip.
8006 ERROR Calibration data won~ fit. Want to use addresses Ox%x to Ox%x. Low limit is Ox%x.
8103 ERROR Fatal chip inltialization memory error. Bad chip.
8104 ERROR Chip initialization data won't fit. Want to use addresses Ox%x to Ox%x. High limit is Ox%x.


December 2010
C-5
Atheros Communications, Incorporated

5480 Great America Parkway
Santa Clara, CA 95054
tel: 408.773.5200
fax: 408.773.9940
ATHEROS~
www.atheros.com
CO/llPANY CONRDENTJAL
Subject tu Change witilout Notiat

AR93xx ART2 Reference Guide MKG-15527

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AR93xx ART2 Reference Guide MKG-15527

Uploaded by

Copyright:

Available Formats

AR93xx

Atheros Radio Test 2

2010 by Atheros Communications, Inc. All rights reserved.

Document Number: MKG-15527 Ver. 1.0

AR93xx ART Reference Guide

Atheros Communications, Inc.

Initial AR93xx document release

Atheros Communications, Inc.

AR93xx ART Reference Guide

Atheros Communications, Inc.

Preface ... ...................................

1 Overview .................................... 1-1

2 Installing & Configuring ART2 ................... 2-1

3 Using the ART2 GUI . ........................... 3-1

Atheros Communications, Inc.

Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Usfng CART/NART Command Lfne Interfaces . . . . . . .

CART Command Line Control . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

5 Interfacing a Custom Process to ART2 ............

Controlling CART using Custom/Vendor Software . . . . . . . . . . . . . 5-2

6 Sample Manufacturing Test Flow. . . . . . . . . . . . . . . . .

Manufacturing Test System Requirements . . . . . . . . . . . . . . . . . . 6-1

Running the Sample Manufacturing Test Flow. . . . . . . . . . . . . . . . 6-6

AR93xx ART Reference Guide

Atheros Communications, Inc.

A Sample CART Command List . . . . . . . . . . . . . . . . . . . .

B Sample NART Command List .................... s-1

Sample Error Code List . . . . . . . . . . . . . . . . . . . . . . . .

Atheros Communications, Inc.

AR93xx ART Reference Guide

Atheros Communications, Inc.

ART2 Directory Structure . . . . . . . . . . . . . . . . . . . . . 1-2

ART2 Software Components . . . . . . . . . . . . . . . . . . . 1-3

CART Startup Options . . . . . . . . . . . . . . . . . . . . . . 4-4

NART Startup Options . . . . . . . . . . . . . . . . . . . . . . 4-4

Function Descriptions . . . . . . . . . . . . . . . . . . . . . . 4-10

Report Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Manufacturing Test System Requirements . . . . . . . . . . . 6-1

Files Used to Control Manufacturing Test Flow . . . . . . . . 6-7

Description of start.art Entries . . . . . . . . . . . . . . . . . . 6-9

Description of ProductList.ref Columns. . . . . . . . . . . . 6-10

Description of test_flow_flags.art . . . . . . . . . . . . . . . 6-13

Description of $refID.ref Commands . . . . . . . . . . . . . 6-18

Description of Target Power File Commands. . . . . . . . . 6-22

Description of CTL command File . . . . . . . . . . . . . . . 6-26

Atheros Communications, Inc.

AR93xx ART Reference Guide

Atheros Communications, Inc.

About this Document

Overview-Gives a brief description of ART2 and its current feature

Installing & Configuring ART2-Describes how to set up ART2 using

Using the ART2 GUI-Describes the ART2 graphical user interface

Using CART/NART Command Line Interfaces-Describes the CART

Interfacing a Custom Process to ART2-Provides information on

Sample Manufacturing Test Flow-Provides an example of how a

Sample CART Command List-A list of CART commands with full

Sample NART Command List-A list of NART commands with full

Atheros Communications, Inc.

AR93xx Single-Chip 802.lln MAC/BB/Radio for 2.4/5 GHz WLANs data

AR93xx EEPROM Device Configuration Guides

AR93xx ART Reference Guide

Atheros Communications, Inc.

ART2 runs on the same three-chain calibration setups as ART, consisting of