Firefly Open Source Community

   Login   |   Register   |

About problem of Rrk3399's I2C being not able to driven up

5

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
5
Posted at 8/8/2018 17:49:26     
We encountered some problem of Camera integration. Currently our R&D progress is blocked at I2C being not able to driven up。 Even we are using official open-source code project and Devicetree file:


The phenomenon is any enabled I2C bus, SDA SCLkeep low. If externally connect to pull-up circuit,SDA become high voltage,but SCL is still less than 0.2V.
Check dmesg, it reports: “rk3x-i2c ff120000.i2c: timeout, ipd: 0x00, state:1”


Does anyone know the reaosn?
Reply

Use props Report

588

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
588
Posted at 8/13/2018 15:18:38     
I thought if you have not changed the code of the i2c2,  it might be the hardware broken.
Reply

Use props Report

76

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
76
Posted at 6/21/2019 22:52:48     
Hi,
I have got the same problem (same error message), but on I2C4.
When you say "It might be the hardware broken" : does Firefly change the board ? It's a brand new one received one week ago !!!
Reply

Use props Report

1034

Credits

0

Prestige

0

Contribution

vip

Rank: 6Rank: 6

Credits
1034
Posted at 6/24/2019 11:39:43     
@wizama

I2C4_SDA & I2C4_CLK are pulled up by the VCC_3V0 regulator.
Plz describe your problem more specifically.
It might be the same error message, but might not be the same reason.
Reply

Use props Report

76

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
76
Posted at 6/25/2019 00:14:14     
Last edited by wizama In 6/26/2019 16:19 Editor

Hi penguin,
Thank you for your message.

I have got 3 boards AIO-3399C, and the issue only concerns one of them.
All three run the same customized firmware which is compiled from the sources with only the LVDS screen resolution modified in the DTS and the boot animation updated with customized logo. No changes have been made about I2C configuration.
On the I2C4 port, a NFC reader is connected, but is never detected whereas it is on the 2 other boards.

Here is the log I got from debug serial port on launch :
  1. [    1.878134] rk3x-i2c ff3d0000.i2c: Initialized RK3xxx I2C bus at ffffff800994a000
Copy the code

which suppose it seems to correctly initialized;
however, when i run "i2cdetect -y 4" command as root, it runs very slow, and for each tested address, I have the following in the logs :
  1. [  288.691942] rk3x-i2c ff3d0000.i2c: timeout, ipd: 0x00, state: 1
Copy the code

SDA is 3V and SCL is 0V, but should be 3V also

On the 2 other boards, this command is fast and displays for each address if a device is connected or not.

Any idea ?


Reply

Use props Report

1034

Credits

0

Prestige

0

Contribution

vip

Rank: 6Rank: 6

Credits
1034
Posted at 7/1/2019 10:11:19     
You need to have the hardware guy check that.  SDA and SCL are pulled up to 3V. If no communication is in place, the voltage should be both 3V.
While communicating, there should be a square clock/signal.
Reply

Use props Report

85

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
85
Posted at 8/31/2019 03:54:23     
See: https://robot-electronics.co.uk/i2c-tutorial
In particular:
It shows how to wire up the I2C bus.
Reply

Use props Report

85

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
85
Posted at 8/31/2019 03:55:03     
Addendum: I've not tested the I2C bus yet, but I plan to.
Reply

Use props Report

1034

Credits

0

Prestige

0

Contribution

vip

Rank: 6Rank: 6

Credits
1034
Posted at 9/3/2019 17:49:54     
Thanks ballsystemlord , for attaching a clear picture and tutorial link.
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list