Hi,
We are currently porting our code to the newest nRf5340 chip.
Everything goes fine when the target is secure (not ending with "ns" and not defining "CONFIG_TRUSTED_EXECUTION_NONSECURE".
However, when changing the target to be "nonsecure", the I2C stops working, with every i2c_xxx function returning -EBUSY.
What do I need to do to enable i2c when using the non-secure target?
Our device tree is using the same philosophy as nrf5340dk, with a common dts file with
&i2c2 {
compatible = "nordic,nrf-twim";
status = "okay";
sda-pin = <34>;
scl-pin = <4>;
clock-frequency = <I2C_BITRATE_STANDARD>;
zephyr,concat-buf-size = <520>;
....
};
Regards
Giuliano