Hi.

I'm having a problem getting cm160 to run on my Raspberry Pi.

When I plug in the Owl I see it appear in /var/log/syslog and a device for it appears at /dev/ttyUSB0.

However, when I run ./cm160, I get this output, with the "No error" message on the first pass and the "could not detach kernel driver..." message from then on.

# ./cm160 
Wait for cm160 device to be connected
Found compatible device #0: 0fde:ca05 (002)
Found 1 compatible device
bulk_read returned -110 (No error)
Wait for cm160 device to be connected
Found compatible device #0: 0fde:ca05 (002)
Found 1 compatible device
bulk_read returned -110 (could not detach kernel driver from interface 0: No data available)
Wait for cm160 device to be connected
Found compatible device #0: 0fde:ca05 (002)
Found 1 compatible device

If I tail /var/log/syslog, I get this the second I run ./cm160

May 28 20:49:31 pi-zero-w kernel: [1043641.132661] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
May 28 20:49:31 pi-zero-w kernel: [1043641.132802] cp210x 1-1:1.0: device disconnected

At this point, /dev/ttyUSB0 no longer exists. If I do the following it reappears until I run ./cm160 again:
rmmod cp210x && modprobe cp210x

So, my uneducated guess is that running cm160 is instantly upsetting the cp210x module.

I've tried building cm160 myself and have tried jesjimher/eagle-owl fork, which explicitly mentions running it on a Raspberry Pi. I've tried two different Owl units, and three different Pi's, all with the same result.

Any help would be appreciated. I bought this Owl specifically to monitor via a Pi and I've hit a bit of a dead-end.

Cheers.