Hitachi 7K320 Specifications - Page 114

Phy Event Counter

Page 114 highlights

7K320 (SATA) OEM Specification The Data Structure Checksum (Byte 511) contains the 2's complement of the sum of the first 511 bytes in the data structure. The sum of all 512 bytes of the data structure will be zero when the checksum is correct. 14.17.5 Phy Event Counter Phy Event Counters are a feature to obtain more information about Phy level events that occur on the interface. The counter values are not retained across power cycles. The counter values are preserved across COMRESET and software resets. 14.17.5.1 Counter Reset Mechanisms There are 2 mechanisms by which the host can explicitly cause the Phy counters to be reset. The first mechanism is to issue a BIST Activate FIS to the drive. The second mechanism uses the Read Log Ext command. When the drive receives a Read Log Ext command for log page 11h and bit 0 in Feature register is set to one, the drive returns the current counter values for the command and then resets all Phy event counter values. 14.17.5.2 Counter Identifiers Each counter begins with a 16-bit identifier. The following table defines the counter value for each identifier. For all counter descriptions, "transmitted" refers to items sent by the drive to the host and "received" refers to items received by the drive from the host. Bits 14:12 of the counter identifier convey the number of significant bits that counter uses. All counter values consumes a multiple of 16-bits. The valid values for bit 14:12 and the corresponding counter size are: 1h 16-bit counter 2h 32-bit counter 3h 48-bit counter 4h 64-bit counter Identifier Description (Bits 11:0) 000h No counter value; marks end of counters in the page 001h Command failed due to ICRC error 009h Transfer from drive PhyRdy to drive PhyNRdy 00Ah Signature D2H register FISes sent due to a COMRESET 00Bh CRC errors within the FIS (received) 00Dh Non-CRC errors within the FIS (received) Table 83 Phy Event Counter Identifier 14.17.5.3 Read Log Ext Log Page 11h The following table defines the format of the Phy Event counter data structure. Page 114 of 176

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176

7K320 (SATA) OEM Specification
Page 114 of 176
anisms
ntifiers
The Data Structure Checksum (Byte 511) contains the 2’s complement of the sum of the first 511
bytes in the data structure.
The sum of all 512 bytes of the data structure will be zero when the
checksum is correct.
14.17.5
Phy Event Counter
Phy Event Counters are a feature to obtain more information about Phy level events that occur on
the interface. The counter values are not retained across power cycles. The counter values are
preserved across COMRESET and software resets.
14.17.5.1
Counter Reset Mech
There are 2 mechanisms by which the host can explicitly cause the Phy counters to be reset. The
first mechanism is to issue a BIST Activate FIS to the drive. The second mechanism uses the Read
Log Ext command. When the drive receives a Read Log Ext command for log page 11h and bit 0 in
Feature register is set to one, the drive returns the current counter values for the command and then
resets all Phy event counter values.
14.17.5.2
Counter Ide
Each counter begins with a 16-bit identifier.
The following table defines the counter value for each
identifier.
For all counter descriptions, “transmitted” refers to items sent by the drive to the host and “received”
refers to items received by the drive from the host.
Bits 14:12 of the counter identifier convey the number of significant bits that counter uses. All
counter values consumes a multiple of 16-bits. The valid values for bit 14:12 and the corresponding
counter size are:
1h
16-bit counter
2h
32-bit counter
3h
48-bit counter
4h
64-bit counter
Identifier
(Bits 11:0)
Description
000h
No counter value; marks end of counters in the page
001h
Command failed due to ICRC error
009h
Transfer from drive PhyRdy to drive PhyNRdy
00Ah
Signature D2H register FISes sent due to a COMRESET
00Bh
CRC errors within the FIS (received)
00Dh
Non-CRC errors within the FIS (received)
Table 83 Phy Event Counter Identifier
14.17.5.3
Read Log Ext Log Page 11h
The following table defines the format of
the Phy Event counter data structure
.