|
|
|
| Ref.: |
|
| ||
|
|
| SpaceWire Router |
| UserManual |
|
| |
|
|
| Issue: | 3.4 |
|
|
| |
|
|
| User Manual |
|
|
| ||
|
|
| Date: | 11th July 2008 |
| |||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
Protocol | The RMAP protocol identifier value 01h. |
|
|
| 1 |
| ||
Identifier |
|
|
|
|
|
|
| |
|
|
|
|
| ||||
Command | Read single address reply command byte. The packet type bits in the |
| 1 |
| ||||
Byte | command byte indicate this packet is a response packet. |
|
|
|
|
| ||
|
|
|
|
| ||||
Status | The command status is returned in this field. The command status can be |
| 1 |
| ||||
|
| command successful or an RMAP error code as defined in section 7.6.6. |
|
|
| |||
|
|
|
|
|
| |||
Destination | The destination logical address is set to the default value FEh as the |
|
| 1 |
| |||
logical | SpaceWire router does not have a logical address. |
|
|
|
|
| ||
address |
|
|
|
|
|
|
| |
|
|
|
|
| ||||
Transaction | The transaction identifier identifies the command packet and reply packet with a |
| 2 |
| ||||
Identifier | unique number. The transaction identifier in the reply packet is copied from the |
|
|
| ||||
|
| command packet and returned in this field, so that the command and the |
|
|
| |||
|
| corresponding reply have the same transaction identifier value. |
|
|
|
| ||
|
|
|
|
| ||||
Data | The data length field is set to 4 bytes as this is a single read command. |
| 3 |
| ||||
Length |
|
|
|
|
|
|
| |
|
|
|
|
| ||||
Header | The header CRC used to detect errors in the header part of the command |
| 1 |
| ||||
CRC | packet. See section 7.6.7 for CRC generation. |
|
|
|
|
| ||
|
|
|
|
|
|
| ||
Data | The data read from the registers in the device. |
|
|
| 4 |
| ||
|
|
|
|
| ||||
Data CRC | The data CRC used to detect errors in the data part of the reply packet. See |
| 1 |
| ||||
|
| section 7.6.7 for CRC generation. |
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
7.6.3 Read Incrementing Command
The read incrementing address characteristics of the SpaceWire router are defined in Table
Preliminary | 60 |