DAP Technology 1394, Руководство по эксплуатации

Страница: 110 / 458

Recorder
110 Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019
Another way to specify a node across reset boundaries is to use the EUI64 of that node. This value will
(normally) be present in the Configuration ROM of the device. All EUI64 values for which one or more
reads have been recorded are listed in the 'Found EUI64 values' box somewhere at the top of the dialog.
When selecting such a value and clicking the 'Select/Add' button to the right of it, the Node Specification
for that device will be added if it is not already present. The node IDs for each reset-segment will be filled
in automatically as follows: If during a particular reset segment, the read of the selected EUI64 is
detected, the node ID of that segment will be filled in with the corresponding node ID, and the cell is set to
not editable (gray cell). For all other segments, the value 'none' will be filled in and the cell will not be
editable (gray) if no transactions are recorded at all for that segment (and thus no node ID is needed). For
the segments for which no corresponding EUI64 read was found you can specify a node ID manually
(unless the cell is gray, indicating that no node needs to be specified).
Adding Node specifications semi automatically by Unit
The protocol-analysis software does not only search for EUI64 reads, but also for Configuration-ROM
reads that read information about Units inside the nodes. Each supported protocol can recognize Units
that comply to the corresponding protocol. These Units are listed in the 'Found Units' box. Selecting such
a Unit in this box and clicking the 'Select/Add' button to the right of it, will add the corresponding Node
Specification just as described in 'Adding Node Specifications semi automatically by EUI64'. In addition,
the Unit specification is also added to the 'Units' table below the 'Node Specifications' table.
Using currently connected devices to add Units
If the 'Found Units' box does not contain the Lun you want to add, but the device containing this Unit is
still connected to the Analyzer, you can click the 'Search current' button. This will add all Units of the
currently connected devices to the 'Found Units' box. Clicking the 'Select/Add' button for such a Unit, will
add the correct Unit information, but the correct node IDs for each reset segment can only be found
automatically if the read of the corresponding EUI64 has been recorded for that segment.
Save Settings
The protocol-analysis settings are stored in the recording file. So, if after making a recording you save the
recording to a file, all current protocol settings are stored in that file as well. If you open a recording file
and change any of the protocol-analysis settings, a dialog box will be displayed before the currently
loaded recording will be removed from memory. This allows you to cancel the action and save the
modified recording.
7.6.3.2. Details
The Protocol-Settings dialog consists of two main parts. The Node-Specifications part at the top to specify
nodes across resets (as explained above), and at the bottom, a protocol-specific part for protocol-specific
information (including Unit information). Between these two parts, general options can be selected.
Node Specifications
The 'Node Specifications' part consists of a table with the Node Specifications and some combo boxes
and buttons to help with the creation of new Node Specifications.
Combo box Found Units
The combo box shows the found units of the nodes on the bus.
Combo box Found EUI64 values
The combo box shows the found EUI64 values of the nodes on the bus.
Table Node specification
Each row in the table 'Node specification' relates to a node on the bus. The table shows in column 'spec'
the defined logical ID of a node; it shows in column 'EUI64' the EUI64 value of a node and it shows in the
columns 'reset 0 .. reset n' the node IDs of a node retrieved from the recorded data in Recorder. The node
ID of a node may change after a bus reset. So the node ID is to be known for each reset segment. With
the reset segment that part of a recording is referred to, where the node IDs do not change. Thus, bus
resets are the boundaries of reset segments. All recorded data up to the first bus-reset event (reset 1) is
called reset segment 0. All recorded data up to the next reset (between reset 1 and reset 2) is called reset
segment 1, etc.
Using the checkbox before each Node Specification in the table you can enable or disable each node
individually for analysis. If the box is not checked, all units inside this node will be excluded from analysis
by any protocol.