Tool/software:
Dear experts
I have enabled the i2C0 device on both the MCU20 and the kernel dts.
const i2c0 = i2c.addInstance(); i2c0.$name = "CONFIG_I2C0"; i2c0.useWakeupDomainPeripherals = false; i2c0.bitRate = "400KHZ"; i2c0.I2C.$assign = "I2C0"; i2c0.I2C.SCL.$suggestSolution = "I2C0_SCL"; i2c0.I2C.SDA.$suggestSolution = "I2C0_SDA";
&main_i2c0 { pinctrl-names = "default"; pinctrl-0 = <&main_i2c0_pins_default>; clock-frequency = <400000>; status = "okay"; bootph-all; ... }
Even if I don't use i2c0 for any reading or writing on MCU20(just design it on syscfg file), the i2c system will get stuck when using I2c0 in the kernel.
root@j722s-evm:~# i2cdetect -y -r 1 -- [ 4087.100091] omap_i2c 20010000.i2c: controller timed out
This is a waveform of quantity
If I2C0 is not enabled on MCU20, I2C0 can be used normally under the kernel.
It seems to be conflicting with each other, which is not a normal phenomenon. Is there a solution?
Thanks.