The directory /sys/bus/i2c has the handy dandy new_device file to add devices. Searching the /sys/bus/iio directory there is no new_device file and there is no /sys/bus/iio on the beagle play. So how do you connect it to the iio bus?
Can you tell more detail
You mean when you check
/sys/bus/i2c/devices : no devices ?
on my bbblue debian 12 (non vscode)
first make sure inv_mpu6050 is installed with “lsmod”
mpu6050 at
/sys/bus/i2c/drivers/inv-mpu6050-i2c/2-0068/iio:device2
there is also
/sys/bus/iio/devices/iio:device2
the above two locations have all the sysfs names that you can use
in /dev there is a corresponding /dev/iio:device2
to use this requires a bit more setup if ya want to use iio-trig-sysfs
you must also understand the data structure being read from /dev/ location
Sorry, off grid, cell service is spotty at best, internet worse.
Entering
grep 6050 /boot/config-*
Returns
CONFIG_INV_MPU6050_IIO=m
CONFIG_INV_MPU6050_I2C=m
CONFIG_INV_MPU6050_SPI=m
So there should be drivers available.
cd /sys/bus/i2c/devices/i2c-2
echo "
echo “MPU6050 0x68” > new_device
Creates a new directory 2-068
Pertty much useless.
you need to do insmod or modprobe of the driver
then the following should work
A little more research into device driver showed it uses the chips interrupt pin. Unfortunately my device has a groove connector, no interrupt signal. Will be getting another device for testing the device tree. Thanks for the lsmod tip, next time I know where to look