Talk:Syscon Thermal Configs

Other Official Thermal Configs

CRC32: F0899A5E (syscon csum: 0E17)

• Found in PS3 models:
  • COK-001 motherboard  PROTO 

33 40 48 4D 5A 66 73 80 99 FF 00 4A 00 4B 00 4C
00 4D 00 4E 00 4F 00 50 00 51 00 52 00 55 00 00
00 45 80 45 00 46 80 46 00 47 80 47 00 48 80 48
00 49 33 FF 01 00 FF FF FF FF FF FF FF FF FF FF

33 40 48 4D 5A 66 73 80 99 FF 00 53 00 54 00 55
00 56 00 57 00 58 00 59 00 5A 00 5B 00 5F 00 00
00 4E 80 4E 00 4F 80 4F 00 50 80 50 00 51 80 51
00 52 33 FF 01 00 FF FF FF FF FF FF FF FF FF FF

33 40 48 4D 5A 66 73 80 99 FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF 33 FF 01 00 00 FF FF FF FF FF FF FF FF FF

33 40 48 4D 5A 66 73 80 99 FF 00 3C 00 3D 00 3E
00 3F 00 40 00 41 00 42 00 43 00 44 00 47 00 00
80 38 00 39 80 39 00 3A 80 3A 00 3B 00 3C 80 3C
00 3D 33 FF 01 00 FF FF FF FF FF FF FF FF FF FF

33 40 48 4D 5A 66 73 80 99 FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF 33 FF 01 00 00 FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF 00 4D 14 FF FF FF FF FF FF FF FF FF FF FF
54 00 55 00 02 00 5E 00 5F 00 02 00 FF FF FF FF
02 00 46 00 47 00 02 00 FF FF FF FF 02 00 FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF 17 0E

CRC32: xxxxxxxx

• Found in PS3 models:
  • ? with NPX-001 motherboard

There is a "bastard brother" of the NPX-001 thermal config from frontpage with CRC32: ABC9DF9E
The only difference in between them are a couple of bytes actually labeled as "unknown"
This sucks because it "breaks" the checksum and it seems is going to be needed to add both examples in the list... but is also very interesting because eventually could help to identify that "unknown" bytes
That might be caused by some line errors while reading the content over UART. Dumping the content at least a second time and comparing it should solve the problem.