On this page: http://www.udoo.org/docs-neo/Hardware_&_Accessories/Bricks_snap_in_sensors.html The sensor address (?) virtual file for the barometer brick is listed as: /sys/class/i2c-dev/i2c-1/device/1-0060/iio\:device0 But on my Neo (full) it's actually at: /sys/class/i2c-dev/i2c-1/device/1-0060/iio\:device2 It's a trifling bug I know, but is this likely to change in future? I'm (throwing together) some monitoring/logging software for IoT use which I hope will prove particularly lightweight and run as a daemon avoiding the overhead from other technologies so the machine can run other tasks.
That happens also with a fresh installation of UDOOBuntu2rc2? Can you please describe your configuration (devices attached, os, post dmesg)? Thanks
I believe it did - but I've also switched off the M4 core - so that may be behind this. I'm going to re-flash a new card with a fresh install and re-check against the known configuration. I'll get update this post (or add another) with the new data as I have it. UPDATE: Confirmed (and I guess @ektor5 can explain why this is). If the M4 core is ON (default) the devices appear at: /sys/class/i2c-dev/i2c-1/device/1-0060/iio:device0 but when it's disabled, it moves to: /sys/class/i2c-dev/i2c-1/device/1-0060/iio:device2 This may, of course, be by design but it's useful to know just in case!
Thanks for pointing this out @I Hate Google!, we're looking into it and I'll add it in a while to the documentation.
