Unable to access qmi via ASC0 on PLS83-W | Telit Cinterion IoT Developer Community
July 26, 2022 - 5:27pm, 476 views
I have a LGADevKit attached to a RaspberryPi 3B via the ASC0 interface.
Attempting to follow the directions in https://iot-developer.thalesgroup.com/tutorial/pls6383-qmirmnet-setup-an... and am having issues.
I have installed the suite of tools (libqmi-utils, modemmanager, network manager, minicom, etc). I am able to 'talk' the PLS83W:
Welcome to minicom 2.8
OPTIONS: I18n
Port /dev/ttyUSB0, 11:04:26
Press CTRL-A Z for help on special keys
^SYSSTART
+CIEV: prov,0,"CDMAless-Verizon"
ATI
Cinterion
PLS83-W
REVISION 01.002
OK
AT^SSRVSET=actSrvSet,11
^SSRVSET: 11
OK
AT+CFUN=1,1
OK
However, when I do look at the usb ports after plugging in the dev kit:
pi@raspberrypi:/boot/proaxion/scripts $ lsusb
Bus 001 Device 005: ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard
Bus 001 Device 010: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 006: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubI followed the above link and attempted the various settings without success. The 'dmesg':
pi@raspberrypi:/boot/proaxion/scripts $ dmesg
[ 2547.433221] usb 1-1.4: USB disconnect, device number 10
[ 2547.434824] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 2547.435053] ftdi_sio 1-1.4:1.0: device disconnected
[ 2550.541235] usb 1-1.4: new full-speed USB device number 11 using dwc_otg
[ 2550.708514] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 2550.708554] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2550.708571] usb 1-1.4: Product: FT232R USB UART
[ 2550.708586] usb 1-1.4: Manufacturer: FTDI
[ 2550.708600] usb 1-1.4: SerialNumber: A507L5JM
[ 2550.721115] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
[ 2550.721333] usb 1-1.4: Detected FT232RL
[ 2550.724495] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0
I finally unplugged the USB cable from the ASC0 port and plugged in the cable to the native port without success (from my understanding this native port is for the PLS83 to use, not for the RaspberryPi). After plugging back into the ASC0 port (and pressing the on button) and looking at the 'dmesg' output:
[ 2650.859251] usb 1-1.4: USB disconnect, device number 11
[ 2650.867749] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 2650.868046] ftdi_sio 1-1.4:1.0: device disconnected
[ 2656.823683] hwmon hwmon1: Undervoltage detected!
[ 2667.224116] hwmon hwmon1: Voltage normalised
[ 2671.384249] usb 1-1.4: new high-speed USB device number 12 using dwc_otg
[ 2671.516082] usb 1-1.4: New USB device found, idVendor=1e2d, idProduct=006f, bcdDevice= 0.00
[ 2671.516124] usb 1-1.4: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[ 2671.516144] usb 1-1.4: Product: PLSx3
[ 2671.516161] usb 1-1.4: Manufacturer: Cinterion Wireless Modules
[ 2671.516179] usb 1-1.4: SerialNumber: 60b86af0
[ 2671.519206] qmi_wwan 1-1.4:1.0: cdc-wdm0: USB WDM device
[ 2671.521580] qmi_wwan 1-1.4:1.0 wwan0: register 'qmi_wwan' at usb-3f980000.usb-1.4, WWAN/QMI device, 56:11:95:6c:71:f7
[ 2671.536068] qmi_wwan 1-1.4:1.2: cdc-wdm1: USB WDM device
[ 2671.537899] qmi_wwan 1-1.4:1.2 wwan1: register 'qmi_wwan' at usb-3f980000.usb-1.4, WWAN/QMI device, 56:11:95:6c:71:f7
[ 2671.543033] qmi_wwan 1-1.4:1.4: cdc-wdm2: USB WDM device
[ 2671.544921] qmi_wwan 1-1.4:1.4 wwan2: register 'qmi_wwan' at usb-3f980000.usb-1.4, WWAN/QMI device, 56:11:95:6c:71:f7
[ 2671.548492] qmi_wwan 1-1.4:1.6: cdc-wdm3: USB WDM device
[ 2671.550242] qmi_wwan 1-1.4:1.6 wwan3: register 'qmi_wwan' at usb-3f980000.usb-1.4, WWAN/QMI device, 56:11:95:6c:71:f7
[ 2671.554374] qmi_wwan 1-1.4:1.8: cdc-wdm4: USB WDM device
[ 2671.556121] qmi_wwan 1-1.4:1.8 wwan4: register 'qmi_wwan' at usb-3f980000.usb-1.4, WWAN/QMI device, 56:11:95:6c:71:f7
[ 2673.464421] hwmon hwmon1: Undervoltage detected!
[ 2674.373387] qmi_wwan 1-1.4:1.2: unknown notification 32 received: index 2 len 2
[ 2674.373892] qmi_wwan 1-1.4:1.6: unknown notification 32 received: index 6 len 2
[ 2674.374146] qmi_wwan 1-1.4:1.4: unknown notification 32 received: index 4 len 2
[ 2674.374496] qmi_wwan 1-1.4:1.0: unknown notification 32 received: index 0 len 2
[ 2674.389016] qmi_wwan 1-1.4:1.0: unknown notification 32 received: index 0 len 2
[ 2674.392256] qmi_wwan 1-1.4:1.2: unknown notification 32 received: index 2 len 2
[ 2674.392996] qmi_wwan 1-1.4:1.4: unknown notification 32 received: index 4 len 2
[ 2674.395009] qmi_wwan 1-1.4:1.2: unknown notification 32 received: index 2 len 2
[ 2674.396010] qmi_wwan 1-1.4:1.4: unknown notification 32 received: index 4 len 2
[ 2674.396119] qmi_wwan 1-1.4:1.6: unknown notification 32 received: index 6 len 2
[ 2674.398996] qmi_wwan 1-1.4:1.6: unknown notification 32 received: index 6 len 2
[ 2674.422013] qmi_wwan 1-1.4:1.0: unknown notification 32 received: index 0 len 2
[ 2675.392242] qmi_wwan 1-1.4:1.2: unknown notification 32 received: index 2 len 2
[ 2675.395116] qmi_wwan 1-1.4:1.4: unknown notification 32 received: index 4 len 2
[ 2675.395993] qmi_wwan 1-1.4:1.6: unknown notification 32 received: index 6 len 2
[ 2675.421106] qmi_wwan 1-1.4:1.0: unknown notification 32 received: index 0 len 2
[ 2677.624502] hwmon hwmon1: Voltage normalised
[ 2678.456437] qmi_wwan 1-1.4:1.2: nonzero urb status received: -71
[ 2678.456481] qmi_wwan 1-1.4:1.2: wdm_int_callback - 0 bytes
[ 2678.456506] qmi_wwan 1-1.4:1.6: nonzero urb status received: -71
[ 2678.456518] qmi_wwan 1-1.4:1.6: wdm_int_callback - 0 bytes
[ 2678.456607] qmi_wwan 1-1.4:1.0: nonzero urb status received: -71
[ 2678.456619] qmi_wwan 1-1.4:1.0: wdm_int_callback - 0 bytes
[ 2678.456637] qmi_wwan 1-1.4:1.8: nonzero urb status received: -71
[ 2678.456650] qmi_wwan 1-1.4:1.8: wdm_int_callback - 0 bytes
[ 2678.456667] qmi_wwan 1-1.4:1.4: nonzero urb status received: -71
[ 2678.456680] qmi_wwan 1-1.4:1.4: wdm_int_callback - 0 bytes
[ 2678.463009] qmi_wwan 1-1.4:1.6: nonzero urb status received: -71
[ 2678.463057] qmi_wwan 1-1.4:1.6: wdm_int_callback - 0 bytes
[ 2678.463090] qmi_wwan 1-1.4:1.4: nonzero urb status received: -71
[ 2678.463102] qmi_wwan 1-1.4:1.4: wdm_int_callback - 0 bytes
[ 2678.463120] qmi_wwan 1-1.4:1.8: nonzero urb status received: -71
[ 2678.463132] qmi_wwan 1-1.4:1.8: wdm_int_callback - 0 bytes
[ 2678.463149] qmi_wwan 1-1.4:1.2: nonzero urb status received: -71
[ 2678.463162] qmi_wwan 1-1.4:1.2: wdm_int_callback - 0 bytes
[ 2678.463179] qmi_wwan 1-1.4:1.0: nonzero urb status received: -71
[ 2678.463191] qmi_wwan 1-1.4:1.0: wdm_int_callback - 0 bytes
[ 2678.470007] qmi_wwan 1-1.4:1.4: nonzero urb status received: -71
[ 2678.470053] qmi_wwan 1-1.4:1.4: wdm_int_callback - 0 bytes
[ 2678.470081] qmi_wwan 1-1.4:1.6: nonzero urb status received: -71
[ 2678.470094] qmi_wwan 1-1.4:1.6: wdm_int_callback - 0 bytes
[ 2678.470112] qmi_wwan 1-1.4:1.8: nonzero urb status received: -71
[ 2678.470124] qmi_wwan 1-1.4:1.8: wdm_int_callback - 0 bytes
[ 2678.470141] qmi_wwan 1-1.4:1.0: nonzero urb status received: -71
[ 2678.470152] qmi_wwan 1-1.4:1.0: wdm_int_callback - 0 bytes
[ 2678.470170] qmi_wwan 1-1.4:1.2: nonzero urb status received: -71
[ 2678.470182] qmi_wwan 1-1.4:1.2: wdm_int_callback - 0 bytes
[ 2678.477007] qmi_wwan 1-1.4:1.4: nonzero urb status received: -71
[ 2678.477053] qmi_wwan 1-1.4:1.4: wdm_int_callback - 0 bytes
[ 2678.477082] qmi_wwan 1-1.4:1.0: nonzero urb status received: -71
[ 2678.477094] qmi_wwan 1-1.4:1.0: wdm_int_callback - 0 bytes
[ 2678.477113] qmi_wwan 1-1.4:1.6: nonzero urb status received: -71
[ 2678.477124] qmi_wwan 1-1.4:1.6: wdm_int_callback - 0 bytes
[ 2678.477140] qmi_wwan 1-1.4:1.8: nonzero urb status received: -71
[ 2678.477152] qmi_wwan 1-1.4:1.8: wdm_int_callback - 0 bytes
[ 2678.477168] qmi_wwan 1-1.4:1.2: nonzero urb status received: -71
[ 2678.477180] qmi_wwan 1-1.4:1.2: wdm_int_callback - 0 bytes
[ 2678.484009] qmi_wwan 1-1.4:1.0: nonzero urb status received: -71
[ 2678.484056] qmi_wwan 1-1.4:1.0: wdm_int_callback - 0 bytes
[ 2678.484089] qmi_wwan 1-1.4:1.6: nonzero urb status received: -71
[ 2678.484102] qmi_wwan 1-1.4:1.6: wdm_int_callback - 0 bytes
[ 2678.484121] qmi_wwan 1-1.4:1.4: nonzero urb status received: -71
[ 2678.484132] qmi_wwan 1-1.4:1.4: wdm_int_callback - 0 bytes
[ 2678.484149] qmi_wwan 1-1.4:1.2: nonzero urb status received: -71
[ 2678.484162] qmi_wwan 1-1.4:1.2: wdm_int_callback - 0 bytes
[ 2678.484179] qmi_wwan 1-1.4:1.8: nonzero urb status received: -71
[ 2678.484190] qmi_wwan 1-1.4:1.8: wdm_int_callback - 0 bytes
[ 2678.491007] qmi_wwan 1-1.4:1.6: nonzero urb status received: -71
[ 2678.491057] qmi_wwan 1-1.4:1.6: wdm_int_callback - 0 bytes
[ 2678.491087] qmi_wwan 1-1.4:1.0: nonzero urb status received: -71
[ 2678.491099] qmi_wwan 1-1.4:1.0: wdm_int_callback - 0 bytes
[ 2678.491116] qmi_wwan 1-1.4:1.8: nonzero urb status received: -71
[ 2678.491128] qmi_wwan 1-1.4:1.8: wdm_int_callback - 0 bytes
[ 2678.491145] qmi_wwan 1-1.4:1.2: nonzero urb status received: -71
[ 2678.491157] qmi_wwan 1-1.4:1.2: wdm_int_callback - 0 bytes
[ 2678.491173] qmi_wwan 1-1.4:1.4: nonzero urb status received: -71
[ 2678.491184] qmi_wwan 1-1.4:1.4: wdm_int_callback - 0 bytes
[ 2678.498007] qmi_wwan 1-1.4:1.8: nonzero urb status received: -71
[ 2678.498052] qmi_wwan 1-1.4:1.8: wdm_int_callback - 0 bytes
[ 2678.498081] qmi_wwan 1-1.4:1.4: nonzero urb status received: -71
[ 2678.498093] qmi_wwan 1-1.4:1.4: wdm_int_callback - 0 bytes
[ 2678.498110] qmi_wwan 1-1.4:1.6: nonzero urb status received: -71
[ 2678.498122] qmi_wwan 1-1.4:1.6: wdm_int_callback - 0 bytes
[ 2678.498141] qmi_wwan 1-1.4:1.2: nonzero urb status received: -71
[ 2678.498152] qmi_wwan 1-1.4:1.2: wdm_int_callback - 0 bytes
[ 2678.498170] qmi_wwan 1-1.4:1.0: nonzero urb status received: -71
[ 2678.498182] qmi_wwan 1-1.4:1.0: wdm_int_callback - 0 bytes
[ 2678.505000] qmi_wwan 1-1.4:1.0: nonzero urb status received: -71
[ 2678.505038] qmi_wwan 1-1.4:1.0: wdm_int_callback - 0 bytes
[ 2678.505061] qmi_wwan 1-1.4:1.4: nonzero urb status received: -71
[ 2678.505073] qmi_wwan 1-1.4:1.4: wdm_int_callback - 0 bytes
[ 2678.505091] qmi_wwan 1-1.4:1.8: nonzero urb status received: -71
[ 2678.505103] qmi_wwan 1-1.4:1.8: wdm_int_callback - 0 bytes
[ 2678.505121] qmi_wwan 1-1.4:1.6: nonzero urb status received: -71
[ 2678.505133] qmi_wwan 1-1.4:1.6: wdm_int_callback - 0 bytes
[ 2678.505150] qmi_wwan 1-1.4:1.2: nonzero urb status received: -71
[ 2678.505162] qmi_wwan 1-1.4:1.2: wdm_int_callback - 0 bytes
[ 2678.509170] usb 1-1.4: USB disconnect, device number 12
[ 2678.509419] qmi_wwan 1-1.4:1.0 wwan0: unregister 'qmi_wwan' usb-3f980000.usb-1.4, WWAN/QMI device
[ 2678.511903] qmi_wwan 1-1.4:1.8: Tx URB error: -19
[ 2678.512064] qmi_wwan 1-1.4:1.8: nonzero urb status received: -71
[ 2678.512077] qmi_wwan 1-1.4:1.8: Tx URB error: -19
[ 2678.512079] qmi_wwan 1-1.4:1.8: wdm_int_callback - 0 bytes
[ 2678.512107] qmi_wwan 1-1.4:1.8: wdm_int_callback - usb_submit_urb failed with result -19
[ 2678.512121] qmi_wwan 1-1.4:1.4: nonzero urb status received: -71
[ 2678.512130] qmi_wwan 1-1.4:1.4: wdm_int_callback - 0 bytes
[ 2678.512138] qmi_wwan 1-1.4:1.4: wdm_int_callback - usb_submit_urb failed with result -19
[ 2678.512140] qmi_wwan 1-1.4:1.8: Tx URB error: -19
[ 2678.512151] qmi_wwan 1-1.4:1.2: nonzero urb status received: -71
[ 2678.512159] qmi_wwan 1-1.4:1.2: wdm_int_callback - 0 bytes
[ 2678.512167] qmi_wwan 1-1.4:1.2: wdm_int_callback - usb_submit_urb failed with result -19
[ 2678.512180] qmi_wwan 1-1.4:1.6: nonzero urb status received: -71
[ 2678.512189] qmi_wwan 1-1.4:1.6: wdm_int_callback - 0 bytes
[ 2678.512196] qmi_wwan 1-1.4:1.8: Tx URB error: -19
[ 2678.512198] qmi_wwan 1-1.4:1.6: wdm_int_callback - usb_submit_urb failed with result -19
[ 2678.512309] qmi_wwan 1-1.4:1.8: usb_submit_urb failed with result -19
[ 2678.512601] qmi_wwan 1-1.4:1.4: Tx URB error: -19
[ 2678.512691] qmi_wwan 1-1.4:1.4: Tx URB error: -19
[ 2678.512750] qmi_wwan 1-1.4:1.4: Tx URB error: -19
[ 2678.513548] qmi_wwan 1-1.4:1.6: Tx URB error: -19
[ 2678.513657] qmi_wwan 1-1.4:1.6: Tx URB error: -19
[ 2678.513722] qmi_wwan 1-1.4:1.6: Tx URB error: -19
[ 2678.514546] qmi_wwan 1-1.4:1.2: Tx URB error: -19
[ 2678.514629] qmi_wwan 1-1.4:1.2: Tx URB error: -19
[ 2678.514690] qmi_wwan 1-1.4:1.2: Tx URB error: -19
[ 2678.585194] qmi_wwan 1-1.4:1.2 wwan1: unregister 'qmi_wwan' usb-3f980000.usb-1.4, WWAN/QMI device
[ 2678.665689] qmi_wwan 1-1.4:1.4 wwan2: unregister 'qmi_wwan' usb-3f980000.usb-1.4, WWAN/QMI device
[ 2678.745115] qmi_wwan 1-1.4:1.6 wwan3: unregister 'qmi_wwan' usb-3f980000.usb-1.4, WWAN/QMI device
[ 2678.805157] qmi_wwan 1-1.4:1.8 wwan4: unregister 'qmi_wwan' usb-3f980000.usb-1.4, WWAN/QMI device
[ 2683.154690] usb 1-1.4: new full-speed USB device number 13 using dwc_otg
[ 2683.312276] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 2683.312316] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2683.312337] usb 1-1.4: Product: FT232R USB UART
[ 2683.312354] usb 1-1.4: Manufacturer: FTDI
[ 2683.312370] usb 1-1.4: SerialNumber: A507L5JM
[ 2683.321089] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
[ 2683.321339] usb 1-1.4: Detected FT232RL
[ 2683.324703] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0
What am I doing incorrectly?
Hello,
QMI works on USB interface, so you need to connect the cable to the native USB port. On ASC0 USB you have the module's RS232 port connected over FTDI chip to ASC0 USB port of the DevKit. You can see it in your logs - please check for FTDI. In your last log FTDI was disconnected and you can see '006f' product ID which is used by the module after setting AT^SSRVSET=actSrvSet,11. Before that with he default setting actSrvSet,1 the product ID was '0069'.
So, you also see that qmi_wwan is there. But there's also some udervoltage issue and other problems. I think that you should check for such a RaspberryPi issues. There must be a way to fix or workaround it in the Pie.
In the end you switched back to FTDI which is what you should not do if you want to use QMI.
Best regards,
Bartłomiej
Hello,
when looking at the dmesg output for the QMI composition one can see that the qmi_wwan driver also tries to attach to the ACM TTYs which is wrong.
Please change the knowledge base article to read
echo '1e2d 006f ff' | ...
so that PLS83-W users who are not able to use Giacinto's Linux kernel patch are not affected by side effects.
Regards,
Reinhard