Hacking Hardware Using Raspberry Pi Pico for syscon reading

[master801]

Had a Raspberry Pi Pico laying around after using it for RGH 3.0 on my Xbox 360 and needed to figure out what is causing YLOD on my PS3. So I figured it'd be best to reuse it instead of buying a $5 device with worse usage.

After poking around in the PS3 syscon reader source code, I eventually figured out it is written in Python and uses UART (this is never stated explicitly - just that a "TTL serial USB" device is needed). I was planning on creating a custom solution for the Raspberry Pi Pico, but couldn't really figure out how to interface the UART serial to USB then to syscon reader.

Searched for "raspberry pi pico uart usb" and in the first 10 results, I saw that someone had already made a UART-USB solution for the Raspberry Pi Pico. This is the best approach since it doesn't require any custom software.

Using the pinout in Pico USB-UART Bridge's GitHub repository, I wired up UART0 to the PS3 syscon. Pico UART0 TX to syscon RX, Pico UART0 RX to syscon TX. For some reason, it didn't work at all and syscon reader was throwing out "Auth1 response invalid" with both "AUTH" and "auth". I even added a ground wire and it still didn't work! As a last resort, I switched the wires around (following the guide).

Now type in AUTH or auth. It is case sensitive, so if one doesn't work try the other. If you get Auth1 response invalid, after trying it both ways, then you got the RX and TX wires reversed.

"AUTH" still didn't work, but "auth" worked and I got an "Auth successful" message.

At this point, I can read syscon and figure out why my console has YLOD.

Since my board is a DIA-001 model, I was able to get into internal access mode. Not exactly sure how this helps, but it seems to give a bit more extra info.

Notes:
DO NOT BLINDLY TYPE IN WHATEVER COMMANDS I USED (IN THE SCREENSHOTS) TO OBTAIN INTERNAL ACCESS MODE! THIS CAN AND WILL BRICK SYSCON.
I used the "Linux" version of ps3syscon on Windows 10 since it just relies on Python 3. The Windows version looked like a packaged version of Python with a user-friendly UI and has no real merits (other than being user-friendly) over the CLI version, in my opinion.

Sources:
https://github.com/Noltari/pico-uart-bridge
https://github.com/db260179/ps3syscon
https://www.psx-place.com/threads/r...s-replacement-ylod.25260/page-192#post-295119

By the way, although I can't confirm this, I'm sure Pico UART-USB Bridge will work for PSP BaryonSweeper.

 

[skelly7769]

do i need to connect something to diag aswell? for pico on a cok-001

 

[master801]

do i need to connect something to diag aswell? for pico on a cok-001

Yes, connect DIAG to GND (don't solder - just leave it hanging on a GND point).

2. Solder the jumper cables to the correct pins - RX, TX and GND go to the USB uart serial cable and DIAG get shorted to GND once the eeprom has set its mode to allow diag mode

https://www.psx-place.com/threads/f...syscon-first-steps-and-error-reporting.30100/

 

[skelly7769]

Yes, connect DIAG to GND (don't solder - just leave it hanging on a GND point).

on a sem 001 i tried to ground the diag then i got no red light also that sem 001 is now not working since the rx or tx pad came off

 

[Calum122]

Hhmm, interesting? I'd be interested in giving this a go rather than relying on some random chip from China

Did you manage to fix your PS3 in the end?

 

[master801]

Hhmm, interesting? I'd be interested in giving this a go rather than relying on some random chip from China

Did you manage to fix your PS3 in the end?

Nope.

Got a YLOD and 3034 error which means the RSX is fucked. I'm not gonna waste money on a reball or franken-GPU since a used PS3 slim is way cheaper.