Users Manual Instruction Manual

CATC FIREINSPECTOR 2.01 CHAPTER 1

User’s Manual FireInspector Overview

• Acknowledge packets

• Transaction codes: cycle start, data quadlet read request, data block read request, data

quadlet read response, data block read response, data quadlet write request, data block

write request, write response, lock request, lock response, isochronous (stream) data

packet, and asynchronous stream packet

• Packet header contents (first four quadlets)

• Data block pattern (first two quadlets)

• Hardware-detected errors: bad PHY packet complement, bad header or data CRC, and

bad acknowledge parity

• External (user-supplied) signals

1.6 Features of FireInspector

• Sophisticated software analyzes all bus transactions

• Identifies & highlights abnormal bus conditions

• Decodes standard CSR accesses and other encapsulated protocols

• 128 MB of physical data recording memory nets 64 MB of raw 1394 traffic

• Programmable real-time event triggering and traffic capture filtering

• CATC Trace graphical presentation of captured data with extensive customization

options

• Graphical display of bus topology

• Adjustable recording size

• Adjustable pre-/post-trigger position

• Comprehensive search functions

• Accurate timestamping of bus packets

• Field upgradeable firmware and BusEngine™

• Software operates as a stand-alone Trace viewer

• Connects to the host computer through a USB port

• One-year warranty and hotline customer support

1.7 System Requirements

The following is the recommended configuration for the host machine that runs the

FireInspector Analyzer application and is connected to the FireInspector Analyzer box.

• Operating system: Microsoft® Windows® 98 SE, Windows 2000, Windows Me, or

Windows XP operating system. The FireInspector application can be used on machines

with a Windows NT® 4.0 operating system to view Trace files; however, in order to