NCS - Devicetree & nrfx coexistence

RE: NCS - Devicetree & nrfx coexistence

Elfving — Tue, 03 Dec 2024 08:09:34 GMT

Oh, I see.

Glad you found a solution that worked for you, and thanks for sharing it in case anyone else runs into the same problem 🙂

Regards,

Elfving

RE: NCS - Devicetree & nrfx coexistence

eyalasko — Mon, 02 Dec 2024 16:18:53 GMT

Thanks Elfving for your reply.

The answer lies in this post - Turning on TWIM/TWIS without devicetree

in short -

Add the following to app.overlay

&i2c0 {

status = "okay";

compatible = "nordic,nrf-twim"; // this is the secret (apparently)

};

&i2c1 {

status = "okay";

compatible = "nordic,nrf-twim";

};

add the following to prj.conf

CONFIG_I2C=y

RE: NCS - Devicetree & nrfx coexistence

Elfving — Mon, 02 Dec 2024 15:04:07 GMT

Hello Eyelasko,

[quote user=""]

As I use interchangeably the same pins as GPIOs and UARTE1, I use UARTE1 with NRFX drivers:

[/quote]

So if I understand you correctly, you want to use nrfx because you want to programmatically change when you use the same pins for multiple different peripherals?

I have to say also that creating a pure nrfx project without dts is not recommended. NCS relies on Zephyr, which is heavily dependent on dts. Disabling a few specific peripherals in order to take control with nrfx however is considered fine.

[quote user=""]What should I do if I want to use NRFX peripherals that ARE defined in the default dts file (specifically - TWIM0 & TWIM1)
[/quote]

I believe you would have to change the dts to disable these peripherals, so that nrfx can take control of them directly. Ie. something like this:

&i2c0 {
    status = "disabled";
};

&i2c1 {
    status = "disabled";
};

Regards,

Elfving