TWIM issue on NRF54L15

[hanks.liu]

hello,
I encountered a problem using TWIM to communicate on nrf54l15
Software and hardware versions:
Using ncs V2.8.0 version. The hardware is NRF54L15 RevB. The compilation instruction uses the
west build -b nrf54l15pdk/nrf54l15/cpuapp
of the v2.7.0 guide.
Detailed description of the problem:
When using TWIM for data communication, in the i2c_nrfx_twim_transfer function in i2c_nrfx_twim.c, the nrfx_twim_xfer function returns success, but the interrupt has not been triggered, resulting in the code
ret = k_sem_take(&dev_data->completion_sync, I2C_TRANSFER_TIMEOUT_MSEC) timeout, and communication cannot be successful.
And on the signal line, only SCL will have a pull-up and pull-down (about 700ms)

[Jared]

Hi,

Are you using a sample from NCS?

NRFX_TWIM_XFER_TX returning, only indicates that the transfer has been scheduled, it's a non blocking asynchronous module, so you have to wait for the NRFX_TWIM_EVT_DONE to be generated to know whether the transfer was successful. 

Can you probe SDA and SCL and check if the slave sends the ACK back to the master during the transfer?

regards

Jared 

[hanks.liu]

hi,it‘s not a sample。
about SDA and SCL，My description above is a little wrong. only SDA  had a pull-up and pull-down,the SCL is always high.

[Jared]

Hi,

Ok, then the I2C transfer is never started before it asserts. 

Can you share the code where the I2C is started and where you take the semaphore?

regards

Jared 

[hanks.liu]

thanks，I'll first see if I can reproduce the problem in the example program.

[Jared]

Ok, keep me posted and specify which sample that you are using,

regards

Jared

[hanks.liu]

hi,
There is no problem with the I2C signal line of the example "npm1300_one_button". One of the reasons for my problem is that the "bias-pull-up" is missing in the i2c part of the device tree.
But I encountered a new problem:
I need to change one of the I2C pins to P1.3. P1.3 is the NFC pin. Currently, even if I use the configuration CONFIG_NFCT_PINS_AS_GPIOS=y, it does not take effect. The register 0x500D66D4 that controls this function is still 1, indicating the NFC function. So if I want to configure P1.3 as non-NFC, is there any other configuration besides this configuration?

[Jared]

hanks.liu said:

There is no problem with the I2C signal line of the example "npm1300_one_button". One of the reasons for my problem is that the "bias-pull-up" is missing in the i2c part of the device tree.

ok, so the original problem was resolved after you added this?

hanks.liu said:

But I encountered a new problem:
I need to change one of the I2C pins to P1.3. P1.3 is the NFC pin. Currently, even if I use the configuration CONFIG_NFCT_PINS_AS_GPIOS=y, it does not take effect. The register 0x500D66D4 that controls this function is still 1, indicating the NFC function. So if I want to configure P1.3 as non-NFC, is there any other configuration besides this configuration?

Can you create a new ticket for this?

regards

Jared

[lu688]

这个问题解决了吗，是如何解决的？