Ill mention myself as friend. You missed an additional feature introduced in v0.3
Which is the ability to type and run your own commands manually also. Like this:
View attachment 32023 To do this, simply open the included execute.exe while using SysconReader_Debug.exe to see what's going on.
Especially useful with SW syscons, since there are many more useful commands available directly.
Credit for making the program goes to SweetDude26, who doesn't even have a PS3.
Of course it is still advised to understand and do everything the manual way. This just makes it even more accessible for newcomers.
Cheers

Click to expand...

I did everything you mentioned and all i get after auth successfull
F00000003
any idea why the execution of the command isnt working?

CD C:\Users\HTPC\Desktop\PS3\SYSCON
python ps3_syscon_uart_script.py COM4 CXRF

The first line just changes the directory to the folder containing the python script. The second line runs it in internal access mode. You'll have to check the device manager to fin what COM port your serial adapter was assigned by windows (it changes). And for external access you'll need to change to "CXR" or possibly "SW" for your model...IDK.
Then "AUTH" or "auth"
Then "GET ERRLOG"
Make sense?
If you can't get past the first part then you need to open the CMD prompt and install the dependencies:

pip install pyserial

pip install pycryptodome 

...then exit and try again.
EDIT 2: If you get an error saying the pip install comand isn't valid in CMD, then you didn't select the "Add to PATH" option in the python installer. Uninstall it and try again, this time look for an option in the installer called "Add Python to PATH". Be sure that is checked!
EDIT 1:corrected a command to "pycryptodome."

did you install drivers for your TTL adapter? also try running hii the script as admin. i think the program also said that it requires windows 10, and you seem to be on 7

Click to expand...

I have successfully retrieved the error codes via GUI. I think that means the TTL is working properly. The execute command isn’t working tho. What could cause this? I was able to successfully install one of your recommended but the “pip install pycrypto” gave the red error.

I have successfully retrieved the error codes via GUI. I think that means the TTL is working properly. The execute command isn’t working tho. What could cause this? I was able to successfully install one of your recommended but the “pip install pycrypto” gave the red error.

Click to expand...

Sorry, I ment:

pip install pycryptodome 

Also, be sure to change the directory first to the folder containing the python script. Hit enter. launch the script in a separate line. You can't do it at the same time. I’m going to try and report back. Maybe the python script I got isn’t the right one. I went to the github, found the uart_script.py file. I click it and it opens a bunch of lines. If I right click it I’m able to save it as a python file. Then I place that saved file in a folder which I specify on the cmd however I get that previously reported error something about line 7.
UPDATE: pycryptodome install successful. Still same error. I have included a picture of what i'm doing. I downloaded the .py file from the github by right clicking and saving to the folder of c:\python27\scripts
photo included. Am i saving the .py file the wrong way? When i left click it opens the file in the browser with a bunch of code. Please advise.
UPDATE 2: I was able to get it done. I got to the "auth" but when i type errlog nothing happens. Here is what i got. Thoughts?
c:\Python27\Scripts>python ps3_syscon_uart_script.py COM3 CXR
>$ auth
Auth successful
>$ errlog get 00
F0000003
>$ ERRLOG GET
F0000006
>$ ERRLOG GET 0
F0000006
>$ get errlog
F0000003
>$ errlog
F0000003
>$ bringup
F0000003

pip install pycryptodome 

Also, be sure to change the directory first to the folder containing the python script. Hit enter. launch the script in a separate line. You can't do it at the same time. y and Here is what I did to get a clean install to the "auth" part. I have windows 7 and hopefully this will help clear it up a bit if you are using windows. I downloaded python from its website. I installed it and in the second window i scrolled down and ticked on the python.exe to be installed (the only one with the red X). I installed python to C:\ directory so it became c:\python27.
Inside the python27 folder is a scripts folder. I went to the github website provided by the man himself DB (shout out bro for the work you done). There i left clicked the ps3_syscon_uart_script.py. It took me to a page with a bunch of script. I selected it all and copied. I opened notepad and paste all of that code. I went to file>save as and the name I put ps3_syscon_uart_script.py
I saved the filed to c:\python27\scripts
Then I opened CMD and did the following:
1. first checked to see if python installed correctly by typing python --version
2. installed pyserial by typing "pip install pyserial "
pyserial installed by said i need to upgrade my pip so i next upgraded my pip (Refer to the line below).
3. I next typed line "pip install pycryptodome"
4. I screwed up by not navigating over to the right directory so i typed "cd c:\python27\scripts"
5. the last step i typed "python ps3_syscon_uart_script.py COM3 CXR"
double check your COM. Mine was COM 3.
Refer to my log below. Let me know if you have success following this.
My only issue is when i type errlog, nothing happens after "Auth".
Microsoft Windows [Version 6.1.7601]
C:\Users\Kleon1876>python --version
Python 2.7.18
C:\Users\Kleon1876>pip install pyserial
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Ple
ase upgrade your Python as Python 2.7 won't be maintained after that date. A fut
ure version of pip will drop support for Python 2.7. More details about Python 2
support in pip, can be found at https://pip.pypa.io/en/latest/development/relea
se-process/#python-2-support
Collecting pyserial
Using cached https://files.pythonhosted.org/packages/07/bc/587a445451b253b2856
29263eb51c2d8e9bcea4fc97826266d186f96f558/pyserial-3.5-py2.py3-none-any.whl
Installing collected packages: pyserial
Successfully installed pyserial-3.5
WARNING: You are using pip version 19.2.3, however version 20.3.4 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' comm
C:\Users\Kleon1876>python -m pip install --upgrade pip
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Ple
ase upgrade your Python as Python 2.7 won't be maintained after that date. A fut
ure version of pip will drop support for Python 2.7. More details about Python 2
support in pip, can be found at https://pip.pypa.io/en/latest/development/relea
se-process/#python-2-support
Collecting pip
Using cached https://files.pythonhosted.org/packages/27/79/8a850fe3496446ff0d5
84327ae44e7500daf6764ca1a382d2d02789accf7/pip-20.3.4-py2.py3-none-any.whl
Installing collected packages: pip
Found existing installation: pip 19.2.3
Uninstalling pip-19.2.3:
Successfully uninstalled pip-19.2.3
Successfully installed pip-20.3.4
C:\Users\Kleon1876>pip install pyserial
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please
upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop s
upport for Python 2.7 in January 2021. More details about Python 2 support in pi
p can be found at https://pip.pypa.io/en/latest/development/release-process/#pyt
hon-2-support pip 21.0 will remove support for this functionality.
Requirement already satisfied: pyserial in c:\python27\lib\site-packages (3.5)
C:\Users\Kleon1876>pip install pycryptodome
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please
upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop s
upport for Python 2.7 in January 2021. More details about Python 2 support in pi
p can be found at https://pip.pypa.io/en/latest/development/release-process/#pyt
hon-2-support pip 21.0 will remove support for this functionality.
Collecting pycryptodome
Using cached pycryptodome-3.10.1-cp27-cp27m-win_amd64.whl (1.5 MB)
Installing collected packages: pycryptodome
Successfully installed pycryptodome-3.10.1
C:\Users\Kleon1876>python ps3_syscon_uart_script.py COM3 CXR
python: can't open file 'ps3_syscon_uart_script.py': [Errno 2] No such file or d
irectory
C:\Users\Kleon1876>python ps3_syscon_uart_script.py COM3 CXR
python: can't open file 'ps3_syscon_uart_script.py': [Errno 2] No such file or d
irectory
C:\Users\Kleon1876>cd c:\python27\scripts
c:\Python27\Scripts>python ps3_syscon_uart_script.py COM3 CXR
>$ auth
Auth successful

After a YLOD, I think what happens a lot of times is that people open the console to retrieve their game and then sell the console for parts.
Just be sure to test voltages and fuses before taking off the tokins (proper troubleshooting first). Also, please consider getting an oscilloscope and helping out. I'm very curious what the O-scope looks like on that 1001/1004.
Okay, internal mode is pretty easy.

AUTH in external CXR mode as normal.

EEP GET 3961 01 --> should return "00000000 FF"

EEP SET 3961 01 00 (changes the bit to allow internal access mode)

EEP GET 3961 01 (verify the change) --> Should now return "00000000 00".

Shut off console & close the CMD prompt/terminal. Connect the Diag wire to GND and turn console back on. It will beep 3 times and start flashing because the checksum doesn't match anymore. This is normal! We're going to fix that next...

You need to use internal command CXRF now. Here's an example of the commands I have to use every time I gain access for a test, but you'll have to change the "COM4" to whichever comm port your usb to serial device was assigned. You can find it under usb devices in the device manager.:

Code:

CD C:\Users\HTPC\Desktop\PS3\SYSCON
python ps3_syscon_uart_script.py COM4 CXRF

AUTH (Uppercase) or auth (lowecase) whichever works. I've had to use both and sometimes is just requires the one or the other. IDK why. Once you get "AUTH successful", you're in!

eepcsum --> will return addresses that "should be" somthing like "0x0038". The address you need to change is the line after the "sum:0x0100" line. The sum indicates the mismatch. Ignore the line before of after, the address you want to change is the one immediately following the sum line. So for example if the that line reads "Addr:0x000039fe should be 0x0038" then you do the following...

w 39fe 38 00 ( don't use this command . yours will be different depending on the address that that didn't pass the checksum above. Just put it in like this example, based on your actual checksum mismatch. For example, if your address should be "0xff38" then your command should be "w 39fe 38 ff") --> should just go to the next line or say write successful, I don't remember (you only have to do this once per console). Notice that the 00 and 38 are swapped? That is endian byte swaping and the reason @squeept doesn't like doing this. Dyslexia make this type of thing more confusing than it already is. Anyway that's the hardest part.

r 39fe 02 (validate the change) --> if the checksums match now, then the "sum:0x0100" line will not be there anymore. That means the console will boot normally now.

Turn off the console and turn it on again. The standby led will be solid red and stop flashing. That's because the checksum matches and you successfully gained internal access. Now you need to use step 6 and 7 from now on. You can now use internal commands like "lasterrlog," "bringup," "powerstate," "errlog," and more. enjoy!

Click to expand...

Great step by step rip! Going to try this tomorrow. So I’m a little confused by the “once per console”. After step 11, if I flip the switch off and on again, while connected to the uart, I open cmd and type in my command with CXRF, I will have access to internal always? Do I need to keep the diag led connected to gnd at all times? @Kleon1876
Your issue is simply that you are not typing the command properly.
There is no such external command as "GET ERRLOG", or even "ERRLOG GET 0" is incorrect too.
The command should be
ERRLOG GET 00
(Up to 19)
It should work both using the GUI and manually of course
Cheers

You need the GND connected to the usb ttl gnd lead, anywhere on the ps3 motherboard metal will be a GND
So USB TTL GND >>>> PS3 motherboard GND (usb sockets case, or pins sticking out etc)

Click to expand...

Aaah, ok this absolutely makes sense. I just wanted to be absolutely sure so I don't fry anything.

@Kleon1876
Your issue is simply that you are not typing the command properly.
There is no such external command as "GET ERRLOG", or even "ERRLOG GET 0" is incorrect too.
The command should be
ERRLOG GET 00
(Up to 19)
It should work both using the GUI and manually of course
Cheers

Click to expand...

Thank you! I was able to get it working. Next step is going into Internal mode. I will update later on.

Click to expand...

From the "tutorial" you quoted in post #772 written by @RIP-Felix (nice one btw) i would say to run the command "eepcsum" in step 10
If you see a line with the "sum:0x0100" in the output of eepcsum in step 10 of the tutorial it means you still have a problem
In other words... the absence of the line "sum:0x0100" (in step 10 of the tutorial) means the checksum has been fixed (in step 9 of the tutorial) I just got down getting into internal mode on my DIA-001. Credit goes to Felix's post on page 31. Nicely done my friend. I followed the instructions and was able to do it no problem. Here is my cmd step by step after connecting the diag pin per his tutorial. For anyone attempting to get into internal mode follow felix's tutorial. Very easy. Look below for my log post diag led connect.
C:\Users\kleon1876>cd c:\python27\scripts
c:\Python27\Scripts>python ps3_syscon_uart_script.py COM3 CXRF
>$ auth
Auth successful
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56c7
Addr:0x000034fe should be 0x980c
sum:0x0100
Addr:0x000039fe should be 0x7360
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ w 39fe 60 73
w 39fe 60 73
w complete!
[mullion]$
>$ r 39fe 02
r 39fe 02
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
60 73
[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56c7
Addr:0x000034fe should be 0x980c
Addr:0x000039fe should be 0x7360
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ EXIT Alright friends. Here is my DIA-001. I have reballed it (might have screwed it up), I have replaced all 8 necs with a total of 32 caps. I have a total of 8 bridges (2 per chip x 2 sides). This is my errlog. It seems error code 22110 is killing me. Any advice on what to try next will help. thanks.
Note this system had GLOD (even when no necs or caps on). I was messing with the usb/wifi board ribbon while it was in GLOD one day and it ylod on me. Been that way ever since. I wonder if i shorted anything.
Also, how do i do the "spoiler" thing so my posts aren't a million miles long like below. Thanks.
C:\Users\kleon1876>cd c:\python27\scripts
c:\Python27\Scripts>python ps3_syscon_uart_script.py C
>$ auth
Auth successful
>$ errlog
errlog
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:0xa0022110, clock:0xffffffff
ofst[ 4]:err_code:0xa0022110, clock:0xffffffff
ofst[ 8]:err_code:0xa0022110, clock:0xffffffff
ofst[ 12]:err_code:0xa0022110, clock:0xffffffff
ofst[ 16]:err_code:0xa0022110, clock:0xffffffff
ofst[ 20]:err_code:0xa0022110, clock:0xffffffff
ofst[ 24]:err_code:0xa0022110, clock:0xffffffff
ofst[ 28]:err_code:0xa0022110, clock:0xffffffff
ofst[ 32]:err_code:0xa0022110, clock:0xffffffff
ofst[ 36]:err_code:0xa0022110, clock:0xffffffff
ofst[ 40]:err_code:0xa0022110, clock:0xffffffff
ofst[ 44]:err_code:0xa0022110, clock:0xffffffff
ofst[ 48]:err_code:0xa0022110, clock:0xffffffff
ofst[ 52]:err_code:0xa0022110, clock:0xffffffff
[mullion]$
>$ 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]$
>$ 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.
>$ powerstate
[SSM] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0022110
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
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]$
>$ shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
>$ errlog
errlog
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0022110, clock:0xffffffff
ofst[ 4]:err_code:0xa0022110, clock:0xffffffff
ofst[ 8]:err_code:0xa0022110, clock:0xffffffff
ofst[ 12]:err_code:0xa0022110, clock:0xffffffff
ofst[ 16]:err_code:0xa0022110, clock:0xffffffff
ofst[ 20]:err_code:0xa0022110, clock:0xffffffff
ofst[ 24]:err_code:0xa0022110, clock:0xffffffff
ofst[ 28]:err_code:0xa0022110, clock:0xffffffff
ofst[ 32]:err_code:0xa0022110, clock:0xffffffff
ofst[ 36]:err_code:0xa0022110, clock:0xffffffff
ofst[ 40]:err_code:0xa0022110, clock:0xffffffff
ofst[ 44]:err_code:0xa0022110, clock:0xffffffff
ofst[ 48]:err_code:0xa0022110, clock:0xffffffff
ofst[ 52]:err_code:0xa0022110, clock:0xffffffff
ofst[ 56]:err_code:0xa0022110, clock:0xffffffff
[mullion]$
>$ lasterrlog
lasterrlog
Last Error Code:0xa0022110, Time:0xffffffff
[mullion]$
Has anybody removed an RSX off of a working board and attempted a power on? What errors you get? what about removing the cell on a working board. Maybe removing both to see what errors etc. perhaps this can help narrow down the exact error codes related to both? Just a newbie thought. I have a board that has the 3034 error.I’m thinking about reflowing it and if it comes to life. Maybe removing the RSX and attempt booting to see if 3034 is back. UPDATE on a different DIA-001. This DIA-001 had ylod never been touched. The error codes were 3034 and 4322. I did a reflow of the RSX and it came to life. Appears to confirm 3034 to be RSX related. I wonder if I remove the RSx chip whether the 3034 will come back or it will be a different error at this point. My next step is to do internal commands on this live board to see what’s what. I’ll also test resistance etc since it’s a working DIA-001. Hoping it can give me insight into my other DIA-001 with the 22110 error