I2C Communication Issue with nPM1300 on Custom Board (nRF54L15)

RE: I2C Communication Issue with nPM1300 on Custom Board (nRF54L15)

Adam W — Tue, 13 May 2025 17:56:42 GMT

That was it. Thank you for help

RE: I2C Communication Issue with nPM1300 on Custom Board (nRF54L15)

Jared — Thu, 08 May 2025 12:50:51 GMT

Hi,

Looks like you're using TWIM instance TWIM20 that is limited to GPIOs in P1. For P0 use TWIM30:

regards

Jared

RE: I2C Communication Issue with nPM1300 on Custom Board (nRF54L15)

Adam W — Tue, 06 May 2025 17:55:28 GMT

Here is trace from logic analyzer

NRF i2c connection:

nPM1300 connections:

Layout, SCL traces:

SDA traces:

I desoldered sensor in bottom part of the board, so now only nPM1300 is connected to the i2c bus. I also tried connecting external module to i2c lines but with the same results.

RE: I2C Communication Issue with nPM1300 on Custom Board (nRF54L15)

Hung Bui — Fri, 02 May 2025 10:57:50 GMT

Hi Adam,
Jared is away until Tuesday. I will try to help in the mean time.
Could you try to capture a logic analyzer trace ?
Please also try to test with a different SDA and SCL pins so we can verify the I2C transaction.

In addition please send us the schematic and layout.

RE: I2C Communication Issue with nPM1300 on Custom Board (nRF54L15)

Adam W — Tue, 29 Apr 2025 14:55:26 GMT

SDA is not shorted, i measured it with meter, and i can see SDA being pulled low by MCU at the start of transaction. Code in only trying to read register from nPM1300, so i doubt the mcu is doing flash erase. Im testing on Custom board.

RE: I2C Communication Issue with nPM1300 on Custom Board (nRF54L15)

Jared — Tue, 29 Apr 2025 12:11:36 GMT

Hi Adam,

From the description in the driver:

/* Whatever the frequency, completion_sync should have

* been given by the event handler.

* If it hasn't, it's probably due to an hardware issue

* on the I2C line, for example a short between SDA and

* GND.

* This is issue has also been when trying to use the

* I2C bus during MCU internal flash erase.

* In many situation, a retry is sufficient.

* However, some time the I2C device get stuck and need

* help to recover.

* Therefore we always call i2c_nrfx_twim_recover_bus()

* to make sure everything has been done to restore the

* bus from this error.

Can you double check that the SDA line hasn't been shorted or if you're performing a flash erase? Are you testing on a custom board or development kit?

regards

Jared

RE: I2C Communication Issue with nPM1300 on Custom Board (nRF54L15)

Adam W — Mon, 28 Apr 2025 13:17:43 GMT

latest, 2.9.1

RE: I2C Communication Issue with nPM1300 on Custom Board (nRF54L15)

Jared — Mon, 28 Apr 2025 13:02:49 GMT

Hi,

Which version of NCS are you using?

regards

Jared