I don't know all the deeper details. I was talking about swapping syscon with the F version (flashable variant). You guys speak in a developer language, which my simple mind can't fathom.

For now, all I have learned is that patching the original eeprom and reflashing it to the new syscon is not enough. We must also flash the correct firmware, but it cannot be done through bus pirate. It is done through UART and a script that currently only works in Linux.
@vyktormvmpay25 has tried to use the script in Windows and that didn't work. (thanks to
@M4j0r for being patient enough to explain it in simple terms) He will eventually make a working script though, so just be patient.
Honestly, this whole ps3 modding is becoming a bit tedious. It's such a niche considering that only a few retrogamers care enough about it. I've been considering shifting my attention elsewhere...
Im not sure if you are used to the official syscon patches but as an introduction for everyone else...
Insdide the PUP (PS3 firmware installers) there are always some PKG's intended to update the firmwares inside Bluray controller, the wifi/BT module, and syscon
Lets say... when we install a PS3 firmware we are also installing firmwares for this 3 components
There are only 8 official firmware updates for syscon (and 3 of them was superceeded)... so the modern PUP files only have 5
https://www.psdevwiki.com/ps3/Syscon_Firmware#Syscon_patches
At an intermediate point of the PS3 firmware instalaltion, the installer does a check to syscon to find his "revision" (also named SoftID... is a software identifyer but it can be used as a hardware identifyer too) and his "version" (the syscon firmware version). The syscon patch is installed
only if the SoftID matches and the version of the patch is newer
The keys needed to build that official patches are public, so now we can build a "custom syscon firmware patch"... using SoftID 0B8E (for the syscon CXR713120-201GB shipped from factory in the motherboards COK-001) and with a version of 6.66 (it needs to be bigger than the officials)
Then we include this patch renamed to SYS_CON_FIRMWARE_06006006.pkg inside a PUP... install the PUP like if it was a standard custom firmware and our custom patch will be installed inside syscon EEPROM
The result is we can "update" the syscon firmware with custom code
Sure... the amount of code we can update is limited, in size, in the amount of areas we can patch (separated from each others), and how tricky are the functions we are trying to patch
This procedure could be used for any other patches, im not telling the problem of the RSX bittraining is something easy to achieve, the last time i was talking with m4j0r about this he said there is no room in the official patch formwat to "update" all the code related to RSX bittraining... but you know... as usually with hacking it could happen that eventually he or someone gets the illumination from the sky and finds how to do it in a unconventional way
Anyway... this trick to apply custom syscon patches using the official format is something handy for many other hacks, if there are some features that can be unlocked just by patching a few bytes it should work
I don't even know more of that EE side, we could swap that? Or is kind tied in wierd way?
Is not logically married, you can replace it without worryes
I would say before reballing or replacing it is important to take a look at the other components dependant of it, it have a couple of RAM chips (16mb each), doesnt seems to be much stressed by temperatures or workloads but the manufacturing technology looks a bit old, maybe are prone to failure
There is also another misterious component that worths to be checked
https://www.psdevwiki.com/ps3/CXD9208GP
This one is related with video output, so i guess is going to be tricky to check because it have a lot of lines with video signals