Device address cannot be detected by i2cdetect on ls1028

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Device address cannot be detected by i2cdetect on ls1028

Jump to solution
1,654 Views
Eddy1
Contributor IV

Hi:

I am using ls1028 to develop my device, but I have encountered a strange problem, which has been bothering me for several days. I hope you can give me some suggestions:

1)I add several device nodes under the i2c1 device tree node, but I can't detect the address with i2cdetect:

First of all, I add our modifications to the RCW file:vi rcw_1500_gpu600.rcw 

1053924360_0-1623057778814.png

Then add our device nodes to the kernel device tree:

1053924360_1-1623057907856.png

Then enter the system, but can't detect address, could you give suggestions?

i2cdetect -y -r 0

1053924360_2-1623058046968.png

 

 

0 Kudos
1 Solution
1,623 Views
Eddy1
Contributor IV

Hi:

Thank you for your reply. The problem has been solved. It's the problem of hardware connection

View solution in original post

0 Kudos
2 Replies
1,636 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please go to u-boot prompt and check whether you could get valid values similar as the following.

=> i2c bus
Bus 0: i2c@2000000 (active 0)
77: i2c-mux@77, offset len 1, flags 0
66: generic_66, offset len 1, flags 0
57: generic_57, offset len 1, flags 0
Bus 1: i2c@2000000->i2c-mux@77->i2c@3
51: rtc@51, offset len 1, flags 0
Bus 2: i2c@2010000
Bus 3: i2c@2020000
Bus 4: i2c@2030000
Bus 5: i2c@2040000
Bus 6: i2c@2050000
Bus 7: i2c@2060000
Bus 8: i2c@2070000

=> i2c dev 0
Setting bus to 0
=> i2c probe
Valid chip addresses: 00 50 52 53 57 66 67 77 7C
=> i2c speed
Current bus speed=100000
=> i2c md 0x50 0
0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
=> i2c dev 1
Setting bus to 1
=> i2c probe
Valid chip addresses: 00 4C 51 66 67 77 7C
=> i2c md 0x51 0
0000: 44 28 20 54 04 03 03 07 30 80 80 80 80 80 20 c2 D( T....0..... .

0 Kudos
1,624 Views
Eddy1
Contributor IV

Hi:

Thank you for your reply. The problem has been solved. It's the problem of hardware connection

0 Kudos