Why can't I assign i2c0 pins to P0.06?

RE: Why can't I assign i2c0 pins to P0.06?

Bk37 — Tue, 14 Nov 2023 01:06:22 GMT

Found a solution that both works for the DK board, and a normal chip.

As pointed out in my post, some pins have 'defaults', and any re-configuration of these protocols is only adding to, not replacing the original pins.

For example, if UART0 has a default setting of TX to P0.06, even if you relocate TX to P0.07, TX will be BOTH P0.06 and P0.07, not just P0.07.

So you need to disable the conflicting protocol (UART0) entirely in the devicetree. For me, this isn't an issue because I don't need UART, and even if I did, I could just use UART1. With UART0 disabled, P0.06 is free to be used for i2c.

RE: Why can't I assign i2c0 pins to P0.06?

Øivind — Mon, 13 Nov 2023 14:23:21 GMT

Hi, could I see how you are setting up the file when you are using P0.06 for i2c0, and changing the pin for uart0?

Also make sure that you are doing a pristine build.

RE: Why can't I assign i2c0 pins to P0.06?

Turbo J — Sat, 11 Nov 2023 08:41:26 GMT

Go to the build folder, zephyr subdirectory and look into the full zeyphr.dts file. There you should find all the pin assignments - at least all done via dts files.

Remember that DTS pulls files from various sources during the build and combines them.