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

RIP-Felix · Dec 20, 2021

Haha, no.

I saw one listing specifically say 'the sticker is in place, so you know it was never opened.' Then go on to say the "top cover slides."

That means they broke the security screw to open the console instead of removing the sticker. I have a couple of consoles where people did this. It pisses me off, because now the top cover is loose and not easily repaired. IDK, bondo? Should I grind it off and 3D print a replacement to glue on? Total DICK move! They are destroying the case just to misrepresent the condition of a console. Hoping to sell it for more.

EDIT:
As a matter of course, I do not buy consoles where the seller avoids picture angles that show the bottom where the security screw/warranty sticker are. If they show every angle except the bottom, they're intentionally hiding it and know why people care. You should be VERY leery of whatever they claim (like working, because it was probably a $h!tty reflow).

EDIT 2:
You are not going to increase the value of a console by reflowing it. Reflows are not repair and should not be sold as "working" consoles unless you disclose the reflow. You should not buy a working console that has been reflowed and I would avoid buying any console that is working, but doesn't have an intact seal. And get a refund if the top cover was broken open in order to keep the seal intact!

A reflow/reball is okay, but you should know what you are buying. And if you are selling, you should never misrepresent what you are selling to your buyers! The console is worth what it's worth in the condition it's in. If you don't know, then take a picture from every angle. Especially the bottom. Then state you don't know the history. Do not misrepresent the condition. That's scamming!

vyktormvmpay25 · Dec 20, 2021

Do kind of 90 degree piece of metal 05 mm sheet steel with one hole for that screw. Is quite hard stick it back with A+B composite glue. Not sure what else can be done.

RIP-Felix · Dec 20, 2021

vyktormvmpay25 said:
Do kind of 90 degree piece of metal 05 mm sheet steel with one hole for that screw. Is quite hard stick it back with A+B composite glue. Not sure what else can be done.

That's not a bad idea. The metal will be harder to break open.

The screw post thing is ABS. Acetone dissolves it. I've used acetone vapor to smooth and harden the finish of 3D prints before (but they shrink). I haven't used it as a glue to good effect, but I bet the soft/molten/glazed surface of a hunk of ABS from a failed print could be used as glue after soaking in acetone vapor for a while.

What I'm worried about is the same thing that happens when you use cyanoacrylate (CA/super glue). CA works, but the vapor as it dries turns the area around it white. I have a couple of "Funtastic" N64 shells that were cracked. One pretty badly. I reinforced the cracks with CA glue, which stiffened and fixed the structural damage, but left an unsightly scar that's more obvious than the cracks were before. I mean, it needed done, but it's doesn't look good. I've always wondered if there were another glue that cures clear without discoloration to the surrounding plastic. But I haven't found it yet.

vyktormvmpay25 · Dec 20, 2021

Poxipol transparent.

sandungas · Dec 20, 2021

RIP-Felix said:
Yeah, I mean it gets super complicated when you get into the details of BGA reliability.

I do have to disagree on a couple of points. I wondered about arcing potentially welding the solder together or oxidizing pads too. I have since dismissed the idea. It would require a much higher voltage to overcome the air gap. Even at microscopic distances, 1 or 2 volts isn't enough potential.

The other is with the solder. The way alloys solidify is similar to rock. The slower they cool from molten to solid, the longer the crystals have to grow. So ideally they should transition from solid, to molten, and back to solid in as little time as possable. Small crystals dont have as many fault lines that can propagate a crack, like long crystals do. That's the grey surface you see in hard solder - long crystals.

The second part to that is oxidation, which further contributes to hard brittle solder. The higher the temp, the faster it oxidizes. So again, fast transitions, with good flux to prevent oxygen from getting at the joint when it's hot, leads to shiny strong bonds.

This is why reflow profiles reduce the time above refolw temps to 45s or less. And often these are done in a nitrogen atmosphere, to prevent oxidation.

Voids and inclusions inside the solder has to do with the flux chemistry. So yeah, it gets complicated. A lot of factors to get right, alot of oppritunaties for murphy to troll. BGA tech just sucks.

Not sure if we are misunderstanding each other but i only see one disagreement in what i said, about the sparks
The damage caused by sparks is more notable when the BGA ball is completly "fractured" like in the photo you posted, in that case the electron needs to do the "jump" to cross the fracture, and when the electron "lands" it burns a bit the surface, this is why some pads from broken BGA balls looks brown, black, or dissapeared
Is not only the oxidation caused by the contact with air, we need to consider the moterboards have a lot more pads made of copper fully exposed to air and they stays "goldie" for many years

But that effect of the sparks happens also in tiny scales in the internal structure, see this photos, it have micro-fractures inside... and i guess the microsparks happens in them too (degrading the microfracture even more)
https://www.semlab.com/bga-solder-joint-microsection/
https://www.circuitnet.com/experts/76178.html (last post at most bottom)
https://www.process-sciences.com/Microsection-Cross_Section_BGA_Analysis

The ony way to see that with the bare eye is because the external surface looks like the skin of a frog (with little bumps everywhere)

-----
What i meant with the semi-solid state is... lets say... we heat up the material to a temperature around 20ºC or 30ºC lower than the melting point (so is still solid but is very close to become liquid), and then we start to pull and squeeze it, the result is something like this

Originally it was an sphere, but is not an shiny sphere anymore, so is obvious it was "deformed" at some point... actually probably for something like this to happen is required to repeat many cycles of warmup<--->cooling of the device to stress the internal atomic structure

------------
Yeah, BGA tech sucks, nothing beats the pins or the sockets

I bet the engineers that designs rockets for aerospatial industry doesnt have any BGA tech in his rockets (maybe elon musk is pioneering a bit on that, but i dont think either)
I remember an story that represents very well how the aerospatial industry prioritizes relliability over anything else
https://www.theverge.com/2015/1/15/7551365/playstation-cpu-powers-new-horizons-pluto-probe
The reason why they choose a old-fart-ass processor for that satellite is because it was one of the most relliable designs they had at that time

Nowadays is obvious they could control all the systems of a rocket, a satellite, a rov, etc... with the processor of an smartpone... but they are not going to do it
Or... if they does they are going to request to the manufacturer of that processors to design a procesor model with pins all around because BGA is the evil

feng_ye · Dec 21, 2021

RIP-Felix said:
My guess based on e-bay listings...

As is for parts/repair. Red Blinking light.

Untested, as I don't have the cables.

In both cases the pictures will avoid an angle showing the voided/missing warranty seal.

Too real

RIP-Felix · Dec 21, 2021

sandungas said:
Not sure if we are misunderstanding each other but i only see one disagreement in what i said, about the sparks
The damage caused by sparks is more notable when the BGA ball is completly "fractured" like in the photo you posted, in that case the electron needs to do the "jump" to cross the fracture, and when the electron "lands" it burns a bit the surface, this is why some pads from broken BGA balls looks brown, black, or dissapeared
Is not only the oxidation caused by the contact with air,...

The dielectric strength of air is 3,000,000 V/m. Or 3V per micrometer. The voltage on the CPU and RSX is 1V - 1.3V. So solder crack would need to be 0.3 microns wide for an arc to form in air (depending on many factors, such as moisture, dust, and contamination). You can see some solder cracks in this study. They have a 50 micron line for scale. The cracks are microscopic, but it's unlikely the airgap is less than a micron wide. Maybe at some points, but not along the entire fault. Certainly not along the full surface of a sheared pad! ANd even it it did arc, it would generate an error because the high resistance would surely cause an interruption in the signal it's carrying. It's not like the spark would be arcing continuously, long enough to scorch a pad.

It doesn't take that long for copper to oxidize in air. And we have no idea what conditions the sheared pads are subjected to for potentially years. Left over flux, residues from a smokers home, and of course the heat/flux of the removal process during the reball accelerates the oxidation. By the time we see the pad, it's been subjected to alot already, unless it was still covered with solder.

sandungas · Dec 22, 2021

RIP-Felix said:
The dielectric strength of air is 3,000,000 V/m. Or 3V per micrometer. The voltage on the CPU and RSX is 1V - 1.3V. So solder crack would need to be 0.3 microns wide for an arc to form in air (depending on many factors, such as moisture, dust, and contamination). You can see some solder cracks in this study. They have a 50 micron line for scale. The cracks are microscopic, but it's unlikely the airgap is less than a micron wide. Maybe at some points, but not along the entire fault. Certainly not along the full surface of a sheared pad! ANd even it it did arc, it would generate an error because the high resistance would surely cause an interruption in the signal it's carrying. It's not like the spark would be arcing continuously, long enough to scorch a pad.

It doesn't take that long for copper to oxidize in air. And we have no idea what conditions the sheared pads are subjected to for potentially years. Left over flux, residues from a smokers home, and of course the heat/flux of the removal process during the reball accelerates the oxidation. By the time we see the pad, it's been subjected to alot already, unless it was still covered with solder.

My way of thinking is... ok, maybe there was a manufacturing defect at the time that individual BGA ball was soldered on factory, or maybe the BGA was broken (like in your photo, where the line is completly interrupted). At the exact instant when the BGA ball breaks (like in your photo), the copper pad surface still should have a goldie color, right ?... in other words, when the BGA ball breaks the copper particles are fine

After that is when the pad starts changing its color to brown... then to black... up to a point where the copper particles are completly decomposed
And i think for this to happen is needed electricity (the electrons doing the "jumps" to cross the gap of the fracture)
This effect of the burned pads seems to be some kind of electro-chemical reaction... but to me it looks more electrical than chemical

feng_ye · Dec 22, 2021

DeadEnd said:
I think the command is there to see what is going on with the system. I believe "WaitResolution" means the system is literally waiting for the RSX to set the resolution, any resolution, which it is not able to do for some reason. There will be black screen until some kind of resolution is set. But this is for HDMI. I guess you could try AV composite cable to see if there's anything on screen and then switch it to HDMI from there.

Still, even if it's not 100% dead, it's on the way there, I would imagine. Of course, you should inspect the board to be sure there are no knocked off components just like Vyctor was trying to tell you. But yeah, don't hold your breath.

Yeah I think you were right. So I gave myself a bit rest then carry on with this CECHC model today. I found "hdmi vbs ffffff" command very useful that prints out verbose debug message when bringup.

Then I checked the service manual diagram. It looks like on page 5/23 and 8/23 show that RSX communicates with HDMI chip with RS_SDOUT0/SII_SD0 and RS_BCLK0/SII_SCK. Refer to the PCB those pins are actually very close to the top edge of RSX, and connecting with R2064 and R2073. I did a press test on RSX's top edge while turning verbose on and bringup, and the resolution was successfully set! But obviously this time if I release my finger, artefacts show up. Logs here:

Code:

hdmi vbs ffffffff
[HDMI VBS] Code:ffffffff
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module               : Set
[HDMI VBS] ( 1) Command Module          : Set
[HDMI VBS] ( 2) I2C Module              : Set
[HDMI VBS] ( 3) Interrupt Module        : Set
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Set
[HDMI VBS] ( 5) Authentication Module   : Set
[HDMI VBS] ( 6) State Machine Module    : Set
[HDMI VBS] ( 7) EDID Read Module        : Set
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module              : Set
[HDMI VBS] ( 9) FRAME Module            : Set
[HDMI VBS] (10) HW Module               : Set
[HDMI VBS] (11) SET Module              : Set
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module           : Set
[HDMI VBS] (13) REQ Module              : Set
[HDMI VBS] (14) SystemEvent Module      : Set
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module              : Set
[HDMI VBS] (17) CH1 Module              : Set
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module              : Set
[HDMI VBS] (25) EEPROM Module           : Set
[HDMI VBS] (30) Hdmi System             : Set
[HDMI VBS] (31) Hdmi ERROR              : Set
[mullion]$
>$ br
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[hdmiEEPROM] HDMI Behavior Mode : 0xff
[hdmiEEPROM] HDMI Source Termination Mode : 0x03
[HDMI] Starting up HDMI ch.0
[HDMI] I2C Module Init ch.0
[HDMI] Init Instance ch.0
[HDMI] Start InitInstance
[HDMI]   Read Vender ID from SiI9032
[HDMI]   Read Vender ID from SiI9032
[HDMI] *** Detect SiI Chip : VID 0001 DID 9132 DRev 01 ***
[HDMI] ChipID Check Done
[HDMI] Initialize SiI9032
[HDMI] Power On SiI9032 internal block
[HDMI] Set SPD Packet
[HDMI] Interrupt Init ch.0
[hdmiINTR](ch.0) *** Ch.0 Initialize Interrupt Registers ***
[HDMI] Ssm Init ch.0
[hdmiSYSEVNT](ch.0) [HDMI] Source Termination Setting.Ch.0
Event Occure : [00004000]
[HDMI] Init Done ch.0
[HDMI] HDMI 1 Channel(s) set up!
[SSM] state: 0201 -> 0102
[hdmiBe] Try to send Event Event Ch.0 Size(4) ID[01]...
[hdmiSSM](ch.0) Un-Plug State.
[hdmiSSM](ch.0) Pluged State.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[0c0000]
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[070000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[060000]
>$
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[SERV NVS] READ CMD
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0a0000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[0a0000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[060000]
[hdmiINTR](ch.0)      Ch.0 Mask [0400e0]  MInt[040000]

Boot Loader SE Version 1.5.0 [hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[070000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[060000]
(Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]

Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]

[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0a0000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[0a0000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[040000]
[hdmiINTR](ch.0)      Ch.0 Mask [0400e0]  MInt[040000]
[hdmiEDID](ch.0) EDID Block Size is 2.
[hdmiEDID](ch.0) ATD Block Revision 3.
[hdmiEDID](ch.0) ATD DTD Offset [1f].
[hdmiEDID](ch.0) ATD CEA Tag Code [4c].
[hdmiEDID](ch.0) ATD CEA Tag Code [23].
[hdmiEDID](ch.0) ATD CEA Tag Code [65].
[hdmiEDID](ch.0) VSDB Code [03][0c][00].
[hdmiEDID](ch.0) HDMI Mode Set.
[hdmiBe] Try to send Event Event Ch.0 Size(260) ID[02]...
[hdmiSSM](ch.0) Wait Power On State.
[hdmiSSM](ch.0) Wait Resolution Setting State.
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
>$
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[hdmiCmd] Command ID : 0x00
[hdmiCmd] Command ID : 0x01
[hdmiCmd] Command ID : 0x11
[hdmiCmd] Command ID : 0x0F
[hdmiCmd] Command ID : 0x10
[hdmiCmd]  Communication Command ON
[SERV NVS]
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090304]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[SERV NVS] READ CMD
[hdmiAUTH](ch.0) KSV Check NG!!
[SERV NVS] READ CMD
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[SERV NVS] READ CMD
[hdmiIN
>$
TR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[SERV NVS] READ CMD
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hd104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmi
>$ sd
INTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100].0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]

So no doubt the RSX needs a reball. Not quite sure about all the KSV Check NG messages though, they keep printing out.

RIP-Felix · Dec 22, 2021

Honestly, I'm surprised I was right about the BGA. That's a win for the research effort, even if it is a loss overall. At least we're steadily demystifying some of these errors.

I'm about ready to add DVE/HDMI errors to the list of errors caused by BGA defects. That list includes 2020/2120, 2022/2122, & 2024/2124. But 2020/2120 especially are the ones most often associated with 3034/4xxx's. Not always, but often. In the case of 2024/2124, they don't appear on 90nm consoles. They are for later models with more reliable RSX chips, so I think that's why they tend to fixed by replacing the AV/HDMI controller IC's. But that doesn't mean they can't be cause by BGA defects too. It's just those BGA's are more reliable and tend to outlive the chips, whereas cases of 2020/2120 on 90nm board the opposite is more prevalent.

Since nearly half of the RSX's BGA pads (those near the edge) are AV/HDMI related (VDDIO), it makes sense anything related to DVE/HDMI can be affected by BGA defects. And it closes the BGA related YLOD vs GLOD conundrum. YLOD = critical system failure affecting the Power on Sequence. A major voltage system, reset, power good, CELL/RSX initialization, BitTraining, or system control. GLOD = non POS critical system, like DVE/HDMI I/O or the bootloader.

It's disappointing that most errors lead back to the BGA. But by now I guess I shouldn't be surprised.

feng_ye · Dec 22, 2021

RIP-Felix said:
Since nearly half of the RSX's BGA pads (those near the edge) are AV/HDMI related (VDDIO), it makes sense anything related to DVE/HDMI can be affected by BGA defects. And it closes the BGA related YLOD vs GLOD conundrum. YLOD = critical system failure affecting the Power on Sequence. A major voltage system, reset, power good, CELL/RSX initialization, BitTraining, or system control. GLOD = non POS critical system, like DVE/HDMI I/O or the bootloader.

I agree. YLOD is when system boots up in an early stage and system boot sequence probably quite fixed so there aren't a lot of different error code so that they can be fit into a pdf page. While when the system enters a more complicated stage, like the OS has been loaded, then there are heaps of problems can occur. It's not feasible to give each of them an error code, even it's possible it will not be very useful to pin down hardware problems. Thus we see GLOD and it's a pain to diagnose.

RIP-Felix · Dec 22, 2021

Yeah, in GLOD the error tends to get logged on shutdown in step #90. So you get 90 2120 alot. We've seen them occur at 20 & 40 before too, so it's not always 90. I just poured back over my spreadsheet of errorlogs and see most of the DVE/HDMI errors occur in 80/90 step numbers. And they're often a prelude to 40 3034's. @Kleon1876 documented the entire sequence of events with his console!

He had Errors 80 1001 & the odd 90 2120. The 80 1001's were still occurring all the time, but 6 months later...
...the error progressed to 80 2022.
2 months later, a 1601/1701 occurred the moment the the BGA broke. The PLL lost lock because the BGA break occurred while the system was on. So it generated a livelock detection / BE attention error code just that once. That's how 1601/1701 get logged when the clock generator is fine BTW. It just means the console was on when the BGA broke. Other BGAs break when the console cools overnight, so it doesn't affect the PLL.
Subsequent attempts to turn on the console generated 40 3034's.
@kleon reflowed and the 3034/2022's disappeared. But the 80 1001's were still there (that's a separate issue that predated the DVE errors and remained afterward).
Unfortunately he scratched the CPU wile delidding before the reflow, so he also got 80 1103 and 90 2203 errors. That gave him a YLOD/GLOD, even though his RSX reflow was successful. He then sent the console to @squeept who repaired the scratched CPU trace. That took care of the 1103/2203 errors.
Unfortunately the reflow began failing, the 80 2022's returned.
The BGA failed again shortly thereafter and the 40 3034's returned.

Kinda neat that the story is starting to make sense.

RIP-Felix · Dec 22, 2021

Bbowes9 said:
A little update to this,

An update to this: I re-attached the resistor and seemed to still have the YLOD as before. I checked all around the CELL to make sure I didn't knock anything else off but can't seem to find anything.

edit: I'm getting two new codes for 2101 and 3034. I'm familiar with 3034 being the rsx but unfamiliar with the 2101. It's very possible the resistor could be the 3032 error like I had before.

Bbowes9 said:
well interestingly enough, i believe i was able to get that knick back where it was supposed to be, as both those errors are now gone and replaced with a 3031 now. this is sure getting interesting.

as for the becount, here that is.

Code:

>$ becount becount Bringup : 921 times Shutdown: 77 times Power-on: 1day 21hour 36min 31sec

edit: here is the bringup command:

Code:

bringup [SSM] state: 0000 -> 0101 Bringup Mode #0 (0xFF) [SSM] ssmCb_OnStartingBePowOn() called. [SSM] Bringup mode : syspm_stat=00000000/00000000 [POWSEQ] PowerSeq_Setup called. [SSM] state: 0101 -> 0201 [POWSEQ] AV Backend Setup [SSM] state: 0201 -> 0102 [SSM] state: 0102 -> 0202 [SSM] state: 0202 -> 0103 [SSM] state: 0103 -> 0203 [SSM] ssmCb_BeforeBeOn() called. [SSM] state: 0203 -> 0104 [SSM] state: 0104 -> 0304 [SSM] ssmCb_AfterBeOn2() called. [SSM] PowSeq Fail : Detected ! [SSM] state: 0304 -> 0700 [POWSEQ] AV Backend Letup [SSM] Shutdown mode : syspm_stat=00000000/00000000 [ERROR]: 0xa0313031

I think I can finally make head or tales of this error now.

What happened is the previous errors were superseeded. The 31 3031 is just occurring before the 40 3034/2101. It probably has to do with the shorting TX1 on that nicked trace. You said you fiddle with it. So, you just raised the seriousness to an earlier error step number. It isn't getting to step #40 anymore. That's all. You need to repair the trace.

I would suggest sending it to @squeept. He might be able to cut the short out and solder a wire to the via. But it looks close to the nick. Either way, that board should be a good candidate for a frankenstein mod.

Related:
No one has seen this error, but I suspect 3033 would occur at step number 31 when BE_REFCLKN is disrupted. This inference is based upon observations of your 3031/3032 errors.

The 3032 was reported earlier when you knocked R5167 off. That's the +1.2V_YC_RC_VDDIO reference voltage for the CPU's Redwood FlexIO Analog to Digital Converter reference clock to interface with the XDR memory (BE_RC_REFCLK_P). That's Pin 24 on IC5004. The CPU lost it's XDR clock interface, because the "True" side of the open drain differential clock output was cut when the external resistor network was disrupted.

You can read about differential signaling here.

So...

3031 = +1.2V_YC_RC_VDDIO reference voltage for the CPU's Redwood XDR/FlexIO ADC
3032 = True side of Differential reference clock pair output (IC5004 Pin 24, BE_RC_REFCLK_P). Who's external resistor network you disrupted by knocking off R5167.
3033 = Complementary side of Differential reference clock pair output (IC5004 Pin 23, BE_RC_REFCLK_N). Who's external resistor network can be disrupted by knocking off R5170 to confirm it generates error A0313033

If anyone wants a simple project that could help test my hypothesis, you can help by testing on a board with a 40 3034. This test should generate an error at step number 31, earlier. So it's a simple test on a dead board. Record the error log before, flick off R5170 and post the results. I'd do it myself, but I don't have a suitable donor board ATM. I destroyed them in reball attempts, so they're all missing an RSX/Cell.

RIP-Felix · Dec 22, 2021

feng_ye said:

Yeah I think you were right. So I gave myself a bit rest then carry on with this CECHC model today. I found "hdmi vbs ffffff" command very useful that prints out verbose debug message when bringup.

Then I checked the service manual diagram. It looks like on page 5/23 and 8/23 show that RSX communicates with HDMI chip with RS_SDOUT0/SII_SD0 and RS_BCLK0/SII_SCK. Refer to the PCB those pins are actually very close to the top edge of RSX, and connecting with R2064 and R2073. I did a press test on RSX's top edge while turning verbose on and bringup, and the resolution was successfully set! But obviously this time if I release my finger, artefacts show up. Logs here:

Code:

hdmi vbs ffffffff
[HDMI VBS] Code:ffffffff
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module               : Set
[HDMI VBS] ( 1) Command Module          : Set
[HDMI VBS] ( 2) I2C Module              : Set
[HDMI VBS] ( 3) Interrupt Module        : Set
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Set
[HDMI VBS] ( 5) Authentication Module   : Set
[HDMI VBS] ( 6) State Machine Module    : Set
[HDMI VBS] ( 7) EDID Read Module        : Set
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module              : Set
[HDMI VBS] ( 9) FRAME Module            : Set
[HDMI VBS] (10) HW Module               : Set
[HDMI VBS] (11) SET Module              : Set
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module           : Set
[HDMI VBS] (13) REQ Module              : Set
[HDMI VBS] (14) SystemEvent Module      : Set
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module              : Set
[HDMI VBS] (17) CH1 Module              : Set
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module              : Set
[HDMI VBS] (25) EEPROM Module           : Set
[HDMI VBS] (30) Hdmi System             : Set
[HDMI VBS] (31) Hdmi ERROR              : Set
[mullion]$
>$ br
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[hdmiEEPROM] HDMI Behavior Mode : 0xff
[hdmiEEPROM] HDMI Source Termination Mode : 0x03
[HDMI] Starting up HDMI ch.0
[HDMI] I2C Module Init ch.0
[HDMI] Init Instance ch.0
[HDMI] Start InitInstance
[HDMI]   Read Vender ID from SiI9032
[HDMI]   Read Vender ID from SiI9032
[HDMI] *** Detect SiI Chip : VID 0001 DID 9132 DRev 01 ***
[HDMI] ChipID Check Done
[HDMI] Initialize SiI9032
[HDMI] Power On SiI9032 internal block
[HDMI] Set SPD Packet
[HDMI] Interrupt Init ch.0
[hdmiINTR](ch.0) *** Ch.0 Initialize Interrupt Registers ***
[HDMI] Ssm Init ch.0
[hdmiSYSEVNT](ch.0) [HDMI] Source Termination Setting.Ch.0
Event Occure : [00004000]
[HDMI] Init Done ch.0
[HDMI] HDMI 1 Channel(s) set up!
[SSM] state: 0201 -> 0102
[hdmiBe] Try to send Event Event Ch.0 Size(4) ID[01]...
[hdmiSSM](ch.0) Un-Plug State.
[hdmiSSM](ch.0) Pluged State.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[0c0000]
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[070000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[060000]
>$
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[SERV NVS] READ CMD
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0a0000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[0a0000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[060000]
[hdmiINTR](ch.0)      Ch.0 Mask [0400e0]  MInt[040000]

Boot Loader SE Version 1.5.0 [hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[070000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[060000]
(Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]

Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]

[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[020000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[020000]
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0a0000]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[0a0000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[040000]
[hdmiINTR](ch.0)      Ch.0 Mask [0400e0]  MInt[040000]
[hdmiEDID](ch.0) EDID Block Size is 2.
[hdmiEDID](ch.0) ATD Block Revision 3.
[hdmiEDID](ch.0) ATD DTD Offset [1f].
[hdmiEDID](ch.0) ATD CEA Tag Code [4c].
[hdmiEDID](ch.0) ATD CEA Tag Code [23].
[hdmiEDID](ch.0) ATD CEA Tag Code [65].
[hdmiEDID](ch.0) VSDB Code [03][0c][00].
[hdmiEDID](ch.0) HDMI Mode Set.
[hdmiBe] Try to send Event Event Ch.0 Size(260) ID[02]...
[hdmiSSM](ch.0) Wait Power On State.
[hdmiSSM](ch.0) Wait Resolution Setting State.
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
>$
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[hdmiCmd] Command ID : 0x00
[hdmiCmd] Command ID : 0x01
[hdmiCmd] Command ID : 0x11
[hdmiCmd] Command ID : 0x0F
[hdmiCmd] Command ID : 0x10
[hdmiCmd]  Communication Command ON
[SERV NVS]
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090304]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[SERV NVS] READ CMD
[hdmiAUTH](ch.0) KSV Check NG!!
[SERV NVS] READ CMD
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[SERV NVS] READ CMD
[hdmiIN
>$
TR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[SERV NVS] READ CMD
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hd104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmi
>$ sd
INTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100].0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090100]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiAUTH](ch.0) KSV Check NG!!
[hdmiSSM](ch.0) Authenticating State.
[hdmiAUTH](ch.0) Step 1 in.
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[090104]
[hdmiINTR](ch.0)      Ch.0 Mask [0e00e0]  MInt[080000]
[hdmiINTR](ch.0) *** Ch.0 Interrupt Process. ***
[hdmiINTR](ch.0) *** 9032 Interrupted Ch0[0d0100]
[hdmiINTR](ch.0)      Ch.0 Mask [0800e0]  MInt[080000]

So no doubt the RSX needs a reball. Not quite sure about all the KSV Check NG messages though, they keep printing out.

Holy crap, is that what you get from the SB UART?

Man, it litterally breaks down exactly what step in the startup sequence it's initializing the HDMI transmitter. Kinda wierd that it referrs to it as a SiI9032 when it's actually a SiI9132, which is a confidential version of the SiI9134 (which you can find the data sheets for). It's similar as far as specs go, may be identical.

SiI9022 is the HDMI transmitter in the N64 Digital. It took me a minute to recall why seeing SiI9032 felt familiar! I reciently read that datasheet to calculate how far I could push the pixel clock using custom modelines on the SiI9022 (1920x1440p is the limit BTW = 184.75MHz pixel clock. 165MHz is max, so it's a mild overclock). That's the same max frequency as the SiI9132/4 in the PS3. So technically speaking the PS3 could support 1920x1440p with a mild overclock, if there was a way to use custom modelines.

I wonder if anyone has looked into that? Would be useful for 4:3 PS1/PS2 games (if your monitor supported the weired resolution). Of course, I'm not sure how much control developers have over the scaling config or firmware. The N64 Digital is purpose built with that in mind, I just thought it was neat to see a similar chip in the PS3 and wondered if it could be tweaked. It would at least be nice to have more control over post-processing besides smooth on/off.

RIP-Felix · Dec 23, 2021

vyktormvmpay25 said:
Ok another strange story with RSX INT error 1802 unsorted what can be motherboard or cpu itself or interface between them.
Board kte001.
Received Sunday one costumer slim dropped floor unit while it was working. All errors on the motherboard 1802, 14ff and 1701.
Board was sometimes started glod without beep for reset image , sometimes 3 seconds one beep.
OK looks like Rsx damage. Desoldering been looking for oxidation for pins. It seems that rsx was missing pads. On motherboard nothing strange. Took another rsx, clean errors, same 1802 error only after adding new rsx. OK Now with all knowledge I was confident my second rsx is fine, cpu from faulty motherboard was looking fine for measurements but still couldn't boot, 3 seconds with one beep.
Moved rsx back to know working board kte001 starting from first try.
Now it's like 4 times in different units I can not understand why slims will give this error while cpu is the real thing that causes this problem and not rsx itself.
Probably the problem occurs with cpu when is working and shock damaged cpu internally or costumer pushed mobo in order to fix it itself. Don't know exactly but if I ever came across to this error, board will be left for scrap. Not necessarily to follow my advice this is as reference. I've done reball both so I am confident for myself not losing time.
At least costumer will get another motherboard.
Full error was A0611802

It was on when it fall, generating errors 80 14ff (Check Stop) & 80 1701 (Be attention) the moment its BGA broke. Thereafter it exhibited 61 1802. Victor removed the RSX and confirmed oxidized pads on K37 (FB MF1), L37 (RSX VI31), N37 (RSX VI27), N36 (GND), P35 (RSX VI20).

Now, K37 is involved in the RSXRAM voltage feedback reference, which might cause this error. It prevents the RSX from initializing correctly, but wouldn't necessarily prevent it from getting this far into the Power on Sequence. Steps 60 - 62 = Finish CPU Initialization. 62 is the last step before power on state. So SYSCON sets up CPU to begin coordinating with SB and RSX over the FlexIO now that it's signal integrity has been confirmed (40 = BitTraining) and the SB/RSX are ready (50-52). Basically, it failed the last bit of CPU/RSX coordination before the POS had finished.

This is pure gold for my POS reverse engineering project. Great work documenting that Victor - recording the step number (full error) in the last sentence was clutch! We're not likely to ever see a 61 again.

These step numbers are really starting to paint a picture of the Power on sequence. "Power Control Topology - Part 3" teaser

Bbowes9 · Dec 23, 2021

RIP-Felix said:
I think I can finally make head or tales of this error now.

What happened is the previous errors were superseeded. The 31 3031 is just occurring before the 40 3034/2101. It probably has to do with the shorting TX1 on that nicked trace. You said you fiddle with it. So, you just raised the seriousness to an earlier error step number. It isn't getting to step #40 anymore. That's all. You need to repair the trace.

I would suggest sending it to @squeept. He might be able to cut the short out and solder a wire to the via. But it looks close to the nick. Either way, that board should be a good candidate for a frankenstein mod.

Related:
No one has seen this error, but I suspect 3033 would occur at step number 31 when BE_REFCLKN is disrupted. This inference is based upon observations of your 3031/3032 errors.

The 3032 was reported earlier when you knocked R5167 off. That's the +1.2V_YC_RC_VDDIO reference voltage for the CPU's Redwood FlexIO Analog to Digital Converter reference clock to interface with the XDR memory (BE_RC_REFCLK_P). That's Pin 24 on IC5004. The CPU lost it's XDR clock interface, because the "True" side of the open drain differential clock output was cut when the external resistor network was disrupted.

You can read about differential signaling here.

So...

3031 = +1.2V_YC_RC_VDDIO reference voltage for the CPU's Redwood XDR/FlexIO ADC

3032 = True side of Differential reference clock pair output (IC5004 Pin 24, BE_RC_REFCLK_P). Who's external resistor network you disrupted by knocking off R5167.

3033 = Complementary side of Differential reference clock pair output (IC5004 Pin 23, BE_RC_REFCLK_N). Who's external resistor network can be disrupted by knocking off R5170 to confirm it generates error A0313033

If anyone wants a simple project that could help test my hypothesis, you can help by testing on a board with a 40 3034. This test should generate an error at step number 31, earlier. So it's a simple test on a dead board. Record the error log before, flick off R5170 and post the results. I'd do it myself, but I don't have a suitable donor board ATM. I destroyed them in reball attempts, so they're all missing an RSX/Cell.

I've actually built my own BGA Rework Station since i posted here, i have 2 rsx mod chips waiting, and a ps3 slim donor with a working 40nm rsx. ive been practicing on dead boards/laptop boards to make sure i dont mess up this good board. It hasn't been done yet, and ive been considering sending it to someone else here who has experience with reballing/frankenstein. If anyone is up for it here, ill gladly provide the rsx mod chips along with the board.

RIP-Felix · Dec 24, 2021

Bbowes9 said:
I've actually built my own BGA Rework Station since i posted here, i have 2 rsx mod chips waiting, and a ps3 slim donor with a working 40nm rsx. ive been practicing on dead boards/laptop boards to make sure i dont mess up this good board. It hasn't been done yet, and ive been considering sending it to someone else here who has experience with reballing/frankenstein. If anyone is up for it here, ill gladly provide the rsx mod chips along with the board.

Just remember, no one looks forward to reballing. I'd rather drink a pan galactic garggle blaster.

DeadEnd · Dec 24, 2021

RIP-Felix said:
It was on when it fall, generating errors 80 14ff (Check Stop) & 80 1701 (Be attention) the moment its BGA broke. Thereafter it exhibited 61 1802. Victor removed the RSX and confirmed oxidized pads on K37 (FB MF1), L37 (RSX VI31), N37 (RSX VI27), N36 (GND), P35 (RSX VI20).

Now, K37 is involved in the RSXRAM voltage feedback reference, which might cause this error. It prevents the RSX from initializing correctly, but wouldn't necessarily prevent it from getting this far into the Power on Sequence. Steps 60 - 62 = Finish CPU Initialization. 62 is the last step before power on state. So SYSCON sets up CPU to begin coordinating with SB and RSX over the FlexIO now that it's signal integrity has been confirmed (40 = BitTraining) and the SB/RSX are ready (50-52). Basically, it failed the last bit of CPU/RSX coordination before the POS had finished.

This is pure gold for my POS reverse engineering project. Great work documenting that Victor - recording the step number (full error) in the last sentence was clutch! We're not likely to ever see a 61 again.

These step numbers are really starting to paint a picture of the Power on sequence. "Power Control Topology - Part 3" teaser

Awesome work Felix. Your research and comprehensive explanations are incredible. It's like engineering deciphered. Finally somebody is able to break it all down into understandable language.

Bbowes9 said:
I've actually built my own BGA Rework Station since i posted here, i have 2 rsx mod chips waiting, and a ps3 slim donor with a working 40nm rsx. ive been practicing on dead boards/laptop boards to make sure i dont mess up this good board. It hasn't been done yet, and ive been considering sending it to someone else here who has experience with reballing/frankenstein. If anyone is up for it here, ill gladly provide the rsx mod chips along with the board.

Curious to what schematics you used ? I have built my own BGA as well, but now realized it still needs more work.

RIP-Felix said:
Just remember, no one looks forward to reballing. I'd rather drink a pan galactic garggle blaster.

In my case, I got the reballing part down after figuring out a perfect amount of flux (extremely thin layer). But with a DIY bga machine and no proper fixture, if the board is allowed to flex too much, the balls could merge or not solder properly. That has been a massive challenge for me personally. Basically the last and most important step of the process...

poot36 · Dec 25, 2021

9th system a VER-001 board. This time I may be lucky as according to the error dump it may just be RSX VRAM power or something to do with the AV or HDMI chips. The CPU has a resistance of 7.5 ohms and the RSX 5.1 ohms. There is slight damage to the CPU where it was delided. The RSX was delided as well. The odd thing about this system is that it will power up when I press the eject button on the disk drive and even get as far as to illuminating the blue light on the system and then give me the YLOD and that is it. Same result with pushing the power button. I am currently doing some more tests on the system.

===================================
ERR 00: 00000000 A0802124 FFFFFFFF
ERR 01: 00000000 A0802124 FFFFFFFF
ERR 02: 00000000 A0801002 FFFFFFFF
ERR 03: 00000000 A0802124 FFFFFFFF
ERR 04: 00000000 A0802124 FFFFFFFF
ERR 05: 00000000 A0801002 FFFFFFFF
ERR 06: 00000000 A0802124 FFFFFFFF
ERR 07: 00000000 A0801002 FFFFFFFF
ERR 08: 00000000 A0802124 0B49D816
ERR 09: 00000000 A0802124 0B49D815
ERR 10: 00000000 A0801002 0B49D800
ERR 11: 00000000 A0802124 12CBA316
ERR 12: 00000000 A0802124 12CBA315
ERR 13: 00000000 A0801002 12CBA315
ERR 14: 00000000 A0802124 12CBA2F6
ERR 15: 00000000 A0801002 12CBA2F5
ERR 16: 00000000 A0802124 12CA4B2E
ERR 17: 00000000 A0802124 12CA4B2D
ERR 18: 00000000 A0801002 12CA4B2D
ERR 19: 00000000 A0802124 12CA3AE6
===================================

Systems 7 and 8 had CPU package damage from deliding so I did not decide to connect them the the syscon reader.

poot36 · Dec 25, 2021

Here is the output of the bringup command ran twice:

>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

>$ bringup
FFFFA605
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.7.0
#!(Build ID: 3517,38879,
#!Build Date: 2009-03-24_23:51:55)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)

I don't think this looks so good.

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

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Forum Noob

Attachments

Forum Noob

Similar threads