Teledyne Conquest User Manual

PROTOCOL SOLUTIONS GROUP
3385 SCOTT BLVD
SANTA CLARA, CA 95054

Analyzer/Exerciser/DC Verification

Conquest

USB 2.0/1.x

User Manual

Version 7.45

For Software Version 7.45

August 2009

Trademarks and Servicemarks

disposal and recycling regulations that
var y b y country and region. Man y
countries prohibit the disposal of
waste electronic equipment in
standard waste receptacles.
For more information about proper
disposal and recycling of your Catalyst
product, please visit
www.getcatalyst.com/recycle.

LeCroy and Conquest are trademarks of LeCroy Corporation.

Universal Serial Bus and On-The-Go are registered trademarks of USB-IF.

Microsoft and Windows are registered trademarks of Microsoft Corporation.

Intel and Pentium are registered trademarks of Intel Corporation.

AMD Duron and AMD Athlon are trademarks of Advanced Micro Devices Inc.

All other trademarks and registered trademarks are property of their respective owners.

Disclaimer

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE
SUBJECT TO CHANGE WITHOUT NOTICE. ALL INFORMATION, EXAMPLES AND
RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE
REPRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS ARE FULLY
RESPONSIBLE FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE
SET FORTH IN INFORMATION THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED
HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR
LIMITED WARRANTY, CONTACT LeCroy FOR A COPY.

Copyright

Copyright © 2009, LeCroy Corporation; All rights reserved.

This document may be printed and reproduced without additional permission, but all copies should contain
this copyright notice.

WEEE Program

This electronic product is subject to

Contents

Table of Contents

Conquest Versions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1

Conquest M2 versus Conquest - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1

Common Software - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1

Conquest M2 (SBAE30) and Conquest Supported Features - - - - - - - - - - - 2

Introduction- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3

Analyzing USB Designs With the Analyzer - - - - - - - - - - - - - - - - - - - - - - - - 4

Conquest M2 Options - - - - - - - - - - - - - - - - - - - - - - - - - - 5

Host Exerciser- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5

Device Emulation- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5

OTG Exerciser - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5

DC Compliance measurement - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5

Timing Analyzer- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5

Conquest M2 Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6

Status LED Function Description - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6

Manual Trigger - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6

External Signals (Ext. Out, Ext. Trig In, and Ext. Clk) - - - - - - - - - - - - - - - - - 6

Ports - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7

Power In - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7

Analyzer/Exerciser Connection Identification - - - - - - - - - - - - - - - - - - - - - - 8

Receiving the Analyzer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9

Conquest M2 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9

Conquest - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9

Unpacking the Analyzer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9

iii

Contents

Installing the Analyzer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10

Hardware Setup - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10

Exerciser Configuration Connections - - - - - - - - - - - - - - - - - - - 11

OTG Analysis Connections - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 11

OTG Exerciser as DRD A-Device Connections - - - - - - - - - - - - - - - - - - - - 12

OTG Exerciser as DRD or Peripheral Only B-Device Connections - - - - - - 12

Device Emulation Connections - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13

Conquest Analyzer Connections - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14

Conquest Exerciser Connections - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14

Conquest M2 External I/O Connector Pin Assignment - - - - - - - - - - 15

Conquest External I/O Connector Pin Assignment - - - - - - - - - - - - - - - - - 15

Software Installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16

Manual USB Driver Installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17

Updating the Conquest USB Driver Manually - - - - - - - - - - - - - - - - - - - - - 17

Directory Structure on Windows XP and Vista - - - - - - - - - - - - - - - - - - - - 18

Windows XP - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18

Windows Vista - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19

Launching the USB Analyzer - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20

Connecting via Ethernet - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21

Connecting to a Network - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22

Connecting via Hub, Switch or Similar device - - - - - - - - - - - - - - - - - - - - - 23

Operating in Simulation Mode - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23

Authorization - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24

Example Projects - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25

Project File Types - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 26

Run an Example Project - - - - - - - - - - - - - - - - - - - - - - - - - 28

Default Capture - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29

Creating Projects- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 30

Capture and Timing Analysis Projects - - - - - - - - - - - - - - - - - - - - - - - - - - 30

Performance Analysis Projects - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 31

Device Emulation & OTG Advanced Exerciser - - - - - - - - - - - - - - - - - - - - 31

Current and Voltage Measurements - - - - - - - - - - - - - - - - - - - - - - - - - - - 31

iv

Contents

Protocol Analysis - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33

Easy Mode (Pre-Defined Setups) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33

Easy Data Capture - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34

Trigger on Data - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36

Data Capture Options - - - - - - - - - - - - - - - - - - - - - - - - - - 43

Custom Transaction - - - - - - - - - - - - - - - - - - - - - - - - - - - 45

Exercise and Capture (Optional) - - - - - - - - - - - - - - - - - - - - - - 46

Programming the Exerciser in Easy Mode - - - - - - - - - - - - - - - - 47

Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50

Auxiliary Port- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 53

Advanced Mode (User-Defined) - - - - - - - - - - - - - - - - - - - - - - 55

Capture Data Project - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55

Defining Packets - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 56

Packet Payload Data - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 58

The Sequencer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 60

Sequencer Operation Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - 60

Programming the Sequencer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61

Protocol Errors - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 66

Setting a Protocol Error Mask - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 66

Host Exerciser (Optional) - - - - - - - - - - - - - - - - - - - - - - - - - - 67

Programming the Exerciser In Advanced Mode - - - - - - - - - - - - - - - - - - - 67

Programming with Transfers - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 68

Specifying a New Class - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 73

Specifying Data for Transfer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 74

Reduced Bit Width - - - - - - - - - - - - - - - - - - - - - - - - - - - - 79

Exerciser Programming Shortcuts - - - - - - - - - - - - - - - - - - - - 80

Creating an Exerciser Program by Importing - - - - - - - - - - - - - - - - - - - 80

Advanced Refresh - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 82

Creating an Exerciser Program by Copying and Pasting - - - - - - - - - - - 83

v

Contents

Creating a Data Block - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 86

Naming a Data Block - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 87

Creating and Editing Data Blocks as Text - - - - - - - - - - - - - - - - - - - - - 91

Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 92

Running the Project - - - - - - - - - - - - - - - - - - - - - - - - - - - 93

Set Data Capture Options - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 93

Run Project - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 93

Reports - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 94

View Statistical Report - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 94

View Data Report - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 95

View Data Report Statistics - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 97

Display Histogram - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 98

Search a Data Report for a Pattern - - - - - - - - - - - - - - - - - - - - - - - - - - 99

High Level Interpretation Assignment - - - - - - - - - - - - - - - - - - 101

User-Defined Decodes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 102

Protocol Errors - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 104

Protocol Errors Detected While Capturing Data - - - - - - - - - - - - - - - - - - 104

Protocol Errors Detected Post-Process - - - - - - - - - - - - - - - - - - - - - - - - 105

Pre-Trigger - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 107

Performance Analysis - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 109

Performance Analysis (Easy Mode) - - - - - - - - - - - - - - - - - - - - - - - - - - - - 109

Performance Analysis (Advanced Mode) - - - - - - - - - - - - - - - - - 112

Real Time Analysis - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 112

Perform a Pre-defined Analysis - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 113

Create a New Analysis - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 113

Define Packets - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 114

Program The Exerciser - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 114

Creating Analysis Expressions - - - - - - - - - - - - - - - - - - - - - - - - - - - - 115

Saved Performance Analysis Review - - - - - - - - - - - - - - - - - - 121

vi

Contents

Timing Analysis (Optional) - - - - - - - - - - - - - - - - - - - - - - - - - - - - 123

Easy Mode Timing Analysis - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 123

Advanced Mode Timing Analysis - - - - - - - - - - - - - - - - - - - - - 125

Device Emulation (Optional) - - - - - - - - - - - - - - - - - - - - - - - - - - - 129

Device Emulation (Easy Mode) - - - - - - - - - - - - - - - - - - - - - - 130

Programming the Device - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 130

Endpoint Errors Generated by OTG DRD & Device Emulation - - - - - 137

Device Emulation (Advanced Mode)- - - - - - - - - - - - - - - - - - - - 138

Test Mode - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 139

Programming the Device - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 139

OTG Exerciser (Optional) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 145

OTG Exerciser as an A-Device - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 145

Programming the Device - - - - - - - - - - - - - - - - - - - - - - - - 146

Create Exerciser Program - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 147

Define OTG Device Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 149

Starting a Session - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 149

Dropping a Session - - - - - - - - - - - - - - - - - - - - - - - - - - - 150

OTG Exerciser as a Peripheral B-Device - - - - - - - - - - - - - - - - - - - - - - - - - 150

Define OTG Device Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 152

Create Exerciser Program - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 152

Requesting a Session - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 153

Terminating the Exerciser Program - - - - - - - - - - - - - - - - - - - - - - - - - - - - 153

Host Negotiation Protocol (HNP) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 153

Session Request Protocol (SRP) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 154

How to Turn Off the VBUS (in an OTG Script) - - - - - - - - - - - - - - - - - - - - 154

How Long Does Conquest Take to Drop D+ Pull-up? - - - - - - - - - - - - - - - 154

vii

Contents

Current Measurement (Optional) - - - - - - - - - - - - - - - - - - - - - - - - 155

Unconfigured Current Measurement - - - - - - - - - - - - - - - - - - - 156

Operating Current Measurement - - - - - - - - - - - - - - - - - - - - - 158

Making the VBus Measurement - - - - - - - - - - - - - - - - - - - - 161

VBus Droop Measurement - - - - - - - - - - - - - - - - - - - - - - - 163

Inrush Current Measurement - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 165

Inrush Current Display Features - - - - - - - - - - - - - - - - - - - - - - - - - - - 167

Suspend Current Measurement - - - - - - - - - - - - - - - - - - - - 170

Current Measurement Calibration Board - - - - - - - - - - - - - - - - 172

Display Manipulation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 175

Results Display Viewing Preferences - - - - - - - - - - - - - - - - - - - - - - - - - - - 176

Compact View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 177

Display Idle Time - - - - - - - - - - - - - - - - - - - - - - - - - - - 178

Waveform Display - - - - - - - - - - - - - - - - - - - - - - - - - - - 179

Filter - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 180

Smart on Screen Filtering - - - - - - - - - - - - - - - - - - - - - - - - 181

Save Display Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 182

Timing Analysis Display - - - - - - - - - - - - - - - - - - - - - - - - - 183

Set Timing Display Viewing Options - - - - - - - - - - - - - - - - - - 184

View Timing Details - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 184

Using the Cursors and Bookmarks - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 186

Search - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 189

Display Configuration- - - - - - - - - - - - - - - - - - - - - - - - - - - 194

Mnemonics - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 197

Utilities - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 198

Self Test - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 198

View Scan Descriptors - - - - - - - - - - - - - - - - - - - - - - - - - - 199

Attach/Detach Device - - - - - - - - - - - - - - - - - - - - - - - - - - 200

Capture Screen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 201

viii

Contents

Appendix A - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 203

Advanced Script Language (ASL) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 203

Document Conventions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 203

Language Elements - - - - - - - - - - - - - - - - - - - - - - - - - - 204

ASL Script Structure - - - - - - - - - - - - - - - - - - - - - - - - - - 206

Protocol Extraction Section - - - - - - - - - - - - - - - - - - - - - - - 208

Protocol Decoding Section - - - - - - - - - - - - - - - - - - - - - - - 214

DefineOptions Block - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 215

ValidRanges Block - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 216

Main Block - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 217

USB Descriptor Section - - - - - - - - - - - - - - - - - - - - - - - - - 227

Descriptor Block - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 228

Functions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 229

Samples - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 232

Script Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 240

Creating the Script - - - - - - - - - - - - - - - - - - - - - - - - - - - 241

China Restriction of Hazardous Substances Table - - - - - - - - - - - - - - - - - 244

Index - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 245

ix

Contents

x

Conquest Versions

Conquest Versions

Conquest M2 versus Conquest

Conquest M2 supersedes all SBAE-30 versions.

Conquest supports a subset of features of Conquest M2.

Conquest does not support the following:

• Device Emulation

• OTG Analysis and Exercising

• Timing Analysis

• VBus Measurement

• Automatic Bus Speed Detection

• Performance Analysis

Common Software

This manual describes the use and operation of all available Conquest
options. In the product that you receive, access to options that were not
included in your purchase are disabled. For feature upgrades and any other
questions, please contact [e-mail].

The following table summarizes the supported features of Conquest M2 and
Conquest.

1

Conquest Versions

Conquest M2 (SBAE30) and Conquest Supported Features

Conquest M2

Feature

Standard

Low Speed (1.5 Mb/s) and Full Speed (12 Mb/s) ++++
High Speed (480 Mb/s) ++++
Trace Memory Size 128 MB 128 MB 394 MB 394 MB
Upload to Host via USB 2.0 or LAN ++++
Global & Raw Bit View ++++
View Hex, Decimal or Binary ++++
Search on Errors ++++
Search within Data Payload ++++
Export Text / ASCII / Binary ++++
Snapshot Capture ++++
Data Report ++++
Upper-level USB Device Class Decodes ++++
User-defined Decodes ++++
Single-level Event Triggering (Easy mode) ++++
Trigger on Protocol Errors ++++
Trigger on Setup / In / Out / Data / Ping ++++
Statistical Reports +++
Multi-level Event Triggering (Advanced mode) +++
Trigger on Split Setup Transaction +++
Trigger on Split Bulk In/Out Transaction +++
Trigger on Split Interrupt In/Out Transaction +++
Trigger on Split Isoch In/Out Transaction +++
Filter In / Out specific Address / Endpoints +++
Trigger on Data Pattern and Length ++
Trigger on Vbus & Operating Current ++
Event Counters ++
Event Timers ++
Auto Run (multiple trace capture) ++
Auto detect Speed ++
Slow-clock Capability ++
Performance Analyzer (Easy \ Advanced Option) ++
OTG Analysis ++
Timing Analysis Display ++
DC Compliance measurement ++
Find Device (View Scan descriptor) +
Exerciser Graphical User Interface (GUI) +
Traffic Generation / Host emulation +
Simultaneous Transmit and Record +
Device emulation +
OTG Device Emulation +

Advanced

Pro

Pro

Exerciser

2

Introduction

Introduction

This manual describes the installation and operation of the
LeCroy Conquest™ and Conquest M2 USB Analyzer/Exerciser. Conquest
has a subset of features of Conquest M2 (see “Conquest Versions” on
page 1).

Conquest – The Conquest is LeCroy’s entry-level USB analyzer, designed
for easy setup with time-saving features like predefined trigger settings. The
Conquest Advanced adds multi-state sequential triggering to provide
sophisticated triggering debugging intermittent problems.

Conquest M2 – The Conquest M2 Pro combines full function analysis
capabilities with an integrated exerciser option. The Pro model includes the
same easy-to-understand display of bus traffic and adds advanced multi-state
triggering, OTG support, real-time performance analysis, special timing and
DC Compliance measurements. The exerciser can be enabled via software
key to allow host, device, and OTG emulation.

Overview

Conquest M2 is a serial bus Analyzer/Exerciser that is capable of analyzing
and exercising data transfers for USB 1.x and USB 2.0 Low speed, Full speed,
and High speed protocols. One upstream and one downstream auxiliary
connector allows convenient testing of Hub input and output I/O ports. The
following is a description of Conquest M2 capabilities if all options are
installed.

Conquest M2 incorporates two modes of operation, Easy and Advanced. You
can operate each of the installed options, except the OTG Exerciser, in any
mode combination. As an example, you can perform a Capture and Trigger
with either the Easy Mode Exerciser or the Advanced Mode Exerciser.

The convenient, easy-to-use Easy Mode allows you to perform 95% of USB
data capture and triggering with a minimum of programming. In the Easy
Mode, you can quickly:

• Capture and Trigger on USB packets.

• Generate Host traffic with the Host Exerciser while monitoring and

• Analyze and Exercise OTG Devices.

• Perform a real time Performance Analysis.

• Perform simultaneous Protocol and Timing Analysis.

analyzing the result.

3

Introduction

USB Host

Host Interface Cables

Windows Based System
With Analyzer Software

100V - 240V In

USB Device

Under Test

The comprehensive Advanced Mode incorporates a powerful easy to use
programming capability that allows you to design projects with sophisticated
data capture and triggering. In the Advanced Mode, you can program the
Analyzer/Exerciser to:

• Capture all bus traffic or specific packets

• Trigger on specific packets or events as programmed in a 32 state
sequencer.

• Generate more flexible host traffic with the Host Exerciser.

• Emulate more complicated devices while monitoring and analyzing the
result.

• Analyze and Exercise OTG Devices.

• Perform a detailed Timing Analysis to trigger as defined in the Sequencer
or on a user-specified bus signal pattern.

• Program Conquest M2 as a Device Emulation for testing the USB
development software.

•Perform Unconfigured, Suspend, Operating, and Inrush current
measurements.

• Perform VBus and VBus Droop measurements.

• Trigger protocol analyzer based on VBus and Operating current
measurements.

Analyzing USB Designs With the Analyzer

The Analyzer allows you to perform comprehensive USB analysis by capturing
data and triggering on events and packets, conduct Performance Analysis in
real-time, capture and trigger on USB errors and also to allow verification and
debug of Hub input and output ports.

Figure 1 Typical USB Test Setup of Basic Analyzer

4

Introduction

Conquest M2 Options

You can expand Analyzer capability with the following options:

Host Exerciser

The Host Exerciser option allows you to generate bus traffic as a host for
analysis.

Device Emulation

This option allows you to operate Conquest M2 as a Device for testing the
USB development system. You can define each Device to include up to 3
configurations with 2 interfaces each and assign up to 7 endpoints to these
interfaces. The Device can be a Low, Full, High, or a High/Full speed device.

OTG Exerciser

This option allows you to operate Conquest M2 as an OTG Dual-Role Device.
In this mode, Conquest M2 is a combination of Device Emulation and
Host Exerciser. A DRD emulation can be either a host or a peripheral.

DC Compliance measurement

This option allows you to measure operational current and inrush current
through a special port over the first 10 milliseconds of Device activation and to
display a pass/fail result with respect to the USB compliance specifications.
This option also allows the measurement of VBus voltage through the
Analyzer port.

Timing Analyzer

This option offers precision timing analysis. The Conquest M2 Timing Analyzer
samples bus signals at different sampling rates depending on the bus speed
selected.

5

Conquest M2 Interface

Status LED Function Description

PWR When illuminated indicates that Analyzer is powered up.

TRG When illuminated indicates that the Analyzer has triggered.

Manual Trigger

Manual trigger is activated by a push button switch on the front panel.

External Signals (Ext. Out, Ext. Trig In, and Ext. Clk)

The Conquest M2 Analyzer can output a unique 8-bit, user-defined CMOS
level when triggered. You can use these outputs for activating external
devices, such as other types of test equipment, when certain events are
detected in USB data capture.

Introduction

Additionally, the Conquest M2 Analyzer provides you with an External Trigger
Input that allows you to trigger the Analyzer from externally generated
sources. Trigger input can be masked or programmed to respond to a 1 or 0
level or a rising or falling edge. For setting the external trigger input options,
see page 51.

Conquest M2 offers a number of internally generated pre-defined low
frequency clock settings, however you can apply an external clock to the
External Clock Input. Supported frequencies are in ranges of 400KHz - 8MHz
for High Speed and 1KHz-100KHz, 400KHz - 8MHz for Full/Low speed.

6

Introduction

Ports

Main Analyzer

This port supports Analyzer using 8 packets and a 32 state sequencer that are
used in Easy Mode or Advanced Mode for data capturing and triggering,
operating and unconfigured current measurement and timing analysis.

InRush

A dedicated connector to allow the measurement of USB Device Inrush
current.

Host Exerciser

A dedicated connector to exercise a USB Device and capture and trigger data
in conjunction with the Analyzer port.

OTG Exerciser

A dedicated connector to exercise an OTG Dual-Role or SRP- capable
Peripheral Device.

Note: Use only one, either Parallel Port or USB connection, for connecting the

Power In

Device Emulation

A dedicated connector used when Conquest M2 is operated as a device.

Paral. Host Interface

Bi-directional Parallel Port interface located on the back of the unit for
connection between the Analyzer and the system hosting the GUI software.

USB Host Interface

Interface connection, located on the back of the unit, for connection between
the Analyzer and the system hosting the GUI software.

Analyzer and the system software.

Conquest and Conquest M2 operate on 100V - 240V 50/60Hz power that is
connected on the back.

7

Analyzer/Exerciser Connection Identification

External Signals (See Note 1.)

USB 2.0/1.x Analyzer Connectors

Inrush/Suspend Current Measurement Connector

Host Exerciser Connector

Manual Trigger Button

Status LEDs

OTG Exerciser Connector

External Clock

Device Emulation

Input

Connector

Introduction

Note 1 For External I/O connector pin assignment, see page 15.

8

Receiving the Analyzer

Receiving the Analyzer

Conquest M2

The Conquest M2 Analyzer includes the following components:

• Carrying Case

• Conquest M2 identified in the packing list

• Software on the CD Rom

• DB-25 -> SCSI II 26, Parallel Port connection

• Two USB 2.0 Cables, 1.8 meter

• USB 2.0 Cable, 4” (10 cm)

• Two USB 2.0 Cables, 2 meter Standard - A to Mini - B

• One Mini - A to Standard - B.

• 3M Ethernet Cable

• External I/O Ribbon and External Clock SMB to BNC Cables

• Current Measurements Calibration Board

• Power cable

• User Manual (PDF version on CD only) for both Conquest and

Conquest M2

Conquest

The Conquest Analyzer includes the following components

• Carrying Case

• Conquest identified in the packing list

• Software on the CD Rom

• Two USB host interface cables, 1.8 M A to Mini - B

• USB, A to B cable, 4” (10cm)

• 3M Ethernet Cable 10ft (3M)

• External trigger cable (SMB2BNC)

• External signals cable

• Power cable, 6ft (1.8M)

• User Manual

Unpacking the Analyzer

Inspect the received shipping container for any damage. Unpack the container
and account for each of the system components listed on the accompanying
packing list. Visually inspect each component for absence of damage. In the
event of damage notify the shipper and LeCroy. Retain all shipping materials
for shippers inspection.

9

Installing the Analyzer

USB Host

Host Interface Cables

Windows Based System
With Analyzer Software

100V - 240V In

USB Device

Under Test

This section covers hardware and software setup.

Hardware Setup

You can set up the Analyzer/Exerciser in any of the following configurations:

• As an Analyzer to analyze USB Host and Device transactions.

• As an Exerciser to exercise a USB Device.

• As an Analyzer/Exerciser for OTG Device testing.

• As an Analyzer/Exerciser in Hub testing.

• To measure Inrush current, Configured current, Unconfigured current,
Suspended current and VBus measurement

• As a Device for Host software testing.

Separate Systems

It is highly recommended that you employ separate systems for the Analyzer
software and the USB Host as shown in Figure 2 (the preferred configuration)
to analyze USB Host and Device transactions. Using just one system for both
functions can lead to confusing results because of shared bus traffic.

Installing the Analyzer

Figure 2 Conquest M2 Configured as an Analyzer

1. Connect Conquest M2 to a Parallel, USB, or Ethernet Port on a system
running the Conquest Protocol Suite software, with the appropriate
cable.

2. Connect the USB Device to the Main Analyzer Port on Conquest M2.

3. Connect the USB Host to the Main Analyzer Port on Conquest M2, using
a USB cable.

10

Installing the Analyzer

Host Interface Cables

Windows Based System
With Analyzer Software

100V - 240V In

USB Device

Exercised

Host Interface Cables

Windows Based System
With Analyzer Software

100V - 240V In

OTG B-Device

OTG A-Device

OTG Std-A to Mini-B Cable

OTG Mini-A to Std-B Cable

Exerciser Configuration Connections

Figure 3 shows Conquest M2 used to exercise a USB Device. In this
configuration, Conquest M2 acts as the USB Host.

Figure 3 Conquest M2 Configured as an Exerciser

1. Connect Conquest M2 to a Parallel, USB, or Ethernet Port on a system

running the Conquest Protocol Suite analysis software, with the
appropriate cable.

2. Connect the USB Device to the Main Analyzer Port on Conquest M2.

3. Connect the Main Analyzer Port to the Host Exerciser Port using a USB

cable.

OTG Analysis Connections

Figure 4 Conquest M2 Connections for OTG Analysis

11

OTG Exerciser as DRD A-Device Connections

Host Interface Cables

Windows Based System
With Analyzer Software

100V - 240V In

OTG B-Device

OTG -A to CableMini Standard-B

DUT

Host Interface Cables

Windows Based System
With Analyzer Software

100V - 240V In

OTG A-Device

OTG -A to -B CableStandard Mini

DUT

Installing the Analyzer

OTG Exerciser as DRD or Peripheral Only B-Device Connections

Figure 5 OTG Exerciser as DRD A-Device

Figure 6 OTG Exerciser as DRD or Peripheral Only B-Device

12

Installing the Analyzer

Host Interface Cables

Windows Based System
With Analyzer Software

100V - 240V In

System

Exercised

Device Emulation Connections

Figure 7 Conquest M2 Connections for Device Emulation

13

Conquest Analyzer Connections

Host Interface Cables

Windows Based System
With Analyzer Software

100V - 240V In

USB Host

USB Device

Under Test

Host Interface Cables

Windows Based System
With Analyzer Software

100V - 240V In

DUT

Installing the Analyzer

Conquest Exerciser Connections

Figure 8 Conquest Connected as an Analyzer

Figure 9 Conquest Connected as an Exerciser

Note: The Exerciser option is no longer available on the Conquest platform.

Exerciser is offered on the Conquest M2 system only.

14

Installing the Analyzer

Conquest M2 External I/O Connector Pin Assignment

The external I/O connector provides the means for accepting a CMOS level
input trigger and 8 CMOS level outputs that represent an 8-bit value.

Table 1 External I/O Connector Pin Assignment

Signal Pin Color Signal Pin Color

External Trigger In 1 Brown External Out 7 2 Red
GND 3 Orange External Out 6 4 Yellow
GND 5 Green External Out 5 6 Blue
GND 7 Violet External Out 4 8 Grey
GND 9 White External Out 3 10 Black
GND 11 Grey External Out 2 12 Red
GND 13 Orange External Out 1 14 Yellow
GND 15 Green External Out 0 16 Blue

Conquest External I/O Connector Pin Assignment

Table 2 External I/O Connector Pin Assignment

Signal Pin Color Signal Pin Color

No connect 1 Brown No connect 2 Red
GND 3 Orange External out 7 4 Yellow
GND 5 Green External out 6 6 Blue
GND 2 7 Violet External out 5 8 Gray
GND 9 White External out 4 10 Black
GND 11 Brown External out 3 12 Red
GND 13 Orange External out 2 14 Yellow
GND 15 Green External out 1 16 Blue

External out 0 N/A

Note 1 Pin 1 is the right-most in the cable (Brown) and pin 16 is the left-most in the

cable (Blue).

Note 2 The signal “External out 0” (LSB) is not externally available.

15

Software Installation

On systems operating under Windows® 2000, Windows XP, and
Windows Vista.

Note: Do not connect the Analyzer to the host system until software

installation is complete!

1. Insert the CD Rom in the CD Rom drive.

2. The installation automatically starts the setup, unless the Auto Run is
turned off. In this case, select the CD Rom from “My Computer” and click
setup.

3. After the warning to close all other programs and before starting the
installation, the Install component selection opens.

4. Select components for installation.

Installing the Analyzer

System Restart

Error Message

5. Click N

You must restart the computer before you can use the Analyzer software.

If you get an error message during installation of the drivers for Windows
2000, XP, or Vista, consult your system administrator. Your system may allow
only an administrator-level user to copy driver files.

ext to complete the installation.

16

Installing the Analyzer

Manual USB Driver Installation

To manually install the USB driver, perform the following:

1. Power up Conquest.

2. Connect the USB cable between the Conquest USB Port interface and

the Host Computer USB port.

3. After Windows detects the new Device, select the Search For Suitable

Driver for My Device option button.

4. Click Next.

5. Choose the Specific location option button and deselect all other option

buttons.

• Click Next.

• Go to the C:\program files\LeCroy\Conquest\usb driver\win2k
folder.

• Choose Ibusb.inf.

• Click OK.

6. Click Next and then Finish to complete the Conquest USB port driver
installation.

Updating the Conquest USB Driver Manually

1. Click S
Device Manager tab.

2. Find the Test To ols entry.

3. Select and right-click the Conquest board.

4. Select Properties and click the drivers tab.

5. Click Update Driver.

6. Select recommended method

7. Choose the Specific location option button and deselect all other option
buttons.

• Click Next.

• Go to the C:\program files\LeCroy\Conquest\usb driver\win2k

• Choose Ibusb.inf

• Click OK.

8. Click Next and then Finish to complete the USB driver update.

tart > Settings > Control Panel > System and click the

folder.

17

Directory Structure on Windows XP and Vista

The Conquest Protocol Suite application stores files in a specific directory
structure under the C:\Program Files\LeCroy\Conquest directory. It also

stores files in Windows-specific locations that differ for Windows
Windows Vista (which uses UAC).

In particular, Windows XP has a Documents and Settings\All Users folder,
and Windows Vista has a Users\Public folder, which are not equivalent.

The Windows XP All Users folder is not readily available to users and is for
storing shared files, to which normal user folders point using shortcuts.

The Windows Vista Users\Public folder and its subdirectories:

• Are available to all users logged onto a system (not just the person who
installed the application).

• Are not hidden.

• Are always present, because it is provided by the Windows Vista OS
installation.

• Are readable and writable by all users.

• Do not require Administrator privileges.

Methods of using shared folders differ for the two operating systems, so the
Conquest Protocol Suite application stores files on them differently, as
described in the next two sections.

Installing the Analyzer

®

XP and

Windows XP

For Conquest Protocol Suite on Windows XP, all application and user files
(such as sample files, user files, default files, and scripts) are in the
<drive>\Program Files\LeCroy\Conquest directory folder and its
subdirectories:

•Doc

• CAPI

•SystemData

•UserData

•Examples

The installation process creates the folder
<drive>\Program Files\Lecroy\Conquest.

Running the application the first time creates the folder

<drive>\Users\Public\Public Documents\LeCroy\Conquest 7.40.xx

18

Installing the Analyzer

Windows Vista

User-modifiable Files

For Conquest Protocol Suite on Windows Vista, user-modifiable files are in the
Windows Explorer
<drive>\Users\Public\Public Documents\LeCroy\Conquest 7.40.xx folder,
which is the same as the Command Tool
<drive>\Users\Public\Public Documents\LeCroy\Conquest 7.40.xx folder
and Desktop\Public Documents\LeCroy\Conquest 7.40.xx folder.

The Command Tool name is the correct folder name when using scripts.

The Users\Public\Public Documents\LeCroy\Conquest 7.40.xx\UserData
folder contains files that the user can modify, such as new.cpr and Out.smp.
It also has the directories:

•SystemData

•Temp

•UserData

Application Files

For Conquest Protocol Suite on Windows Vista, read-only application files
(such as the application, bus engine, firmware, user manual, help, and read­me files) are in the <drive>\Program Files\LeCroy\Conquest folder, which
has the directories:

• CAPI

•Doc

•Examples

•SystemData

• usb driver

•UserData

Note On Windows Vista systems, the Conquest Protocol Suite application creates

an image of its directories in

Public\Public Documents\LeCroy\Conquest 7.40.xx.

Note 2 For Windows Vista systems, the Conquest Protocol Suite application creates

directories for Conquest when the application is first run, not when it is
installed.

19

Launching the USB Analyzer

Open sample file

Open last saved project

Default data blocks

Mnemonics

Protocol error mask

Default capture

Set up project

Launching the USB Analyzer

To launch the software, select LeCroy > Conquest in the Start menu or
double-click the Conquest Suite button in the Program Manager Window.

Each time you run the software, it searches for a default host interface and, if it
is found, the software launches. If no interface is found, the software launches
in simulation mode.

Establish Interface

If no interface is detected initially, then establish an available interface and
relaunch the software.

Click OK. The Analyzer launches and displays the Analyzer toolbar as shown
below.

Note: The very first time that you run the software, the USB Class Decodes loads.

This process takes approximately one minute.

20