Changeset 1620
- Timestamp:
- 11/18/02 21:42:01 (11 years ago)
- Files:
-
- 1 modified
-
lm-sensors/trunk/doc/chips/eeprom (modified) (8 diffs)
Legend:
- Unmodified
- Added
- Removed
-
lm-sensors/trunk/doc/chips/eeprom
r1040 r1620 12 12 Microchip (www.microchip.com) 13 13 14 Chip Size (bits) Address 15 24C01 1K 0x50 (shadows at 0x51 - 0x57) 16 24C01A 1K 0x50 - 0x57 (Typical device on DIMMs) 17 24C02 2K 0x50 - 0x57 18 24C04 4K 0x50, 0x52, 0x54, 0x56 19 (additional data at 0x51, 0x53, 0x55, 0x57) 20 24C08 8K 0x50, 0x54 (additional data at 0x51, 0x52, 21 0x53, 0x55, 0x56, 0x57) 22 24C16 16K 0x50 (additional data at 0x51 - 0x57) 14 Chip Size (bits) Address 15 24C01 1K 0x50 (shadows at 0x51 - 0x57) 16 24C01A 1K 0x50 - 0x57 (Typical device on DIMMs) 17 24C02 2K 0x50 - 0x57 18 24C04 4K 0x50, 0x52, 0x54, 0x56 19 (additional data at 0x51, 0x53, 0x55, 0x57) 20 24C08 8K 0x50, 0x54 (additional data at 0x51, 0x52, 21 0x53, 0x55, 0x56, 0x57) 22 24C16 16K 0x50 (additional data at 0x51 - 0x57) 23 Sony 2K 0x57 23 24 24 25 … … 50 51 ----------- 51 52 52 This is a simple EEPROM module meant to enable reading the first 128bytes53 of an EEPROM (on a SDRAM DIMM ). However, it will access serial EEPROMs54 on any I2C adapter. This module will probably need to be53 This is a simple EEPROM module meant to enable reading the first 256 bytes 54 of an EEPROM (on a SDRAM DIMM for example). However, it will access serial 55 EEPROMs on any I2C adapter. This module will probably need to be 55 56 expanded. A /dev file interface would probably be more effective. 56 57 This module was a programming exercise to get used to the new project … … 69 70 eeprom. 70 71 72 Recent Sony Vaio laptops have an EEPROM at 0x57. We couldn't get the 73 specification, so it is guess work and far from being complete. 74 71 75 72 76 Lacking functionality: 73 77 74 * Read bytes 128-255. There is no technical restriction for not doing75 this, but making a zillion dataxx-xx files would be a bit rediculous.76 EEPROMs on DIMMs shouldn't use the contents past byte 128, so we are fine.77 78 78 * Full support for larger devices (24C04, 24C08, 24C16). These are 79 79 not typically found on a PC. These devices will appear as separate 80 devices at multiple addresses, with every other 128-byte block inaccessable 81 because of the missing 128-255 functionality. 80 devices at multiple addresses. 82 81 83 * Support for really large devices (24C32, 24C64, 24C128, 24C256, 24C5 412).82 * Support for really large devices (24C32, 24C64, 24C128, 24C256, 24C512). 84 83 These devices require two-byte address fields and are not supported. 85 84 86 85 * Enable Writing. Again, no technical reason why not, but making it easy 87 86 to change the contents of the EEPROMs (on DIMMs anyway) also makes it easy 88 to disable the DIMMs until the values are restored somehow. 87 to disable the DIMMs until the values are restored somehow. 89 88 90 89 … … 101 100 EEPROMs reported are not nessesarily all from DIMMs. Xeon processors, for 102 101 example, have serial EEPROMs in them connected to the SMBus which will be 103 found by the module. Take care to ignore the output of decode_dimms.pl for 104 these EEPROMs. 102 found by the module. Take care to ignore the output of decode-dimms.pl for 103 these EEPROMs. There is decode-xeon.pl for them. Same applies to Vaio 104 EEPROMs, which have decode-vaio.pl. 105 105 106 106 The driver caches the data from the monitor and only rereads it … … 108 108 109 109 110 D ECODE_DIMMS.PL110 Decode-dimms.pl 111 111 --------------- 112 112 … … 115 115 Intel. When finished, it will decode and report all the values defined in 116 116 the spec. Much of the information is technical timing and interfacing info 117 (probably not all used by the B ios or clocking IC.117 (probably not all used by the BIOS or clocking IC). 118 118 119 119 Note: During testing, we noticed that many DIMMs have trucated SPD records. 120 120 I'm not sure if these conform to an old spec, or if the manufacturers are 121 simply just taking short -cuts. But, many DIMMs have all zeros stored past121 simply just taking shortcuts. But, many DIMMs have all zeros stored past 122 122 byte 21. I asked an Intel SDRAM tester, Sat Kolli (skolli@smartm.com), 123 123 about this and this is what he had to say: … … 130 130 inconsistencies between spd data from different manufacturers. You could 131 131 read the timing information or the special Intel bytes (126 & 127) but I do 132 not know how many program that information. These inconsistencies may be132 not know how many program that information. These inconsistencies may be 133 133 minimized if you or your customers stay with some of the better known 134 manufacturers." (Thanks goes to Sat Kolli for his comments and help )134 manufacturers." (Thanks goes to Sat Kolli for his comments and help.) 135 135 136 136 Use: 137 137 138 After inserting the ne ssesary modules, run the script!138 After inserting the necessary modules, run the script! 139 139 140 140 Notes: … … 142 142 The script assumes that Perl can be found at /usr/bin/perl. If different, 143 143 you will need to adjust the first line of the file accordingly, or else 144 you will get a strange "decode _dimms.pl: no such file or directory" error.144 you will get a strange "decode-dimms.pl: no such file or directory" error. 145 145 146 146 Also note that the script assumes that _all_ the eeproms belong to DIMMs, 147 147 which may not be the case. 148 149 150 Decode-vaio.pl 151 -------------- 152 153 This Perl script looks for a Sony Vaio EEPROM at 0x57. If your system is not 154 a Sony Vaio laptop, you just don't care. If your system is an old Vaio, you 155 probably don't have an EEPROM on it and this script will be useless to you 156 as well. 157 158 Use: 159 160 After inserting the necessary modules, run the script! 161 162 Notes: 163 164 The script assumes that Perl can be found at /usr/bin/perl. If different, 165 you will need to adjust the first line of the file accordingly, or else 166 you will get a strange "decode-vaio.pl: no such file or directory" error.
