truemaster
Member
have a good gaming on that cecha friend
it is fully working hdmi? ps2 games?
it is fully working hdmi? ps2 games?
Workz_777
Senior Member
Workz_777
Senior Member
Regarding 40nm Frankie... for SEM-001 which has the BD35231HFN fixed 1.2V (output) voltage regulator for RSX, i was thinking of replacing it with it's brother, the BD35230HFN which is fixed at 1.0V (output), apart from the fixed outputs they are almost identical, and both are case/package HSON-8. Also, no need for added resistors R1 + R2 to set the voltage output like with BD3504FVM-TR.
Although it's not the ideal target of 0.95V, still though 1.0V would be better than 1.2V. What do you guys think?
I did however buy 50 x BD3504FVM-TR (MSOP8) recently, but after realized these are for COKs 40nm Frankies, opps. When / if the BD3504FVM-TR arrive i would be more than happy to sell them for cheap, because i have no need for them. If anyone wants them let me know, i'd be happy to sell them at a loss just to help get some of the money back i paid.
Although it's not the ideal target of 0.95V, still though 1.0V would be better than 1.2V. What do you guys think?
I did however buy 50 x BD3504FVM-TR (MSOP8) recently, but after realized these are for COKs 40nm Frankies, opps. When / if the BD3504FVM-TR arrive i would be more than happy to sell them for cheap, because i have no need for them. If anyone wants them let me know, i'd be happy to sell them at a loss just to help get some of the money back i paid.
...but, but, but, oh man
Yeah, yeah, I'll get you taken care of eventually if nobody else does. Just remember, the cheap option I'll be doing as a favor for a few people will be board only, no guarantee or warranty.
Last edited:
have a good gaming on that cecha friend
Won't have time to get it back together and actually play a game on it until the weekend, I'll report back then.
Mine (KTE-001) is M130 on the left by the RSX, and M132 on the right.
marciolsf
Member
Definitely interested in the cheap option, even without guarantee/warranty! It think it's 100% fair all around.
sandungas
Developer
With the same "M" logo, made by mitsumi ?
It seems the mitsumi ICs are labeled in a bit weird way, they have 2 rows of text but the row at top varyes, it seems to be dependant of the manufacturing date, or some internal identifyer for the production batches
The product identifyer is the row at bottom, so the IC next to RSX that generates the VDDR power line is a Mitsumi 810X
*The other IC mentioned by felix that feeds the HDMI controller is a Mitsumi 348A, but is not related with the other, could be very different
cfreddykrueger
Member
Yo, does this look a little small to anyone else?
So....still don't know why I couldn't get those modchips working, but this fired right up with the syscon changes! Thanks to everyone that's been working on this so hard. @M4j0r @sandungas @RIP-Felix and anyone else I'm forgetting.
I'm still pretty much on a work sabbatical for a few months, I just couldn't help myself since I had a 40nm sitting on the shelf. Once I really get back to work, I can do a few boards for devs/longtime members here for free/cheap if you provide the parts. Anyone else, suck it, you're paying full price for a whole, finished system! Maybe I'll set a discount for forum folks that predate this post...
I look forward to seeing you post these on your eBay! I'll pay for this service whenever you get back to work. I have an A01 that's never been open and is not in use. I'm in the "anyone else" category because I've been following the progress of this thread but haven't contributed any knowledge to it.
Sent from my iPhone using Tapatalk
RIP-Felix
Senior Member
PS3 #13 - Huston we Have a Problem!
(...learning from disaster!)
(...learning from disaster!)
This one was described as, "For Parts Or Repair (CBEH1000)." TIM was replaced, flux residue indicates RSX was reflowed/reballed. Errorlog shows 3034, 1701, and 1802 in indicating RSX BGA defect in 2012. It lasted 13 months before another 3034 in 2013. But just the one. Usually you see a string of new errors occurring every 3 months or so, indicating it was sold, sat, tested, then sold again. But this one didn't show that. Whoever sold it to me described it wrong and didn't test it. Clearly they were disinterested in the console.
After I received it, the console turned on and overheated because I wasn't expecting it to work! I applied TIM and tested it many times to get voltage readings from a working console. It never experienced a YLOD in all of those idle tests. However, it did YLOD in XMB after a few minutes. I setup WIFI and checked the FW ver (4.11), then it YLOD's after maybe 5 minutes of being on. So it was a cold-start YLOD.
It forced a video reset every time it YLOD's. Sometimes it errors quick with A0801802. Most of the time it errors in 30s-5min with 1701/1601. BE Attention signal received because of a livelock condition. These indicate RSX BGA defect. It does have 255 days of use on it, which is on the higher end of the time frame we expect to see a BGA defect. So I thought it would be a good candidate for a 40nm RSX...
Let's do this!
Yesterday I made my first attempt to frankie this beast. I had one NOS 40nm RSX left. I decided to leave the Lead-Free balls on because I'm layze and didn't want to reball the chip. And honestly, lead free is fine for the 40nm. It just requires more heat to install. I don't thaink that's an issue, since I would have to use mouch more heat to ball the chip with lead balls anyway. It probly is better for the chip not to put it through that and just install it as is. So that's what I did.
Code:
Microsoft Windows [Version 10.0.19044.1526]
(c) Microsoft Corporation. All rights reserved.
C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM5 CXRF
>$ AUTH
Auth successful
>$ w 3242 03 61 82 80 01 91
w 3242 03 61 82 80 01 91
w complete!
[mullion]$
>$ w 3254 21 EC
w 3254 21 EC
w complete!
[mullion]$
>$ w 348B 8B
w 348B 8B
w complete!
[mullion]$
>$ w 34AF 8B
w 34AF 8B
w complete!
[mullion]$
>$ eepcsum
eepcsum
sum:0xee10
Addr:0x000032fe should be 0xffff64a7
sum:0x1800
Addr:0x000034fe should be 0x5915
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ w 32fe a7 64
w 32fe a7 64
w complete!
[mullion]$
>$ w 34fe 15 59
w 34fe 15 59
w complete!
[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x64a7
Addr:0x000034fe should be 0x5915
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
>$ 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
>$
[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)
[mullion]$
>$ 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:0xa0403034, clock:0xffffffff
[mullion]$
>$Now the RSX I used was a CXD5301 and I did write w 3254 21 EC. So that should be kosher. I took this to mean there is a BGA defect still. Since the error was complaining about the BE, and I was confident in my RSX reflow, I thought the heat must have popped a CPU BGA.
This morning I reflowed the CPU. No @vyktormvmpay25, I didn't reball the CPU. I just did a quick and dirty little reflow. However, it was a high quality reflow. I had cleaned the board thoroughly after the RSX install, running IPA underneath both the RSX and CELL for long enough I'm sure it was clean. Then I used ample flux and nudged the chip to be sure it flowed. It did and I'm sure the CELL is good now. It was working before, so if a BGA popped, it was fresh and didn't have time to get oxidized. So this reflow should be strong.
However, I didn't put aluminum tape all around the CELL during the reflow and some of the resistors for the thermal monitor took a swim. So I had to fix them...
Code:
Microsoft Windows [Version 10.0.19044.1526]
(c) Microsoft Corporation. All rights reserved.
C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM5 CXRF
>$ AUTH
Auth successful
>$ errlog
errlog
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:0xa0403034, clock:0xffffffff
ofst[ 4]:err_code:0xa0403034, clock:0xffffffff
ofst[ 8]:err_code:0xa0213013, clock:0xffffffff
ofst[ 12]:err_code:0xa0213013, clock:0xffffffff
ofst[ 16]:err_code:0xa0213013, clock:0xffffffff
[mullion]$
>$ 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 -> 0302
[SSM] PowSeq Fail : Detected !
[SSM] state: 0302 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0213013
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[mullion]$
>$ lasterrlog
lasterrlog
Last Error Code:0xa0213013, Time:0xffffffff
[mullion]$
>$I attached the bottom 2 resistors onto the pad wrong...lol! So I guess now we know what happens when you do that. R1173 is a 10k resistor. This supplies voltage to BE_SPI_CLK from +1.2V_MC2_VDDIO. R1014 is a 0 ohm resistor for BE_SPI_CLK (clock). So error 3013 is a missing SPI voltage, which jives with the step number of the error. Step# 21 is when the CELL is first initialized. It needs it's SPI clock to do pretty much anything. @Kleon1876 had a 21 3013 when he damaged a CPU trace while deliding. It caused a BE_SPI DI/DO ERROR. Many others have had 3013 errors. Usually associated with Reflows or Mods involving the CPU (eraser mod).
One thing that's interesting about this is that the bottom resistor is 0 ohms (basically a fuse). While I was re-installing it I managed to burn it out. It failed open. I had to replace it with one from a donor board. However, that's something to check on consoles that have 3013, because the purpose of a 0 ohms resistor is to blow out and prevent damage to the CELL. It's possable that's what happens in console's with this error.
So that's one silver lining to this screw up on my part. I always learn more from mistakes than I do from successes.
Anyway I fixed those resistors, tested the console again and...
Code:
Microsoft Windows [Version 10.0.19044.1526]
(c) Microsoft Corporation. All rights reserved.
C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM5 CXRF
>$ AUTH
Auth successful
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
>$ btingup
btingup
*** Unknown Command ***
[mullion]$
>$ 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
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SERV THERM] Thermal Error Detected!
[SSM] fatalreq delayed.
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[ERROR]: 0xa0401200
[POWERSEQ] Error : BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] *** Thermal Alert (ZONE) ***
[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)
[mullion]$
>$ errlog
errlog
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:0xa0401200, clock:0xffffffff
ofst[ 4]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
>$ shutdown
[ADT7461] *** alert flags still stay high(sts_reg:96) ***
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
>$ 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
[SERV THERM] Thermal Error Cleared!
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SERV THERM] Thermal Error Detected!
[SSM] fatalreq delayed.
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[ERROR]: 0xa0401200
[POWERSEQ] Error : BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] *** Thermal Alert (ZONE) ***
[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)
[mullion]$
>$ reelog
reelog
*** Unknown Command ***
[mullion]$
>$ errlog
errlog
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:0xa0401200, clock:0xffffffff
ofst[ 4]:err_code:0xa0403034, clock:0xffffffff
ofst[ 8]:err_code:0xa0401200, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
>$What I wasn't expecting was this 40 1200. That's a special kind of BE thermal error...
Code:
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SERV THERM] Thermal Error Detected!
[SSM] fatalreq delayed.
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[ERROR]: 0xa0401200Turns out that other resistor I didn't have properly soldered wasn't making a connection to the pad. R1107 is STI_THERMAL1. It's part of a differential pair (+/-) for the thermal monitor's external thermal couple, which connects to a TC inside the CELL to monitor die temps. Without that resistor properly soldered the thermal monitor couldn't setup the external TC temperature information and went into an error state. SYSCON records it as "NO COMMTAG SPECIFIED!" and issues an 40 1200. 40 means that it occured during BitTraining, when SPI connections are checked and calibrated. Aparently this is when that's done.
I'm learning alot form this screw up!
Ok, so I fix that and try again...
Code:
Microsoft Windows [Version 10.0.19044.1526]
(c) Microsoft Corporation. All rights reserved.
C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM5 CXRF
>$ AUTH
Auth successful
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
>$ 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
[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)
[mullion]$
>$ 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:0xa0403034, clock:0xffffffff
[mullion]$
>$So the CPU reflow was a bust. I guess the RSX reflow didn't go as good as I thought. The only thing I could thik it could be is a cold BGA joint. So I decided to reflow the RSX. This MB has really been through a beating at this point. Long story short...
Code:
Microsoft Windows [Version 10.0.19044.1526]
(c) Microsoft Corporation. All rights reserved.
C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM5 CXRF
>$ AUTH
Auth successful
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
>$ 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 -> 0302
[SSM] PowSeq Fail : Detected !
[SSM] state: 0302 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
>$
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0213013
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[mullion]$
>$ errlog
errlog
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:0xa0202120, 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:0xa0213013, clock:0xffffffff
[mullion]$
>$Little jerks merged! Grrr...
At least we know what happens when VDDIO dies! So that finally solves the 2120 / 3013 error combo. Either VDDIO balls have merged in a failed relow/reball attempt, the RSX VDDIO has died on the RSX itself (or BGA defect), or an IC/SMD in the line that supplies RSX_VDDIO has failed. We can put that one to bed!
So yeah, frankie's got a 40! But a lot of good it does him with the VDDIO short to ground. Obviously, I need to reball this RSX again. What a PITA! And this board has been through 4 reflow cycles already, at least 5 if you count it's history before I got it. IDK how much more of this it can take!
...to be continued!
Last edited:
DeadEnd
Senior Member
Just for future reference, if you install a new RSX and you get errors such as : BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS (or probably any RX_Status errors for that matter) then most likely your balls either merged or didn't solder properly somewhere. You didn't need to touch Cell. Victor might disagree, but that's his opinion. Seeing "BE" in the error also isn't a clue towards Cell. It's almost never Cell. I also don't recommend using lead free, they require a lot of heat which is bad for RSX (ram bleed risk) and the board . I also don't solder them with IHS on. But if you really must , at least use support SMD caps in the corners of the chip otherwise balls will merge under the weight. The smd caps must be correct height
Last edited:
sandungas
Developer
I find interesting in one of the "shutdown" commands you had a warning i never seen before
Is mentioning the name of the thermal monitor ADT7461... so... i opened in a hexeditor a ROM dump of the first reltail syscon CXR713120-201GB to search for that texts, there are 2 messages related with them:
As you can see the first sentence ends with a %x because it could vary, it seems to be some kind of register for an alert flag, whatever you did with the resitors was identifyed by syscon as an alert signal, the value 96 seems to be an identifyer of the register (inside the thermal monitor ?)
Anyway, the most weird detail of what im talking about is the thermal monitors are documented in wiki as model ADT7467 (instead of ADT7461)
https://www.psdevwiki.com/ps3/Thermal#Temperature_Monitors
But... that doesnt means that your thermal monitor is really an ADT7461, because it could happen that syscon is not detecting the exact model accuratelly... you know if ADT7461 and ADT7467 are fully compatible with each other it could happen the software engineers that wrote the syscon firmware just added the name ADT7461 and later they didnt cared about adding the other names
Code:
>$ shutdown
[ADT7461] *** alert flags still stay high(sts_reg:96) ***
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)Is mentioning the name of the thermal monitor ADT7461... so... i opened in a hexeditor a ROM dump of the first reltail syscon CXR713120-201GB to search for that texts, there are 2 messages related with them:
Code:
[ADT7461] *** alert flags still stay high(sts_reg:%x) ***
[ADT7461] *** alert flags cleared ***Anyway, the most weird detail of what im talking about is the thermal monitors are documented in wiki as model ADT7467 (instead of ADT7461)
https://www.psdevwiki.com/ps3/Thermal#Temperature_Monitors
But... that doesnt means that your thermal monitor is really an ADT7461, because it could happen that syscon is not detecting the exact model accuratelly... you know if ADT7461 and ADT7467 are fully compatible with each other it could happen the software engineers that wrote the syscon firmware just added the name ADT7461 and later they didnt cared about adding the other names
RIP-Felix
Senior Member
Either it's a mistake on the wiki, or there are variants. I have ADT7461 data sheet in my datasheets folder for the thermal monitors. I label them by IC number so I can quickly pull them up. And its the data sheet for ADT7461. The monitor pictured above has the indicator "T1B" which according to the datasheet is ADT7461ARM or ADT7461ARMZ.
EDIT:
It's a typo. Above it they are listed as 7461, but in the table it's written wrong.
_XBrD4shDOE_808_
Member
First of all sorry for not replying sooner, I was busy the last few days.
So if I understand correctly, Syscon is a memory chip, where most of it is "one-time recording", as in a CD after being burned in a recorder, where they can only be read but cannot have their data changed.
But we also have parts where we can both read and write, like on an HDD, where data like the error codes are written to this part, and this part is called the EEPROM.
Following this logic, the only way to maybe write on the chip would be to buy one of this Syscon that was never recorded and write on it and put it on the new board, but it's worth it to simply change it
RIP-Felix
Senior Member
There is a rewritable model we were considering back when we thought we would need to flasth changes a new chip for the frankie. That's why we thought it would be more difficult to do than the ORBIS. But now all we have to do is make a few writes to the eeprom (writable portion) to train the new RSX.
Ah, yeah, got it now. Mine are 810 and 348, yes. I thought the date code would be the second number, and the company logo would be next to the part number. Weird that we have any matching date codes from only a few boards, there's usually so goddamn many. I could go in my scrap pile and probably only find one or two matching.
Last edited:
And just to add my experience to the pile, I do not rework with IHS in place. I don't think there's any IPC guidance on this subject, but I've got probably a thousand reballs under my belt on a variety of systems. Specifically with the 90nm PS3, the solder bleed is real, and rework with the IHS in place directs more heat through the RAM chips to make it worse. I also agree with the extra weight likely being the cause of those bridged balls.
It could also be too much flux leading to a little bit of chip surfing. I just kind of know how much to use at this point, it can't really be explained (1 grain of rice for putting balls on chip, 6 grains of rice for putting chip on board?). So, two solutions: one, you can make tiny loops of kapton tape that stick up around the sides of the chip to keep it from sliding around. Or two, Zephyrtronics makes a flux specifically for BGA rework that is formulated to prevent hydroplaning. Something about the surface tension or voodoo or I don't know. Whatever, just check it out: http://www.zeph.com/bga_flux.htm
Personally, I use Kingbo for everything. Fraud is rampant and you're likely to end up with vaseline, but if you buy 3 jars at once from 3 different sources, you'll end up with at least one good batch and it'll still be half the price of Amtech or Zephytronics. Test it out by leaving a big blob of solder on the end of your iron, wait until it oxidizes and turns to slag, then touch it with a dab of the flux. If it instantly turns back in to sweet delicious shiny solder, you're good to go.
It could also be too much flux leading to a little bit of chip surfing. I just kind of know how much to use at this point, it can't really be explained (1 grain of rice for putting balls on chip, 6 grains of rice for putting chip on board?). So, two solutions: one, you can make tiny loops of kapton tape that stick up around the sides of the chip to keep it from sliding around. Or two, Zephyrtronics makes a flux specifically for BGA rework that is formulated to prevent hydroplaning. Something about the surface tension or voodoo or I don't know. Whatever, just check it out: http://www.zeph.com/bga_flux.htm
Personally, I use Kingbo for everything. Fraud is rampant and you're likely to end up with vaseline, but if you buy 3 jars at once from 3 different sources, you'll end up with at least one good batch and it'll still be half the price of Amtech or Zephytronics. Test it out by leaving a big blob of solder on the end of your iron, wait until it oxidizes and turns to slag, then touch it with a dab of the flux. If it instantly turns back in to sweet delicious shiny solder, you're good to go.
Last edited:
sandungas
Developer
The technical name is a "microcontroller", lets say... it have a CPU to run programs, the ROM is to store the bootloader and the operative system and some programs, and the EEPROM is to store the configuration of some of that programs, and many other settings passed to the PS3 firmware to lock/unlock features of the PS3First of all sorry for not replying sooner, I was busy the last few days.
So if I understand correctly, Syscon is a memory chip, where most of it is "one-time recording", as in a CD after being burned in a recorder, where they can only be read but cannot have their data changed.
But we also have parts where we can both read and write, like on an HDD, where data like the error codes are written to this part, and this part is called the EEPROM.
Following this logic, the only way to maybe write on the chip would be to buy one of this Syscon that was never recorded and write on it and put it on the new board, but it's worth it to simply change it
The programs uses to run as services at the background, you can start/stop them
It also makes an intensive use of concepts like "virtual" or "emulated" memory, and "layered filesystems" (thought it doesnt uses filesystems) to protect areas and to prevent bricks
Everytime i think in it comes to mind the chips from the routers, it have many things in common with the routers
Anyway, for backup purposes we are covered because we can backup all the areas that are sensitive to be corrupted by user mistakes
The list in the wiki link from my previous post only contains the chips i considered that could be "voltage regulators" when i was trying to map the syscon pinout in a CECH-25xx JTP-001 or JSP-001 motherboard
https://www.psdevwiki.com/ps3/Talk:Regulators#Mitsumi_348A_.28voltage_regulator.29
It would be interesting to see which ones was used in a CECH-21xx because thats the first PS3 model with a 40nm RSX
Aand CECH-20xx too (the last 65nm RSX) to compare them, i guess CECH-21xx is the first time they started using the mitsumi 810X
If you take a extensive look at your crap pile keep attention at the other numbers at top just for curiosity sake, it seems yours and felix was around 132 from a KTE-001 motherboard CECH-30xx (whatever that means, maybe a datecode), and mines was 037 because was a CECH-25xx (bit older than CECH-30xx)
I was not able to map the pinout of the mitsumi 810X though, most of the pins goes to a VIA and dissapears (and probably emerges under RSX) but the motherboard was working and i didnt removed the RSX to check where is connected each pin of the mitsumi 810X
My goal at that point was to find the connections in between syscon and other motherboard components, the bastard have connections to everywhere like a spiderweb
While you are at it looking at your scrap pile, please take a fast look at the thermal monitors too, i been updating the wiki page right now to clarify the part numbers and the way how are labeled in the big table at top here
https://www.psdevwiki.com/ps3/Thermal#Temperature_Monitors
The ones manufactured by texas instrument are straightforward because the part numer and the label matches
But the others manufactured by onsemi and another company named "analog devices" sucks because are labeled with garbage (as far i know only posible names are either T1L or T1B), and that names are very different than the real part number
I have doubts about that labels, is a long story, onsemi and "analog devices" was 2 different companies, at some point onsemi bought "analog devices" company, but they kept manufactuing this temperature monitors with the onsemi labeling, later they added the logo of "analog devices" that is like a "play" key, but is the same component, and still they refused to label it properly
The only way to clarify all this mess is if some of you takes a bunch of motherboards and try to see in how many different ways was labeled
Last edited:
DeadEnd
Senior Member
My style is desolder with IHS in place, but solder to the board without it. Also I recommend Chip Quik flux. It works great, doesn't smell too terrible and is highly affordable https://www.chipquik.com/store/index.php?cPath=300
RIP-Felix
Senior Member
I was not able to map the pinout of the mitsumi 810X though, most of the pins goes to a VIA and dissapears (and probably emerges under RSX) but the motherboard was working and i didnt removed the RSX to check where is connected each pin of the mitsumi 810X
My goal at that point was to find the connections in between syscon and other motherboard components, the bastard have connections to everywhere like a spiderweb
I took this picture cuz I thought you might want it @sandungas. Its from that KTE-001...
It's nice just to see how the traces are laid out under the RSX.
Similar threads
-
-
PS3 PS3 CECHA RSX Swap (40nm) – JP Limited – SYSCON Patch, VDDC Mod – Need Detailed Help- Started by jw0710
- Replies: 4
-
-
