static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

RE: static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

noob_123 — Tue, 28 Jun 2022 15:56:04 GMT

If you go to pinctrl.dtsi file you will find the pinctrl for i2c1 as follow

i2c1_default: i2c1_default {

group1 {

psels = <NRF_PSEL(TWIM_SDA, 0, 30)>,

<NRF_PSEL(TWIM_SCL, 0, 31)>;

};

i2c1_sleep: i2c1_sleep {

group1 {

psels = <NRF_PSEL(TWIM_SDA, 0, 30)>,

<NRF_PSEL(TWIM_SCL, 0, 31)>;

low-power-enable;

};

From there you can find the Pins for i2c1 or i2c0 whatever you are using. Then you can remove pin configuration from overlay and it will start communicating. At least this works for me

RE: static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

JSCBLOG — Tue, 28 Jun 2022 15:31:17 GMT

I've finally got it working. I changed from trying to get i2c0 working to i2c3, as I figured I had to disable uart0, which might already be used for the terminal (could be wrong). The only thing I changed was my prj.conf file, which probably could be improved such as changing i2c0_default_alt to i2c3_default_alt. But it works and I'm happy. Side note: I have never had to work so hard to figure out how to get a peripheral working on any microcontroller, as I had to do with this.

Also, I'm using the nRF9160 DK board.

prj.conf

&pinctrl {

i2c0_default_alt: i2c0_default_alt {

group1 {

psels = <NRF_PSEL(TWIM_SDA, 0, 12)>,

<NRF_PSEL(TWIM_SCL, 0, 11)>;

};

&i2c3 {

status = "okay";

compatible = "nordic,nrf-twim";

pinctrl-0 = <&i2c0_default_alt>;

pinctrl-names = "default";

// pinctrl-1 = <&i2c0_sleep_alt>;

clock-frequency = <I2C_BITRATE_STANDARD>;

};

/* These two lines are probably not needed below as I'm not using i2c0 */

&spi0 {

status = "disabled";

};

&pwm0 {

status = "disabled";

};

RE: static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

JSCBLOG — Tue, 28 Jun 2022 14:36:47 GMT

My I2C2 port is enabled by default. I think my application was based on an example, but it's been a while and I don't even know what one it was.

RE: static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

noob_123 — Tue, 28 Jun 2022 14:30:21 GMT

Did you manage to get I2C working with any other port?

RE: static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

JSCBLOG — Tue, 28 Jun 2022 14:28:04 GMT

No sorry, I'm so lost with this. I just want to use another I2C port 😭

RE: static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

noob_123 — Tue, 28 Jun 2022 14:20:06 GMT

Did you manage to find a solution?

RE: static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

noob_123 — Tue, 28 Jun 2022 14:18:21 GMT

I tried disabling pincontrol from configuration file but again it ends with a new error. About migrating the device tree files can you show any specific example for i2c.

RE: static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

Kazi Afroza Sultana — Tue, 28 Jun 2022 13:57:43 GMT

Hello,

I think you have two options to resolve the issue either disable pin controls or migrating the device tree files. You can see this link

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_pinctrl.html

Thanks.

Best Regards,

Kazi Afroza Sultana

RE: static assertion failed: "/soc/i2c@40004000 has legacy *-pin properties defined although PINCTRL is enabled"

JSCBLOG — Tue, 28 Jun 2022 13:03:08 GMT

Yea, I have to same problem when trying to add I2C1 in the overlay file.