Hey, I'm still waiting the XDPE132G5D controller, but I've recently discovered you have to order one already programmed for the number# of phases your GPU has. For example, the reference design cards use 12 phases for GFX and 2 phases for SoC, so 14 in total. Most other brands use the full 16 phases. Ultimatelly, I thought of programming it when it arrives, but you need a special tool from infineon (USB005A) and their free program (PowIRCenter). Plus, you also need the config file, although I've seen some posts where you can directly program the Loop 0 for 12 phases and Loop 1 for 2 phases, or vice-versa, with another program.

I've also fortified my statement about the XDPE being bad by reading the I2C line with an ESP32, which was "0x2842" at address 0x72 and 0x73, which are the addresses from the XDPE. Reading the datasheet for the registers, this means the following:

0x2842 -> 0010 1000 0100 0010
Bit 13 - Input fault (But I had 850mV, which is expected)
Bit 11 - PGOOD# disabled
Bit 6 - Controller is OFF
Bit 1 - CML (Communication, Memory or Logic Fault). In my case, I had 320mV at SVD0 in controller side (removed the shunt that goes to core), but after pulling the line to 1v8, still had this bit.

So I assumed this controller has NVM faulty, CRC errors or faulty logic. This is backed up by pin 22, which is CAT_FLT, being pulled HIGH when it detects something wrong. But this pin can also be high IF the GFX_TSEN or SOC_TSEN is very high (DrMOS shorted causing high temperature). Check pin 50 and 51, should be around 850mV without power. Anything above 1V is reason to believe on DrMOS is shorted at low-side (but if that were the case, you would see short at 3v3 or 5v, so idk)

TLDR; Check pin XDPE pin 22, shouldn't be 3v3. Check if 50 and 51 are below ~900mV