Jetson Tx2 camera I2C communication problem

I develop custom camera porting in Jetson Tx2 board.

custom sensor slave address : 0x20

I am testing by modifying the ov5693 device driver.

I2C communication is not working.
i2cdetect It looks like you read some data like the message below.

jpchae@jpchae-desktop:~/Downloads$ sudo i2cdetect -y -r 2
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: 10 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

dmesg message is shown below.

[ 840.443150] tegra-i2c 3180000.i2c: no acknowledge from address 0x3

I checked for a hardware connection problem.

pwdn-gpio, reset-gpio high / low operation check is okay
scl-gpio Oscilloscope to check 8-bit clock generating is okay
sda-gpio Oscilloscope to check 8-bit data signal is okay

I have also lowered the speed of the i2c clock.

i2cset and i2cget commands give an error. (The symptoms are the same for the ov5693 camera.)

jpchae@jpchae-desktop:~/Downloads$ sudo i2cset -f -y 2 0x20 0x01 0x00
Error: Write failed

jpchae@jpchae-desktop:~/Downloads$ sudo i2cget -f -y 2 0x20
Error: Read failed

This test hardware confirms that it works on the evm board for camera testing, and attempts to connect to jetson tx2.

Where should I check?
Please let me know if there is a way to test the operation of i2C in device driver separately.

Do you mean you have the signals waveform of I2C dat/clk are correct but can’t get ACK? Is the address correct? Why it is 0x20 but get message of "[ 840.443150] tegra-i2c 3180000.i2c: no acknowledge from address 0x3? If waveform output is correct, then seems like it is problem of sensor itself which need to check based on its datasheet or support of vendor.

Hi Trumany,

As your advise, I checked address value.
technical document is very confuseing address value, finally i knew the address,
I solved problem.

Thank you for your help.