nPM1300 Configuration

[levijo]

Hi,

I would like your support in reviewing and helping define the correct configuration for the NPM1300 charger in our application.

Here is the current configuration we are using:

npm1300_charger: charger {
    compatible = "nordic,npm1300-charger";
    status = "okay";
    term-microvolt = <4100000>;
    term-warm-microvolt = <4000000>;
    current-microamp = <130000>;
    dischg-limit-microamp = <1340000>;
    vbus-limit-microamp = <500000>;
    thermistor-ohms = <10000>;
    thermistor-beta = <3435>;
    charging-enable;
};

We are using the following battery: renata ICP621333PA-01 3.7V / 230mAh

Could you please confirm whether this configuration is appropriate for the battery in use? I noticed that the PMIC offers additional protection and safety configurations. If possible, I would appreciate your guidance on defining a recommended and more complete set of parameters.

We are also encountering a couple of issues:

1. Occasionally, the PMIC does not detect the USB-C charger connection during boot.

2. When the USB connection is not recognized, the fuel gauge reports 0% state of charge (SOC).

Any advice or suggestions to address these issues would be greatly appreciated.

[Edvin]

The device_is_ready function does communicate via I2C. So if it fails, then there is reason to believe that it may fail at a later point. 

If you were able to reproduce it on a DK, then I could reproduce it here on my desk, or even forward it to our PMIC team, which could analyze it. 

levijo said:

We have the same issue with the IMU driver as well but much less often than the fuelgague.

That could be related. Perhaps some collission/HW issues. 

So while the device_is_ready() is not strictly needed, the fact that it sometimes returns an error indicates that something is not correct. Do you see any other issues with the PMIC? Some bad/weird battery measurements? 

Best regards,

Edvin

[levijo]

Not really, at list in the meanwhile.

What is strange, is that immediately after the device_is_ready, there are 1 or more api function that uses I2C and works fine, without any failures. so ironically removing this function solved it, and the frequent failures we had disappeared. 

While I would love to analyze and debug it farther, for now this solution satisfies us, and I'm forced to focus on other burning issues.

Did anyone report on similar issues before? Can upgrading to ncs 2.9.0 fix this issue?