Professional Documents
Culture Documents
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.
List of Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Chapter 3 Using the ART2 GUI-Describes the ART2 graphical user interface
and its menu functions.
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.
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:
• AR93xx Single-Chip 802.lln MAC/BB/Radio for 2.4/5 GHz WLANs data
sheets
• AR93xx EEPROM Device Configuration Guides
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 Structure
Table 1-1 descnbes the directory structure of the ART2 package.
Table 1-1. ART2 Dtrectory Structure
Directomy Contents
AP 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.
art_driver Contains the Wmdows driver files needed when the radio being tested is
a STA card within a PC.
bin Contains the ART2 executables and is the directory from which ARI2
software should be run.
command Contains test flow files and reference design specific files needed for
testing Atheros WLAN radios.
docs Contains the Release Notes as well as the ART2 GUI support documents.
support 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
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 ··-·····------·------------·------···············----------·-····
CART
Instruments
Optional 2•• Radio Optional 511o Radio
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.
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.
Test
Instruments CART
NART
WiFi Device
AP
PCl
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.
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
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 ..................................................
CART ····"lo
I Instruments
Optional 2°• Radio Optional 3"' Radio
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.
Jn;tial Screen
Upon execution of the artGUI.exe file, the initial screen is shown:
-
l.OOY~ CIO
WfkC1¥1t toART?!
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.
.if Alh uo1 Radio lcs l 2 (A.IU:l-C.iUI) rnrEJ
... ...................................
• t•tT1U.UATIOS t• PaOOU SS .
. . ........
.Pt.EASE . • tT •
~
~
_
T"-'
..°'''"'""'
r"""cm
lltQstetS
5 103 llll'O COllP9oted to paat.rol proo• -
local.hon 2')99 .
on
~-·
Figure 3-3. lntttal ART2 GUI Screen, wtth Hterarchtcal Screen Displayed
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:
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.
-·--
O txpows:
b~d°l~N P«k.et~
(l'Jc7;(t.1J1d\l ,d'\2 Y ~ y
G!Se«~ ~erfrtr"<O~
O nar~ Ot.<100
:ir x 0 Cl.99
lswrt T14f'Ofll l 1 •
FAAN'IETER COOTP.«.
NO TRANSMISSION JN PROGRESS
I I
h«r :?412!+!: 1Tx?\o.r: L___,
Rat:t: lfG-S-• MbpsOft+1 1rxGs,...- ~
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
Test Parameters 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.
The ContTx window shows three buttons: Commit, Start Transmit, and Stop
Transmit Only the buttons that are relevant are available to the user.
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. ...
0
'""
.........
ltpom "~ ~
....., .....
........ b: Ox'1dl0,d\l.dll •
!!bi; 0,.7'; d'(l,ch1.o12 ..
.. .
""""""'
"''"'
NO UNK TEST IN PROGRESS
~ feits""""'"' .....
rransmtteir
0 W1
UN< Tai IN PROGRESS
.......
8 Recbtert
fu~k.c diS!t
lb ~ 0.:7. d·(l,.c;M,(fl2 v
0 1\.:.""sk
?tt.-;,iotcf't!o~
~l't Ccut
0 Atun.itt« ~ <Ollt«ll
~v
o0 ""'"""'"'''
........ """'
I AOt-~ l*~•sl
' ~
....................
"" - IH
....,..,•••i...t••···-··········
• Llg TElr UPORT •
2U2
6
2U2
9
2U2
12
2U2
18
2U2 2U2
21 l6
2 1.12
18 ,.
21.12 2 1.12
11
21.12
2J.
H.12
2S
2 1 .12 2U2 2U2 2U2
H• SS 111 us
Ha
USI
100
u
100
SI
100
u
100
,. 100
SI
100
,. 100
H ,.
100 100
12
100
n
100
n
100
52
100
52
100
SJ
100
SJ
1100 tllf'O c~ ln prOll,P"••• Try p•u.a C'Dftttiw. or ••op report • c,-, . _ . . i tp.1eu9d for l•t•r
prot"••• lng.
To retrieve the current full description for the link command, type help link
at the CART command line.
.....
-
............
~
~ '""'-''
FrtOAnCY: ~
-1·-
:; ::: ::::
-- .... """
.. ..
'"
- _:: ..::
~; ~tmO
.... ..........................
r;J feprom
..,._ _.....,.
--
~OC1t1: 30
--
L f9t(Y o HTlO
nc: OIO:d'IO.chLd'l2 •
..... HT20,Hf4J
R.ltlf ....
Kr4J
-·-
-·-
HH
HU
11
••
-;: ..:!
......
"
-·- . ... _
AX! 01r1:dl),di1,ct.2 •
,... .
""""""""
.........................
.._,. ,,._,
...-·-
...... ..::.. - .. .....
-·-
-- ,,_
~:
.. ,.,. '"
""
._
.a
H lJ
H I•
U
II " .,.. • itet
STA'IUS
TPUT TEST IN PROGRESS ... _..,.
.........................
I 11111 -·-
-·-
-·-
..........
::!! :: ......
HU ••
.
i:
" ... ., ...
-:! :--:r:
- ..... .,,
==
HU U .. 7J •
·
--
-·-
-n••-·
-
.........................
::::: .... .. ...
. .H I-
....
Hilt
H U
":
"~ ... ......
........ .. ...... ... ....
-"' -
-·- " HU
OK ] [ Cancel
~ s.... ...
~ NotwAtheros Radio Tt:i.t(HART--Gl.IQ
,...,., , <•llbr.thOr'I £q...Pft'ltnl ~•Med ......... ~
..,_ - ,>D'.lilol.Qil
,,.
Hom<
l oadC•rd' ......
lte.st.\'t1l:e OpiHbors
....,..,. .,...
Ollw ooer•'»W
.
Ii' '""CGtith
,...
"""
• arr
....,,
~,.~.Mi
.,_,
"""'
.
ftesCl;if•ftP'Oll.
• "'
-
e t19rom v-..: 1- -..- - 1
E::Zl!::I 1- ............ 1
Jtcgt.ttcrs ~@~@
"'9'1Pl"•-
....,,
....m>U-
. L """"==i
YM:
~@
I -
Figure 3-9. EEPROM Operations Control Screen
.. ..
101 1uo nrro qnnnH~»»n~~•N»nM•~nu
....., .,
-------------------------------------------------------------------
-· .
IOI 7510 UIFO
101 rno 1uo
IDJ 1\10 IUO
•etDOMtn
'IX1!419k
.....
1
, """'
°'"'OM • 91fD-.&D 7
__ _....
101 Tt.uft9 ca.. co, l) 1 (00 . 00) lnbl c ......-auon Odd
•• ......
·....--
IOI JUO llfnl GPIO eeptfrite ltn•bleo OP lO r d.... teleeottcm our
101 7"10
101 1510 llrrO
101 JUO IUO
''"'° •PIO Mlen N•• lll•
lnt.arnal ret'llatM'
.....
0.00000000
eHO "'1an UD
....-r..weou.... •
101 JUO 10'0
JOI 7UO tlr'F'O Sftz Nodal •••
101 1uo urro
.....,.
........,.
101 JUO 10'0 lat•. . . C - 1 ' 0x00041HH
101 n 10 urn Ant Chain 0 a.t C'tNJ.• 1 0.0010
101 1uo nrro
IOI l'UO 1..-0
101 JUO llSR
IOI JUO 1..-0
Ant C'baln t
-u- -tt-
a.att..,. DI dtO 1.ow
x.tt- 1111 C'h2 Law
UI C'hl
19
19
aau. . Im ch1 i.ow
a.ti-
lD9 CbO
1119 Ch2
...
...
19
19
101 1uo nrro
(01 1!110 IU'O
IOI UlO IUV
101 1UO IH'O
- • • - D• C'hO 91...
x.&U.. . l»I C'h2 hi. .
-.u.. 1Har'191nO LDlil
••t ten 1Henji.n2 LUM
••
....
....
-u-
sat t - 1J)li C'h1 Ml...
lltu'...•1
sat • - llkrqlnO
a....
lt
Utilities Screen
Open the Utilities screen by choosing Registers > Utilities in the hierarchical
menu.
.. -..
tjf~Ctl\
.... <Nd<
tl l ftl:',it'i
fil P.elW.erS
!tZll
-·
RMl#Wrtt ODt't«Kltlt
0M Q G<ldon Q ci.,..>
1t:t ...-SWl ~t;lrQ1\'io~ lTt
Adcten: v ]
LogWadorr'
5103 1•ro Cannltl't ... la ttant.rol 1R•tt••• 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
C\l
..........................................
•
l ~UO
IWITIALI ZATJ08 DOllE , , PLEASE C'OHHIB •
Equipm• nt Advanced
Home Client IP Address togwr.dow
ourcoi loc.lllos1 • I Loodcard
Cortlonbon
Golde1 (tl • I Loodcard
Nut locatton
0en12 m • I Lood card •••••••••••••••••••••••••••
NM cmd conrole •••••••••••••••••••••••••••
Gui aerver llabtning' • ••
Option Description
Home Returns the user to the Load Cards page
Cmd C011SOle Spawns a command console
Exit Application Exits the ART2 GUI application
Setup Menu
.• I[~]
Loodc..d I
•••••••••••••••••••••••••••
• I l.oldc..d l * INITIALllATIOll IN PllOm&q
•••••••••••••••••••••••••••
Option Description
Pathloss Enter setup path losses (overwrites defaults from start.art)
Change Startup Pushes a new startup script (similar to stut.art) into CART
Script without exiting the application
Client.s Menu
Unload
{O) lo<atlost • I LoodCNd I
qi-Tests
dJ-~cprom
Info
(I)
• I LoodCNd I •••••••••••••••••••••••••••
I Rtgisttrs Hello • I LoodCord I * I NIT IALIZATION IN ~
Storage
Option Description
Load 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.
Unload Unloads the card
Detaches the currently attached card. Unload must be run before
removing the card.
Info Provides basic information about a plugged and loaded card
Hello Pings all clients
Storage 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.
Tools Menu
r&
mm
r ..
Open script • I toad card
1.
I& Eeprom
Sondcmd • I toad Gord ••••••••••••••••••••
- Registers WnteoS<npt
• I toadeord * JlflTIALI ZA%JON Jlf
••••••••••••••••••••
Error display priority Gui -rver liatening' .
CntlMsgsON
Show Cmd Lin• I 5103 INFO Connected
Option Description
Run Script Allows the user to select a script to run; enter script name
Open Script 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.
SendCmd Opens a text box for commands, similar to a command line interface.
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
P. Enor O.SplayS.•oct1on ? I X
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
OK II CMcel
Calibration Menu
IJ-l°' New Athetos Radio Test (NART-GUI)
1-------'...:..----..,
Homm
File Setup Clients Tools
St•rt
I Trns
E<prom
- Rogistors
Stop
P1u~
Continue
Ttst seltttions
Loadc.td
load Cord
load Cord
•••••••••••••••••••••••••••
• I N IT IALIZATION I N PJUJGRBS
•••••••••••••••••••••••••••
OU1 •erver lleteldaq •••
./ Show script di•log
./ Show c•rd ID dialog 5103 JNIO Coaneatecl to con
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
Show Script When checked, this option prompts users to run a script.
Dialog When unchecked, the application runs the last script that was run.
Show Card ID When checked. prompts the user to enter a card ID (SSID, RBFname,
Dialog etc.). When unchecked, the application does not prompt the user.
········································
•••• • ••• • CUll UTT09 l • I U ••• • •••• ••
l . . . .. . . . . . . . . . . lln9I' M>14
l _ .• • • .rim- ~ M>H
D l lll'O LoMffl ctU' • f or aart l•J
20• . .... 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 ~ · · · -
• lm"O k • f ...... . - D U2
· • n~OJO 00001 • fur ••rt••· aua.r-1.. ....
............
m
"" ...
11 •
•
•••
.
1 1 1. 0 c-t t•
Ht2
.,,,,.,
He?
QK J [ ~ancel
Advanced Menu
IJ.:' New Alheros Radio T.st (NART-OUI)
Fil• Setup Clients Tools
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
Hoiim
! losts
Eeprom
- Rogistcr>
Colden (I)
Cl<nt2(2)
Save- log window to file.
•••••••••••••••••••••••••••
Option Description
Clear Log Cl.ears the log window
Wmdow
Save Log Saves the log to a designated file
Window to File
Help Menu
~
mm
Tosts Goldon (I)
locahost Boords Supportod
About ART
dJ E•prom Cliont2 (2)
._ Rcgistm loadG!wd • INIT IALIZATIOll I N
•••••••••••••••••••••••••••
5103 INFO Conneoted to oon
Option Description
Boards Displays a list on the log window of the boards supportEd by the
Supported application
About ART Information about the application version and build date
.................................................................
Test .....,
Instruments
Optional 2°d Radio Optional 5111 Radio
••• Driver
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.
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.
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], Connects to NART on the specified host and port for the DUT or local machine. The
-local [host :port] 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), Connects to NART on the specified host and port for the golden unit or remote
-remote [host :port) 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.
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).
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
• Increments can be negative, such as for ISS sweeps, which are generally
performed as:
iss=-50:-100:-1;
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.
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.
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.
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.OOt•rx.bytes would display the value in kilobytes as opposed to bytes.
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
Report Types
Table 4-4 describes the standard report types.
Table 4-4. Report Types
Table 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 3.0 4.0 5.0 6.0 7.0
2.0 -24.l -22.4
l. 0 -23.7 -21. 9
0.0 -23.2
3.0 -22.9
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]
y Shorthand for setting field[l]
z 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 Increment on the chart axis and bin size for histograms
size 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 Data type: f, d, x, or s (Default = f)
width Width of the data fields (Default = 10)
decimal Number of decimal places shown (Default= 1 on f type; none on s, d, and x)
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
This response lists the type of parameter value NART expects, the allowed
range of values, and any special values.
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.
Custom
Process
................................................................,
Test ......
CART
Instruments
Optional 2•d Radio Optional 5111 Radio
••• Driver
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
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 4-
digit 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.
WiFi
Device
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.
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:
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
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:
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
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.
Golden Unit
Attenuator
HP 11713A Connection
Attenuator/ RF Cable
Switch Driver x3
Ethernet Router
HP E4416A HP 4404B
Power Meter Spectrum
f---,-,-~- io---1-G-PI
_ B _ _ _ _ _ _ _ _ _ _ _ _ Analyzer
National Inst ruments
GPIB-ENET/100
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.
NOTE: Make sure that the attenuator switch drivers are all set to Owhen measuring
the path losses between instruments/golden and the DUT.
ft"""'... ·· · I !lefre•h I
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
!fostname: j i i iil:fj:ti
(' .QbtaO> .,.. 1p oddreos outomotic~ (DHCP)
!;onwnenl (Olltional)
OK Cancel
I
Rgure 6-3. GPIB Device Conflguratlon Properties Dialog
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.
Hosl Name
c. Select Configure and enter the same IP address that was assigned to
the GPIB-ENET /100 and click OK.
lij§i;J1ICd§i;j @lit4!I!M
Hardware Settings ------~
Hosl Name
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).
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).
File Description
bin\start.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.
bin \ProductList.ref
• 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.
command\ test_flow_flags.art
• Called from start.art, thus it is called at CART startup time
• Contains the flags to disable tests within the manufacturing test flow
$refName \$refID.ref
• 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
$refName \$refID _power.art
• Called from the refID.ref file called during manufacturing calibration
• Sets the reference design specific target powers
$refName\ctl_$refID.art
• 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.
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 to golden
path device=go1den;f=2442,5240,SSOO,SBOS;chain=l;loss=7.6,9.9,10.3,10.6;
path device=go1den;f=2442,5240,5500,5805;chain=2;1oss=7.6,9.9,10.2,10.6;
path 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;
Table 6-3 describes each of the setting used within the start.art.
Entries Description
path 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.
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
SSID ref ID refName prodID
----------------------------------------------
Ox3112 XB112-035 XB112 200
Ox3113 XB113-024 XB113 203
Ox3113 XB113B-112 XB113 203
Ox3114 XB114-235 XB114 204
Oxalll APlll APlll 206
Ox3116 HB116-041 HB116 209
Ox3110 HB112-241 HB112 205
Table 6-4 describes the meaning of the columns within this file.
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.
##-----------------------------------------------------------------
## For Tx Test
##-----------------------------------------------------------------
assign txPwrDisable2g=O
assign txPwrDisableSg=O
assign txPwrA11ChainDisable2g=l
assign txPwrA11ChainDisable5g=l
assign maskDisable2g=l
assign maskDisableSg=l
assign txEVMDisable2g=l
assign txEVMDisableSg=l
assign channAccDisable2g=l
assign channAccDisable5g=l
##-----------------------------------------------------------------
## For Rx Test
##-----------------------------------------------------------------
assign rxsensDisable2g=O
assign rxsensDisable5g=O
assign rxPerDisable2g=0
assign rxPerDisableSg=O
##-----------------------------------------------------------------
## For TX unicast Throughput Test
##-----------------------------------------------------------------
assign txPerDisable2g=O
assign txPerDisable5g=0
assign tputTx2gDisable=O
assign 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 btxPerDisable2g=l
assign btxPerDisableSg=l
assign btputTx2gDisable=l
assign 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
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.
$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;
#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;
#SGHz
set antctrlcommon5g=220;
set antctrlcommon25g=44444;
set antCtrlChain5g=10, 10, 10;
set miscellaneous.quickdropenable=l;
set quickdrop2g=-44;
set quickdropSg=-34;
set quickdroplow=-34;
set 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
#CTL Files
#common\ctl_generic.art
Table 6-6 describes the flags that set within these files.
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.
2 Generic
3 HB112
4 HB116
5 XB112
6 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 Set the device type of the adapter. Available choices are:
1 CardBus
2 PCI
3 MiniPCI
4 AP
5 PCieMini
6 PCIExpress
7 PCIE Desktop
regdmn Set the regulatory domain code that should be written to EEPROM/OTP /Flash.
Refer to Table 2-8 of the AR93xx EEPROM Guide
$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 freq piers for OFDM legacy 5G, Max 8 piers, in order of fO, fl, ... f7
set caltgtfreq5g=5180,5240,5320,5400,5500,5600,5700,5825;
# 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
# 14 values represent the target power in dBm for the following data rate
#
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;
set caltgtpwrht202g=v. (16,16,16,16,16,15,16,16,15,14,14,14,14,13),f.2;
#Target power freq piers for HT20 5G, Max 8 piers, in order of fO, fl, ... f7
set caltgtfreqht205g=5180,5240,5320,5400,5500,5700,5745,5825;
# Target power freq piers for HT40 2G, Max 3 piers, in order of fO, fl, f2
set caltgtfreqht402g=2412,2437, 2472;
#Target power freq piers for HT40 5G, Max 8 piers, in order of fO, fl, ... f7
set caltgtfreqht405g=5180,5240,5320,5400,5500,5700,5745,5825;
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.
Command Description
caltgtfreqcck Set the Frequency piers for 2 GHz CCK rates. Refer to Table 2-14 of the AR93xx
EEPROM Guide
caltgtpwrcck 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
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.
Refer to Table 2-17 of the AR93xx EEPROM Guide
caltgtfreq5g Set the Frequency piers for 5 GHz OFDM rates. Refer to Table 2-14 of the AR93xx
EEPROM Guide
Command Description
caltgtpwr5g Used to set the per rate powers for each frequency pier of the 5 GHz OFDM rates.
Refer to Table 2-20 of the AR93xx EEPROM Guide
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.
Refer to Table 2-18 of the AR93xx EEPROM Guide
caltgtfreqht205g Set the Frequency piers for 5 GHz HT20 rates. Refer to Table 2-14 of the AR93xx
EEPROM Guide
caltgtpwrht205g Used to set the per rate powers for each frequency pier of the 5 GHz HT20 rates.
Refer to Table 2-18 of the AR93xx EEPROM Guide
caltgtfreqht402g Set the Frequency piers for 2 GHz HT40 rates. Refer to Table 2-14 of the AR93xx
EEPROM Guide
caltgtpwrht402g Used to set the per rate powers for each frequency pier of the 2 GHz HT40 rates.
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 Used to set the per rate powers for each frequency pier of the 5 GHz HT40 rates.
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
#Test Group Oxl5: us and CANADA (FCC) 802.lln HT20 2GHz mode CTL
set 2GHz.ctl.Index[2]=0xl5;
set 2GHz.ctl.Frequency[2]=2412,2417,2422,2462;
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;
set 2GHz.ctl.Frequency[3]=2422,2427,2432,2452;
set 2GHz.ctl.Power[3]= 9.5 ,13 ,13 ,9.5;
set 2GHz.ctl.BandEdge[3]= 1 ,1 ,1 ,O;
#Test Group Ox45: Japan (MKK) 802.lln HT20 2GHz mode CTL
set 2GHz.ctl.Index[6]=0x45;
set 2GHz.ctl.Frequency[6]=2412,2417,2422,2472;
set 2GHz.ctl.Power[6]= 17.5,17.5,17.5,17;
set 2GHz.ctl.BandEdge[6]= 1 ,1 ,1 ,O;
#Test Group Ox47: Japan (MKK) 802.lln HT40 2GHz mode CTL
set 2GHz.ctl.Index[7]=0x47;
set 2GHz.ctl.Frequency[7]=2422,2427,2432,2462;
set 2GHz.ctl.Power[7]= 15 ,17.5,17.5,17.5;
set 2GHz.ctl.BandEdge[7]= 1 ,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;
set 2GHz.ctl.Power[10]= 12.5,13 ,12.5,12.5;
set 2GHz.ctl.BandEdge[10]= 1 ,1 ,1 IO;
#Test Group Ox37: Europe (ETSI) 802.lln HT40 2GHz mode CTL
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;
#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;
set SGHz.ctl.Frequency[2]=5190,5230,5270,5310,5510,5670,5755,5795;
set 5GHz.ctl.Power[2]= 11 ,13.5,12 ,8.5 ,14 ,14.5,15.5,15;
set 5GHz.ctl.BandEdge[2]= 1 ,1 ,1 ,1 ,1 ,1 ,1 ,O;
#Test Group Ox46: Japan (MKK) 802.lln HT20 5GHz mode CTL
set 5GHz.ctl.Index[4]=0x46;
set SGHz.ctl.Frequency[4]=5180,5200,5220,5240,5260,5500,5520,5700;
set 5GHz.ctl.Power[4]= 15 ,15 ,15 ,15 ,15 ,15.5,15.5,14.5;
set 5GHz.ctl.BandEdge[4]= 1 ,1 ,1 ,1 ,1 ,1 ,1 ,O;
#Test Group Ox48: Japan (MKK) 802.lln HT40 5GHz mode CTL
set 5GHz.ctl.Index[5]=0x48;
set 5GHz.ctl.Frequency[5]=5190,5230,5270,5310,5510,5550,5590,5670;
set 5GHz.ctl.Power[5]= 14.5,14 ,14.5,14.5,14.5,14 ,14 ,14.5;
set 5GHz.ctl.BandEdge[5]= 1 ,1 ,1 ,1 ,1 ,1 ,1 ,O;
#Test Group Ox36: Europe (ETSI) 802.lln HT20 5GHz mode CTL
set SGHz.ctl.Index[7]=0x36;
set 5GHz.ctl.Frequency[7]=5180,5200,5220,5240,5260,5500,5520,5700;
set 5GHz.ctl.Power[7]= 16.5,16.5,16.5,16.5,16.5,13.5,13.5,14;
set 5GHz.ctl.BandEdge[7]= 1 ,1 ,1 ,1 ,1 ,1 ,1 ,O;
#Test Group Ox38: Europe (ETSI) 802.lln HT40 SGHz mode CTL
set 5GHz.ctl.Index[8]=0x38;
set 5GHz.ctl.Frequency[8]=5190,5230,5270,5310,5510,5550,5590,5670;
set 5GHz.ctl.Power[8]= 15.5,15.5,15.5,15.5,14 ,14 ,14 ,14;
set 5GHz.ctl.BandEdge[8]= 1 ,1 ,1 ,1 ,1 ,1 ,1 ,O;
Command Description
2GHz.ctl.Index Set the 2 GHz regulatory domain Index. Refer to Table 2-21 of the AR93xx EEPROM
Guide
2GHz.ctl.Frequency Set the 2 GHz band edge frequencies. Refer to Table 2-22 of the AR93xx EEPROM
Guide
2GHz.ctl.Power Set the 2 GHz band edge power values. Refer to Table 2-22 of the AR93xx EEPROM
Guide
2GHz.ctl.BandEdge Set the 2 GHz band edge flags values. Refer to Table 2-22 of the AR93xx EEPROM
Guide
SGHz.ctl.Index Set the 5 GHz regulatory domain Index. Refer to Table 2-21 of the AR93xx EEPROM
Guide
5GHz.ctl.Frequency Set the 5 GHz band edge frequencies. Refer to Table 2-22 of the AR93xx EEPROM
Guide
SGHz.ctl.Power Set the 5 GHz band edge power values. Refer to Table 2-22 of the AR93xx EEPROM
Guide
5GHz.ctl.BandEdge Set the 5 GHz band edge flags values. Refer to Table 2-22 of the AR93xx EEPROM
Guide
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]
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]
interleaveRates, ir: interleave packets from different rates?
no[O]
yes[1]
CART[2]
packetCount, pc, np: the number of packets sent
type=decimal; minimum=-1: maximum=2147483647; default=100; dimension=[200];
infinile[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
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]
duration: the maximum duration of the operation
type=decimal; minimum=-1; maximum=2147483647; default=60000; untts=ms;
forever[-1]
dump: the number of bytes of each packet displayed in the nart log
type=unsigned; minimum=O; maximum=4000; default=O;
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
type=mac address: default=20:22:22:22:22:02;
macrx: the mac address used by the receiver
type=mac address; default=10:11 :11 :11 :11 :01;
calibrate: calibrate transmtt power
none[O]: nothing is measured
combined[1]: the combined output signal is measured
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
nf: noise floor value
type=decimal; minimum=-200; maximum=200; default=O;
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
type=decimal; minimum=O; maximum=3; default=3;
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
no[O]
yes[1]
tx.100: use tx100 mode, continuous data transmission
no[O]
yes[1]
interFrameSpacing, ifs, fs: spacing between frames
type=decimal; minimum=-1; maximum=1; default=-1;
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
type=decimal; minimum=-1: maximum=2147483647; default=100; dimension=[200];
infinile[O]
packetlength, pl: the length of the packets
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];
txChain: 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];
no[O]
yes[1]
duration: the maximum duration of the operation
type=decimal; minimum=-1; maximum=2147483647; default=60000; unlts=ms;
foreverf-1]
dump: the number of bytes of each packet displayed in the nart log
type=unsigned; minimum=O; maximum=4000; default=O;
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
type=mac address; default=20:22:22:22:22:02;
macrx: the mac address used by the receiver
type=mac address; default=10:11:11 :11 :11 :01;
calibrate: calibrate transmit power
none[O]: nothing is measured
combined[1]: the combined output signal is measured
isola1ed[2]: attenuators are used to isolate and measure each chain separately
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
type=decimal; minimum=-200; maximum=200; default=O;
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
type=decimal; minimum=O; maximum=3; default=3;
ht40: use 40MHz channel
none[O]
low[-1]
high[1)
automalic[2]
gi, sgi: use short guard interval
no[O]
yes[1]
tx99: use tx.99 mode, small, constant interframe spacing
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]
deafMode: disable receiver during transmission
no[O]
yes[1)
pattern: data pattern
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]
interleaveRates, ir: interleave packets from different rates?
no[O]
yes[1]
CART[2]
packetCount, pc, np: the number of packets sent
type=decimal; minimum=-1; maximum=2147483647; default=100; dimension=[200];
infinile[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
type=hexadecimal; minimum=1; maximum=7; default=7; dimension=[200];
txChain: 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 tempera1ure at which the test is run
type=decimal; minimum=-1; maximum=100; default=-1; units=deg C; dimension=[200];
dut[O]
golden[1]
blocker12]
screen: show results on the screen
no[O]
yes[1]
sw: sticky write of a device field/register, sticky writes are perfonned after every device reset
instance: which device
type=decimal; minimum=-1; maximum=2; default=O;
dut[O]
golden[1]
blockert2]
screen: show results on the screen
no[O]
yes[1]
sc: clear sticky field/register from list, last-0n, first-0ff order
instance: which device
type=decimal; minimum=-1; maximum=2; default=O;
dut[O]
golden[1]
blockert2]
screen: show results on the screen
no[O]
yes[1]
fr: field read
instance: which device
type=decimal; minimum=-1; maximum=2; default=O;
dut[O]
golden[1]
blockert2]
screen: show results on the screen
no[O]
yes[1]
fw: field write
instance: which device
type=decimal; minimum=-1; maximum=2; default=O;
dut[O]
golden[1]
blockert2]
screen: show results on the screen
no[O]
yes[1]
fl: list all the matching fields
instance: which device
type=decimal; minimum=-1; maximum=2; default=O;
dut[O]
golden[1]
blockert2]
screen: show results on the screen
no[O]
yes[1]
mr: memory read
instance: which device
type=decimal; minimum=-1; maximum=2; default=O;
dut[O]
golden[1]
blockert2]
screen: show results on the screen
no[O]
yes[1]
nolsefloor, nf: compute the noise floor
instance: which device
type=decimal; minimum=-1; maximum=2; default=O;
dut[O]
golden[1]
blocker[2]
screen: show results on the screen
no[O]
yes[1]
nfg: retrieve and display the calibrated noise floor measurements
instance: which device
type=decimal; minimum=-1; maximum=2; default=O;
dut[O]
golden[1]
blocker[2]
screen: show results on the screen
no[O]
yes[1]
targetPower, tp: retrieve and display the target power values
instance: which device
type=decimal; minimum=-1; maximum=2; default=O;
dut[O]
golden[1]
blocker[2]
screen: show results on the screen
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
instance: which device
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]
ht40: use 40MHz channel
none[O]
low(-1]
high[1]
automalic[2]
mean[-100]
[OJ
[O]
txgminimum: minimum txgain for calibration search
type=decimal; minimum=O; maximum=100; default=O;
txgmaximum: maximum txgain for calibration search
type=decimal; minimum=O; maximum=100; default=100;
nf: noise floor value
type=decimal; minimum=-200; maximum=200; default=O;
current[O]
calculate[1]
rssical: measure and calibrate rssi
no[O]
yes[1]
rxiqcal, iqcal: perform rx iq calibration
no[O]
yes[1]
average, avg: number of measurements taken and averaged
type=decimal; minimum=-1; maximum=1000; default=-1;
automatic[-1]
reset: reset device before operation
no[O]
yes[1]
automatic[-1]
pdgain: pdgain
type=decimal; minimum=O; maximum=3; default=O;
statistic: statistic
type=decimal; minimum=O; maximum=3; default=3;
gi, sgi: use short guard interval
no[O]
yes[1]
interframeSpacing, ifs, fs: spacing between frames
type=decimal; minimum=-1; maximum=1; default=-1;
regular[-1]
tx100[0]
tx99[1]
deafMode: disable receiver during transmission
no[O]
yes[1]
pattern: data pattern
type=hexadecimal; minimum=O; maximum=ff; default=O;
chipTemperab.Jre: wait for chip temperature to exceed this value
type=unsigned; minimum=O; maximum=255; default=O;
receive, rx, r: causes the specified device to receive
frequency, f: the channel carrier frequency
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]
yes[1]
ht40: use 40MHz channel
none[O]
low[-1]
high[1]
automatic[2]
packetCount, pc, np: the number of packets sent
type=decimal; minimum=-1; maximum=2147483647; default=100;
infinile[O]
aggregate: the number of aggregated packets
type=decimal; minimum=O; maximum=32; default=1;
duration: the maximum duration of the operation
type=decimal; minimum=-1; maximum=2147483647; default=60000; units=ms;
forevert-1]
packetLength, pl: the length of the packets
type=unsigned; minimum=30; maximum=4000; default=1000; units=Byte;
transmitPower, tp, txp: the transmit power used
type=ftoat; minimum=-100; maximum=31.5; default=-100; units=dBm;
target[-1 00]
pcdac, txgain, txg: the tx gain used by the transmitter
type=decimal; minimum=O; maximum=100; default=30;
broadcast, be: if set to 1the packets are broadcast, if set to 0 the packets are unicast
no[O]
yes[1]
retry: the number of times a packet is retransmitted
type=unsigned; minimum=O; maximum=15; default=O;
tx99: use tx99 mode, small, constant interframe spacing
no[O]
yes[1]
tx100: use tx100 mode, continuous data transmission
no[O]
yes[1]
carrier: transmit carrier only
no[O]
yes[1]
chain, ch: the chain mask used for both transmit and receive
type=hexadecimal; minimum=1; maximum=7; default=7;
txChain: the chain mask used for transmit
type=hexadecimal; minimum=1; maximum=7; default=7;
rxChain: the chain mask used for receive
type=hexadecimal; minimum=1; maximum=7; default=7;
dump: the number of bytes of each packet displayed in the nart log
type=unsigned; minimum=O; maximum=4000; default=O;
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
type=mac address; default=20:22:22:22:22:02;
macrx: the mac address used by the receiver
type=mac address; default=10:11:11 :11 :11 :01;
attenuation: the attenuation between the golden unit and the dut
type=decimal; minimum=O; maximum=110; default=O; units=dB;
inputSignalStrength, iss: the expected input signal strength at the dut
type=decimal; minimum=-120; maximum=O; default=O; units=dB;
calibrate: calibrate transmit power
none[O]: nothing is measured
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
type=hexadecimal; minimum=1; maximum=7; default=7;
txChain: transmit chain mask
type=hexadecimal; minimum=1; maximum=7; default=7;
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
address: the address
type=hexadecimal;
rw: writes a device register with the specified value
address: the address
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
address, name: the field name or address
5GHz.SwltchSettling, SwltchSettling5g:
type=hexadecimal; minimum=O; maximum=ff; default=O;
5GHz.AdcSize, AdcDesiredSize5g:
type=decimal; minimum=-127; maximum=127; default=O;
5GHz.Thresh62, Thresh625g:
type=hexadecimal; minimum=O; maximum=ff; default=O;
5GHz. PaPredistortion.Ht20, papd5gRateMaskHt20: pa predistortion mask for HT20 rates
type=hexadecimal; minimum=O; maximum=flfllflf; default=O;
5GHz. PaPredistortion.Ht40, papd5gRateMaskHt40: pa predistortion mask for HT40 rates
type=hexadecimal; minimum=O; maximum=flfllflf; default=O;
5GHz.Future, future5g: reserved words, should be set to 0
type=hexadecimal; minimum=O; maximum=ff; default=O; dimension=[10];
5GHz.Transmitcalibration.Frequency, calPierFreq5g: frequencies at which calibration is performed
type=unsigned; minimum=4000; maximum=7000; default=5180; units=MHz; dimension=[8];
5GHz.Transmitcalibration.PowerConection, CalPierRefPower5g: transmit power calibration correction values
type=decimal; minimum=-127; maximum=127; default=O; dimension=[3][8];
5GHz.TransmitCalibration.Voltage, CalPierVoltMeas5g: voltage measured during transmit power calibration
type=unsigned; minimum=O; maximum=255; default=O; dimension=[3][8];
5GHz.TransmitCalibration.Temperature, CalPierTempMeas5g: temperature measured during transmit power calibration
type=unsigned; minimum=O; maximum=255; default=O; dimension=[3][8];
5GHz. ReceiveCalibration .NoiseFloor, CalPierRxNoiseftoorCal5g: noise floor measured during receive calibration
type=decimal; minimum=-127; maximum=127; default=O; dimension=[3][8];
5GHz.ReceiveCalibration.Power, CalPierRxNoiseftoorPower5g: power measured during receive calibration
type=decimal; minimum=-127; maximum=127; default=O; dimension=[3][8];
5GHz.ReceiveCalibration.Temperature, CalPierRxTempMeas5g: temperature measured during receive calibration
type=unsigned; minimum=O; maximum=255; default=O; dimension=[3][8];
5GHz.Target.Frequency.Legacy, calTGTFreq5g: frequencies at which target powers for legacy rates are specified
type=unsigned; minimum=4000; maximum=7000; default=5180; units=MHz; dimension=[B];
5GHz.Target.Power.Legacy, calTGTpwr5g: target powers for legacy rates
type=ftoat; minimum=O; maximum=35; default=10; units=dBm; dimension=[8][4];
5GHz.Target.Frequency.Ht20, calTGTFreqht205g: frequencies at which target powers for ht20 rates are specified
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];
5GHz.Target.Frequency.Ht40, calTGTFreqht405g: frequencies at which target powers for ht40 rates are specified
type=unsigned; minimum=4000; maximum=7000; default=5180; units=MHz; dimension=[B];
5GHz.Target.Power.Ht40, calTGTpwrht405g: target powers for ht40 rates
type=float; minimum=O; maximum=35; default= 1O; units=dBm; dimension=[8][14];
5GHz.Ctl.lndex, Ctllndex5g: ctl indexes, see eeprom guide for explanation
type=hexadecimal; minimum=O; maximum=ff; default=O; dimension=[9];
5GHz.Ctl.Frequency, Ct1Freq5g: frequencies at which maximum transmit powers are specified
type=unsigned; minimum=O; maximum=7000; default=5180; units=MHz; dimension=[9][8];
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
type=hexadecimal; minimum=O; maximum=3; default=O; dimension=[9][8];
Config:
type=hexadecimal; minimum=O; maximum=flfllflf; default=O;
ConfigPCle:
type=hexadecimal; minimum=O; maximum=flfllflf; default=O;
DevicelD, devid: the device id
type=hexadecimal; minimum=O; maximum=fllf; default=O;
SSID, subSystemld: the subsystem id
type=hexadecimal; minimum=O; maximum=fllf; default=O;
VID, vendorld: the vendor id
type=hexadecimal; minimum=O; maximum=fllf; default=O;
SVID, subVendorld: the subvendor id
type=hexadecimal; minimum=O; maximum=fllf; default=O;
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
preference, default: the prefered starting template
type=decimal; minimum=2; default=2;
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]
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]
otp[3]
size: memory size used for calibration data
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
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].
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.
ATHEROS~
www.atheros.com
CO/llPANY CONRDENTJAL
Subject tu Change witilout Notiat