NRF54L10: I2C configuration error

Hello Team,

I'm using nrf54l15 dk and ncs version 2.9.0 for the development. I am getting an error while configuring I2C. I selected i2c20 from the device tree and assigned P1.00 for SCL and P1.01 for SDA. It generated the following code in the nrf54l15dk_nrf54l10_cpuapp.overlay file

&i2c20 {
	pinctrl-0 = <&i2c20_default>;
	pinctrl-names = "default";

};

&pinctrl {
	i2c20_default: i2c20_default {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 1, 1)>, <NRF_PSEL(TWIM_SCL, 1, 0)>;
		};
	};
};

Added the following configuration in the prj.conf file

CONFIG_I2C=y
CONFIG_PINCTRL=y
And wrote the following code to initialize I2C
#define I2C_NODE        DT_NODELABEL(i2c20)
const struct device *const i2c_dev = DEVICE_DT_GET(I2C_NODE);
const uint16_t i2c_addr = 0x68;
const struct i2c_dt_spec *i2c_spec;

i2c_spec = I2C_DT_SPEC_GET(I2C_NODE);
I'm getting the following error
devicetree error: 'pinctrl-0' is marked as required in 'properties:' in C:/ncs/v2.9.0/zephyr/dts/bindings\i2c\nordic,nrf-twim.yaml, but does not appear in <Node /soc/peripheral@50000000/i2c@c6000 in 'C:/ncs/v2.9.0/zephyr/misc/empty_file.c'>
Kindly help me resolve the error.
Regards,
Payal
Parents
  • Hi,

     

    P1.00 / P1.01 is by default used for the external LFXO. If testing on a DK, you should choose other pins.

    I am testing blinky, with your proposed overlay file in ncs v2.9.0, and I am unable to see this issue when compiling for nrf54l15/nrf54l10/cpuapp.

     

    Have you done any board-related changes in the zephyr/boards/nordic/nrf54l15dk catalog? If yes, try reverting those.

     

    Kind regards,

    Håkon

  • Hi,

    I tried configuring P1.02 for SDA and P1.03 for SCL. Now I am getting the following error.

    CMake Error at C:/ncs/v2.9.0/zephyr/cmake/modules/FindDeprecated.cmake:40 (if):
    if given arguments:

    "CROSS_COMPILE" "IN_LIST" "Deprecated_FIND_COMPONENTS"

    I am testing blinky, with your proposed overlay file in ncs v2.9.0, and I am unable to see this issue when compiling for nrf54l15/nrf54l10/cpuapp.

    While compiling the blinky sample for nrf54l10, I didn't add the .overlay file, but still I was getting the error.

    Have you done any board-related changes in the zephyr/boards/nordic/nrf54l15dk catalog? If yes, try reverting those.

    No, I didn't change anything in the zephyr/boards/nordic/nrf54l15dk catalog.

    While compiling any of the sample codes for nrf54l10 (not including .overlay file), I am getting the "devicetree error: 'pinctrl-0' is marked as required in 'properties:' in C:/ncs/v2.9.0/zephyr/dts/bindings\i2c\nordic,nrf-twim.yaml, but does not appear in <Node /soc/peripheral@50000000/i2c@c6000 in 'C:/ncs/v2.9.0/zephyr/misc/empty_file.c'>" error

  • Hi,

     

    It looks like you have altered the mcuboot app.overlay file:

    ....
    -- Found devicetree overlay: C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/app.overlay
    devicetree error: 'pinctrl-0' is marked as required in 'properties:' in C:/ncs/v2.9.0/zephyr/dts/bindings\i2c\nordic,nrf-twim.yaml, but does not appear in <Node /soc/peripheral@50000000/i2c@c6000 in 'C:/ncs/v2.9.0/zephyr/misc/empty_file.c'>
    CMake Error at C:/ncs/v2.9.0/zephyr/cmake/modules/dts.cmake:295 (execute_process):
      execute_process failed command indexes:
      
    ....
    I would recommend that you revert the changes done in this file:

    Go to folder "C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/" and open a cmd line in this path, then write:

    git checkout app.overlay

     

    Kind regards,

    Håkon

  • Hi,

    Go to folder "C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/" and open a cmd line in this path, then write:

    git checkout app.overlay

    I tried this, but I still get the same error while compiling for nrf54l10.

  • Hi,

     

    That is strange.

    Q1: Is the issue due to path length on your end?

    Try using a shorter path, for instance c:\sdk\my_app

    Q2: are you using a custom board, since you always add mcuboot even for blinky?

     

    Kind regards,

    Håkon

  • Try using a shorter path, for instance c:\sdk\my_app

    Tried. Not working.

    Q2: are you using a custom board, since you always add mcuboot even for blinky?

    No.

  • Hi,

    Could you share the full blinky project that fails, including which board you configure towards?

     

    Kind regards,

    Håkon

Reply Children
No Data
Related