I2C Configuration Issue in nrf5340 audio dk

RE: I2C Configuration Issue in nrf5340 audio dk

helsing — Fri, 12 Sep 2025 13:51:36 GMT

Hi Dhruvish Patel,

Could you please verify that you have added a label like for example "I2C_2" to your overlay? Please also verify that you have updated the main file with this label as well.

Please try adding the I2C_2 label as shown below.

&i2c2 {
	status = "okay";
	label = "I2C_2";

	/* Azoteq IQS323: touch/wear detection */
	iqs323: iqs323@44 {
		compatible = "azoteq,iqs323";
		reg = <0x44>;
		enable-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>; /* P0.12 - RDY pin */
		status = "okay";
	};

	/* Azoteq IQS7211E: touch/slider */
	iqs7211e: iqs7211e@56 {
		compatible = "azoteq,iqs7211e";
		reg = <0x56>;
		enable-gpios = <&gpio0 13 GPIO_ACTIVE_LOW>; /* P0.13 - RDY pin */
		status = "okay";
	};
};

RE: I2C Configuration Issue in nrf5340 audio dk

Dhruvish Patel — Mon, 08 Sep 2025 13:27:12 GMT

&i2c2 {
	status = "okay";

	/* Azoteq IQS323: touch/wear detection */
	iqs323: iqs323@44 {
		compatible = "azoteq,iqs323";
		reg = <0x44>;
		enable-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>; /* P0.12 - RDY pin */
		status = "okay";
	};

	/* Azoteq IQS7211E: touch/slider */
	iqs7211e: iqs7211e@56 {
		compatible = "azoteq,iqs7211e";
		reg = <0x56>;
		enable-gpios = <&gpio0 13 GPIO_ACTIVE_LOW>; /* P0.13 - RDY pin */
		status = "okay";
	};
};

RE: I2C Configuration Issue in nrf5340 audio dk

helsing — Tue, 26 Aug 2025 13:53:19 GMT

Would you be able to share the output logs from when the binding error occurs (use Insert->Code in DevZone)? Could you please also share the overlay? Is nrf5340_audio the application you are using? Which nRF Connect SDK is it?

Have you enabled the config for TWIM number two?

CONFIG_NRFX_TWIM2=y

RE: I2C Configuration Issue in nrf5340 audio dk

Dhruvish Patel — Tue, 26 Aug 2025 08:35:41 GMT

hi helsing ,

I have done same device tree configuration in nrf5340 audio firmware.so it is always throwing binding error.
same this i am doing for i2c1 it is working fine.

FYI, i am using nrf5340 audio FW and using Nordic 5340 audio dK kit.

Kindly help on this issue.

Regards,

Dhruvish Patel

RE: I2C Configuration Issue in nrf5340 audio dk

helsing — Mon, 25 Aug 2025 13:05:50 GMT

When selecting an instance for i2c, make sure that instance has not been used before. For example, do not select i2c3 if uart3 is already in use in your project. Try selecting i2c2 for the nRF5340 Audio DK.

Try something like this in the overlay:

&i2c2 {
    status = "okay";
    pinctrl-0 = <&i2c2_default>;
    pinctrl-names = "default";
    clock-frequency = <I2C_BITRATE_STANDARD>;

    iqs323: iqs323@44 {
        compatible = "i2c-device";
        reg = <0x44>;
        label = "IQS323";
    };

    iqs7211a: iqs7211a@56 {
        compatible = "i2c-device";
        reg = <0x56>;
        label = "IQS7211A";
    };
};

&pinctrl {
    i2c2_default: i2c2_default {
        group1 {
            psels = <NRF_PSEL(TWIM_SCL, 0, 26)>,
                    <NRF_PSEL(TWIM_SDA, 0, 25)>;
        };
        
    };
};

Add pinctrl for sleep as well, as seen in this exercise.

RE: I2C Configuration Issue in nrf5340 audio dk

Dhruvish Patel — Wed, 20 Aug 2025 06:30:28 GMT

hi,

Thanks for reply.

I have already gone through this.

I am modifying existing nrf5340 audio code because i want functionality in that code only.

i want to configure Azoteq IQS323 wear detection(0x44) and Azoteq IQS7211a(0x56) both single I2C.

But everytime whenever i try to configure I2C binding is not happening,

I2C0 and I2C1 cannot be utilized because it is already configured in nrf5340 audio firmware.

Kindly guide through in I2C configuration in existing firmware of nrf5340 audio.

Thanks & regards,

Dhruvish Patel

RE: I2C Configuration Issue in nrf5340 audio dk

helsing — Tue, 19 Aug 2025 11:52:56 GMT

Hi Dhruvish,

Thank you for the request. I will take a closer look and get back to you. Meanwhile, have you had a look at the Lesson on I2C Driver over at DevAcademy?

Regards,

Håkon