Hi,
I am having an intermittent problem with a MPQ4241 on a custom board when charging a Google Pixel 10 Pro XL via PPS.
The problem is that the output sometimes appears to get “stuck” and no longer responds to an CC signals. The output stays at 9V even when the cable is completely disconnected. It appears to happen somewhat randomly, sometimes right after a connect and sometimes after be connected for 5 or 10 minutes. I have replicated it on multiple MPQ4241 chips.
The MPQ4241 does not report a fault and says it is still attached with a contracted power of 48W through APDO:
Using a PD analyser (POWER-Z KM003C) it shows CC2 dropping to around 0.5V when the failure happens and no matter what it stays there until the power is reset even if the phone is unplugged.
The CC lines from the MPQ4241 are connected directly to the type-C port with a 390pF cap to GND and a 2.2Ohm series resistor on each line.
Full register dump from the MPQ4241:
| PDO_SET1 | 0 | Byte | 47 |
|---|---|---|---|
| PDO_SET2 | 1 | Byte | 48 |
| HOST_SET | 2 | Byte | 168 |
| PDO_I1 | 3 | Byte | 150 |
| PDO_V2 | 4 | Byte | 90 |
| PDO_V2_H | 5 | Byte | 0 |
| PDO_I2 | 6 | Byte | 150 |
| PDO_V3 | 7 | Byte | 120 |
| PDO_V3_H | 8 | Byte | 0 |
| PDO_I3 | 9 | Byte | 150 |
| PDO_V4 | 10 | Byte | 150 |
| PDO_V4_H | 11 | Byte | 0 |
| PDO_I4 | 12 | Byte | 150 |
| PDO_V5 | 13 | Byte | 200 |
| PDO_V5_H | 14 | Byte | 110 |
| PDO_I5 | 15 | Byte | 150 |
| PDO_V6 | 16 | Byte | 33 |
| PDO_V6_H | 17 | Byte | 160 |
| PDO_I6 | 18 | Byte | 60 |
| PDO_V7 | 19 | Byte | 33 |
| PDO_V7_H | 20 | Byte | 210 |
| PDO_I7 | 21 | Byte | 60 |
| PD_CTL1 | 22 | Byte | 16 |
| PD_CTL2 | 23 | Byte | 5 |
| PWR_CTL1 | 24 | Byte | 201 |
| PWR_CTL2 | 25 | Byte | 81 |
| VOUT | 26 | Byte | 2 |
| VOUT_H | 27 | Byte | 31 |
| IOUT_LIM | 28 | Byte | 72 |
| CTL_SYS0 | 29 | Byte | 0 |
| CTL_SYS1 | 30 | Byte | 1 |
| CTL_SYS2 | 31 | Byte | 226 |
| CTL_SYS3 | 32 | Byte | 30 |
| CTL_SYS4 | 33 | Byte | 140 |
| CTL_SYS5 | 34 | Byte | 35 |
| CTL_SYS6 | 35 | Byte | 54 |
| CTL_SYS7 | 36 | Byte | 136 |
| CTL_SYS8 | 37 | Byte | 30 |
| CTL_SYS9 | 38 | Byte | 8 |
| CTL_SYS10 | 39 | Byte | 60 |
| CTL_SYS11 | 40 | Byte | 238 |
| CTL_SYS12 | 41 | Byte | 20 |
| CTL_SYS13 | 42 | Byte | 8 |
| CTL_SYS14 | 43 | Byte | 21 |
| CTL_SYS15 | 44 | Byte | 144 |
| CTL_SYS16 | 45 | Byte | 12 |
| CTL_SYS17 | 46 | Byte | 18 |
| CTL_SYS18 | 47 | Byte | 50 |
| STATUS1 | 48 | Byte | 164 |
| STATUS2 | 49 | Byte | 13 |
| STATUS3 | 50 | Byte | 32 |
| STATUS4 | 51 | Byte | 96 |
| ID1 | 52 | Byte | 0 |
| ID2 | 53 | Byte | 0 |
| FW_REV | 54 | Byte | 0 |
| MAX_REQ_CUR | 55 | Byte | 0 |
| MFR_ID | 56 | Byte | 9 |
| DEV_ID | 57 | Byte | 88 |
| CLK_ON | 59 | Byte | 0 |
| CTL_SYS19 | 60 | Byte | 15 |
I have tried to provide as much information as possible but let me know if there is anything else you would like to know.
My next step is to try replicate the problem on the EVQ4241-LE-00A dev kit, but any other suggestions would be appreciated!
Thanks,
Josh
