nPM Power Up - "PMIC Not powered" and "No response from PMIC"

[jeremy_mtigs]

In attempting to set up the nPM1300-EK for battery characterization, I  keep seeing the connection status "PMIC Not powered" and repeating errors: "module_pmic: No response from PMIC."

I have tried several things, I'll note first that checking with a meter I see 4.1 V on VBAT (jumpered to VBATIN) and 5.0 V on VBUS.  The battery attached is a two terminal battery, on J1 with the NTC 10Kohm jumper placed. Said battery reads 4.1 V, and has been in use with / recently charged by the nPM1300 on our prototype.

I have a USB C cable attached to the nPM controller port, another to the USB PMIC port, and the battery.  

I have tried both the order of attachment shown below:

https://docs.nordicsemi.com/bundle/ug_npm1300_ek/page/UG/nPM1300_EK/use_ek_power_up.html

https://www.youtube.com/watch?v=2vBOIpyCltY

I have tried several power supplies, USB C ports and cables, all of which are in use regularly, and some with this nPM1300-EK in other configurations.  

Resetting the device after attachment / plugging in appears to result in the same error state.  

I have collected a log and will attempt to attach.

[jeremy_mtigs]

2025-03-21T20_43_21.667Z-log.txt

[jeremy_mtigs]

Possibly noteworthy:
2025-03-22T00:30:39.504Z INFO Using JLink version: JLink_V8.12a
2025-03-22T00:30:39.504Z WARN Installed JLink version does not match the expected version (JLink_V7.94i)

[Priyanka]

Hi Jeremy,

Could you tell me the details on the white sticker on your EK?

Also, hopefully you have followed this:

Also, could you tell me how the LD4 is blinking, according to the table here:

https://docs.nordicsemi.com/bundle/ug_npm1300_ek/page/UG/nPM1300_EK/npm_controller.html 

-Priyanka

[jeremy_mtigs]

I have:

PCA10152
1.1.0
2024.17
4F23972E0E8FF2EB

The first link directs to power the PMIC first, and I had followed that for multiple attempts.  I will try that again.
docs.nordicsemi.com/.../use_ek_power_up.html

LD4 is an on/off blink with a period of around 1 sec.  

[jeremy_mtigs]

Another member on my team found that we need to have a jumper between VDDIO and VOUT2.  This appears to resolve the issue, and the system is working.
 
Thanks for your time.