User`s manual

A
t least 20MB of free hard disk space is required for the installation. Additional disk space is needed for the
operation of the applications and for storing the recorded data in files during the recordings process (can be as
much as 150MB when recording a full buffer size).
Display:
Resolution of at least 1024 x 768 with at least 16-bit color depth is recommended (resolution of 800 × 600 with
16-bit color is a minimum).
Connectivity:
A
PCMCIA slot is required to connect to the USBMobileHS™ analyzer card. This is not a requirement if the
application is going to be used only as a viewer
3. Release Notes
3.1. What’s New
• This is version 2.32 of the USBMobileHS ™ protocol analyzer.
•
This release contains the following components, which are necessary for the operation of the product:
o
USB MobileHS™ Application Version 2. 32.
o
USB MobileHS™ Bus Engine Version 1.03.
•
This release includes the following updates:
o
The following USB Class decoding is now supported:

Video Class 1.1

Communications Data Interface Class

Cable Based Association Framework (WUSB implementation)

Smart-Card Class (CCID + ICCD)

RNDIS
•
This release includes the following fixes:
{ wChannelConfig standard audio descriptor incorrect decoding in description [362]
{ iTerminal text for standard audio descriptor says input when it is an output terminal [363]
{ HID report descriptor parser incorrectly decodes 32-bit tags [605]
3.2. Known Issues
• Errors may appear in the last couple of packets of a recording, which are not real errors. They are a side
effect of the recording terminated during the middle of a packet. Also, the first packet in a trace may be a
partial one.
•
Installation requires the existence of command.com file, which is not present on a fresh install of Windows
2000.
•
Upon plug-in or unplug, it is possible to see K and J signals that may not reflect the real bus conditions, but
are a side-effect of the circuitry of the analyzer probe. These should be ignored.
•
In order to use Automation, you must first launch UsbMobileHS.exe on the server, then connect from the
client.
•
According to the MTP Specification Revision 0.83 by Microsoft Corp., NumberOfInterdependencies and
NumberOfPropDescs in InterdependentPropDescDataset are UINT16 value with size of 2 bytes. However,
we have encountered some products on the market that are using UINT32 instead, which could mess up the
whole InterdependentPropDesc Dataset decoding. If you have decoding problems with the
GetInterdependentPropDesc operation, set the variable ‘InterdependentPropDescDatasetSizeBytes’ equal to
4 in the \Scripts\StillImageClass\PTPUserEditParams.inc script file.
[275]
•
For PTP Transactions that would decode into a very large number of fields, the script decoding will
automatically stop creating display fields after a user-configurable amount of fields have been processed. By
default, once this limit has been reached, the script decoding will also stop processing the rest of the data,
meaning it will not discover any more errors that might occur deeper in the data. You can configure these
behaviors by changing the variables ‘MAX_CELLS_TO_DISPLAY’ and
‘IF_CONTINUE_ON_PROCESSING_DATA’ in the \Scripts\StillImageClass\PTPUserEditParams.inc script
file.
•
When invoking the View Decoded Fields dialog for a large PTP Transaction, the application may appear to
hang and become unresponsive while it processes the data. Once the application finishes processing the
Page 2 of 7USBMobileHS™ Release Notes
5/7/2007file://C:\Pro
g
ram Files\LeCro
y
\USBMobileHS\USBMobileHS
_
ReadMe.htm