PS3 SYSCON Tutorial (Windows)

Hi Guys,

Any advice on next steps to take on this BC CECHC03 model (COK-002)? Error codes are showing as 3034 and 4432.

I replaced the NEC Tokins with tantalums back in 2020 because I think this was the most commonly suggested fix at that time... and its been sat for a while waiting for me to hook up and get codes from the syscon which I have finally got round to doing !

I havent attempted anything else and didnt want to just go straight in with a hot air gun and try and reflow the RSX like a complete noob, so wondering what the best next steps would be?

I have a certain level of skill with a soldering iron etc but feel a reball looks well beyond a feasable home repair without expensive tools.

I am based in the UK if anyone knows of a decent repair service that wont break the bank. I dont really want to just give up at this point but it might be beyond economical repair.

Let me know your thoughts.

Much Appreciated!

errlog / becount / bringup logs below:

errlog

ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0404432, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0404432, clock:0xffffffff
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
ofst[ 4]:err_code:0xa0404432, clock:0xffffffff
ofst[ 8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0404432, clock:0xffffffff
ofst[ 16]:err_code:0xa0403034, clock:0xffffffff
ofst[ 20]:err_code:0xa0404432, clock:0xffffffff
ofst[ 24]:err_code:0xa0403034, clock:0xffffffff
ofst[ 28]:err_code:0xa0404432, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0404432, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0404432, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0404432, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0404432, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0404432, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0404432, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0404432, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0404432, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0404432, clock:0xffffffff

becount
Bringup : 1193 times
Shutdown: 1149 times
Power-on: 105day 05hour 13min 36sec

bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[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
Psbd_SbTransMode_Half:0x21e2
[POWERSEQ] Error : BitTraining RSX:RRAC:RX3:GLOBAL1:RX_STATUS
[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]: 0xa0404432
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
 
Not sure if this is the correct place to ask, but trying this to pull codes for my J model (DIA-002 board). External mode worked, trying to access internal mode. Changed the bit, did the power cycle and connected DIAG to GND, but when trying to run the script and typing in "AUTH" both with and without caps, I get met with an "scopen response invalid" error. Has anyone seen this before and have some ideas on where I could have gone wrong?

Code: 
C:\Users\msmat\OneDrive\Desktop\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM4 CXRF
Press Ctrl+C to exit
>$ auth
scopen response invalid
Press Ctrl+C to exit
>$ AUTH
scopen response invalid
Press Ctrl+C to exit
>$
 
Good morning guys!

I have yet another K04 (DIA-002) wtih the following issue: some very minor graphical artifacting (I mean grey-bars flickerig rarely) on XMB and under light load (interestingly never had any issues under games with artifacts), and YLODs with heavy load. Nr. 8-14 seem like a bad omen, however I can see a lot of 1001/1002 codes as well, in addition the most recent after clearing it, is an rsx pwr failure. Never had a GLOD before with it.

The following issues were present before clearing log (from :
Code: 
>$ errlog
errlog
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[  0]:err_code:0xa0801004, clock:0x125de2c4  2009/10/06 11:13:08
ofst[  4]:err_code:0xa0611701, clock:0x1302cdf7  2010/02/08 13:28:23
ofst[  8]:err_code:0xa06114ff, clock:0x1302cdf7  2010/02/08 13:28:23
ofst[ 12]:err_code:0xa0611701, clock:0x1302ce1d  2010/02/08 13:29:01
ofst[ 16]:err_code:0xa06114ff, clock:0x1302ce1d  2010/02/08 13:29:01
ofst[ 20]:err_code:0xa0611701, clock:0x1302ce35  2010/02/08 13:29:25
ofst[ 24]:err_code:0xa06114ff, clock:0x1302ce35  2010/02/08 13:29:25
ofst[ 28]:err_code:0xa0801001, clock:0xffffffff
ofst[ 32]:err_code:0xa0801001, clock:0xffffffff
ofst[ 36]:err_code:0xa0801002, clock:0x0b4d9600  2006/01/03 20:07:28
ofst[ 40]:err_code:0xa0801002, clock:0x0b503d1a  2006/01/05 20:24:58
ofst[ 44]:err_code:0xa0802022, clock:0x0b48ba1b  2005/12/31 03:40:11
ofst[ 48]:err_code:0xa0802022, clock:0x0b48bbff  2005/12/31 03:48:15
ofst[ 52]:err_code:0xa0802022, clock:0x0b488777  2005/12/31 00:04:07
ofst[ 56]:err_code:0xa0801002, clock:0x0b493193  2005/12/31 12:09:55


After this, I cleared the error log, and the only thing that came back after partial reassembly after, and YLOD within the menu of Bioshock Infinite:

Code: 
ofst[  0]:err_code:0xa0801002, clock:0x0b48870f  2005/12/31 00:02:23

What do you guys think? Is it worth tacking on a few new caps? or is it a lost cause with a dead gpu?

ps:
I'll grab a few new CR2032s today. I seem to burn through them fairly quickly, and I ran out.


Edit: Matthias: did you unplug your serial to usb converter? Maybe you reversed the RX and TX pins.
Also, make sure you changed the right bits.
 
Last edited:
Casualdehid/Aerials said:
Good morning guys!

I have yet another K04 (DIA-002) wtih the following issue: some very minor graphical artifacting (I mean grey-bars flickerig rarely) on XMB and under light load (interestingly never had any issues under games with artifacts), and YLODs with heavy load. Nr. 8-14 seem like a bad omen, however I can see a lot of 1001/1002 codes as well, in addition the most recent after clearing it, is an rsx pwr failure. Never had a GLOD before with it.

The following issues were present before clearing log (from :
Code: 
>$ errlog
errlog
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[  0]:err_code:0xa0801004, clock:0x125de2c4  2009/10/06 11:13:08
ofst[  4]:err_code:0xa0611701, clock:0x1302cdf7  2010/02/08 13:28:23
ofst[  8]:err_code:0xa06114ff, clock:0x1302cdf7  2010/02/08 13:28:23
ofst[ 12]:err_code:0xa0611701, clock:0x1302ce1d  2010/02/08 13:29:01
ofst[ 16]:err_code:0xa06114ff, clock:0x1302ce1d  2010/02/08 13:29:01
ofst[ 20]:err_code:0xa0611701, clock:0x1302ce35  2010/02/08 13:29:25
ofst[ 24]:err_code:0xa06114ff, clock:0x1302ce35  2010/02/08 13:29:25
ofst[ 28]:err_code:0xa0801001, clock:0xffffffff
ofst[ 32]:err_code:0xa0801001, clock:0xffffffff
ofst[ 36]:err_code:0xa0801002, clock:0x0b4d9600  2006/01/03 20:07:28
ofst[ 40]:err_code:0xa0801002, clock:0x0b503d1a  2006/01/05 20:24:58
ofst[ 44]:err_code:0xa0802022, clock:0x0b48ba1b  2005/12/31 03:40:11
ofst[ 48]:err_code:0xa0802022, clock:0x0b48bbff  2005/12/31 03:48:15
ofst[ 52]:err_code:0xa0802022, clock:0x0b488777  2005/12/31 00:04:07
ofst[ 56]:err_code:0xa0801002, clock:0x0b493193  2005/12/31 12:09:55


After this, I cleared the error log, and the only thing that came back after partial reassembly after, and YLOD within the menu of Bioshock Infinite:

Code: 
ofst[  0]:err_code:0xa0801002, clock:0x0b48870f  2005/12/31 00:02:23

What do you guys think? Is it worth tacking on a few new caps? or is it a lost cause with a dead gpu?

ps:
I'll grab a few new CR2032s today. I seem to burn through them fairly quickly, and I ran out.


Edit: Matthias: did you unplug your serial to usb converter? Maybe you reversed the RX and TX pins.
Also, make sure you changed the right bits.
Click to expand...
From your description it sounds like a bad rsx, but I didn't see any errors like 3034. errors 1001 and 1002 that most likely NECTokin failures. 2022 DVE error doesn't seem to be a big problem. If you have soldering skills, you can add a Tantalum cap like the one on the Felix tantalizer next to the neckokin to try to revive it. They are available on slim model motherboards. This is probably the lowest-cost experimental method without having to buy a whole set of Tantalizers.
Google Translated English, sorry XD
 
NightLess said:
From your description it sounds like a bad rsx, but I didn't see any errors like 3034. errors 1001 and 1002 that most likely NECTokin failures. 2022 DVE error doesn't seem to be a big problem. If you have soldering skills, you can add a Tantalum cap like the one on the Felix tantalizer next to the neckokin to try to revive it. They are available on slim model motherboards. This is probably the lowest-cost experimental method without having to buy a whole set of Tantalizers.
Google Translated English, sorry XD
Click to expand...

Yeah, done that on a few consoles, but I doubted this one.
I tried on this a few days ago, now I get a GLOD :|
I'll have to do a SB Uart on this. Dunno what happened. Possibly the RSD Balls?
 
Casualdehid/Aerials said:
Yeah, done that on a few consoles, but I doubted this one.
I tried on this a few days ago, now I get a GLOD :|
I'll have to do a SB Uart on this. Dunno what happened. Possibly the RSD Balls?
Click to expand...
Are you talking about RSX ball? I also had an A00 with GLOD before, but syscon didn't seem to find any faults like 3034 using the brintup command. But I have seen this machine output artifacts on the screen. I wonder if you have seen it before.
 
NightLess said:
Are you talking about RSX ball? I also had an A00 with GLOD before, but syscon didn't seem to find any faults like 3034 using the brintup command. But I have seen this machine output artifacts on the screen. I wonder if you have seen it before.
Click to expand...

Same happened here. Slight artifacts, HDMI Digital audio clicks and pops, no 3034, nothing. It boots, but no controller connection not even from USB.
 
KiMk4YW.png
P1Rs1l9.png

I plug in my PS3 to the PC via the USB to TTL adapter (I used the "USB to TTL Serial Adapter CH340 chip Converter Module Debug Cable TTL to USB Serial Cable" on Amazon.com) and it says that communication with the Syscon is OK (keep in mind I don't use ground wires and the one time I did try it it didn't let me do this.), however doing AUTH or auth both give me an "Auth1 response invalid" error and a "SETCMDLONG" error in PowerShell.

What should I do? Is this fixable?
Using CECH-2004B PS3 Slim.
 
Help, I messed up on the custom fan curve for my Slim 25xx, the final verification was w 7fe and I wrote w 7f2, since I didn't back up the syscon eeprom, can 25xx slim users use w 7f2 1a, what's in it?

Scwarzkop said:
KiMk4YW.png
P1Rs1l9.png

I plug in my PS3 to the PC via the USB to TTL adapter (I used the "USB to TTL Serial Adapter CH340 chip Converter Module Debug Cable TTL to USB Serial Cable" on Amazon.com) and it says that communication with the Syscon is OK (keep in mind I don't use ground wires and the one time I did try it it didn't let me do this.), however doing AUTH or auth both give me an "Auth1 response invalid" error and a "SETCMDLONG" error in PowerShell.

What should I do? Is this fixable?
Using CECH-2004B PS3 Slim.
Click to expand...
Try using the Linux folder in the syscon folder and follow Felix's video, or the RX TX cables are connected in reverse.
 
Last edited by a moderator:
Scwarzkop said:
RX TX cable orientation should be fine (I keep track of wire colour), but I also get Communication OK when swapping them. However, if I take one of the cables out, it no longer works.
Click to expand...
Maybe it's not grounded? I followed Felix's tutorial and grounded it and it worked fine.
 
Hola amigo,quiero preguntarle si podre usar un programador CH341, ya que no consigo el del tutorial,desde ya les doy las gracias por todos sus aportes y un cordial saludo.

Google transation provided by moderator
Hello friend, I would like to ask you if I can use a CH341 programmer, since I cannot find the one from the tutorial. I thank you in advance for all your contributions and best regards.
 
Last edited by a moderator:
hiiii
I am trying to see if there's anything that I can do for my sister's fat ps3.
It gets ylod but only during gaming stress. I can turn it on and navigate normally most of the time so I used the webpage diagnosis.
These are the error codes that I got:
0xA0801002
0xA0802124
0xFFFFFFFF

The former two made up of almost every single line. 0xFFFFFFFF was only in the last line.
It would seem that A0801002 stands for RSX tokin failure. Do you think this can be fixed by replacing the tokins?
It also seems that A0802124 stands for an error in the HDMI encoder, although I don't know what that means tbh. Anybody knows by any chance?
It seems that FFFFFFFF means that there was a loop in the previous error? or something about the battery?

The console isn't jailbroken. It's on official 9.41 firmware.
It's a fat model but not the very first one (it doesn't have a lid, and only has 2 usb ports, and the grey part is opaque).
 
Last edited:
ando966 said:
hiiii
I am trying to see if there's anything that I can do for my sister's fat ps3.
It gets ylod but only during gaming stress. I can turn it on and navigate normally most of the time so I used the webpage diagnosis.
These are the error codes that I got:
0xA0801002
0xA0802124
0xFFFFFFFF

The former two made up of almost every single line. 0xFFFFFFFF was only in the last line.
It would seem that A0801002 stands for RSX tokin failure. Do you think this can be fixed by replacing the tokins?
It also seems that A0802124 stands for an error in the HDMI encoder, although I don't know what that means tbh. Anybody knows by any chance?
It seems that FFFFFFFF means that there was a loop in the previous error? or something about the battery?

The console isn't jailbroken. It's on official 9.41 firmware.
It's a fat model but not the very first one (it doesn't have a lid, and only has 2 usb ports, and the grey part is opaque).
Click to expand...
Yes, that's the classic behavior of a tokin failure. And 1002 confirms it.

The 2124 is likely incidental and will go away when you fix the tokins.

FFFFFFFF means there was no error in that slot. An empty errorlog on a perfect console would be all ff.

What model of console was it BTW? The model number is on the barcode at the back of the console.
 
RIP-Felix said:
Yes, that's the classic behavior of a tokin failure. And 1002 confirms it.

The 2124 is likely incidental and will go away when you fix the tokins.
Click to expand...
Oh, nice.

RIP-Felix said:
FFFFFFFF means there was no error in that slot. An empty errorlog on a perfect console would be all ff.
Click to expand...
Yeah I ended up guessing this was the case.

RIP-Felix said:
What model of console was it BTW? The model number is on the barcode at the back of the console.
Click to expand...
Just checked. The model is CECHL11

-----------------------

I often try to learn this type of stuff and do everything myself but I try to stop myself when it comes to electronics because I don't think I have the time (at least nowadays) to acquire the necessary skill, and I fear I might screw it up on my first attempts and I really don't want to ruin a good ol' ps3, so I am thinking of taking it to a local service place. The problem with that is that, at least in my experience and here, almost every service place tries to scam clients one way or the other, and I imagine that a way to minimize that risk is by explaining to them what I did and know so far about this to indirectly convince them that I kinda know what's up and that I will know whether they did an actual attempt or just some reflow or similar temporary and low effort attempt when they give it back to me.
So I plan on telling them that I could figure out what the issue is (the nec tokins needing to be replaced) and I will expect them to do that and only that.

Btw, since I will give this to some local service place, I made sure to log off psn so they don't have my data, although all I could do was delete the password and uncheck the automatic log in and automatic password fill options. Do you think this will be enough? or is there a better and more safe way to completely forget account credentials? I kinda wanna give this sdd to them because the loaded account has sonic generations in it which makes the ps3 go ylod in a matter of less than a minute so I think it's a good measurement method. The online (from the ps3) syscon method gave me all X's on the account credentials so I assume that what I did is good enough, but it doesn't hurt to ask I guess.

Btw2, been watching your videos and they were the best introduction that I found to this issue and also fun to go through, so tyvm. Idk why I didn't say this in my previous post, I got no manners.
 
Last edited:
I suggest you only go with a trusted service. There is always stuff they can steal if they're savvy and corrupt. Like the PSID and IDPS. Even if you were to factory reset or pull the HDD 1st.

IG you just have to take a risk and hope for the best.
 
I might have found a decent place in my city so I will take it there probably next week or so. They insisted that it will also need reballing in addition to replacing the nec tokins. I'm not sure about that, afaik the code for fatal RSX malfunction which is often related to ball cracks is 3034 and I ain't getting that, but I assume that it could be a good idea to get rid of that being another potential problem in the near future? I'll think a bit about it. They charge around 65usd for both replacing the nec tokins and reballing. Honestly I thought it was gonna be at least twice as expensive, but it still remains to see whether they will do a good job or not.

Either way, I am definitely going to come back here to report how it went once I have it back.

tyvm for everything really!
 
Hello everyone
Trying to fix ps3 CechG08 Sem-001
Came into my hands without Tokins
The error code at that time was 3004
After replacing with tantalum capacitors (2R5TPE470M7) I get error 3032
Previously there were no errors like 3034 and 4412 in the logs, so I think that rsx is alive
Having found the circuit diagram for the board, I looked at all the elements along the +1.2V_YC_RC_VDDIO and +1.5V_YC_RC_VDDA lines and they were all intact
If you try to turn it on, there is no voltage on the elements
The Cell was most likely reballed
Now I'm at a dead end and don't know what else to check
Please help

Syscon logs

Code: 
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xa0093004, clock:0xffffffff
ofst[ 96]:err_code:0xa0093004, clock:0xffffffff
ofst[100]:err_code:0xa0093004, clock:0xffffffff
ofst[104]:err_code:0xa0093004, clock:0xffffffff
ofst[108]:err_code:0xa0093004, clock:0xffffffff
ofst[112]:err_code:0xa0093004, clock:0xffffffff
ofst[116]:err_code:0xa0093004, clock:0xffffffff
ofst[120]:err_code:0xa0093004, clock:0xffffffff
ofst[124]:err_code:0xa0093004, clock:0xffffffff
ofst[  0]:err_code:0xa0093004, clock:0xffffffff
ofst[  4]:err_code:0xa0093004, clock:0xffffffff
ofst[  8]:err_code:0xa0093004, clock:0xffffffff
ofst[ 12]:err_code:0xa0313032, clock:0xffffffff
ofst[ 16]:err_code:0xa0313032, clock:0xffffffff
ofst[ 20]:err_code:0xa0313032, clock:0xffffffff
ofst[ 24]:err_code:0xa0313032, clock:0xffffffff
ofst[ 28]:err_code:0xa0313032, clock:0xffffffff
ofst[ 32]:err_code:0xa0313032, clock:0xffffffff
ofst[ 36]:err_code:0xa0313032, clock:0xffffffff
ofst[ 40]:err_code:0xa0313032, clock:0xffffffff
ofst[ 44]:err_code:0xa0313032, clock:0xffffffff
ofst[ 48]:err_code:0xa0313032, clock:0xffffffff
ofst[ 52]:err_code:0xa0313032, clock:0xffffffff
ofst[ 56]:err_code:0xa0313032, clock:0xffffffff
ofst[ 60]:err_code:0xa0313032, clock:0xffffffff
ofst[ 64]:err_code:0xa0313032, clock:0xffffffff
ofst[ 68]:err_code:0xa0313032, clock:0xffffffff
ofst[ 72]:err_code:0xa0313032, clock:0xffffffff
ofst[ 76]:err_code:0xa0313032, clock:0xffffffff
ofst[ 80]:err_code:0xa0313032, clock:0xffffffff
ofst[ 84]:err_code:0xa0313032, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[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]: 0xa0313032
Press Ctrl+C to exit
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
Press Ctrl+C to exit
 
You must log in or register to reply here.

Similar threads

Back
Top