In fact there are other errors:
- The scramble XORing is performed incorrectly on the first dword. It should be C3D2768Dh not D2D2768Dh
- The scrambler value for the crc slot should be 3D2D7984h not 9AFCB3DDh
 
The corrected table is below:

Data

dword

number

 

SSP frame contents

SMP frame contents

Desired

pattern

(ON THE WIRE)

Scrambler

output

 

Scrambled

pattern

 

Not

applicable

SOF

SOF

Not applicable

SOF

0

FRAME TYPE field set

to 01h (i.e., DATA

frame) and 23

subsequent bytes

each set to 00h

 

SMP FRAME TYPE field

set to 01h (i.e.,

reserved) and 23

subsequent

frame-type dependent

bytes each set to 00h

 

C3D2768Dh

C2D2768Dh

01000000h

1

1F26B368h

1F26B368h

00000000h

2

A508436Ch

A508436Ch

00000000h

3

3452D354h

3452D354h

00000000h

4

8A559502h

8A559502h

00000000h

5

BB1ABE1Bh

BB1ABE1Bh

00000000h

6

 

INFORMATION UNIT field

Frame-type

dependent bytes

See the INFORMATION UNIT field in table A.4

117

 

118

CRC field

79C211AAh

 3D2D7984h

44EF682Eh

Not

applicable

EOF

EOF

Not applicable

EOF

 
 
Thanks
 
Tamer Kafafi
Senior Product Design Engineer, ESD
PMC-Sierra

From: owner-t10@t10.org [mailto:owner-t10@t10.org] On Behalf Of Tamer Kafafi
Sent: Tuesday, July 24, 2007 4:31 PM
To: 't10@t10.org'
Subject: SAS2 CJTPAT with SSP header

Robert,
Regarding the proposal 07-297r1 , Table A.6 - CJTPAT with fixed content -  is incorrect.

The columns "desired pattern" and "scrambled pattern" should be interchanged for rows 1 to 6. The "desired pattern" column represents what should be on the wire, while the "scrambled pattern" column represents what the application/transport layer sees. Obviously the newly added SSP header should be visible at the application/transport layer not on the wire.

Also, as a result, the CRC values in row 118 will be completely different.


Thanks

Tamer Kafafi
Senior Product Design Engineer, ESD
PMC-Sierra