RE: NRF54L15 I2C Issue (I2C22)

Thibaut LALUQUE — Thu, 10 Jul 2025 08:01:20 GMT

Abhijith, thanks for your reply.

I followed the old DevZone thread and it solved the problem !

As explained in this thread, by default pins P1.02 and P1.03 are routed to NFC functions, and it's necessary to add a directive in the device tree to specify that these pins must be used as standard GPIOs.

This can be done by adding these lines in the device tree :

&uicr {

nfct-pins-as-gpios;

};

To test on the nrf54l15dk board, according the hardware shemes, it's necessary to mount 0ohm on R33/R34 and to unmount R21/R22.

Kind regards,

Thibaut

RE: NRF54L15 I2C Issue (I2C22)

Menon — Tue, 08 Jul 2025 08:44:38 GMT

Hello,

Thanks for the update and the shared files.

If you take a look at the nRF54L15DK datasheet, you'll see that P1.02 and P1.03 are not connected to the GPIO headers by default, they are physically routed to the NFC antenna path. You need to configure them to be used as regular GPIOs. See this old DevZone thread.

Kind regards,
Abhijith

RE: NRF54L15 I2C Issue (I2C22)

Thibaut LALUQUE — Fri, 04 Jul 2025 12:41:35 GMT

Abhijith, thanks for your reply.

Here the log. Even with CONFIG_I2C_LOG_LEVEL_DBG=y they are nothing that appears in logs about I2C

*** Booting nRF Connect SDK v3.0.1-9eb5615da66b ***
*** Using Zephyr OS v4.0.99-77f865b8f8d0 ***

[00:00:06.613,090] <dbg> AniTrack: main: Test log debug level
[00:00:10.024,711] <inf> AniTrack: Testing ACC
[00:00:10.024,743] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x200026e0 - rx_bufs 0x200026f0 - 1
[00:00:10.024,753] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x200026d8 (1), current_rx 0x200026e8 (1), tx buf/len 0x200026d0/2, rx buf/len 0x200026d4/2
[00:00:10.024,793] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len 0/0
[00:00:10.024,801] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0/0
[00:00:10.024,808] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:10.024,827] <inf> AniTrack: Requested WHO AM I, received : 69
[00:00:10.024,832] <inf> AniTrack: ACC is responding !
[00:00:10.024,837] <inf> AniTrack: Testing FLASH
[00:00:10.024,851] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x200026e0 - rx_bufs 0x200026f0 - 1
[00:00:10.024,870] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x200026d8 (1), current_rx 0x200026e8 (1), tx buf/len 0x200026d0/4, rx buf/len 0x200026d4/4
[00:00:10.024,924] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len 0/0
[00:00:10.024,931] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0/0
[00:00:10.024,938] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:10.024,958] <inf> AniTrack: Requested WHO AM I, received : 44 37
[00:00:10.024,963] <inf> AniTrack: FLASH is responding !
[00:00:10.024,968] <inf> AniTrack: Testing EEPROM
[00:00:10.024,972] <inf> AniTrack: Writting EEPROM
[00:00:10.525,138] <inf> AniTrack: result : -5
[00:00:10.525,153] <wrn> AniTrack: Fail to write EEPROM
[00:00:10.936,546] <inf> AniTrack: Testing ACC
[00:00:10.936,556] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x200026e0 - rx_bufs 0x200026f0 - 1
[00:00:10.936,565] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x200026d8 (1), current_rx 0x200026e8 (1), tx buf/len 0x200026d0/2, rx buf/len 0x200026d4/2
[00:00:10.936,605] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len 0/0
[00:00:10.936,613] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0/0
[00:00:10.936,621] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:10.936,639] <inf> AniTrack: Requested WHO AM I, received : 69
[00:00:10.936,644] <inf> AniTrack: ACC is responding !
[00:00:10.936,658] <inf> AniTrack: Testing FLASH
[00:00:10.936,667] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x200026e0 - rx_bufs 0x200026f0 - 1
[00:00:10.936,676] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x200026d8 (1), current_rx 0x200026e8 (1), tx buf/len 0x200026d0/4, rx buf/len 0x200026d4/4
[00:00:10.936,729] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len 0/0
[00:00:10.936,737] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0/0
[00:00:10.936,743] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:10.936,763] <inf> AniTrack: Requested WHO AM I, received : 44 37
[00:00:10.936,768] <inf> AniTrack: FLASH is responding !
[00:00:10.936,773] <inf> AniTrack: Testing EEPROM
[00:00:10.936,777] <inf> AniTrack: Reading EEPROM
[00:00:11.436,946] <inf> AniTrack: result : -5
[00:00:11.436,962] <wrn> AniTrack: Fail to read EEPROM

This is a custom board. I also tried to run my code on the nrf54l15dk board and I get the same behavior. They are no I2C signals on P1.03(SCL) and P1.02(SDA).

Please, find bellow the zephyr.dts file that was generated for my custom board.

devzone.nordicsemi.com/.../8228.zephyr.dts

Kind regards,

Thibaut

RE: NRF54L15 I2C Issue (I2C22)

Menon — Thu, 03 Jul 2025 18:18:04 GMT

Hello,

Could you share the complete log here? If you haven’t enabled debug-level logs, please try enabling them and then share the full output. See the configuration option CONFIG_I2C_LOG_LEVEL_DBG.

Is this a custom board or a Development Kit (DK)? Also, could you share the zephyr.dts file from the build folder?

Kind regards,
Abhijith