crw-rw---- 1 radio radio 188, 0 2009-01-01 01:00 /dev/ttyUSB0
crw-rw---- 1 radio radio 188, 1 2009-01-01 01:00 /dev/ttyUSB1
crw-rw---- 1 radio radio 188, 2 2009-01-01 01:00 /dev/ttyUSB2
ls -l /dev/qcqmi*
ls: /dev/qcqmi*: No such file or directory
logcat -b radio shows below error continuously:
01-01 01:01:41.941 698 698 I use-Rlog/RLOG-RIL: QCWWAN2kEnumerateDevices unable to find device… 6
Till now we have updated firmware on 3 modules and after successful update we are facing the same issue on all modules.
What could be the issue with newer firmware? How we can debug it to find where module is stuck with new firmware.
Please refer the return of AT!USBCOMP?
at!usbcomp?
Config Index: 1
Config Type: 3 (Generic)
Interface bitmask: 0000010D (diag,nmea,modem,rmnet0)
OK
Have you verified the module in Linux PC with GobiSerial and GobiNet driver? → We have not verified the module in Linux PC but we are planning to test it on next coming days.
We have tested module on Evaluation Kit with windows host and with windows host modules are working fine.
We have checked PID VID from GobiUSBNet.c and it matches with our module.
We found that in " Android 10.0 RIL Release Note" in section 2.1. Version 10.0.7.0 mentioned that “Fixed qcqmi interface may not enumerate issue”. Can anyone provide details about this fix.
We are using Android 8.1 RIL Software 8.1.2.0 and after updating firmware on module, /dev/qcqmic0 not coming up. We want fix to resolve qcqmi interface enumeration issue for Android 8.1 RIL.
I don’t have physical access to the standalone module right now. I will have it in the next few days. In the meanwhile, we are trying to understand what can be the issue. Could you share patch/issue info if you have more idea about this issue fixed in android 10.0.7.0 RIL?
We have ported the USB driver from android 10.0.7.0 RIL on our platform. After updating kernel driver the issue is still there. The /dev/qcqmi0 mode is not coming.
Please refer below AT commands results after updating kernel driver and please suggest what next we can do.
OK
at!gstatus?
!GSTATUS:
Current Time: 276 Temperature: 29
Reset Counter: 1 Mode: LOW POWER MODE
OK
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 1 0 0 ?? 01.07.02.00?
FW 2 GOOD 2 0 0 ?? 01.14.02.00?
FW 3 EMPTY 0 0 0
FW 4 EMPTY 0 0 0
Max FW images: 4
Active FW image is at slot 2
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.035_000 01.14.02.00_GENERIC
Max PRI images: 50
OK
at!priid?
PRI Part Number: 9907344
Revision: 002.001
Customer: Generic-M2M
Carrier PRI: 9999999_9907259_SWI9X50C_01.14.02.00_00_GENERIC_002.035_000
OK
at!impref?
!IMPREF:
preferred fw version: 01.14.02.00
preferred carrier name: GENERIC
preferred config name: GENERIC_002.035_000
preferred subpri index: 000
current fw version: 01.14.02.00
current carrier name: GENERIC
current config name: GENERIC_002.035_000
current subpri index: 000
We have installed GobiNet and GobiSerial driver on ubuntu 18.04 and blacklisted qmi_wwan module. After installing these drivers we are able to get /dev/qcqmi0 node.
But the module still shows in LPM. To change module mode from LPM to ONLINE we did below steps.
Set AT!USBCOMP=1,3,10D
AT!RESET
AT!ENTERCND=“A710” followed by AT!USBPID=9091,9090
at!openlock?
AT!RESET
AT!GSTATUS?
After this module shows ONLINE. We have connected same module on our Android platform. On Android platform /dev/qcqmi0 node is not able to up but module status shows ONLINE.
Could you please help us to get /dev/qcqmi0 node on our Android platform?
We have installed GobiNet driver of Android RIL 10 on our platform successfully and now we are able to get /dev/ttyUSB* and /dev/qcqmi0 mode.
Now we are able to get wwan0 interface up with IP address. SIM network registered.
We have updated firmware on 3 modules and after updating firmware module goes in Low Power Mode. We did not get why module goes in LPM after updating firmware.
Is there any specific condition or process because of which modules are going in LPM?
