PS3 Release: PS3 Advanced Tools

bucanero said:
I don't have my PS3 hardware around so I wasn't able to test that version. I also had to rebuild my compiler and tools so I can't tell until I get my hardware setup running again.


we talked about the Toolset & syscon log on Twitter, @M4j0r said it was tested and working. Maybe @zecoxao and @M4j0r can provide more feedback, they probably have ps3 hardware available to test the latest release.

In any case, the GUI code hasn't changed at all, so you could install the older version, and then add the syscon log dumper manually.
Click to expand...

Thank you, may i ask how can add this manually?
 
bucanero said:
I don't have my PS3 hardware around so I wasn't able to test that version. I also had to rebuild my compiler and tools so I can't tell until I get my hardware setup running again.

we talked about the Toolset & syscon log on Twitter, @M4j0r said it was tested and working. Maybe @zecoxao and @M4j0r can provide more feedback, they probably have ps3 hardware available to test the latest release.
Click to expand...
I compiled the syscon tool (1.1.0) myself and used the 1.0.0 frontend and it works, but your 1.1.0 version doesn't work (neither the frontend nor the tool). So it's related to your toolchain.
 

Attachments

M4j0r said:
I compiled the syscon tool (1.1.0) myself and used the 1.0.0 frontend and it works, but your 1.1.0 version doesn't work (neither the frontend nor the tool). So it's related to your toolchain.
Click to expand...

thanks for the confirmation! I'll have to build my ps3toolchain again. I moved to a M1 (arm64) processor and was rebuilding everything from scratch. I had to apply some patches to get things compiled, so I assume the results went wrong.

Time to check if I can solve these toolchain issues :eek:
 
bucanero said:
thanks for the confirmation! I'll have to build my ps3toolchain again. I moved to a M1 (arm64) processor and was rebuilding everything from scratch. I had to apply some patches to get things compiled, so I assume the results went wrong.

Time to check if I can solve these toolchain issues :eek:
Click to expand...
When you solve everything could you please push/upload the working version of the pkg? Thank you in advance.
 
Nosdio said:
When you solve everything could you please push/upload the working version of the pkg? Thank you in advance.
Click to expand...

yes I'll update it eventually when I have my hardware setup and a working toolchain ready.

if you need, just install the old version, and then download the tool.self that @M4j0r attached in the previous message. Finally use a file manager or FTP, and check /dev_hdd0/game/PS3T000LZ/TOOLS
open any of those folders (e.g. "UP0001-REBOOT003_00-0000000000000000"), then you can replace "tool.self" and edit "title.txt" so you know it's the Syscon log tool.
 
@bucanero many thanks for your reply. I did as you said and when i run the reboot option i get the sm_error on my usb.
The results are strange but thank you all for the help. These are the errors just for the reference.
upload_2021-9-28_2-34-46.png
 
Nosdio said:
@bucanero many thanks for your reply. I did as you said and when i run the reboot option i get the sm_error on my usb.
The results are strange but thank you all for the help. These are the errors just for the reference.
View attachment 34953
Click to expand...

good to hear it worked! I don't have any experience about hardware troubleshooting, but there are forum threads about syscon logs and errors, they can probably give you some feedback about it. Ping @sandungas as he can point you into the right forum threads
 
bucanero said:
good to hear it worked! I don't have any experience about hardware troubleshooting, but there are forum threads about syscon logs and errors, they can probably give you some feedback about it. Ping @sandungas as he can point you into the right forum threads
Click to expand...
Hey, thanks for you reply again. I did a small check and this is an error from the AV ic, i can suspect why. My question is why the dates are off (and other info as well)? Can i somehow clear the log as i was advised to? I am only asking because it is strange that some info is correct in the log whereas other is not.
 
bucanero said:
hi @Nosdio
I have rebuilt the app with a working (older) toolchain, and updated the Advanced toolset .pkg

I know that you already got the logs, but could you try again installing this new v1.0.1 version from GitHub? it should include the syscon log dumper and everything should work as expected.

https://github.com/bucanero/psl1ghtv2_ports/releases/tag/v1.0.1

let me know, thanks!
Click to expand...
Sure i can testing is essential, i will do it today. My PS3 that has the errors probably broke completely but i will doit on my slim model. I will post soon enough. Thanks for uploading this.
 
@bucanero , i tested this on the old machine. It is in a zombie state. Here is my findings:

1) Application does not start if you dont have the BD attached.
2) It works in regards to the system error logs (well done!!)
3) The system error logs at least to my case does not seem correct because:

The machine shows error code A0802022 who is an AV/HDMI ic issue but judging from what i see i have RSX issue and an not an IC issue.
Console starts when i press in the RSX. If not it does not start so that is not a good sign....
Another argument is the out of the blue logs in regards to system time etc. Please check the attached.
-----------------------------------
Firmware Version: 4.88 (build 50731)
Platform ID: CokD10
Product Code: 00 87
Product Sub Code: 00 06
Hardware Config: 4E00FFFF0007BCBF
Syscon Fimware Version: 0E69.0001000400040002 (EEPROM: 0001000400040002)
Bringup Count: 527, Shutdown Count: 495
Runtime: 4 Days, 0 Hours, 37 Minutes, 9 Seconds
Error Log
01: A0802022 Sat Dec 31 01:04:11 2005
02: A0802022 Sat Dec 31 00:56:18 2005
03: A0802022 Sat Dec 31 00:43:56 2005
04: A0802022 Sat Dec 31 00:43:16 2005
05: A0802022 Tue Jan 3 19:51:27 2006
06: A0802022 Tue Jan 3 19:50:43 2006
07: A0802022 Tue Jan 3 19:43:07 2006
08: A0802022 Tue Jan 3 19:39:18 2006
09: A0802022 Tue Jan 3 19:30:55 2006
10: A0802022 Tue Jan 3 19:05:12 2006
11: A0802022 Tue Jan 3 18:53:17 2006
12: A0802022 Tue Jan 3 18:50:46 2006
13: A0802022 Tue Jan 3 18:47:28 2006
14: A0802022 Tue Jan 3 18:33:10 2006
15: A0802022 Tue Jan 3 18:31:45 2006
16: A0802022 Tue Jan 3 18:30:07 2006
17: A0802022 Tue Jan 3 18:28:34 2006
18: A0802022 Tue Jan 3 15:52:28 2006
19: A0802022 Tue Jan 3 15:50:28 2006
20: A0802022 Tue Jan 3 15:44:05 2006
21: A0802022 Tue Jan 3 15:44:03 2006
22: A0802022 Tue Jan 3 15:43:53 2006
23: A0802022 Tue Jan 3 15:32:24 2006
24: A0802022 Tue Jan 3 15:32:22 2006
25: A0802022 Tue Jan 3 15:32:11 2006
26: A0802022 Tue Jan 3 15:30:54 2006
27: A0802022 Tue Jan 3 15:26:39 2006
28: A0802022 Tue Jan 3 14:59:29 2006
29: A0802022 Tue Jan 3 14:59:28 2006
30: A0802022 Tue Jan 3 14:59:17 2006
31: A0802022 Tue Jan 3 14:53:45 2006
32: FFFFFFFF Tue Jan 3 14:53:44 2006

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

Maybe i am missing something, please let me know so i can test again.

Thanks, John
 
Hi, thanks for testing the new .pkg :encouragement:

the no-BD issue is expected. I think that you need to install a noBD CFW if you want to be able to run stuff without the Blueray drive. If not, you won't be able to run any app or game.

About the syscon errors, try asking in this thread: https://www.psx-place.com/threads/f...syscon-first-steps-and-error-reporting.30100/

the guys that actually know about hardware troubleshooting, Syscon, RSX, delid, etc, are there.
 
bucanero said:
Hi, thanks for testing the new .pkg :encouragement:

the no-BD issue is expected. I think that you need to install a noBD CFW if you want to be able to run stuff without the Blueray drive. If not, you won't be able to run any app or game.

About the syscon errors, try asking in this thread: https://www.psx-place.com/threads/f...syscon-first-steps-and-error-reporting.30100/

the guys that actually know about hardware troubleshooting, Syscon, RSX, delid, etc, are there.
Click to expand...
Soon i will post the log from my other machine, it would be funny to see what will be. I suppose it should not be the same.
Working fine on my slim :)
Happy to test anytime man
 
@bucanero Hey, please check the data from the slim model.
The app works, indeed dumps some data, but the data does not seem correct...at least in regards to the errors
This is from an early model slim machine which is working perfect.
Never existed in 2006 or 1999, the errors are the same in number and code.
The runtime seems correct though especially comparing this to the other log because the slim has seen some gameplay whereas the FAT had not.

Really it is a nice app, i think the issue with the data can be fixed.

Firmware Version: 4.88 (build 50731)
Platform ID: CokG11
Product Code: 00 87
Product Sub Code: 00 09
Hardware Config: 4E00FFFF0203BC3C
Syscon Fimware Version: 0832.00010002083E0832 (EEPROM: 00010002083E0832)
Bringup Count: 1751, Shutdown Count: 1423
Runtime: 78 Days, 20 Hours, 2 Minutes, 53 Seconds
Error Log
01: A0802022 Fri Dec 29 02:22:48 2006
02: A0802022 Fri Dec 29 02:12:36 2006
03: A0802022 Fri Dec 29 01:56:32 2006
04: A0802022 Fri Dec 29 01:56:30 2006
05: A0802022 Fri Dec 29 01:56:23 2006
06: A0802022 Sat Nov 11 06:24:32 2006
07: A0802022 Sat Nov 11 06:23:59 2006
08: A0802022 Sat Nov 11 06:19:26 2006
09: A0802022 Sat Nov 11 06:16:56 2006
10: A0802022 Sat Sep 9 05:10:18 2006
11: A0802022 Sat Sep 9 05:00:30 2006
12: A0802022 Fri Sep 8 06:26:41 2006
13: A0802022 Fri Sep 8 06:19:18 2006
14: A0802022 Wed Jan 4 05:38:35 2006
15: A0802022 Wed Jan 4 05:37:23 2006
16: A0802022 Wed Jan 4 05:22:23 2006
17: A0802022 Wed Jan 4 05:17:17 2006
18: A0802022 Tue Jan 3 05:28:46 2006
19: A0802022 Tue Jan 3 05:25:18 2006
20: A0802022 Mon Jan 2 22:34:40 2006
21: A0802022 Mon Jan 2 22:32:05 2006
22: A0802022 Mon Jan 2 22:29:13 2006
23: A0802022 Mon Jan 2 22:25:05 2006
24: A0802022 Mon Jan 2 22:15:29 2006
25: A0802022 Mon Jan 2 22:05:09 2006
26: A0802022 Mon Jan 2 12:11:17 2006
27: A0802022 Mon Jan 2 12:04:59 2006
28: A0802022 Mon Jan 2 09:24:04 2006
29: A0802022 Mon Jan 2 09:22:54 2006
30: A0802022 Mon Jan 2 09:21:30 2006
31: A0802022 Mon Jan 2 09:20:48 2006
32: FFFFFFFF Fri Dec 31 23:59:59 1999
 
Maybe but in regards to data the logs are strange. Two different consoles have the exact number and codes for errors and the dates are off for both of them.
Maybe i do not understand correctly, u should get the exact output from every unit?
 
I am not well versed in the error logs system but those values might just be the default values from manufacturing (2006 is the ps3 initial release, this part of the syscon could have remained untouched since then) & if no error has been logged since the console was made, it may be normal to get those values...

Ask the guys posting in hardware & syscon errors threads, they should be able to tell you what default values should look like...
 
Nosdio said:
3) The system error logs at least to my case does not seem correct because:

The machine shows error code A0802022 who is an AV/HDMI ic issue but judging from what i see i have RSX issue and an not an IC issue.
Click to expand...
These are the errors as they're reported by Syscon.

Nosdio said:
@bucanero Hey, please check the data from the slim model.
The app works, indeed dumps some data, but the data does not seem correct...at least in regards to the errors
This is from an early model slim machine which is working perfect.
Never existed in 2006 or 1999, the errors are the same in number and code.
Click to expand...
2006 means that the RTC was reset at some time, 1999 means blank. The Syscon starts counting at year 2000. "Blank" errors are are set to one second before that.

Nosdio said:
Maybe but in regards to data the logs are strange. Two different consoles have the exact number and codes for errors and the dates are off for both of them.
Maybe i do not understand correctly, u should get the exact output from every unit?
Click to expand...
It is the exact output, that's what you would get if you would get the errors using the Syscon UART interface.

To get help with these errors, please post the logs here: https://www.psx-place.com/threads/f...-syscon-first-steps-and-error-reporting.30100 and the describe what fails.
 
M4j0r said:
These are the errors as they're reported by Syscon.


2006 means that the RTC was reset at some time, 1999 means blank. The Syscon starts counting at year 2000. "Blank" errors are are set to one second before that.


It is the exact output, that's what you would get if you would get the errors using the Syscon UART interface.

To get help with these errors, please post the logs here: https://www.psx-place.com/threads/f...-syscon-first-steps-and-error-reporting.30100 and the describe what fails.
Click to expand...
Great i see, thanks for the support and app.
 
bucanero said:
hi @Nosdio
I have rebuilt the app with a working (older) toolchain, and updated the Advanced toolset .pkg

I know that you already got the logs, but could you try again installing this new v1.0.1 version from GitHub? it should include the syscon log dumper and everything should work as expected.

https://github.com/bucanero/psl1ghtv2_ports/releases/tag/v1.0.1

let me know, thanks!
Click to expand...
Tried that but I couldn't seem to get the syscon log dumper to work. All it does is show a black screen then take me back to the XMB.

Running on EvilNAT CEX COBRA 8.3, v4.88.
 
You must log in or register to reply here.

Similar threads

Back
Top