Asset ID:	1-71-1386626.1
Update Date:	2011-12-28
Keywords:

---

Solution Type  Technical Instruction Sure

Solution  1386626.1 :   Decoding DIMM fruid data collected by snapshot  

In this Document
  Goal
  Solution

---

Oracle Confidential (PARTNER). Do not distribute to customers
Reason: Intended for internal support personnel only

Applies to:

Sun SPARC Enterprise T5440 Server - Version: Not Applicable to Not Applicable - Release: N/A to N/A
Sun SPARC Enterprise T5240 Server - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun SPARC Enterprise T5220 Server - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun SPARC Enterprise T5140 Server - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun SPARC Enterprise T5120 Server - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Information in this document applies to any platform.

Goal

Convert FRUID data files into a hex dump format ready for decoding

Solution

snapshot data collected from the ILOM includes fruid information in data format for each installed component including MB, SASBP, PSUs, physical memory - and for DIMMs this data is the raw Serial Presence Detect programming which can be useful when diagnosing certain types of compatibility orientated events such as link training and channel initialisation issues.

All .dat FRUID output can be found in the fruid directory within the snapshot.

Refer to the XML file for mapping the .dat files to each component, for example;

bash-3.00 # grep /SYS/MB/CMP0/BR0/CH0/D0 @persist@[email protected]
<Container name="/SYS/MB/CMP0/BR0/CH0/D0" imagefile="fru3.dat">
</Container> <!-- /SYS/MB/CMP0/BR0/CH0/D0 -->
bash-3.00 #

bash-3.00 # file @persist@[email protected]
persist@[email protected]: data
bash-3.00 #

Convert the .dat file into a hex dump using od;

bash-3.00 # od -Ax -vtx1 @persist@[email protected]
0000000 92 12 09 12 49 23 07 10 51 01 04 0c 20 33 3c 42
0000010 3c 82 60 3c 1e 3c 00 b4 dc fe 01 1e 1e 03 07 01
0000020 c2 51 31 04 0f 0a 0b 18 12 15 00 00 00 00 00 00
0000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 22
0000050 00 02 00 10 36 34 32 2a 62 77 61 9f 84 00 00 00
0000060 00 00 1f 0a 00 00 e2 62 20 80 9c 00 00 f0 70 60
0000070 60 60 60 7f b3 80 2c 0c 09 21 d6 3d 79 b1 b5 6e
0000080 35 30 31 2d 37 39 35 34 2d 30 31 20 52 65 76 20
0000090 35 31 45 31 80 2c 00 00 ff ff ff ff ff ff ff ff
00000a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000b0 20 05 01 79 54 01 05 00 00 02 01 00 05 00 00 00
00000c0 00 00 00 00 00 00 00 00 00 00 00 4e e6 19 01 00
00000d0 21 28 8f 1b 44 00 00 00 00 00 00 00 00 00 00 00
00000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000f0 00 00 00 00 00 00 00 00 4e e6 28 53 00 00 00 1a
0000100
bash-3.00 #

This provides the byte values that can then be referenced against the address map for this module type - in this example the dump is from a FBDIMM.

So for example;

byte 1 is the SPD revision = 0x12.
byte 122-125 is the module serial number = d63d79b1

The specifications for each module type can be found on www.jedec.org and include further details on each of the byte fields and how to decode them further. The specification for each module type is covered in a separate annex - please refer to document JESD21-C.

For example bytes 84-86 determine the access time delays set for northbound and southbound transactions to the AMB on each module.

Here is the converted .dat from a DDR3 module installed in a T3-1 system;

0000000 92 10 0b 01 02 11 00 09 0b 52 01 08 0c 00 3c 00
0000010 69 78 69 30 69 11 20 89 70 03 3c 3c 00 f0 83 01
0000020 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000030 00 00 00 00 00 00 00 00 00 00 00 00 0f 11 01 05
0000040 00 80 b3 61 00 00 50 00 00 00 00 00 00 00 00 00
0000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000070 00 00 00 00 00 80 ce 01 10 06 06 03 8e 06 63 54
0000080 4d 33 39 33 42 35 36 37 33 46 48 30 2d 43 48 39
0000090 20 20 00 00 80 ce 00 00 00 31 45 30 30 44 30 31
00000a0 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08
00000b0 20 05 11 16 15 01 01 00 00 00 ec 00 03 da a1 4f
00000c0 59 8f ad 30 b4 a6 64 3b 9e 82 64 4c b1 03 62 00
00000d0 21 28 a6 58 5e 00 00 00 00 00 00 00 00 00 00 00
00000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000f0 00 00 00 00 00 00 00 00 4e e8 80 e1 00 07 22 92
0000100

This information is most useful when dealing with potential compatibility issues where you need to compare operational parameters from multiple DIMMs.

Certain bytes will differ between modules of the same part number, such as manufacturing location (byte 119), manufacturing date (byte 120-121), serial number (byte 122-125). However the remaining bytes will typically be programmed the same, differences would need to be investigated further.

Attachments

This solution has no attachment