TWIM issue on NRF54L15

RE: TWIM issue on NRF54L15

lu688 — Mon, 19 May 2025 11:41:11 GMT

厉害，在跑SDK的情况下，有没有发现,P1.06也是用不了的？

RE: TWIM issue on NRF54L15

hanks.liu — Fri, 16 May 2025 08:44:53 GMT

解决了，除了CONFIG_NFCT_PINS_AS_GPIOS=y，还要在overlay加入&uicr {
nfct-pins-as-gpios;
};

RE: TWIM issue on NRF54L15

lu688 — Thu, 15 May 2025 14:56:19 GMT

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

RE: TWIM issue on NRF54L15

Jared — Fri, 20 Dec 2024 10:30:24 GMT

[quote user="hanks.liu"]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.[/quote]

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

[quote user="hanks.liu"]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?[/quote]

Can you create a new ticket for this?

regards

Jared

RE: TWIM issue on NRF54L15

hanks.liu — Fri, 20 Dec 2024 06:50:34 GMT

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?

RE: TWIM issue on NRF54L15

Jared — Thu, 19 Dec 2024 11:02:27 GMT

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

regards

Jared

RE: TWIM issue on NRF54L15

hanks.liu — Thu, 19 Dec 2024 10:40:00 GMT

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

RE: TWIM issue on NRF54L15

Jared — Thu, 19 Dec 2024 10:24:03 GMT

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

RE: TWIM issue on NRF54L15

hanks.liu — Thu, 19 Dec 2024 00:39:41 GMT

yss,no CLK signal on SCL and no data on SDA。

RE: TWIM issue on NRF54L15

Jared — Wed, 18 Dec 2024 12:01:07 GMT

Hi,

Ok, so you see no CLK signal on SCL and no data on SDA?

regards

Jared

RE: TWIM issue on NRF54L15

hanks.liu — Wed, 18 Dec 2024 10:38:23 GMT

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.

RE: TWIM issue on NRF54L15

Jared — Wed, 18 Dec 2024 10:32:17 GMT

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