Howdy,
I'm trying to get the rtc working on an armada-370 device but am having trouble getting the i2c bus to work. I can tell from the dmesg output from the stock firmware that the rrtc works and is connected via i2c. In fact I've had no trouble with some very similar devices (with the same stock dmesg output) but haven't had luck with this one but am encountering this on multiple units of this same model (i'm confident it isn't an issue with the individual device).
I've tried changing the pins from the default for the device to some of the alternates and have tried adjusting the bus speed but haven't had much luck. I have noticed that after I unplug the device and plug it back in (but not after a soft reboot) I get the following when starting the scan:
The dmesg output I see in stock firmware and on other working devices in debian is:
The error I'm seeing when i2cdetect fails is:
The device tree for this device can be seen here:
https://github.com/1000001101000/Debian_on_Buffalo/blob/master/Buster/device_trees/armada-370-terastation-ts1400d.dts
does @bohdi or anyone have any advice on how to troubleshoot i2c issues like this? I'm reloading the stock firmware now examine a working system but don't know exactly what to look for.
any help would be greatly appreciated.
I'm trying to get the rtc working on an armada-370 device but am having trouble getting the i2c bus to work. I can tell from the dmesg output from the stock firmware that the rrtc works and is connected via i2c. In fact I've had no trouble with some very similar devices (with the same stock dmesg output) but haven't had luck with this one but am encountering this on multiple units of this same model (i'm confident it isn't an issue with the individual device).
I've tried changing the pins from the default for the device to some of the alternates and have tried adjusting the bus speed but haven't had much luck. I have noticed that after I unplug the device and plug it back in (but not after a soft reboot) I get the following when starting the scan:
client found at address 0x48This makes me think the chip might be getting into a bad state which requires power cycling to clear.
The dmesg output I see in stock firmware and on other working devices in debian is:
i2c /dev entries driver rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6 rtc-rs5c372 0-0032: create wakealarm rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
The error I'm seeing when i2cdetect fails is:
[ 6945.844595] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
The device tree for this device can be seen here:
https://github.com/1000001101000/Debian_on_Buffalo/blob/master/Buster/device_trees/armada-370-terastation-ts1400d.dts
does @bohdi or anyone have any advice on how to troubleshoot i2c issues like this? I'm reloading the stock firmware now examine a working system but don't know exactly what to look for.
any help would be greatly appreciated.