I have added myself to the usergroup dialout, thinking it’s the issue of the permissions, but it seems that is not enough.
Could you guys please help me out in this regard ?
It is the permissions that the current log in has with regards the /dev/qcqmi interfaces. You can either login as root (this might not be enough or send the below command to give yourself full rights.
Thanks. I fixed the permission issue. I have observed another behaviour worth sharing here.
This is when we reconnect the device over USB. (Plug out the device and plug it back in). I believe the SDK threads are already initialised and and they take a while before recognising the device when it’s plugged back in. Somehow I think the SDK threads have a polling procedure to refresh their device contexts. Or there is some delay in the system that’s not letting SDK threads to recognise the device in it’s new context early enough. I get the message “Unable to find device…” for a while even though the device files have been created and I can AT into the serial terminal, and then device gets recognised.
Can you provide a little more detail on how you resolved the permission issue? I am seeing the exact same behavior with an EM7565 module under Ubuntu 18.x. I have rebuilt and installed the GobiNet and GobiSerial drivers as root via sudo. I tried changing the perms on /dev/qcqmi0 as suggested above and am running the conman via sudo as well. I am seeing the same USB IOCTL permission error.