Recent content by CodeKiller

  1. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    If it's FW error, then you should check the SB UART too (and see if goes past lv2) And also, if the machine is below 3.55, then you can trigger the QA mode with DIY dongle or through syscon somehow(?) But the VRM error seems more like bad TOKINs to me.. Yes, it can reach full voltage level...
  2. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    CECH-30xx KTE-001 still there and on the other end is the SB_RX/TX testpoints
  3. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    Some more log after a longer "test" and shutdown: lv2(2): lv2(2): Prepare to shutdown rsx ctxsw driver timeout! please report So RSX may be bad? (board had overheating Cell/now delidded, new paste/ and smoking from a bad laser-head cable install -- but seems the drive still loads and spins up a...
  4. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    Is there a way to fix a broken flash on a "not supported" Slim (CECH-30xxx (KTE-001) Lowest fw: 3.65 )? Or can this mean a different source of problem? /*****Syscon dump*****/ # [SSM] Bringup Start. # [SSM] PS0 ok. # [SSM] PS1 ok. # [SSM] PS2 ok. # [SSM] PS3 ok. # [SSM] PS4 ok. # (PowerOn...
  5. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    No, those are the EEPROM values (at least in COK). After setting new values with it, the eepcsum will fail, but if fixed, in the next boot it will remember and use those. Unlike values set with plain set. There are full tables in the setini/getini and the first values in every table are always...
  6. CodeKiller

    PS3 Frankenstein PHAT PS3: CECHA with 40nm RSX

    Xc2c32a is pretty basic (but fast -- 300MHz @1.8V), it only has 32macrocells and every macrocell only has one flip-flop. And because it's on the SPI bus, it needs to use flip-flops to propagate the bits, both in the input and on the output, As far as i can think it could have one of the...
  7. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    The old errors don't go away unless you clear them manually. Having 3031 AFTER 3003-2031-2030 means you had them already. A0A0 -error after syscon reset (just after plugged in) , 2030/2031 thermal sensor error (maybe I2C bus error-- missing pullup resistors?) A009 - error in power off state ...
  8. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    If you look the available schematics carefully, you can see the HDMI chip does not get any control signal from the RSX, just sync, video data and audio data. The Syscon is the one that can interface with its I2C bus and setup or init or something -- that's why there is that much HDMI commands in...
  9. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    I've got a (now) working 2500 and that shows an LED code of GGRR GGGG GGGG GGRR .. so it doesn't really help. I think it's not the syscon but some minimal FW code -- but maybe @M4j0r or @zecoxao could clarify it. It would also be nice to find a new way to externally enable the QA Flags now as...
  10. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    Yes, aaaand?? Any idea whar that is for? Any available Slim syscon dump?
  11. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    Been there done that --- that's how I got the 'lv2...done.' in the first place. (at least in COK002 boards) I would not look into this deep if the recovery mode would work HDMI status: waiting / WaitResolution /Unset... -- also no screen on DVE (analog AV out) On the Slims have one (3000)...
  12. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    Is there a way to debug after the lv2 loaded? I have a few units that loads past lv2 ( lv2(2): initial system process done.) but still black screen. Sometimes beeps once or twice later, but nothing on syscon or SB uart.
  13. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    I already have the service manual, and already said i checked the capacitors in the schematic..... But investigating further revealed the VRM is smoking hot (60+°C on the "PSU side" rater than the component side) after just 1-2 minutes -- while the Cell itself does need about 10-20 min to reach...
  14. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    Well, it's still kind-of ontopic, as my goal is to find the fault and fix my machine, using SYSCON logs and sort.... Yeah, checked the 12V-to-5V converter and 5V_USB and 5V_HDD rails, seemed fine. (the USBs have their own power switches controlled by a USB HUB IC, that i think only powers up, if...
  15. CodeKiller

    PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

    It was for a while. Now it is more severe, The PS3 booted, but displayed: "Cannot start. The appropriate system storage was not found." Then shutting down and starting up fixed it until switched off for longer/cooled down.
Back
Top