PS5 Slim (EDM-040) – Error 80871055 / 0.170A Amp Draw (SSD Controller Replaced

BASHEER · Jul 22, 2026

Hi everyone,

I’m working on a PS5 Slim motherboard (EDM-040) and could use some diagnostic advice.

Issue & UART Logs:

WeeTools / UART Error: ⁠80871055⁠ (⁠2156335189⁠)

SSD Banks IO Error Between SSD Controller

Flash Controller ScCmd Response Error Reason: 85 [0x55]

Current Draw: The board draws around 0.170A (170mA) on power-on and hangs there.

Work Done So Far:

Replaced the SSD Controller IC, but the symptom remains identical—same 0.170A draw and exact same UART error code.

Questions / Next Steps:

Since the controller IC replacement didn't alter the behavior, what’s the most likely culprit on the EDM-040 revision?

1. Is it more likely a faulty NAND Flash chip or a cracked BGA joint underneath one of the NANDs (needing reball/reflow)?

2. Could this be caused by missing or unstable output rails from the SSD PMIC?

3. Are there specific resistor arrays / filter caps on the I/O lines between the NANDs and the controller that are known to fail on EDM-040?

Any insights or measurement points from anyone who has dealt with this specific error on EDM-040 would be greatly appreciated. Thanks in advance!

cene · Aug 3, 2026

Same problem here

BASHEER · Aug 4, 2026

Same thing

stetofix · Saturday at 4:07 PM

If the issue is not solved with changing the SSD controller, till now, I haven't seen a solution for the UART error 80871055.
Some tried and change the not married SSD NANDs but stuck to the same error.

thesjaakspoiler · 2026-08-17T01:57:19+0100

Found this in the documentation of another Marvel SSD controller :

0x55 indicates a Failed NAND Flash Initialization / Bad NAND ID error.

When the SSD powers on, the Marvell controller executes its core bootloader code (stored in its internal ROM). Its first job is to reach out across its memory channels, wake up the physical NAND flash chips, and read their unique hardware IDs. If the controller receives complete garbage, a completely silent response, or unreadable bits instead of the expected vendor IDs, it enters a hard panic state and locks up, throwing the 0x55 code to the serial debug interface or ROM monitor.

Primary Causes of a 0x55 Panic cacn indicated but may not be limited to :

NAND Core Power Rail Failure: If a small capacitor shorts out or a PMIC for the NAND chips fails, the controller stays on, but the NAND chips stay dead, forcing a 0x55 timeout.
Broken BGA Solder Joints: If the communication traces with the NAND chips break, the controller can no longer communicate with the storage array.
Completely Corrupted Boot Blocks: If the very first sector of the NAND flash (where the controller's main lookup tables and secondary firmware reside) has suffered catastrophic data degradation, the controller cannot boot past its internal ROM phase.

PS5 Slim (EDM-040) – Error 80871055 / 0.170A Amp Draw (SSD Controller Replaced

Active Member

Attachments

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum