npm1300 problem

RE: npm1300 problem

helsing — Wed, 18 Sep 2024 11:34:55 GMT

Hi Sun Yang, sorry for not replying to this ticket in a long time. Please let us know if you are still working on this issue and we will look into it again.

RE: npm1300 problem

sunnyyang — Fri, 28 Jun 2024 13:51:46 GMT

hi,

I have confirmed with the dealer that I am using rev1. Now if i configure any bulk register for example get voltage, The above issues will arise.Please give me some advice.

RE: npm1300 problem

AlbanM — Fri, 28 Jun 2024 12:25:54 GMT

thanks for the kind answer

best regards

bob

RE: npm1300 problem

helsing — Fri, 28 Jun 2024 11:49:22 GMT

Hi Bob, sorry for the late reply.

[quote user="AlbanM"]please you confirm that the topic above applies to engineering samples of the nPM1300, and not revision 1 of nPM1300 ?[/quote]

Our PMIC team is pointing towards errata 24, however, Sun Yang has not confirmed whether the workaround works.

[quote user="AlbanM"]the errata 24 is supposed to have been fixed in rev1 so there is no more risk of a faulty power cycling or shipmode exit right ?[/quote]

Yes, anomaly 24 has been fixed in Revision 1. None of the remaining errata for Revision 1 are related to shipmode exit or difficulties power cycling the device. Anomaly [32] leads to reduced efficency in Hysteretic mode.

You are very much welcome to open a new ticket in case you would like to further discuss the details of your project.

Best regards,

Håkon

RE: npm1300 problem

AlbanM — Thu, 13 Jun 2024 16:17:20 GMT

i'm currently designing around a nPM1300 + nRF52840

please you confirm that the topic above applies to engineering samples of the nPM1300, and not revision 1 of nPM1300 ?

the errata 24 is supposed to have been fixed in rev1 so there is no more risk of a faulty power cycling or shipmode exit right ?

best regards

bob

RE: npm1300 problem

helsing — Fri, 12 Apr 2024 08:12:44 GMT

Hi sun yang, sorry for the delay.

Thank you for the traces. Feedback from the PMIC team is that this might be errata 24:

[Errata 24] BUCK, CONTROL: Restart fails after reset with VBUS and VBAT connected.

Could you try the suggested workaround?

RE: npm1300 problem

sunnyyang — Fri, 29 Mar 2024 14:59:16 GMT

hi,

The parts related to npm1300 include the following code and dts.

static const struct device *regulators = DEVICE_DT_GET(DT_NODELABEL(npm1300_ek_regulators));

static const struct device *charger = DEVICE_DT_GET(DT_NODELABEL(npm1300_ek_charger));

static const struct device *leds = DEVICE_DT_GET(DT_NODELABEL(npm1300_ek_leds));

static const struct device *pmic = DEVICE_DT_GET(DT_NODELABEL(npm1300_ek_pmic));

static float max_charge_current;

static float term_charge_current;

static int64_t ref_time;

static const struct battery_model battery_model = {

#include "lq_25C.inc"

};

/********************thread define*******************************/

#define PMIC_STACK_SIZE 1024

#define PMIC_PRIORITY 2

K_THREAD_STACK_DEFINE(pmic_stack_area, PMIC_STACK_SIZE);

struct k_thread pmic_thread_data;

static int read_sensors(const struct device *charger, float *voltage, float *current, float *temp)

{

struct sensor_value value;

int ret;

ret = sensor_sample_fetch(charger);

if (ret < 0) {

return ret;

}

sensor_channel_get(charger, SENSOR_CHAN_GAUGE_VOLTAGE, &value);

*voltage = (float)value.val1 + ((float)value.val2 / 1000000);

sensor_channel_get(charger, SENSOR_CHAN_GAUGE_TEMP, &value);

*temp = (float)value.val1 + ((float)value.val2 / 1000000);

sensor_channel_get(charger, SENSOR_CHAN_GAUGE_AVG_CURRENT, &value);

*current = (float)value.val1 + ((float)value.val2 / 1000000);

return 0;

}

int fuel_gauge_init(const struct device *charger)

{

struct sensor_value value;

struct nrf_fuel_gauge_init_parameters parameters = { .model = &battery_model };

int ret;

memset(&gBatteryStatus, 0x00,sizeof(gBatteryStatus));

ret = read_sensors(charger, &parameters.v0, &parameters.i0, &parameters.t0);

if (ret < 0) {

return ret;

}

/* Store charge nominal and termination current, needed for ttf calculation */

sensor_channel_get(charger, SENSOR_CHAN_GAUGE_DESIRED_CHARGING_CURRENT, &value);

max_charge_current = (float)value.val1 + ((float)value.val2 / 1000000);

term_charge_current = max_charge_current / 10.f;

nrf_fuel_gauge_init(&parameters, NULL);

ref_time = k_uptime_get();

return 0;

}

int fuel_gauge_update(const struct device *charger)

{

float voltage;

float current;

float temp;

float soc;

float tte;

float ttf;

float delta;

int ret;

struct sensor_value error;

struct sensor_value status;

//static int led_set = 0;

static int buzzer_count = 0;

ret = read_sensors(charger, &voltage, &current, &temp);

if (ret < 0) {

printk("Error: Could not read from charger device\n");

return ret;

}

delta = (float) k_uptime_delta(&ref_time) / 1000.f;

soc = nrf_fuel_gauge_process(voltage, current, temp, delta, NULL);

tte = nrf_fuel_gauge_tte_get();

ttf = nrf_fuel_gauge_ttf_get(-max_charge_current, -term_charge_current);

sensor_channel_get(charger, SENSOR_CHAN_NPM1300_CHARGER_STATUS, &status);

sensor_channel_get(charger, SENSOR_CHAN_NPM1300_CHARGER_ERROR, &error);

printk("V: %.3f, I: %.3f, T: %.2f, ", voltage, current, temp);

printk("SoC: %.2f, TTE: %.0f, TTF: %.0f\n", soc, tte, ttf);

printk("Charger Status: %d, Error: %d\n", status.val1, error.val1);

return 0;

}

/**********************************************************

* function:pmic_thread_run

* description:pmic thread run

* err = k_sem_take(&ble_sem, K_FOREVER);

* date:k_sched_lock(); k_sched_unlock();

**********************************************************/

static void pmic_thread_run(void *p1, void *p2, void *p3)

{

if (!device_is_ready(charger))

{

printk("Charger device not ready.\n");

return 0;

}

if (fuel_gauge_init(charger) < 0) {

printk("Could not initialise fuel gauge.\n");

return 0;

}

printk("PMIC device ok\n");

led_on(leds, 0U);

while (1)

{

fuel_gauge_update(charger);

k_msleep(PMIC_SLEEP_TIME_MS);

}

return;

}

/**********************************************************

* function:pmic_init

* description:pmic module init

* err = k_sem_take(&ble_sem, K_FOREVER);

* date:k_sched_lock(); k_sched_unlock();

**********************************************************/

int pmic_init(void)

{

k_tid_t my_tid;

if (!device_is_ready(leds)) {

printk("Error: led device is not ready\n");

return;

}

if (!device_is_ready(pmic)) {

printk("Pmic device not ready.\n");

return;

}

if (!device_is_ready(regulators)) {

printk("Error: Regulator device is not ready\n");

return 0;

}

led_off(leds, 0U);

my_tid = k_thread_create(&pmic_thread_data, pmic_stack_area,

K_THREAD_STACK_SIZEOF(pmic_stack_area),

pmic_thread_run,

NULL, NULL, NULL,

PMIC_PRIORITY, 0, K_NO_WAIT);

k_thread_name_set(&pmic_thread_data, "pmic_thread");

return 0;

}

RE: npm1300 problem

sunnyyang — Fri, 29 Mar 2024 14:52:35 GMT

hi,I'm sorry for the late reply.As shown as the picture,The picture one is VBUSOUT, the picture two is bulk2 and the last picture is vbusin.

RE: npm1300 problem

helsing — Tue, 12 Mar 2024 14:48:26 GMT

[quote user="sunnyyang"]My device uses a very low current, less than 1mA.[/quote]

How is the current is measured?

Would you be able to provide a scope trace with VSYS and BUCK2? Perhaps you could include VBUS as well?

RE: npm1300 problem

Parth Parekh — Fri, 08 Mar 2024 04:41:48 GMT

can you please share your code ?

RE: npm1300 problem

sunnyyang — Wed, 06 Mar 2024 13:43:58 GMT

Yes，I use an internal pull-up resistor in the CPU.

RE: npm1300 problem

sunnyyang — Wed, 06 Mar 2024 13:43:06 GMT

hi，

My device uses a very low current, less than 1mA.

RE: npm1300 problem

helsing — Wed, 06 Mar 2024 13:35:36 GMT

Reviewing the schematic, using the nPM1300 Reference circuitry as a reference there was not much to comment on. The only thing is that you could consider, which you might already have done, the optional pull-up resistors for TWI, as according to the reference circuitry.

RE: npm1300 problem

helsing — Wed, 06 Mar 2024 09:08:55 GMT

Thank you for the update.

The issue you're experiencing could be because the device is drawing more current than what the USB host can provide. The current limit for VBUS is set at 500mA. If the device draws more than this, the system's voltage (VSYS) will drop.

Vsys can also drop if the USB host can only deliver, for example, 100mA, and the device draws more than this. Even if the VBUS current limit is set to 500mA.

The overlay looks OK and works as expected when we are testing it.

RE: npm1300 problem

sunnyyang — Tue, 05 Mar 2024 15:00:27 GMT

I'm sorry, there's an issue with my description.When VBAT is connected, the bulk 2 voltage is fixed and outputs 3.3v, regardless of whether VBUS is connected or not. When only VBUS is connected,the bulk 2 output power supply varies between 1V and 3.3V. The schematic is detailed in the following image.

RE: npm1300 problem

helsing — Tue, 05 Mar 2024 14:47:08 GMT

[quote user=""]When VBAT and VBUS are connected simultaneously, the bulk 2 output power supply varies between 1V and 3.3V.[/quote]

What are the voltages on VBAT and VBUS when this occur?

RE: npm1300 problem

helsing — Tue, 05 Mar 2024 14:44:33 GMT

Hi sun yang,

[quote user=""]When VBAT and VBUS are connected simultaneously, the bulk 2 output power supply varies between 1V and 3.3V[/quote]

Do you have any plot from an oscilloscope showing this?

[quote user=""]The npm1300 is used for power management on my borad.[/quote]

Would you be able to share the schematic of your design? Has anyone at Nordic reviewed your design? We offer a review of the Nordic related part of the design as a free service. If you would like us to do this, we could make the ticket private so that you can add upload the files.

RE: npm1300 problem

helsing — Mon, 04 Mar 2024 15:27:17 GMT

Hi sun yang,

Just letting you know we have started looking into this.