Anyone can repair a DECR-1000A?

N

NiQ

Senior Member
I was idiot enough to trip over it and it fell and one of the hard drives popped out and while I managed to slide it in just fine, the system won't recognize it at all and won't boot...
I've already ruled out the possibility of the hard drive being faulty by swapping it with known working drives and nada... also popped the case open, couldn't find anything wrong.
I'm kinda out of ideas at this point and these units aren't too common so I don't want to give up on it easily.

Is there anyone here who can help me repair it or who knows someone who can help?
Will pay if needed.
 
NiQ said:
I was idiot enough to trip over it and it fell and one of the hard drives popped out and while I managed to slide it in just fine, the system won't recognize it at all and won't boot...
I've already ruled out the possibility of the hard drive being faulty by swapping it with known working drives and nada... also popped the case open, couldn't find anything wrong.
I'm kinda out of ideas at this point and these units aren't too common so I don't want to give up on it easily.

Is there anyone here who can help me repair it or who knows someone who can help?
Will pay if needed.
Click to expand...
The console boot log from the Target Manger would help diagnosing the problem. Can you provide that?
 
NiQ said:
I was idiot enough to trip over it and it fell and one of the hard drives popped out and while I managed to slide it in just fine, the system won't recognize it at all and won't boot...
I've already ruled out the possibility of the hard drive being faulty by swapping it with known working drives and nada... also popped the case open, couldn't find anything wrong.
I'm kinda out of ideas at this point and these units aren't too common so I don't want to give up on it easily.

Is there anyone here who can help me repair it or who knows someone who can help?
Will pay if needed.
Click to expand...

You could probably flash the firmware via TM (ProDG), the reason why it's not booting is likely due to missing/corrupted region that's on your drive.
 
M4j0r said:
The console boot log from the Target Manger would help diagnosing the problem. Can you provide that?
Click to expand...
Nothing is displayed. The only console output I get is
```CP v1.3.1
Power is OFF```
Which is the usual output when connecting to it when it's switched off. Pressing the power button does not result in anything being printed, like zero bytes received.

Joonie said:
You could probably flash the firmware via TM (ProDG), the reason why it's not booting is likely due to missing/corrupted region that's on your drive.
Click to expand...
It's not possible to flash from Target Manager since it doesn't reach the boot stage which allows that.
 
NiQ said:
Nothing is displayed. The only console output I get is
```CP v1.3.1
Power is OFF```
Which is the usual output when connecting to it when it's switched off. Pressing the power button does not result in anything being printed, like zero bytes received.
Click to expand...
Ok, if you want to dump the syscon error log you don't need to do any soldering.
You can relay the Syscon serial port from the DECR to your PC over the network.

First, you need to exploit the CP - you can use the "root_cp.py" script for that: https://github.com/jevinskie/ps3-decr-stuff/blob/master/root_cp.py .
After that, open a telnet shell which connects to the CP, the username is "rt" with no password.
Also connect a FTP client to the CP, port 21 with username "rt" and no password.
Transfer the files "ser2net" and "ser2net.conf" in the (default) root user directory on the CP via the FTP client.
Then run "chmod +rx ser2net" and "./ser2net -c ser2net.conf" in the telnet shell.

This maps the Syscon serial port to the network.
The changes aren't persistent, if the CP is rebooted you need to follow the previous steps again.
Now you need to connect to it and map it to a local serial port on your PC.

For Windows: https://gist.github.com/DraTeots/e0c669608466470baa6c#client
( use this com0com version if you're on Windows 8.1 or later: https://sourceforge.net/projects/co...0/com0com-2.2.2.0-x64-fre-signed.zip/download )
For Linux: https://gist.github.com/DraTeots/e0c669608466470baa6c#linux-client

After the local serial port is available (in the Windows sample ""COM20"), you can connect to it using the normal syscon script (https://www.psdevwiki.com/ps3/Talk:..._squeasy_way_.28UART.29_.28CXR.2FCXRF.2FSW.29) and run the errlog command (the Syscon in the DECR runs by default in internal (CXRF) mode and has no external mode).
Please note that the terminal which runs the "com2tcp-rfc2217.bat" has to stay open during the script operation else the port isn't actively mapped.
 

Attachments

NiQ said:
Nothing is displayed. The only console output I get is
```CP v1.3.1
Power is OFF```
Which is the usual output when connecting to it when it's switched off. Pressing the power button does not result in anything being printed, like zero bytes received.


It's not possible to flash from Target Manager since it doesn't reach the boot stage which allows that.
Click to expand...

I remember missing flash region turns the console itself off but you should still be able to access the recovery menu, maybe from there you could flash your pup via USB unless it's bricked, if so then you should follow @M4j0r's suggestion
 
M4j0r said:
Ok, if you want to dump the syscon error log you don't need to do any soldering.
You can relay the Syscon serial port from the DECR to your PC over the network.

First, you need to exploit the CP - you can use the "root_cp.py" script for that: https://github.com/jevinskie/ps3-decr-stuff/blob/master/root_cp.py .
After that, open a telnet shell which connects to the CP, the username is "rt" with no password.
Also connect a FTP client to the CP, port 21 with username "rt" and no password.
Transfer the files "ser2net" and "ser2net.conf" in the (default) root user directory on the CP via the FTP client.
Then run "chmod +rx ser2net" and "./ser2net -c ser2net.conf" in the telnet shell.

This maps the Syscon serial port to the network.
The changes aren't persistent, if the CP is rebooted you need to follow the previous steps again.
Now you need to connect to it and map it to a local serial port on your PC.

For Windows: https://gist.github.com/DraTeots/e0c669608466470baa6c#client
( use this com0com version if you're on Windows 8.1 or later: https://sourceforge.net/projects/co...0/com0com-2.2.2.0-x64-fre-signed.zip/download )
For Linux: https://gist.github.com/DraTeots/e0c669608466470baa6c#linux-client

After the local serial port is available (in the Windows sample ""COM20"), you can connect to it using the normal syscon script (https://www.psdevwiki.com/ps3/Talk:..._squeasy_way_.28UART.29_.28CXR.2FCXRF.2FSW.29) and run the errlog command (the Syscon in the DECR runs by default in internal (CXRF) mode and has no external mode).
Please note that the terminal which runs the "com2tcp-rfc2217.bat" has to stay open during the script operation else the port isn't actively mapped.
Click to expand...
Thank you for the detailed instructions!
Where can I find the logs? The "errlog" command seems to do nothing...

EDIT: NVM found my mistake, here's the log:


C:\Temp>C:\Python36\python.exe sysconauth.py COM4 CXRF
> errlog
(PowerOff State)
errlog
ofst[ 8]:err_code:0xffffffff, clock:0x15388fd3 2011/04/13 16:46:11
ofst[ 12]:err_code:0xa0801001, clock:0x15a2fb2f 2011/07/03 10:04:31
ofst[ 16]:err_code:0xa0901004, clock:0x15a2fb2f 2011/07/03 10:04:31
ofst[ 20]:err_code:0xa0801001, clock:0x167cabad 2011/12/15 12:59:25
ofst[ 24]:err_code:0xa0901004, clock:0x167cabae 2011/12/15 12:59:26
ofst[ 28]:err_code:0xa0902020, clock:0x167cabae 2011/12/15 12:59:26
ofst[ 32]:err_code:0xa0801001, clock:0x18805df8 2013/01/09 16:57:28
ofst[ 36]:err_code:0xa0901004, clock:0x18805df8 2013/01/09 16:57:28
ofst[ 40]:err_code:0xa0801001, clock:0x188801ff 2013/01/15 12:03:11
ofst[ 44]:err_code:0xa0801004, clock:0x188801ff 2013/01/15 12:03:11
ofst[ 48]:err_code:0xa0801001, clock:0x1a10d6fc 2013/11/09 11:20:28
ofst[ 52]:err_code:0xa0901004, clock:0x1a10d6fc 2013/11/09 11:20:28
ofst[ 56]:err_code:0xa0801004, clock:0x0b4ea4fe 2006/01/04 15:23:42
ofst[ 60]:err_code:0xa0003001, clock:0xffffffff
ofst[ 64]:err_code:0xa0003001, clock:0xffffffff
ofst[ 68]:err_code:0xa0003001, clock:0xffffffff
ofst[ 72]:err_code:0xa0003001, clock:0xffffffff
ofst[ 76]:err_code:0xa0003001, clock:0xffffffff
ofst[ 80]:err_code:0xa0003001, clock:0xffffffff
ofst[ 84]:err_code:0xa0003001, clock:0xffffffff
ofst[ 88]:err_code:0xa0003001, clock:0xffffffff
ofst[ 92]:err_code:0xa0003001, clock:0xffffffff
ofst[ 96]:err_code:0xa0003001, clock:0xffffffff
ofst[100]:err_code:0xa0003001, clock:0xffffffff
ofst[104]:err_code:0xa0003001, clock:0xffffffff
ofst[108]:err_code:0xa0003001, clock:0xffffffff
ofst[112]:err_code:0xa0003001, clock:0xffffffff
ofst[116]:err_code:0xa0003001, clock:0xffffffff
ofst[120]:err_code:0xa0003001, clock:0xffffffff
ofst[124]:err_code:0xa0003001, clock:0xffffffff
ofst[ 0]:err_code:0xa0003001, clock:0xffffffff
ofst[ 4]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
> errlog
(PowerOff State) (Fatal)
errlog
ofst[ 12]:err_code:0xffffffff, clock:0x15a2fb2f 2011/07/03 10:04:31
ofst[ 16]:err_code:0xa0901004, clock:0x15a2fb2f 2011/07/03 10:04:31
ofst[ 20]:err_code:0xa0801001, clock:0x167cabad 2011/12/15 12:59:25
ofst[ 24]:err_code:0xa0901004, clock:0x167cabae 2011/12/15 12:59:26
ofst[ 28]:err_code:0xa0902020, clock:0x167cabae 2011/12/15 12:59:26
ofst[ 32]:err_code:0xa0801001, clock:0x18805df8 2013/01/09 16:57:28
ofst[ 36]:err_code:0xa0901004, clock:0x18805df8 2013/01/09 16:57:28
ofst[ 40]:err_code:0xa0801001, clock:0x188801ff 2013/01/15 12:03:11
ofst[ 44]:err_code:0xa0801004, clock:0x188801ff 2013/01/15 12:03:11
ofst[ 48]:err_code:0xa0801001, clock:0x1a10d6fc 2013/11/09 11:20:28
ofst[ 52]:err_code:0xa0901004, clock:0x1a10d6fc 2013/11/09 11:20:28
ofst[ 56]:err_code:0xa0801004, clock:0x0b4ea4fe 2006/01/04 15:23:42
ofst[ 60]:err_code:0xa0003001, clock:0xffffffff
ofst[ 64]:err_code:0xa0003001, clock:0xffffffff
ofst[ 68]:err_code:0xa0003001, clock:0xffffffff
ofst[ 72]:err_code:0xa0003001, clock:0xffffffff
ofst[ 76]:err_code:0xa0003001, clock:0xffffffff
ofst[ 80]:err_code:0xa0003001, clock:0xffffffff
ofst[ 84]:err_code:0xa0003001, clock:0xffffffff
ofst[ 88]:err_code:0xa0003001, clock:0xffffffff
ofst[ 92]:err_code:0xa0003001, clock:0xffffffff
ofst[ 96]:err_code:0xa0003001, clock:0xffffffff
ofst[100]:err_code:0xa0003001, clock:0xffffffff
ofst[104]:err_code:0xa0003001, clock:0xffffffff
ofst[108]:err_code:0xa0003001, clock:0xffffffff
ofst[112]:err_code:0xa0003001, clock:0xffffffff
ofst[116]:err_code:0xa0003001, clock:0xffffffff
ofst[120]:err_code:0xa0003001, clock:0xffffffff
ofst[124]:err_code:0xa0003001, clock:0xffffffff
ofst[ 0]:err_code:0xa0003001, clock:0xffffffff
ofst[ 4]:err_code:0xa0003001, clock:0xffffffff
ofst[ 8]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
>
 
Joonie said:
I remember missing flash region turns the console itself off but you should still be able to access the recovery menu, maybe from there you could flash your pup via USB unless it's bricked, if so then you should follow @M4j0r's suggestion
Click to expand...
Doesn't look that way. It switches itself off literally one second after I switch it on.
 
NiQ said:
Thank you for the detailed instructions!
Where can I find the logs? The "errlog" command seems to do nothing...

EDIT: NVM found my mistake, here's the log:


C:\Temp>C:\Python36\python.exe sysconauth.py COM4 CXRF
> errlog
(PowerOff State)
errlog
ofst[ 8]:err_code:0xffffffff, clock:0x15388fd3 2011/04/13 16:46:11
ofst[ 12]:err_code:0xa0801001, clock:0x15a2fb2f 2011/07/03 10:04:31
ofst[ 16]:err_code:0xa0901004, clock:0x15a2fb2f 2011/07/03 10:04:31
ofst[ 20]:err_code:0xa0801001, clock:0x167cabad 2011/12/15 12:59:25
ofst[ 24]:err_code:0xa0901004, clock:0x167cabae 2011/12/15 12:59:26
ofst[ 28]:err_code:0xa0902020, clock:0x167cabae 2011/12/15 12:59:26
ofst[ 32]:err_code:0xa0801001, clock:0x18805df8 2013/01/09 16:57:28
ofst[ 36]:err_code:0xa0901004, clock:0x18805df8 2013/01/09 16:57:28
ofst[ 40]:err_code:0xa0801001, clock:0x188801ff 2013/01/15 12:03:11
ofst[ 44]:err_code:0xa0801004, clock:0x188801ff 2013/01/15 12:03:11
ofst[ 48]:err_code:0xa0801001, clock:0x1a10d6fc 2013/11/09 11:20:28
ofst[ 52]:err_code:0xa0901004, clock:0x1a10d6fc 2013/11/09 11:20:28
ofst[ 56]:err_code:0xa0801004, clock:0x0b4ea4fe 2006/01/04 15:23:42
ofst[ 60]:err_code:0xa0003001, clock:0xffffffff
ofst[ 64]:err_code:0xa0003001, clock:0xffffffff
ofst[ 68]:err_code:0xa0003001, clock:0xffffffff
ofst[ 72]:err_code:0xa0003001, clock:0xffffffff
ofst[ 76]:err_code:0xa0003001, clock:0xffffffff
ofst[ 80]:err_code:0xa0003001, clock:0xffffffff
ofst[ 84]:err_code:0xa0003001, clock:0xffffffff
ofst[ 88]:err_code:0xa0003001, clock:0xffffffff
ofst[ 92]:err_code:0xa0003001, clock:0xffffffff
ofst[ 96]:err_code:0xa0003001, clock:0xffffffff
ofst[100]:err_code:0xa0003001, clock:0xffffffff
ofst[104]:err_code:0xa0003001, clock:0xffffffff
ofst[108]:err_code:0xa0003001, clock:0xffffffff
ofst[112]:err_code:0xa0003001, clock:0xffffffff
ofst[116]:err_code:0xa0003001, clock:0xffffffff
ofst[120]:err_code:0xa0003001, clock:0xffffffff
ofst[124]:err_code:0xa0003001, clock:0xffffffff
ofst[ 0]:err_code:0xa0003001, clock:0xffffffff
ofst[ 4]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
> errlog
(PowerOff State) (Fatal)
errlog
ofst[ 12]:err_code:0xffffffff, clock:0x15a2fb2f 2011/07/03 10:04:31
ofst[ 16]:err_code:0xa0901004, clock:0x15a2fb2f 2011/07/03 10:04:31
ofst[ 20]:err_code:0xa0801001, clock:0x167cabad 2011/12/15 12:59:25
ofst[ 24]:err_code:0xa0901004, clock:0x167cabae 2011/12/15 12:59:26
ofst[ 28]:err_code:0xa0902020, clock:0x167cabae 2011/12/15 12:59:26
ofst[ 32]:err_code:0xa0801001, clock:0x18805df8 2013/01/09 16:57:28
ofst[ 36]:err_code:0xa0901004, clock:0x18805df8 2013/01/09 16:57:28
ofst[ 40]:err_code:0xa0801001, clock:0x188801ff 2013/01/15 12:03:11
ofst[ 44]:err_code:0xa0801004, clock:0x188801ff 2013/01/15 12:03:11
ofst[ 48]:err_code:0xa0801001, clock:0x1a10d6fc 2013/11/09 11:20:28
ofst[ 52]:err_code:0xa0901004, clock:0x1a10d6fc 2013/11/09 11:20:28
ofst[ 56]:err_code:0xa0801004, clock:0x0b4ea4fe 2006/01/04 15:23:42
ofst[ 60]:err_code:0xa0003001, clock:0xffffffff
ofst[ 64]:err_code:0xa0003001, clock:0xffffffff
ofst[ 68]:err_code:0xa0003001, clock:0xffffffff
ofst[ 72]:err_code:0xa0003001, clock:0xffffffff
ofst[ 76]:err_code:0xa0003001, clock:0xffffffff
ofst[ 80]:err_code:0xa0003001, clock:0xffffffff
ofst[ 84]:err_code:0xa0003001, clock:0xffffffff
ofst[ 88]:err_code:0xa0003001, clock:0xffffffff
ofst[ 92]:err_code:0xa0003001, clock:0xffffffff
ofst[ 96]:err_code:0xa0003001, clock:0xffffffff
ofst[100]:err_code:0xa0003001, clock:0xffffffff
ofst[104]:err_code:0xa0003001, clock:0xffffffff
ofst[108]:err_code:0xa0003001, clock:0xffffffff
ofst[112]:err_code:0xa0003001, clock:0xffffffff
ofst[116]:err_code:0xa0003001, clock:0xffffffff
ofst[120]:err_code:0xa0003001, clock:0xffffffff
ofst[124]:err_code:0xa0003001, clock:0xffffffff
ofst[ 0]:err_code:0xa0003001, clock:0xffffffff
ofst[ 4]:err_code:0xa0003001, clock:0xffffffff
ofst[ 8]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
>
Click to expand...
Ok, error 0xA0003001: https://www.psdevwiki.com/ps3/Syscon_Error_Codes#3001 means no 12V power.
So either the PSU is bad or the connection through the two connectors CN7800 and CN7801 (at the front of the board) or some circuitry around that is bad.
Since the 5V standby lane is working, the PSU is at least partially fine.
 
M4j0r said:
Ok, error 0xA0003001: https://www.psdevwiki.com/ps3/Syscon_Error_Codes#3001 means no 12V power.
So either the PSU is bad or the connection through the two connectors CN7800 and CN7801 (at the front of the board) or some circuitry around that is bad.
Since the 5V standby lane is working, the PSU is at least partially fine.
Click to expand...
Oh, nice, that explains why switching the hard drives did nothing.
Do you think I could just take the PPU to some electronics repair store?
 
NiQ said:
Oh, nice, that explains why switching the hard drives did nothing.
Do you think I could just take the PPU to some electronics repair store?
Click to expand...
Well, as I said, I would first check the connection and visually inspect the circuitry near the power connectors on the TMU-520.
 
M4j0r said:
Ok, if you want to dump the syscon error log you don't need to do any soldering.
You can relay the Syscon serial port from the DECR to your PC over the network.

First, you need to exploit the CP - you can use the "root_cp.py" script for that:
After that, open a telnet shell which connects to the CP, the username is "rt" with no password.
Also connect a FTP client to the CP, port 21 with username "rt" and no password.
Transfer the files "ser2net" and "ser2net.conf" in the (default) root user directory on the CP via the FTP client.
Then run "chmod +rx ser2net" and "./ser2net -c ser2net.conf" in the telnet shell.

This maps the Syscon serial port to the network.
The changes aren't persistent, if the CP is rebooted you need to follow the previous steps again.
Now you need to connect to it and map it to a local serial port on your PC.
Click to expand...

Hello, I also have a DECR-1000A with a boot start fail. Something that could be related with NEC/TOKIN proadlizers? I would like to get the error log from the syscon. I have tried the serial port of the DECR using a serial to USB cable, but I cannot run the syscon script. I guess it could be related with needed some serial commands auth different for attaching to it?
Anyways, I have tried your method for mapping the serial port to network using the ser2net binary. I have successfully done the root_cp, transferring the files and connecting to CP by telnet. But when I run the "ser2net" after giving execution permissions, it always gives me an error: "bash: cannot allocate memory".
Are other steps that I am missing? "top" command shows that memory used is around 0.1% so I guess it is not related with not memory enough. Do you know what it could be happening?

Thanks in advance.
 
@NiQ Is this the DECR-1000A that was lent to Hard4Games YouTube channel for video analysis?

I don't own one so I couldn't really tell you how to fix it but perhaps some safety pointers...

1. I know some of these still have their vertical stand, which is bad idea to make something 40lbs. stand up and expect it to maintain balance. I imagine that if it was standing (especially on the edge of something or on a glass stand), all it would take is a half-strength accidental bump of your arm to knock it all the way to the floor or down onto the shelving and damage the stand/unit/shelving

2. Perhaps keep the unit wires out of your walk-able path? I know everybody has "different" setups but I haven't knocked a console onto the floor since the days of PS2 when your controller had to be wired to the machine... and I probably learned that lesson about 5 times with my PS2 when getting up to get something and tripping over my gamepad wire only to yeet the whole console onto the floor.

I was so happy when controllers finally became wireless. As for wires that extend from the back of the DECR unit, I feel like those wires should be shoved behind your shelf or TV stand so that they would never be in a path that they could be tripped on?

As for frontal ports, I imagine that there shouldn't be nearly as many wires as what you have on the back? I know the DECR1000A has like 6 USB ports on it's face but the real question is if you ever really have to use more than 2? I also know of the foot-switch but more questions in place of whether you still possess the foot-switch or even actually use it?

Idk... just try harder to keep things setup in a safe manner? I mean, it is a $10K development/debugging unit... and you tripped over it like it is a commonplace living room electronic. Sorry for the abrasiveness, it just offends to hear about something that should be historically preserved getting damaged when the environment it was put in did not appear to be safe for it.
 
I would like to amend the information about the free memory since I read the memory used by "top" command. This is the output of the top command, and the output from ser2net execution:

Windows PowerShell
Copyright (C) Microsoft Corporation. Todos los derechos reservados.
6:41pm up 7 min, 2 users, load average: 0.11, 0.12, 0.06
41 processes: 40 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 0.6% user, 0.8% system, 0.0% nice, 98.6% idle
Mem: 238976K total, 106604K used, 132372K free, 1228K buffers
Swap: 0K total, 0K used, 0K free, 87096K cached

bash: ./ser2net: Cannot allocate memory

@M4j0r @NiQ I hope you can guide/help me with this "little" issue. Thanks in advance.
 
euchloedtj said:
Hello, I also have a DECR-1000A with a boot start fail. Something that could be related with NEC/TOKIN proadlizers? I would like to get the error log from the syscon. I have tried the serial port of the DECR using a serial to USB cable, but I cannot run the syscon script. I guess it could be related with needed some serial commands auth different for attaching to it?
Click to expand...
The serial port on the back connects to the CP and is responsible to set the network config, but that's a deprecated feature.
The TMU-520 board does have pads for the SB (CN4402) and SC (CN6123) serial ports but they're not populated.
Anyways, I have tried your method for mapping the serial port to network using the ser2net binary. I have successfully done the root_cp, transferring the files and connecting to CP by telnet. But when I run the "ser2net" after giving execution permissions, it always gives me an error: "bash: cannot allocate memory".
Are other steps that I am missing? "top" command shows that memory used is around 0.1% so I guess it is not related with not memory enough. Do you know what it could be happening?
Click to expand...
Make sure that the CP runs the latest firmware (1.3.3) and that you copied the files using binary mode and that the executable and config are in the root user directory.
 
M4j0r said:
The serial port on the back connects to the CP and is responsible to set the network config, but that's a deprecated feature.
The TMU-520 board does have pads for the SB (CN4402) and SC (CN6123) serial ports but they're not populated.

Make sure that the CP runs the latest firmware (1.3.3) and that you copied the files using binary mode and that the executable and config are in the root user directory.
Click to expand...
Thanks @M4j0r it was my mistake with FileZilla FTP transferring the ser2net as ASCII instead of binary. I guess I was not far from the source of the issue since most of the errors are power related:

> errlog
(PowerOn State)
(PowerOff State) (Fatal)
errlog
ofst[ 72]:err_code:0xffffffff, clock:0x0b488f37 2005/12/31 00:37:11
ofst[ 76]:err_code:0xa0801002, clock:0x0b488f7e 2005/12/31 00:38:22
ofst[ 80]:err_code:0xa0801002, clock:0x0b489086 2005/12/31 00:42:46
ofst[ 84]:err_code:0xa0801002, clock:0x0b489118 2005/12/31 00:45:12
ofst[ 88]:err_code:0xa0801002, clock:0x0b489153 2005/12/31 00:46:11
ofst[ 92]:err_code:0xa0801002, clock:0x0b489196 2005/12/31 00:47:18
ofst[ 96]:err_code:0xa0801002, clock:0x0b4891c7 2005/12/31 00:48:07
ofst[100]:err_code:0xa0801002, clock:0x0b489232 2005/12/31 00:49:54
ofst[104]:err_code:0xa0801002, clock:0x0b489507 2005/12/31 01:01:59
ofst[108]:err_code:0xa0801002, clock:0x0b48952a 2005/12/31 01:02:34
ofst[112]:err_code:0xa0801002, clock:0x0b489577 2005/12/31 01:03:51
ofst[116]:err_code:0xa0801002, clock:0x0b4895b2 2005/12/31 01:04:50
ofst[120]:err_code:0xa0801002, clock:0x0b4895dd 2005/12/31 01:05:33
ofst[124]:err_code:0xa0071002, clock:0x0b4895f2 2005/12/31 01:05:54
ofst[ 0]:err_code:0xa0071004, clock:0x0b4895f2 2005/12/31 01:05:54
ofst[ 4]:err_code:0xa0093003, clock:0x0b4895f2 2005/12/31 01:05:54
ofst[ 8]:err_code:0xa0801002, clock:0x0b489663 2005/12/31 01:07:47
ofst[ 12]:err_code:0xa0801002, clock:0x0b489686 2005/12/31 01:08:22
ofst[ 16]:err_code:0xa0801002, clock:0x0b4896c2 2005/12/31 01:09:22
ofst[ 20]:err_code:0xa0801002, clock:0x0b489715 2005/12/31 01:10:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b489744 2005/12/31 01:11:32
ofst[ 28]:err_code:0xa0801002, clock:0x0b489781 2005/12/31 01:12:33
ofst[ 32]:err_code:0xa0801002, clock:0x0b4897c8 2005/12/31 01:13:44
ofst[ 36]:err_code:0xa0801002, clock:0x0b4898cb 2005/12/31 01:18:03
ofst[ 40]:err_code:0xa0801002, clock:0x0b48996e 2005/12/31 01:20:46
ofst[ 44]:err_code:0xa0801002, clock:0x0b488688 2005/12/31 00:00:08
ofst[ 48]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 52]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 56]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 60]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 64]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 68]:err_code:0xa0801002, clock:0x0b488688 2005/12/31 00:00:08

I will try replace NEC/TOKIN proadlizers from RSX side. I have the original NEC/TOKIN replacements and also the tantalizer PCB with tantalum caps. I am not sure if goes in the original design way or try the tantalizers. I would not like to solder/desolder many times on this main board. Have you ever tried this?
 
euchloedtj said:
I will try replace NEC/TOKIN proadlizers from RSX side. I have the original NEC/TOKIN replacements and also the tantalizer PCB with tantalum caps. I am not sure if goes in the original design way or try the tantalizers. I would not like to solder/desolder many times on this main board. Have you ever tried this?
Click to expand...
The TMU-520 uses the same Tokins like the other boards. Two NEC TOKIN 0E128 for CELL and two for RSX.
It does have more power phases though.
 
You must log in or register to reply here.

Similar threads

Back
Top