I think I have an explanation for why SONY has 1002 labeled "RSX VRAM Power Fail." I think they meant to type "RSX VRM Power Fail." I mean, that makes A LOT more sense! VRM is more encompassing than "no drive signal," which is a symptom not the cause. So it would cover a broader spectrum of potential causes. And they have this section on the service manual labeled "VRM for RSX (2Phases)." I'm pretty sure that's just a typo.
\o/ im going to sound like an smartass but that description mentioning VRAM was smelling fishy to me too since time ago, it was mostly an intuition but i could not make sense of it
My reasoning is... "vram" = "video ram" (the 4 chips soldered at the corners of the RSX substrate, that are dedicated to video)... but there was people reporting 1002 errors that was related with the tokins
And this doesnt makes sense, because the tokins are located in a power line, and the vram chips in a different power line
So yeah... i think you are right, is "VRM" nstead of "VRAM"
@sandungas I haven't seen a console get stuck reiterating the same thermal settings. It's like it's stuck there. Could that be due to a corrupt thermal config? Maybe someone bothched a DIY fan curve? Or bad thermal monitor? IDK, haven't seen this before.
Is the first time i see that, and i cant figure why it happens but the thermal values are fine, in the logs is reporting CELL/RSX around 30ºC-50ºC and moving up, thats normal for a startup from ambient, so the thermocouple/diode inside CELL/RSX are fine, the thermal monitors are fine too, and the I2C/SMbus data channel in beteen syscon and the thermal monitors seems to be working fine too
The thermal config probably is correct too, keep in mind his integrity is "protected" by a checksum, so incase of having a "bad block" inside syscon EEPROM the checksum of the thermal config EEPROM region would break and the PS3 would refuse to boot (3 beeps), the only way it could have a weird thermal config is if the previous owner was playing around with the thermal config and fixed the checksum at the end
So... thermal related hardware seems to be fine, and syscon firmware/config seems to be fine too
I think what happens is he is connecting in a special mode with the PC terminal app that displays more info of the services that runs at background, as far i remember
@vyktormvmpay25 mentioned it in the forum, he was surprised and explained how to do it
I was using the CFW fan control in another console with manual speed for PS2 games and max temp otherwise and had some problems with PS2 games don't starting, going back to OFW solved the issue, I tried again with WMM fan control and had no problems while paying PS2 games.
Changing the fantables is something I am thinking about, just need to be more familiar with how it works.
The other day i wrote an small "how to" configure the thermal config in raw
https://www.psx-place.com/threads/syscon-fan-settings-coordinate-graphs.31188/page-10#post-314405
The most notable difference with other methods is im not modifying the temperature values, when we use the command "fantbl setini" we are writing 3 values (tempD=2 bytes, tempU=2 bytes, duty=1 byte) for a total of 5 bytes
As example, in this command is writing 68.00 (2 bytes), 78.00 (2 bytes), 0x5a (1 byte)
Code:
fantbl setini 0 p4 68.00 78.00 0x5a
But in the method i explained i just want to modify the "duty" (1 byte) so the "fantbl" comand is not convenient because it would cause uneeded writes to syscon EEPROM
The other most notable difference is im not changing the "thermal shutdown" values, but thats because we was talking about a DYN-001 motherboard, and that values for thermal shutdowns are fine in the official thermal config of the DYN-001... anyway, incase you want to change them (or any other setting inside the thermal config region) is the same story... find the offset where is lcoated and write in "raw" over it
This gives you full access to the thermal config region, there are a bunch of commands intended to read/write settings from inside the thermal config region, but there are some other values inside the thermal config region that doesnt have specific commands so the only way to read/write them is in raw
And btw... get used to how your thermal config region looks in a hexeditor by:
1) use the python script to dump the EEPROM
2) compare it with the collection of thermal configs in wiki, there is a high probability that yor thermal config is already in the collection (if not, please advise me and share it to add it to the collection)
3) check the coordinate graphs i made, there are some motherboards missing but if you are lucky it could help you a lot to get an overview of how is configured
4) check the "duty" values for your specific motherboard in your official thermal config, the duty values i was overriding (checking them with a "read" command) was from a DYN-001... if you do the "read" in a different motherboard the official duty values are going to be different
Another btw... the method i explained is relatively safe, as something visual... take one of the coordinate graphs i made and imagine you "move up" the horizontal lines (that represents speeds), and thats exactly the same i explained
And final btw... in the custom speeds i suggested to use i was increasing it + 0x04 in every step but thats not a requirement, i was trying to do it easy for the tutorial
![20211207_194118_HDR[1].jpg](/data/attachments/33/33959-976f8a28a16f1a49e43ad8253b9193a4.jpg?hash=l2-KKKFvGk)
