I recently began testing with the nPM1300EK and it seems like something is wrong with it. A number of different tasks don't seem to be working correctly:
- Profiling a battery - About 5 seconds after the profiling starts, the charger seems to turn itself off and the PMIC stops responding. I've tried different options, like lowering the charging current, but it still fails. I have the fuel gauge board attached, but I haven't even been able to use it.
- Fuel gauge sample - I've connected an nRF54l15 and used the sample nPM1300 and nPM1304: Fuel gauge. It takes some fiddling to get it to work (I have to get things working and enabled in PowerUP). Pretty quickly it fails, though:
nRF Fuel Gauge version: 1.0.1
Constant voltage charging
PMIC device ok
Constant voltage charging
V: 4.169, I: 0.083, T: 25.10, SoC: 94.23, TTE: nan, TTF: 1902
V: 4.165, I: 0.093, T: 25.10, SoC: 94.24, TTE: nan, TTF: 2024
V: 4.165, I: 0.094, T: 25.10, SoC: 94.25, TTE: nan, TTF: 2033
V: 4.165, I: 0.094, T: 25.10, SoC: 94.25, TTE: nan, TTF: 2039
V: 4.165, I: 0.095, T: 25.10, SoC: 94.26, TTE: nan, TTF: 2046
Error: Could not read from charger device
Error: Could not read from charger device
Error: Could not read from charger device - Power UP - Sometimes even just manipulating settings in PowerUP causes problems. For example I turned off buck 1 in PowerUP and the board disconnected:
11:18:25.817 module_pmic: No response from PMIC.11:18:26.322 module_pmic: No response from PMIC.11:18:26.820 module_pmic: No response from PMIC.11:18:27.320 module_pmic: No response from PMIC.
Sometimes I'll see errors logged like "USB buffer too small". I just reset everything and tried turning buck 1 off again and got:
11:22:54.200 npmx buck status set 0 1 => Error: IO error. Error: unable to set buck status.11:22:54.220 npmx buck status get 0 => Error: IO error. Error: unable to get buck status.and now all the controls on PowerUP are disabled. The LED on the nPM1300EK is still pulsing like it's connected, though.
When it starts having issues like this, the only way to fix it seems to be to remove all power from the board. Often I need to reset the device with PowerUP and sometimes it connects to the bootloader and requires a firmware update.
