That’s a good idea. I’ll try that when I go back down there again. I think I did actually get them at 9600 baud rate, last week during one of my tests. But to be totally honest I’ve forgotten what all I’ve done as there have seen so many different things, lol…
But it’s a good idea though, so I’ll definitely try it when I’m in the lab next.
By the way–there’s another thread on the forum here, and it’s related to the i2c bus. It appears to me as though there’s an issue with the i2c bus(es) on the Linux side as well, but I haven’t yet put much time into exploring that. I did want to tell you though that your -r flag tip seems to come in handy with i2c-0, i2c-1 and i2c-2, as many of the addresses are apparently read-only. If if just use i2cdetect -y 0 for instance, there are a BUNCH of addresses that don’t show up. But throw in the -y flag, and they all seem to show up. So your trick seemed to work!