|
Clusterboard Armbian
|
02-19-2018, 02:09 PM
This is a build of "minimal" Armbian with the change I had to make to get networking working. Do not update the the dtb file or it will break again. I am waiting on some feadback so I can upstream the fix if it works on other versions.
https://storage.googleapis.com/pine64-im....20.img.xz
04-09-2018, 09:18 AM
Should i2c be working in this build? I tried connecting a device and installing the i2c tools package but I get errors when I try to run i2cdetect (can't open the device file).
I tried a few things but then I think I updated the wrong packages and broke it  I'm going to take another pass with a fresh image but any feedback as to the state of i2c support in the base build is appreciated. Thanks again for putting this image together! jjg
04-09-2018, 11:22 AM
As far as I know. I really only did a one line change in the dtb to change rgmii to rgmii-txid, which is related to network timing. If i2c is broke I might of built the image incorrectly or it might just be broken in latest source for armbian when I built it.
04-09-2018, 12:41 PM
(04-09-2018, 11:22 AM)aww Wrote: As far as I know. I really only did a one line change in the dtb to change rgmii to rgmii-txid, which is related to network timing. If i2c is broke I might of built the image incorrectly or it might just be broken in latest source for armbian when I built it. Cool, thanks for the feedback. I'll keep poking at it and report back if I find anything interesting
04-10-2018, 03:09 AM
Is the I2C node you are using enabled in your devicetree?
Come have a chat in the Pine IRC channel >>
04-10-2018, 06:32 AM
04-10-2018, 06:42 AM
(04-10-2018, 03:09 AM)xalius Wrote: Is the I2C node you are using enabled in your devicetree? Unsure; what's the best way to check that? I'm pretty green to the i2c stuff so part of my problem is that I don't know what all of the dependencies are or how to check them : I managed to fumble my way through it on an A64 but looks like I need to understand it better to get things working on the Clusterboard.
04-11-2018, 09:27 AM
Update: I was able to get armbian-config to run correctly with this latest image (thanks @aww!) and I was able to enable the i2c bus(s) that way.
04-13-2018, 09:28 PM
(04-10-2018, 06:32 AM)aww Wrote: https://storage.googleapis.com/pine64-im....33.img.xz Thanks very much for this. I have noticed that this version seems to leave the sopine module hung if you try to do a "reboot". The 4.14.20 version rebooted clean. This is surprisingly important in the clusterboard where you really don't have the option of a power cycle w/out dropping all the other nodes at the same time. Also, I'm still having trouble with the SoC temperature sensors. If you read /sys/devices/virtual/thermal/thermal_zone0/temp you get a negative number instead of the SoC temp. This works on Ayufan's load but his build doesn't start up consistently when all 7 modules are on the clusterboard.
04-16-2018, 12:37 PM
So my PR to armbian upstream has been merged for clusterboard, at least into the development branch. So in the near future you should be able to just use upstream armbian builds.
As far as the temperature stuff I think that's a known issue with the mainline kernel and is supposedly in progress: http://linux-sunxi.org/Linux_mainlining_effort |
