64-bit build of Kuiper Linux with IndustrialIO for Raspberry Pi 4B

Kuiper needs to support 32-bit systems and currently, there is no plan to make variants of Kuiper. However, libiio (and iiod) do work fine under 64-bit systems. Assuming you have IIO enabled in your kernel.

Here is the Kuiper build process for reference: https://github.com/analogdevicesinc/adi-kuiper-gen

-Travis

Thanks Travis. I built a Kuiper image last night and it boots up. With the Kuiper image I was using previously I'd load the ADIS16465 overlay using this in my config.txt:

dtoverlay=adis16475
dtparam=device=adis16465,interrupt=25

But I think this changes as of the patch at https://github.com/analogdevicesinc/linux/commit/c1c7b4143b0621527a63484ec40fc7f03f34222b . What should this new overlay parameter look like in config.txt? If you have a link to more documentation on it that'd be really helpful.

nsa  can you answer this one?

-Travis

Hi,

You should just need to have 'drdy_gpio25' instead of 'interrupt=25'

- Nuno Sá

I tried 

dtoverlay=adis16475
dtparam=drdy_gpio25

And when I run

sudo vcdbg log msg

I see the overlay is loaded but I don't see the device at /dev/iio:device0. I don't know what's missing that prevents the device from showing up. The same system does have /dev/iio:device0 when booted up with the prebuilt Kuiper image.

Is there somewhere else I can look for diagnostic messages?

Does the device=adis16465 matter at all? It appears to show up as OF_COMPATIBLE_0 when reading /sys/bus/spi/devices/spi0.0/uevent. The working (prebuilt) Kuiper image reports "adi,adis16477-1" for this value, even though the IMU reports a product ID of 16465.

Hi,

Rob_Russell said:

Does the device=adis16465 matter at all? It appears to show u

Yes, it matters. Without that your device won't probe as you can see. That parameter corresponds to the devicetree 'compatible' property. You need to set it to the device you are using. We made it this way because the adis16475 driver supports lots of IMUs and we don't want different overlays just because of different 'compatibles'.

- Nuno Sá

Thanks for the details, that helps a lot. I had tried setting it to adis16465 and tried strings from the driver like "adis16465-2", which also didn't work. But since the working image showed "adi,adis16477-1" I used a value like that and now I have an iio device.

In case anyone else needs it, this is exactly what I added to /boot/config.txt for Kuiper built with a 5.10.63 kernel:

dtoverlay=adis16475
dtparam=device="adi,adis16465-2"
dtparam=drdy_gpio25

The output from vcdbg log mesg was also really useful for seeing what dtparam value was applied.

Thanks for the details, that helps a lot. I had tried setting it to adis16465 and tried strings from the driver like "adis16465-2", which also didn't work. But since the working image showed "adi,adis16477-1" I used a value like that and now I have an iio device.

In case anyone else needs it, this is exactly what I added to /boot/config.txt for Kuiper built with a 5.10.63 kernel:

dtoverlay=adis16475
dtparam=device="adi,adis16465-2"
dtparam=drdy_gpio25

The output from vcdbg log mesg was also really useful for seeing what dtparam value was applied.