Jump to content

Recommended Posts

hi everyone

I think I'm doing smth wrong with my tinker board 2

I've turned on all i2c overlays and connected i2c device to pins 3,5, double checked wires

i2cdetect can't detect any device, prints empty bus, but device is connected

What am I missing ?

Share this post


Link to post
Share on other sites

hello @giseleznev

what's the config.txt that you modified and what's the i2c device you connected to?

Share this post


Link to post
Share on other sites
Posted (edited)

Device is si5351chip
I've just changed 

#intf:i2c6=off to intf:i2c6=on

from the default, i do have 6-th here:

ls /dev/i2c*

but i get empty line from 

sudo i2cdetect -y 6
Edited by giseleznev

Share this post


Link to post
Share on other sites

hello @giseleznev

1. have you made a reboot after saving the config.txt?

2. what's the result of this command?

2 hours ago, giseleznev said:

ls /dev/i2c*

 

 

3. by empty, does it mean that only slave address is shown but the device is not found?

2 hours ago, giseleznev said:

sudo i2cdetect -y 6

 

Share this post


Link to post
Share on other sites

@tooz

By the way, here is my dmesg with some errors. What does it mean ?

linaro@linaro-alip:~$ dmesg | grep i2c

[    1.865109] i2c /dev entries driver

[    1.869490] of_get_named_gpiod_flags: parsed 'vsel-gpios' property of node '/i2c@ff3c0000/fan53200@60[0]' - status (0)

[    1.883092] rk3x-i2c ff3c0000.i2c: Initialized RK3xxx I2C bus at ffffff8009858000

[    1.891296] rk3x-i2c ff110000.i2c: Initialized RK3xxx I2C bus at ffffff800985a000

[    1.899201] rk3x-i2c ff120000.i2c: Initialized RK3xxx I2C bus at ffffff800985c000

[    1.907105] rk3x-i2c ff150000.i2c: Initialized RK3xxx I2C bus at ffffff800985e000

[    1.915409] of_get_named_gpiod_flags: parsed 'vsel-gpios' property of node '/i2c@ff3d0000/fan53200@60[0]' - status (0)

[    1.928973] rk3x-i2c ff3d0000.i2c: Initialized RK3xxx I2C bus at ffffff8009860000

[    1.937317] rk3x-i2c ff3e0000.i2c: Initialized RK3xxx I2C bus at ffffff8009862000

[    1.964363] tinker-mcu: tinker_mcu_probe: i2c_id= 0x8

[    2.027682] tinker-mcu: tinker_mcu_ili9881c_probe: i2c_id= 0x8

[    2.210914] of_get_named_gpiod_flags: can't parse 'dvs-gpios' property of node '/i2c@ff3c0000/pmic@1b[0]'

[    2.210925] of_get_named_gpiod_flags: can't parse 'dvs-gpio' property of node '/i2c@ff3c0000/pmic@1b[0]'

[    2.217168] of_get_named_gpiod_flags: can't parse 'dvs-gpios' property of node '/i2c@ff3c0000/pmic@1b[1]'

[    2.217179] of_get_named_gpiod_flags: can't parse 'dvs-gpio' property of node '/i2c@ff3c0000/pmic@1b[1]'

[    2.295962] of_get_named_gpiod_flags: parsed 'int-n-gpios' property of node '/i2c@ff3d0000/fusb30x@22[0]' - status (0)

[    2.296029] of_get_named_gpiod_flags: parsed 'vbus-5v-gpios' property of node '/i2c@ff3d0000/fusb30x@22[0]' - status (0)

[    2.296073] of_get_named_gpiod_flags: can't parse 'vbus-other-gpios' property of node '/i2c@ff3d0000/fusb30x@22[0]'

[    2.296083] of_get_named_gpiod_flags: can't parse 'vbus-other-gpio' property of node '/i2c@ff3d0000/fusb30x@22[0]'

[    2.296128] of_get_named_gpiod_flags: can't parse 'discharge-gpios' property of node '/i2c@ff3d0000/fusb30x@22[0]'

[    2.296138] of_get_named_gpiod_flags: can't parse 'discharge-gpio' property of node '/i2c@ff3d0000/fusb30x@22[0]'

[    2.315813] input: Typec_Headphone as /devices/platform/ff3d0000.i2c/i2c-4/4-0022/input/input0

[    3.141361] of_get_named_gpiod_flags: parsed 'irq_gpio_number' property of node '/i2c@ff110000/gsl3673@40[0]' - status (0)

[    3.141394] of_get_named_gpiod_flags: parsed 'rst_gpio_number' property of node '/i2c@ff110000/gsl3673@40[0]' - status (0)

[    3.141697] input: gsl3673 as /devices/platform/ff110000.i2c/i2c-1/1-0040/input/input1

[    3.197419] gsl3673 1-0040: GSL3673 test_i2c error!

[    3.780928] of_get_named_gpiod_flags: parsed 'enable-gpios' property of node '/i2c@ff110000/imx219@10[0]' - status (0)

[    4.654953] i2c i2c-9: of_i2c: modalias failure on /hdmi@ff940000/ports

[    4.692103] i2c i2c-10: of_i2c: modalias failure on /dp@fec00000/ports

 

Share this post


Link to post
Share on other sites

hello @giseleznev

i didn't see anything that relates to i2c-6 from your dmesg result. have you used 1. another device and see if the 40 pin header works? 2. check the hardware signal?

i don't have the a si5351 so i use a rtc for testing, vcc3.3v=pin1, sda=pin3, scl=pin5, gnd=pin9

sudo vim /boot/config.txt
intf:i2c6=on

save and reboot

sudo i2cdetect -y 6

Screenshot from 2023-06-20 10-53-35.png

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...