1221更新，聯絡到之前維修沒成功的版友來返修看看狀態
更新在下面
--------------------------------------------------------------------------------------------------------------
不想看我碎碎念的可以直接看快速版維修影片
回到正題
這次文字很多，先說結論...
結論就是因為從電玩店老闆那邊拿到兩台殺肉機，想說除了灰塵超級厚超級多之外
一台PS3厚機，60GB硬碟都還在~
機器看起來很完整，沒有做什麼維修的感覺
另一台則是有拆過，只剩硬碟架螺絲也有少也沒有鎖緊，但好像也沒有維修的痕跡
在拆光碟排線的Connector來殺肉的同時的時候想說可以用之前看文章利用syscon來看代碼的方式來試著看看是什麼問題。而之前看syscon文章所買的USB轉TTL串口(FT232RL串口模塊訊號)終於用上了!!!!
然後就.....
莫名又救回一台PS3 60GB厚機了(最完整沒有拆的痕跡還有60GB硬碟那台)
原先因為PS3死亡黃燈的關係，所以有去研讀國外的論壇PSX PLACE搜尋文章
原先是看這篇文章
"Research/Experimental" - NEC/TOKIN Capacitors Replacement - YLOD
所以才知道會誘發出YLOD可能是因為NEC/TOKIN的電容所導致的
所以才會有Part1的文章產生
當然，因為運氣好吧
用這個方法除了一台經手的PS360GB 厚機更換後不行之外
其他處理過的，目前為止都是有成功延續其壽命
包括我朋友本來要丟掉的那台只是多做了一個開蓋的動作就都好了....
應該算是運氣好吧!!!!!
當初除了看文章得知，誘發出YLOD可能是因為NEC/TOKIN的電容所導致的之外
還有一些人回文有提出用syscon的方式去看PS3的代碼
可以更快更準確地知道可能出現問題的點在哪裡
因為從電玩店老闆那邊拿到兩台殺肉機來殺肉光碟機排線Connector
想說除了灰塵超級厚超級多之外，其他部分看起來很完整好像也沒有動作什麼手術。
重點是有一台裡面居然連60GB的硬碟都還在!!!!!
想當然爾...火速清潔之後裝回去開機看看
沒有意外的就是YLOD發生了
然後因為之前購買的USB轉TTL串口(FT232RL串口模塊訊號)放置很久，所以就想說來玩看看
(其實是之前有嘗試著用syscon，但是卡在無法溝通的環節所以就收在抽屜很久很久....)
當初的文章如下
Fault finding YLOD with the SYSCON - First steps and Error reporting
因為出現YLOD，所以就先做電容的處理以及CPU、GPU的開蓋
在用syscon之前想說先直接換電容以及開蓋。
結果電容開蓋都處理完後開機，一樣是YLOD
所以就試試看用syscon的方式來讀代碼
搜尋一下文章
論壇PSX PLACE裡的版友RIP Felix有發表一篇更直覺的文章
SYSCON Tutorial (Windows)
搭配RIP Felix網友的youtube影片
以及Amateur Hardware Repair網友的youtube影片
(這邊是因為USB轉TTL串口模組跟他用的是一樣的所以就也參考他的影片)
工具除了
USB轉TTL串口模組之外還需要下載軟體
PYTHON
和
ps3syscon
標示一下下載的位置...
下載之後就可以得到ps3syscon-master.zip這個壓縮檔，解壓縮之後如下
然後照著RIP Felix網友的youtube影片，一步一腳印來做
11/22補充增加照片及步驟
************************************************************************************************
步驟一，焊接訊號線
因為我拿到的殺肉機是60GB的
所以依照上述資料夾PS3-Serial-Connection-Points -> COK-001-002-(A-E-Models)裡面的
圖片位置來找RX、TX、DIAG的位置
我焊接的照片如下
因為不小心，所以測試點被弄掉了
只能刮漆來焊線....
步驟二，連接USB轉TTL串口模組
這邊就發現一個問題，因為我買的USB轉TTL串口模組並沒有DIAG可以連接的位置
這時可以依照下圖這樣來連接
PS3板上的RX連接到USB轉TTL串口模組的TXD
TX連接到USB轉TTL串口模組的RXD
DIAG連接到USB轉TTL串口模組的GND
再用兩頭都是鱷魚夾的線一頭夾PS3的板邊GND另一頭夾USB轉TTL串口模組的GND
如下圖這樣
就是用兩頭都是鱷魚夾的線一頭夾PS3的板邊GND另一頭夾USB轉TTL串口模組的GND
步驟三，接上電源PS3的電源開關切到ON
這邊要注意如果照上面步驟來接的話PS3的電源燈不會亮，這是正常的
因為DIAG接到GND了，如果要看到有電源燈的話可以先把DIAG但GND線從USB轉TTL串口模組的GND移開重新開關一下電源就會看到燈亮了
步驟四，安裝所下載的PYTHON
這邊可以參考影片13:07的位置
步驟五，安裝所下載的ps3syscon-master.zip解壓縮裡的檔案
這邊可以參考影片13:14的位置
或是照下圖這樣打指令
在Windows的開始鈕按右鍵 -> 搜索 輸入CMD，找到命令提示字元然後對著他點右鍵
點以系統管理員身分執行就會開啟畫面
然後依照下面來輸入
- 輸入 CD ps3syscom-master的位置，將目錄路徑改為ps3syscom-master的位置
- 輸入pip install pyserial
- 輸入pip install pycrypodomex
這些都做完後就可以將USB轉TTL串口模組接到電腦上了
可以在電腦的裝置管理員裡的連接埠(COM和LPT)裡面看到你所連接的裝置
我的連接裝置位置之前是COM9，今天11/22測試時我手動將他更新為COM2
再來就是輸入CD Linux進入Linux的位置
進入後輸入ps3_syscon_uart_script.py COM2 CXR
COM2是我裝置的位置，要改成你的裝置的位置
按Enter之後如果出現>$就表示進去了
接下來就是在輸入AUTH
如果出現Auth successful的話就表示可以讀取外部的資訊了
如果是出現Auth1 response invalid的話
請打auth
應該就可以出現Auth successful
這裡只是盡到外部去讀取資料，接下來還要進到內度去讀資料
依照順序我放在下面
************************************************************************************************
接下來就是第一次接上後所看到的ERRLOG
因為是讀取外部資訊所以 ERRLOG只能一筆一筆讀取
輸入ERRLOG GET 00~1F來讀取訊息
C:\Users\UU\OneDrive\桌面\ps3syscon\ps3syscon-master\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM9 CXR
Press Ctrl+C to exit
>$ AUTH
Auth successful
>$ ERRLOG GET 00
00000000 A0022110 FFFFFFFF
>$ ERRLOG GET 01
00000000 A0022110 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0022110 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0022110 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0022110 FFFFFFFF
>$ ERRLOG GET 05
00000000 A0022110 0EC4E884
>$ ERRLOG GET 06
00000000 A0022110 0EB9E121
>$ ERRLOG GET 07
00000000 A0022110 0E715B63
>$ ERRLOG GET 08
00000000 A0022110 0E323B67
>$ ERRLOG GET 09
00000000 A0022110 0DE0E595
>$ ERRLOG GET 0A
00000000 A0022110 0DD665E8
>$ ERRLOG GET 0B
00000000 A0022110 0DD665D9
>$ ERRLOG GET 0C
00000000 A0022110 0DD665D1
>$ ERRLOG GET 0D
00000000 A0022110 0DC7414C
>$ ERRLOG GET 0E
00000000 A0022110 0DBF5D6C
>$ ERRLOG GET 0F
00000000 A0022110 0DBF5D63
>$ ERRLOG GET 10
00000000 A0022110 0DB6C00C
>$ ERRLOG GET 11
00000000 A0022110 0DB6C004
>$ ERRLOG GET 12
00000000 A0022110 0D989DEC
>$ ERRLOG GET 13
00000000 A0022110 0D94B178
>$ ERRLOG GET 14
00000000 A0022110 0D8DCC26
>$ ERRLOG GET 15
00000000 A0022110 0D8DCC22
>$ ERRLOG GET 16
00000000 A0022110 0D8DCC1C
>$ ERRLOG GET 17
00000000 A0022110 0D8C691B
>$ ERRLOG GET 18
00000000 A0022110 0D8C49BE
>$ ERRLOG GET 19
00000000 A0022110 0D8C49AB
>$ ERRLOG GET 1A
00000000 A0022110 0D8C4994
>$ ERRLOG GET 1B
00000000 A0022110 0D8C4989
>$ ERRLOG GET 1C
00000000 A0022110 0D8C4981
>$ ERRLOG GET 1D
00000000 A0022110 0D8C496B
>$ ERRLOG GET 1E
00000000 A0022110 0D8C4968
>$ ERRLOG GET 1F
00000000 FFFFFFFF 0D8C4964
從這邊可以看到都是出現A0022110，根據上面壓縮檔裡的Syscon-error-log-codes.pdf
可以得知最主要是要看後四碼的2110
對應下來2110來看是Clock Generator Error (IC5001)感覺好像不太對....
如果是這顆壞掉了話就殺另一台肉的零件來換了
保險起見，先用ps3syscon A0022110搜尋看看，然後就在
在Syscon Error Codes這裡看到這一段話
This error has been resolved by a number of users who had a short on F6001. It is important to note that something usually causes that fuse to blow, like a short. So it's important to troubleshoot the board to find and repair the shorting component before replacing the fuse. Otherwise the new one will blow too.
所以說F6001保險絲有可能燒毀了，翻看線路查到F6001的位置
量出來的結果，果然燒毀不通
當下沒有想那麼多所以就先殺另一片版子的零件來更換
本以為換了就OK了，但沒想到一樣出現YLOD....
版子又拆下來量，結果又是燒毀的狀態...
這時候才想到，可能是後段有短路所以才讓他燒毀
然後就先從最有可能的電容下手，果然....在另一面的C6019、C6020電容已經短路了
直接把這兩顆電容移除後短路的問題就消失了
所以就繼續殺肉來更換零件
更換後確認沒有短路，也將其他保險絲都量個一遍都沒有問題就裝機上電看看了!!!!
上電開機後...
沒有出現YLOD換來的是PS3的LOGO出現~~~~
PS3的系統為4.65版，原先60GB的硬碟裡面的資料只有三國無雙7以及PS2版的三國無雙3就沒有其他資料了
光碟機看起來也可以讀PS3的遊戲片，所以先裸機測試一下之後再裝回機殼來跑
你以為這樣就結束了嗎?
並沒有!!!!
在裝回機殼要測試時又出現YLOD......
有一些詭異的感覺，難道有沒有發現的問題嗎?
所以又拆了一次，這次不知道想到了什麼就想說測試看看先移除光碟機的電源線來開機
X的
移除光碟機電源就可以開機不會出現YLOD，接上光碟機電源就會出現YLOD...
這又是什麼狀況?!?!?!?!?!
光碟機排線的12V和5V都很正常啊!!!!
測了三次都是一樣的狀況
然後就又想說在開機後把光碟機的電源線接上去看光碟機會不會動
結果不試還好試了兩三次之後光碟機確定在開機的時候再機上去是不會動作
而且連帶的在沒有接光碟機的情況下也YLOD了....
然後就又再看一次syscon的ERRLOG
>$ ERRLOG GET 00
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 01
00000000 A0611001 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0303030 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0301001 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 05
00000000 A0503036 FFFFFFFF
>$ ERRLOG GET 06
00000000 A0501001 FFFFFFFF
>$ ERRLOG GET 07
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 08
00000000 A0523039 FFFFFFFF
>$ ERRLOG GET 09
00000000 A0511001 FFFFFFFF
>$ ERRLOG GET 0A
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 0B
00000000 A0402101 FFFFFFFF
>$ ERRLOG GET 0C
00000000 A0301001 FFFFFFFF
>$ ERRLOG GET 0D
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 0E
00000000 A0611001 FFFFFFFF
>$ ERRLOG GET 0F
00000000 A0611001 FFFFFFFF
>$ ERRLOG GET 10
00000000 A0611001 FFFFFFFF
>$ ERRLOG GET 11
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 12
00000000 A0611001 FFFFFFFF
>$ ERRLOG GET 13
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 14
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 15
00000000 A0402101 FFFFFFFF
>$ ERRLOG GET 16
00000000 A0401001 FFFFFFFF
>$ ERRLOG GET 17
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 18
00000000 A0611001 FFFFFFFF
>$ ERRLOG GET 19
00000000 A0303030 FFFFFFFF
>$ ERRLOG GET 1A
00000000 A0301301 FFFFFFFF
>$ ERRLOG GET 1B
00000000 A0301001 FFFFFFFF
>$ ERRLOG GET 1C
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 1D
00000000 A0231001 FFFFFFFF
>$ ERRLOG GET 1E
00000000 A0101001 FFFFFFFF
>$ ERRLOG GET 1F
00000000 FFFFFFFF FFFFFFFF
這次除了2120、2101、1001、1301、3030、3036、3039之外還有更恐怖的3034....
3034表示可能是GPU或是CPU需要重新植球回焊....
感覺好像又沒輒了...我沒有BGA焊接台可以動手....
11/22補充增加照片及步驟
************************************************************************************************
想說近到syscon去讀內部的資料
這邊可以參考影片19:41的位置
這邊就是要進入到Syscon內部去讀取資料的前置作業
步驟一
先輸入EEP GET 3961 01
可以讀到這個位置的值是FF
然後再輸入EEP SET 3691 01 00
將值改為00
改完之後輸入EEP GET 3961 01
可以確認所改的值是00
之後將PS3的AC電源斷電
重點!!!!
如果原先DIAG以及鱷魚夾接到USB轉TTL串口模組的GND的線有移除的話請在AC重新上電前接回去(我沒有這樣接會近不去，所以我都會接上)
再將AC電源上電，就可以看到PS3的指示燈閃紅光 逼逼逼三聲這就可以進到內部去看值了
這邊我所讀到的值就跟RIP Fliex所讀到的值不同，所以我也節錄他影片的畫面來比較
一樣進入到所放置的ps3syscon-master\Linux
進入後輸入ps3_syscon_uart_script.py COM2 CXRF
出現>$就表示成功了
一樣輸入AUTH
如果出現Auth successful的話就表示可以讀取了
如果是出現Auth1 response invalid的話
請打auth
應該就可以出現Auth successful
然後輸入eepcsum，會秀出eepsum的資料
看到下面紅框的sum:0x0100，然後在下面Addr:0x000039fe後面的黃框的值是0x0f38
輸入w 39fe 38 0f，將值寫進去
解進去後再打一次eepcsum確認沒有再出現sum:0x0100就可以了
下面是RIP Fliex所讀到的值，我在猜想可能每一台所讀到的都不同吧~
請依照自己所讀到的值來做寫入即可不用跟影片一樣
************************************************************************************************
這時可以輸入errlog可以看到更多資訊
而我看到的狀況也是一樣，也是有3034出現
C:\Users\UU\OneDrive\桌面\ps3syscon\ps3syscon-master\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM9 CXRF
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
ofst[ 16]:err_code:0xa0101001, clock:0xffffffff
ofst[ 20]:err_code:0xa0231001, clock:0xffffffff
ofst[ 24]:err_code:0xa0902120, clock:0xffffffff
ofst[ 28]:err_code:0xa0301001, clock:0xffffffff
ofst[ 32]:err_code:0xa0301301, clock:0xffffffff
ofst[ 36]:err_code:0xa0303030, clock:0xffffffff
ofst[ 40]:err_code:0xa0611001, clock:0xffffffff
ofst[ 44]:err_code:0xa0902120, clock:0xffffffff
ofst[ 48]:err_code:0xa0401001, clock:0xffffffff
ofst[ 52]:err_code:0xa0402101, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0902120, clock:0xffffffff
ofst[ 64]:err_code:0xa0611001, clock:0xffffffff
ofst[ 68]:err_code:0xa0902120, clock:0xffffffff
ofst[ 72]:err_code:0xa0611001, clock:0xffffffff
ofst[ 76]:err_code:0xa0611001, clock:0xffffffff
ofst[ 80]:err_code:0xa0611001, clock:0xffffffff
ofst[ 84]:err_code:0xa0902120, clock:0xffffffff
ofst[ 88]:err_code:0xa0301001, clock:0xffffffff
ofst[ 92]:err_code:0xa0402101, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0511001, clock:0xffffffff
ofst[104]:err_code:0xa0523039, clock:0xffffffff
ofst[108]:err_code:0xa0902120, clock:0xffffffff
ofst[112]:err_code:0xa0501001, clock:0xffffffff
ofst[116]:err_code:0xa0503036, clock:0xffffffff
ofst[120]:err_code:0xa0902120, clock:0xffffffff
ofst[124]:err_code:0xa0301001, clock:0xffffffff
ofst[ 0]:err_code:0xa0303030, clock:0xffffffff
ofst[ 4]:err_code:0xa0611001, clock:0xffffffff
ofst[ 8]:err_code:0xa0902120, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
感覺沒招了，就想說玩一下指令看一下內部的資料
用becount看總使用時間，總使用時數只有76天又4個小時
>$ becount
becount
Bringup : 1526 times
Shutdown: 1466 times
Power-on: 76day 04hour 04min 09sec
[mullion]$
Press Ctrl+C to exit
用指令bringup開機看看...沒有意外就是YLOD
>$ bringup
bringup
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
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
Psbd_SbTransMode_Half:0x20e2
Press Ctrl+C to exit
然後用指令shutdown來關機
其中[SERV THERM] Thermal Error Cleared!這段文字以及
[ERROR]: 0xa0801200
[ERROR]: 0xa0902203
[ERROR]: 0xa0902203
[ERROR]: 0xa0902203
讓我覺得好像有機會
因為我沒有接散熱器來開機.....又加上我有開蓋
所以出現[SERV THERM] Thermal Error Cleared!
感覺是過熱.....
>$ shutdown
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV THERM] Thermal Error Cleared!
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[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
[SERV NVS] READ CMD
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SERV THERM] Thermal Error Detected!
[SSM] *** Thermal Alert (ZONE) ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[BE-SC COMM] msg_to_be() : Explicit BUG !
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[ERROR]: 0xa0801200
[ERROR]: 0xa0902203
[ERROR]: 0xa0902203
[ERROR]: 0xa0902203
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
所以再裝上去散熱器之後
打bringup來開機，得到的是[SSM] *** Power Fail BE ***
>$ bringup
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] fatalreq delayed.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[ERROR]: 0xa0101001
[SSM] *** Power Fail BE ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Press Ctrl+C to exit
>$ shutdown
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
其中，a0101001這段其實不太懂...因為1001的可能太多了
Wiki上面寫道下面三個可能
1.
Conversely, A0101001 may result from various other factors, simply because there is a larger number of things that can go wrong. Therefore, it's possible that the NEC/TOKINs are not the source of the error.
2.
System Errors
1001 (Power CELL)
Components Involved:
CELL (IC1001 on COK-001)
NEC/TOKIN Proadlizers (C6140/C6141/C6142/C6143 on COK-001)
Other nearby components of the power block
This error may result from inadequate filtering on the CPU's core voltage (VDDC) or an unexpected system shutdown. Voltage ripple or noise within a certain range could cause errors before they worsen into a CELL VDDC Power Failure (3003). There are several SMD filters, but the most critical ones are the NEC/TOKIN Proadlizers (capacitors). Bad NEC/TOKINs are responsible for 1002 errors on the GPU, but diagnosing 1001 errors is not as straightforward. You must observe the console experiencing YLOD while under load and confirm the generation of a new 1001 error. Otherwise, the 1001 code may indicate the console was not turned off correctly.
1001 errors can be recorded automatically when the system experiences an unexpected shutdown or loss of AC power. These errors frequently arise during testing when the console is frequently turned on or off instead of being gracefully shut down. A0801001 errors alone cannot prove that NEC/TOKINs are failing. Such errors are regularly found in the log of properly functioning machines and are not cause for concern unless the system is unexpectedly shutting down on its own.
A machine that can power on but displays graphical artifacts or no video may lead to misinterpretation of 1001 errors. In such cases, the console must be turned off forcibly using the power switch at the back of Phat/Fat models or by pulling the power cord in Slim and Super Slim models. This may cause 1001 or 1004 errors, which can be ignored if they were not generated under normal circumstances. If a console is showing artifacts/GLOD, fix the larger problem first (usually a GPU problem requiring a reball/replacement). Only after that, if stress testing results in 1001 errors, should you troubleshoot the CPU NEC/TOKINs.
Anecdote: One console, with faulty CPU NEC/TOKINs, displayed an A0901001 error only during shutdown. The Last of Us, a strenuous game, showed no signs of typical bad NEC/TOKIN behavior, and the system remained stable. However, it remained in shutdown for a prolonged period, resulting in the YLOD (3 beeps and flashing red light). It required a reset to power back on. Replacing the NEC/TOKINs resolved the problem.
3.
Fatal Errors
2110 (Clock Subsystems)
Clock Generator Error (IC5001)
This error can be caused by a 5V_MISC short to ground. One user had an A0022110 after replacing IC6105 (Buck Converter) and accidentally bridging the 5V voltage input. So check the 5V line for shorts.
This error has been resolved by a number of users who had a short on F6001. It is important to note that something usually causes that fuse to blow, like a short. So it's important to troubleshoot the board to find and repair the shorting component before replacing the fuse. Otherwise the new one will blow too.
One user, who resolved this error on his C model PS3, noted "very short YLOD. Error code shows 2110[...]Some earlier code shows 1001 and 1002." The 1001 & 1002 errors he noted in the log before the 2110 appeared may have been a clue that C6019 or C6020 (as they are in parallel) was deteriorating. Further investigation is needed to confirm this hypothesis, however. In his case, C6019 was shorting and caused F6001 to blow. This short overloaded F6001 and cut power to many Subsystems, such as the HDD, USB ports, South bridge, CPU, GPU, etc. Another user confirmed this. The error log was showing code 2110 and one entry earlier was showing code 1001. Checking both capacitors after removing them from the board, confirmed that one capacitor was reading 140 ohms and not reading as a capacitor, so it was working as a resistor causing extra load in the fuse.
One particularly noteworthy component is IC6020, which supplys +3.3v_MK_Vdd to the clock generator (IC5001). When F6001 blows, a 02 2110 is generated. A step number of 02 is very early in the power on sequence (POS), which explains why 2110 is triggered instead of another error code. Since the clock generator is critical for timing, it is one of the first things the SYSCON checks during the POS.
接下來不知道要測什麼了所以又回到了玩指令的時候了，想說現在都是看之前的訊息不如清掉errlog看看
下clearerrlog指令果然前面的err_code都變成err_code:0xffffffff，後面的clock:0xffffffff可以不用管。
因為RTC電池沒電了，所以紀錄不了時間
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 0]:err_code:0xffffffff, clock:0xffffffff
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xffffffff, clock:0xffffffff
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
ofst[ 16]:err_code:0xffffffff, clock:0xffffffff
ofst[ 20]:err_code:0xffffffff, clock:0xffffffff
ofst[ 24]:err_code:0xffffffff, clock:0xffffffff
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
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
[mullion]$
Press Ctrl+C to exit
然後又玩了幾次bringup、errlog、clearerrlog指令
這個真的玩很多次，只節錄一些
>$ 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
Psbd_SbTransMode_Half:0x20e2
Press Ctrl+C to exit
>$ bringup
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[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
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
POWER Button pressed
[SERV NOTIF] RING_BUZZER
POWER Button released
[SSM] *** Power Fail BE ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801001
[mullion]$ bringup
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xffffffff, clock:0xffffffff
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
ofst[ 16]:err_code:0xffffffff, clock:0xffffffff
ofst[ 20]:err_code:0xffffffff, clock:0xffffffff
ofst[ 24]:err_code:0xffffffff, clock:0xffffffff
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
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:0xa0801001, clock:0x0b48869f 2005/12/31 00:00:31
[mullion]$
Press Ctrl+C to exit
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
Press Ctrl+C to exit
然後又嘗試了lasterrlog，因為前面有clearerrlog所以讀出來是Last Error Code:0xffffffff, Time:0xffffffff
>$ lasterrlog
lasterrlog
Last Error Code:0xffffffff, Time:0xffffffff
[mullion]$
Press Ctrl+C to exit
讀eepcsum
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
Press Ctrl+C to exit
沒有用bringup的指令下，打powerstate看Power的狀態
>$ powerstate
powerstate
ATA Power : OFF
PCI Power : OFF
RSX Power : OFF
XDR Power : OFF
Eurus Power : OFF
SB Power : OFF
RSX Thermal Sensor : UNAVAILABLE
BE Thermal Sensor : UNAVAILABLE
[mullion]$
Press Ctrl+C to exit
打version看syscon的版本
>$ version
version
v1.0.0_k1
[mullion]$
Press Ctrl+C to exit
然後又打errlog看了一下
>$ errlog
errlog
ofst[ 0]:err_code:0xffffffff, clock:0xffffffff
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xffffffff, clock:0xffffffff
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
ofst[ 16]:err_code:0xffffffff, clock:0xffffffff
ofst[ 20]:err_code:0xffffffff, clock:0xffffffff
ofst[ 24]:err_code:0xffffffff, clock:0xffffffff
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
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
[mullion]$
Press Ctrl+C to exit
然後打了bringup......靠~ 開機了，沒有YLOD!!!!!
馬上打shutdown關機再打errlog看有沒有error....
重複三四次後感覺好像就莫名其妙好了?!?!?!
>$ 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
Psbd_SbTransMode_Half:0x20e2
Press Ctrl+C to exit
>$ shutdown
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[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
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 0]:err_code:0xffffffff, clock:0xffffffff
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xffffffff, clock:0xffffffff
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
ofst[ 16]:err_code:0xffffffff, clock:0xffffffff
ofst[ 20]:err_code:0xffffffff, clock:0xffffffff
ofst[ 24]:err_code:0xffffffff, clock:0xffffffff
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
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
[mullion]$
Press Ctrl+C to exit
因為莫名其妙好了所以就上遊戲測試....
然後就順便破解一下(因為這樣才能看到溫度，順便調整風扇的最低轉速...)
重複做了4、5次開關機、斷電靜置一段時間再上電開機測試，都沒有問題
就真的是莫名其妙就好了~
一切都是從clearerrlog開始....感覺蠻奇怪的好像沒有抓出真正的點...
然後.....就放著給Run GT6，周一再看看狀況如何了!!!
最後，syscon真很好用....
雖然最後真不知道發生什麼事就又莫名又好了
但如果沒有用syscon看到YLOD的話應該都是直接判斷是電容或是BGA錫球脫焊吧~
根本不會知道F6001保險絲燒斷了...
上面步驟算是說的蠻清楚了，有興趣的人可以自己玩看看~~~
感覺變成了解決PS3本體的問題是一種成就
比玩遊戲更吸引人~~~
然後會不會現在連YLOD的PS3都變搶手了~
11/22 更新狀態
************************************************************************************************
該台完整的60GB殺肉機PS3在長時間RUN GT6的測試下看起來"很正常"沒有問題....
光碟機讀取頭讀取PS、PS2的遊戲有些慢但也算是還可以使用，不用換讀取頭
所以說正式宣告復活....
接下來就是另外一台殺肉機的判讀了...除了外部零件有缺之外主板都很完整
照上面的步驟來做一次，所讀到的是1002
C:\Users\UU\OneDrive\桌面\ps3syscon\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM2 CXR
>$ AUTH
Auth successful
>$ ERRLOG GET 00
00000000 A0061002 FFFFFFFF
>$ ERRLOG GET 01
00000000 A0071002 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0101002 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0801002 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0801002 27564A57
>$ ERRLOG GET 05
00000000 A0801002 27558EEF
>$ ERRLOG GET 06
00000000 A0801002 27558EB1
>$ ERRLOG GET 07
00000000 A0801002 27558EA5
>$ ERRLOG GET 08
00000000 A0801002 27558E62
>$ ERRLOG GET 09
00000000 A0801002 27558E5D
>$ ERRLOG GET 0A
00000000 A0801002 27558E55
>$ ERRLOG GET 0B
00000000 A0801002 27558E4A
>$ ERRLOG GET 0C
00000000 A0801002 27558D7F
>$ ERRLOG GET 0D
00000000 A0801002 27558D6E
>$ ERRLOG GET 0E
00000000 A0801002 27558D69
>$ ERRLOG GET 0F
00000000 A0801002 27558D60
>$ ERRLOG GET 10
00000000 A0801002 27558D59
>$ ERRLOG GET 11
00000000 A0801002 27546FCC
>$ ERRLOG GET 12
00000000 A0801002 27546FC5
>$ ERRLOG GET 13
00000000 A0801002 2754387B
>$ ERRLOG GET 14
00000000 A0801002 2754385B
>$ ERRLOG GET 15
00000000 A0801002 27543854
>$ ERRLOG GET 16
00000000 A0801002 27543842
>$ ERRLOG GET 17
00000000 A0801002 27543820
>$ ERRLOG GET 18
00000000 A0801002 27543806
>$ ERRLOG GET 19
00000000 A0801002 27543800
>$ ERRLOG GET 1A
00000000 A0801002 275437C3
>$ ERRLOG GET 1B
00000000 A0801002 27543783
>$ ERRLOG GET 1C
00000000 A0801002 27543773
>$ ERRLOG GET 1D
00000000 A0801002 27543717
>$ ERRLOG GET 1E
00000000 A0801002 275436EB
>$ ERRLOG GET 1F
00000000 FFFFFFFF 275436AE
進到內部輸入errlog也看到一堆1002
C:\Users\UU\OneDrive\桌面\ps3syscon\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM2 CXRF
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 80]:err_code:0xffffffff, clock:0x275436ae 2020/11/27 22:14:06
ofst[ 84]:err_code:0xa0801002, clock:0x275436eb 2020/11/27 22:15:07
ofst[ 88]:err_code:0xa0801002, clock:0x27543717 2020/11/27 22:15:51
ofst[ 92]:err_code:0xa0801002, clock:0x27543773 2020/11/27 22:17:23
ofst[ 96]:err_code:0xa0801002, clock:0x27543783 2020/11/27 22:17:39
ofst[100]:err_code:0xa0801002, clock:0x275437c3 2020/11/27 22:18:43
ofst[104]:err_code:0xa0801002, clock:0x27543800 2020/11/27 22:19:44
ofst[108]:err_code:0xa0801002, clock:0x27543806 2020/11/27 22:19:50
ofst[112]:err_code:0xa0801002, clock:0x27543820 2020/11/27 22:20:16
ofst[116]:err_code:0xa0801002, clock:0x27543842 2020/11/27 22:20:50
ofst[120]:err_code:0xa0801002, clock:0x27543854 2020/11/27 22:21:08
ofst[124]:err_code:0xa0801002, clock:0x2754385b 2020/11/27 22:21:15
ofst[ 0]:err_code:0xa0801002, clock:0x2754387b 2020/11/27 22:21:47
ofst[ 4]:err_code:0xa0801002, clock:0x27546fc5 2020/11/28 02:17:41
ofst[ 8]:err_code:0xa0801002, clock:0x27546fcc 2020/11/28 02:17:48
ofst[ 12]:err_code:0xa0801002, clock:0x27558d59 2020/11/28 22:36:09
ofst[ 16]:err_code:0xa0801002, clock:0x27558d60 2020/11/28 22:36:16
ofst[ 20]:err_code:0xa0801002, clock:0x27558d69 2020/11/28 22:36:25
ofst[ 24]:err_code:0xa0801002, clock:0x27558d6e 2020/11/28 22:36:30
ofst[ 28]:err_code:0xa0801002, clock:0x27558d7f 2020/11/28 22:36:47
ofst[ 32]:err_code:0xa0801002, clock:0x27558e4a 2020/11/28 22:40:10
ofst[ 36]:err_code:0xa0801002, clock:0x27558e55 2020/11/28 22:40:21
ofst[ 40]:err_code:0xa0801002, clock:0x27558e5d 2020/11/28 22:40:29
ofst[ 44]:err_code:0xa0801002, clock:0x27558e62 2020/11/28 22:40:34
ofst[ 48]:err_code:0xa0801002, clock:0x27558ea5 2020/11/28 22:41:41
ofst[ 52]:err_code:0xa0801002, clock:0x27558eb1 2020/11/28 22:41:53
ofst[ 56]:err_code:0xa0801002, clock:0x27558eef 2020/11/28 22:42:55
ofst[ 60]:err_code:0xa0801002, clock:0x27564a57 2020/11/29 12:02:31
ofst[ 64]:err_code:0xa0801002, clock:0xffffffff
ofst[ 68]:err_code:0xa0101002, clock:0xffffffff
ofst[ 72]:err_code:0xa0071002, clock:0xffffffff
ofst[ 76]:err_code:0xa0061002, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
輸入becount看總使用時數，大約開了137天
應該還算不操吧~
>$ becount
becount
Bringup : 1550 times
Shutdown: 1408 times
Power-on: 137day 11hour 02min 14sec
[mullion]$
Press Ctrl+C to exit
輸入bringup和shutdown
看到的[ERROR]: 0xa0091002
和[SSM] Power Fail RS
應該就是表明了是電容的問題了
>$ 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] fatalreq delayed.
[ERROR]: 0xa0091002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Press Ctrl+C to exit
>$ shutdown
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$
網站上寫明了1002應該就是電容的問題
後續....有時間再來更換電容和開蓋了
如果真的可以開機的話，剛好有一台被我自己開蓋不慎玩死的60GB外殼以及內部零件可以來二合一
(這台RSX還是65mm的版本，真的哭死
)這台後續有時間處理再更換電容看看~
12/06 更新
************************************************************************************************
拆開電容的外殼來看，電容四周都有輕微的焦黃
CELL端正面的電容
CELL端背面的電容
RSX端正面的電容
RSX端背面的電容
就目前我所拆過的PS3，看到的電容都有這樣的狀況
可能是因為熱的關係所以電容老化吧~
然後就按照之前的步驟，這邊就沒有再作紀錄了因為都一樣的過程...
拆電容更換坦質電容，開蓋更換散熱膏。
一切都弄好後就上電開機，也順利開機了...
殺肉機的光碟機無法讀片
所以拆了被我弄壞的PS3光碟機來直接更換光碟機PCB板再裝回去就可以使用了。
PS、PS2、PS3、CD讀片都很順暢
目前手上的PS3除了被我玩壞的那台修復不能之外
其他經手的目前看起來沒有RSX、CELL的BGA有脫焊的問題，算是運氣好吧~
手上最後一台PS3處理完畢....
結束....
--------------------------------------------------------------------------------------------------------------
1221更新
從舊電腦裡的LINE訊息找到了之前維修失敗的聯絡方式了
也拿到了之前維修的PS3就不多說了直接拆機來看
一樣用Syscon來看狀態，步驟都跟上面一樣所以就不贅述了
直接看ERRLOG
errlog
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xa0202120, clock:0xffffffff
ofst[100]:err_code:0xa0202120, clock:0xffffffff
ofst[104]:err_code:0xa0202120, clock:0xffffffff
ofst[108]:err_code:0xa0202120, clock:0xffffffff
ofst[112]:err_code:0xa0202120, clock:0xffffffff
ofst[116]:err_code:0xa0202120, clock:0xffffffff
ofst[120]:err_code:0xa0202120, clock:0xffffffff
ofst[124]:err_code:0xa0202120, clock:0xffffffff
ofst[ 0]:err_code:0xa0213013, clock:0xffffffff
ofst[ 4]:err_code:0xa0202120, clock:0xffffffff
ofst[ 8]:err_code:0xa0202120, clock:0xffffffff
ofst[ 12]:err_code:0xa0202120, clock:0xffffffff
ofst[ 16]:err_code:0xa0202120, clock:0xffffffff
ofst[ 20]:err_code:0xa0202120, clock:0xffffffff
ofst[ 24]:err_code:0xa0202120, clock:0xffffffff
ofst[ 28]:err_code:0xa0202120, clock:0xffffffff
ofst[ 32]:err_code:0xa0202120, clock:0xffffffff
ofst[ 36]:err_code:0xa0202120, clock:0xffffffff
ofst[ 40]:err_code:0xa0202120, clock:0xffffffff
ofst[ 44]:err_code:0xa0213013, clock:0xffffffff
ofst[ 48]:err_code:0xa0202120, clock:0xffffffff
ofst[ 52]:err_code:0xa0202120, clock:0xffffffff
ofst[ 56]:err_code:0xa0202120, clock:0xffffffff
ofst[ 60]:err_code:0xa0202120, clock:0xffffffff
ofst[ 64]:err_code:0xa0202120, clock:0xffffffff
ofst[ 68]:err_code:0xa0202120, clock:0xffffffff
ofst[ 72]:err_code:0xa0202120, clock:0xffffffff
ofst[ 76]:err_code:0xa0202120, clock:0xffffffff
ofst[ 80]:err_code:0xa0202120, clock:0xffffffff
ofst[ 84]:err_code:0xa0202120, clock:0xffffffff
ofst[ 88]:err_code:0xa0213013, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
出現的ERRLOG是2120和3013
2120 (HDMI)
HDMI Error (IC2502)A0202120/A0213013 error combinations are common. They appear to
be related to VDDIO. IC6301 is involved in the formation of +1.7V_MISC,
which amonge other things provides input power to the DC-DC converters
that output +1.2V_YC_RC_VDDIO, +1.5V_YC_RC_VDDA, +1.2V_SB_VDDC and
+1.2V_SB_VDDR. Lack of voltage to these DC/DC converters downstream of
IC6301 suggests F6302 has blown. A number of people have fixed these
2120/3013 errors by finding shorts at or near C6320 and replacing Fuse
F6302. But there are many other SMD nearby that might cause these fuses
to blow. So you will need to track the source of the short and fix it,
or the fuse will just blow again.
A bad thermistor (TH2501) has been reported to cause A0002120.
A0802120 and A0902120 errors may be related to the actual HDMI
transmitter (IC2502). Or they can be caused by BGA/Bump defects
affecting VDDIO, on the RSX or CELL. BGA defects on the RSX VDDIO pads
have been confirmed with a pressure test to have caused 2120 errors.
3013
BE_SPI DI/DO ERRORCELL
not communicating to syscon via SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no
output) = Possible shorts on the line, check C4001 and trailing caps.
Possible dead CPU?
Another user had one on a CPU he damaged while deliding.
A0212120/A0213013 error combinations are common. They appear to
be related to VDDIO. IC6301 is involved in the formation of +1.7V_MISC,
which among other things provides input power to the DC-DC converters
that output +1.2V_YC_RC_VDDIO, +1.5V_YC_RC_VDDA, +1.2V_SB_VDDC and
+1.2V_SB_VDDR. Lack of voltage to these DC/DC converters downstream of
IC6301 suggests F6302 has blown. A number of people have fixed these
2120/3013 errors by finding shorts at or near C6320 and replacing Fuse
F6302. But there are many other SMD nearby that might cause these fuses
to blow. So you will need to track the source of the short and fix it,
or the fuse will just blow again.
One person reported A0202120/A0213013 when his CPU substrate (interposer) was cracked in half by a failed delid attempt.
Through sabotage testing is was found that disabling +1.2V_YC_RC_VDDIO caused A0213013.
Also through sabotage testing, it was found that when L6305 is
removed it cut's off +1.8V_RSX_FBVDDQ (VRAM voltage). It caused a 10x
A0202120 & 1x A0213013 error combo.
照上面的描述看起來應該只是F6302保險絲因為後端短路所以燒斷了
檢查一下線路及位置，F6302確實已經呈現斷路的狀態了
再檢查後端電路...後端的MOSFET應該沒有問題
F6302後面接的C6320和C6322這兩棵MLCC 22UF的電容有短路
移除之後就沒有短路了...所以就從殺肉的板子上拆零件來更換
然後上電測試，本來想說又成功了一台
結果一樣YLOD....
看了一下SYSCON的ERRLOG，結果出現了恐怖的3034!!!!!
errlog
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xa0202120, clock:0xffffffff
ofst[108]:err_code:0xa0202120, clock:0xffffffff
ofst[112]:err_code:0xa0202120, clock:0xffffffff
ofst[116]:err_code:0xa0202120, clock:0xffffffff
ofst[120]:err_code:0xa0202120, clock:0xffffffff
ofst[124]:err_code:0xa0202120, clock:0xffffffff
ofst[ 0]:err_code:0xa0202120, clock:0xffffffff
ofst[ 4]:err_code:0xa0213013, clock:0xffffffff
ofst[ 8]:err_code:0xa0202120, clock:0xffffffff
ofst[ 12]:err_code:0xa0202120, clock:0xffffffff
ofst[ 16]:err_code:0xa0202120, clock:0xffffffff
ofst[ 20]:err_code:0xa0202120, clock:0xffffffff
ofst[ 24]:err_code:0xa0202120, clock:0xffffffff
ofst[ 28]:err_code:0xa0202120, clock:0xffffffff
ofst[ 32]:err_code:0xa0202120, clock:0xffffffff
ofst[ 36]:err_code:0xa0202120, clock:0xffffffff
ofst[ 40]:err_code:0xa0202120, clock:0xffffffff
ofst[ 44]:err_code:0xa0202120, clock:0xffffffff
ofst[ 48]:err_code:0xa0213013, clock:0xffffffff
ofst[ 52]:err_code:0xa0202120, clock:0xffffffff
ofst[ 56]:err_code:0xa0202120, clock:0xffffffff
ofst[ 60]:err_code:0xa0202120, clock:0xffffffff
ofst[ 64]:err_code:0xa0202120, clock:0xffffffff
ofst[ 68]:err_code:0xa0202120, clock:0xffffffff
ofst[ 72]:err_code:0xa0202120, clock:0xffffffff
ofst[ 76]:err_code:0xa0202120, clock:0xffffffff
ofst[ 80]:err_code:0xa0202120, clock:0xffffffff
ofst[ 84]:err_code:0xa0202120, clock:0xffffffff
ofst[ 88]:err_code:0xa0202120, clock:0xffffffff
ofst[ 92]:err_code:0xa0213013, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
應該就是RSX的問題了....
但是，我還沒開蓋有可能只是過熱而已
往好的方面想，所以就又花了些時間來開蓋
在開蓋的時候發現RSX周圍有好像回焊的助焊劑的痕跡...
感覺有些不妙，所以詢問了一下
當事人是說在之前找我弄電容前有請同事幫忙做回焊的動作.....
基本上如果只做回焊應該是沒有用的，可能需要拿下來重新植球換上去
有40nm的RSX也可以換上去!!!!(不過這工程比較大，好像還要改FW裡的東西和跳電阻)
回頭望下被我玩壞的40nm PS3厚機...
下面兩張圖可以看的出來有手術的痕跡
我沒有BGA紅外線返修拆焊設備，所以肯定不是我弄得....
而且出現3034了....除了換BGA之後應該別無他法了
然後下面這張感覺好像有看到BGA下面有個微笑曲線的感覺...
也怕有變形
所以在開蓋之後也覺得應該是沒有辦法了，但該做的還是要做
總是有機會的，所以開完蓋後重上散熱膏組裝來開機
>$ bringup
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
Psbd_SbTransMode_Half:0x20e2
Press Ctrl+C to exit
>$ shutdown
[POWERSEQ] Error : BitTraining BE:RRAC:RX0: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]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
果然開機還是出現3034
看errlog也是在一次出現3034
>$ errlog
errlog
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xa0202120, clock:0xffffffff
ofst[112]:err_code:0xa0202120, clock:0xffffffff
ofst[116]:err_code:0xa0202120, clock:0xffffffff
ofst[120]:err_code:0xa0202120, clock:0xffffffff
ofst[124]:err_code:0xa0202120, clock:0xffffffff
ofst[ 0]:err_code:0xa0202120, clock:0xffffffff
ofst[ 4]:err_code:0xa0213013, clock:0xffffffff
ofst[ 8]:err_code:0xa0202120, clock:0xffffffff
ofst[ 12]:err_code:0xa0202120, clock:0xffffffff
ofst[ 16]:err_code:0xa0202120, clock:0xffffffff
ofst[ 20]:err_code:0xa0202120, clock:0xffffffff
ofst[ 24]:err_code:0xa0202120, clock:0xffffffff
ofst[ 28]:err_code:0xa0202120, clock:0xffffffff
ofst[ 32]:err_code:0xa0202120, clock:0xffffffff
ofst[ 36]:err_code:0xa0202120, clock:0xffffffff
ofst[ 40]:err_code:0xa0202120, clock:0xffffffff
ofst[ 44]:err_code:0xa0202120, clock:0xffffffff
ofst[ 48]:err_code:0xa0213013, clock:0xffffffff
ofst[ 52]:err_code:0xa0202120, clock:0xffffffff
ofst[ 56]:err_code:0xa0202120, clock:0xffffffff
ofst[ 60]:err_code:0xa0202120, clock:0xffffffff
ofst[ 64]:err_code:0xa0202120, clock:0xffffffff
ofst[ 68]:err_code:0xa0202120, clock:0xffffffff
ofst[ 72]:err_code:0xa0202120, clock:0xffffffff
ofst[ 76]:err_code:0xa0202120, clock:0xffffffff
ofst[ 80]:err_code:0xa0202120, clock:0xffffffff
ofst[ 84]:err_code:0xa0202120, clock:0xffffffff
ofst[ 88]:err_code:0xa0202120, clock:0xffffffff
ofst[ 92]:err_code:0xa0213013, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
所以基本上沒有BGA拆焊台的我只能宣告這台PS3 GG了...
沒辦法救回來這台
所以只能當殺肉機了
但....因為電玩店給我兩台PS3殺肉機有被我修起來，所以給了他一台....
只是青春的紀錄就只能放水流了
多年的維修就此結案了~
