Pretty sure the resisters were acting as pull-ups. Sorry I misunderstood and thought perhaps the eeprom you mentioned as something on board the BPI-R2. I am running 4.14 compiled after a checkout from your repo. I do see error -110 in the dmesg output after attempting to insert the device via echo > new_device.
I might just try grabbing another module designed for a RPI where everything is expecting 3v logic based on your clarification, as I don’t have anything else to test this module out with.
Hi. I am Frank’s 4.14.28 kernel and I can find that the I2C0 & I2C1 are exist on /dev/.
However, i2cdetect -y 0/1 detected nothing. I am using 420mA Serial to I2C converter. I confirmed that my I2C module is working fine on RPI board. So I assume, I no need to worry up the pullups.
For experiment, I also tried with DS3231 RTC module. Still it is not detected anything on the I2C port.
I have an issue on BPi-R2 and time is always behind. After one night the clock is 15minutes behind current time.
I have sync (ntp) the time yesterday after boot as it was 1 week behind current time. How come the BPI-R2 is always behind current time? I have “RTC_DRV_DS1307” enable in the kernel. Do i have to buy a physical new card for RTC (Real Time Clock) ?
Exactly, because attached it to i2c-1.
But it applies time after kernel modules loaded. Does it make sense? It should know time from startup, shouldn’t it?
I got it from a friend of mine, didn’t read any of its advantage.
What is your suggestion regarding hdmi problem?