DAP Technology 1394, Operation Manual

Page: 312 / 458

Serial Bus Protocol (SBP)
312 Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019
skipped.
·
Node Spec.: A Unit is part of a node. As explained before, nodes are specified using Node
Specifications. The number in this column corresponds to the Node-Specification numbers of the table
in the upper part of the dialog.
· Management Agent: This is the offset (in the CSR registers) of the Management-Agent registers. If this
value can not be found automatically, you could try to figure out this value yourself by looking in the
Transactions View of the Recorder and searching for one of the first 8-byte writes to the SBP device.
This could be the write of the Management-agent register to start a login request. Just subtract
0xFFFFF0000000 from the offset written to and use that value as the Management-Agent offset value
in the table.
· ORB size: This is the maximum size of the ORB block in bytes. Normally this is 32.
· Command Set: This defines the command set to be used for the command-set-specific formatting. If
you have to fill it in manually, you can select one of the supported command sets. If you do not know
which command set the SBP device supports, just try one and check for formatting errors after
analyzing. If not all commands could be displayed in command-set-specific format, you probably have
selected the wrong set.
initial Logins
If the login command (and response) are not recorded, you will have to fill in some login information that
normally is obtained by the login command and response of the login command, to be able to analyze
SBP commands. Note that if the login command and responses are recorded properly, no 'initial Logins'
need to be specified. It is called 'initial' logins, because the analyzer uses this information and starts as if a
login command and response were detected with the specified values, before it starts analyzing the
transactions.
The information consists of:
·
Login ID: This is the login ID normally returned by the login response. Its value is only needed for some
Management Agent commands like logout and reconnect. If you do not know the value, use 0. A wrong
value results in not matching the logout or reconnect to the correct login. But after analyzing once, you
will probably see additional logins in the 'relation' pane that lead you to the correct value.
· Requesting Node: This is the node ID of the node that requested the login. This value is needed to
correctly identify accesses to the SBP device. If you do not know the value, try to find a
Command-Agent write transaction (see below) and use the node ID of the requester of that transaction.
Note that it should correspond to the node ID of the SBP device in the first reset segment. After the first
reset, this value is not used anymore, because a new login or reconnect will result in a new value.
·
Command Agent: To be able to detect Command-Agent access (doorbell write, ORB pointer write, etc)
the Command-Agent offset is needed. Normally this value is returned by the login response. If a login is
not recorded, you have to try to find this value yourself.
To find this value, search in the Transaction View of the Recorder for write transactions to the SBP
device, which write to one of the CSR registers of the SBP device. During the SBP protocol the
requesting device probably does write a lot of times to the doorbel register (register offset 0x10 from
start of Command Agent and 4 bytes size) or ORB pointer write register (register offset 0x08 form start
of Command Agent and size of 8 bytes). From these transaction offsets you can calculate the
Command-Agent offset (subtract 0xFFFFF0000000 and the little register offset mentioned above).
·
Status Fifo: The address to which the SBP device should write status information is normally given in
the login command. So to correctly analyze the commands that include status information, while a login
command is not recorded, you should find out this value yourself.
Search in the Transactions View for write transactions of 8 bytes (mostly) to maximal 32 bytes (seldom),
with the SBP device as requester. If you see many of these transactions that write to the same address,