IMU address 0x0E is caught as UU in I2C-4

VIM3
1

Which Khadas SBC do you use?

VIM3
**Delete this line and post your answer here.**

Which system do you use? Android, Ubuntu, OOWOW or others?

UBUNTU
**Delete this line and post your answer here.**

Which version of system do you use? Khadas official images, self built images, or others?

KHADAS OFFCIAL IMAGE
**Delete this line and post your answer here.**

Please describe your issue below:

hi
I am a user of vim3 and I know the i2c address of KXTJ3-1057 is 0x0e, but when I run i2cdetect -r 4, the address is displayed as UU. Is there any way to solve this?
**Delete this line and post your answer here.**

Post a console log of your issue below:

WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-4 using receive byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- UU --
10: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
20: UU -- 22 -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --
70: -- -- -- -- -- -- -- --  
**Delete this line and post your log here.**
2

It should be readable, UU indicates that address is being used, this is assuming it is your accel. chip. Disconnect the KXT board and that should disappear.

3

Sadly my vim3 doesn’t have anything connected to it, is there any way to disable the built-in KTX board, and also does anyone know where to find it?

4

You might break the system disabling some of that stuff in the device tree.
Can you change the address of your device and reconnect it and see what happens?
Also, make sure you have the correct device tree loaded. Some place is a list of the different combinations of I2c/Uart/Gpio. You might be seeing the internal i2c of the SoC and not your external device.

5

i2c3 is fine, what I want is ktxj3 connected to i2c4
When I do dmesg|i2c in my vim3, it looks like this
[ 0.998816] i2c /dev entries driver
[ 7.358582] i2c i2c-4: sensor_probe: kxtj3,ffffffc046d52000
[ 7.359355] input: gsensor as /devices/platform/soc/ff800000.aobus/ff805000.i2c/i2c-4/4-000e/input/input4
It seems to be connected fine, and when I search for i2c4, it shows up as uu, unlike the tutorials I found, so I can’t use the i2cdump command.

6

It is in the same status as the topic in the link above I want to know how to resolve or access 0x0e or resolve uu

In the tutorials I see, the address comes up fine and the
i2cdump -y 0x0e
i2cget -y 0x0e 0x0f to access it

7

now used os “vim3-ubuntu-20.04-gnome-linux-4.9-fenix-1.5-230425-emmc”