LGA DevKit + PLS83-W Module / AT Commands problem | Thales IoT Developer Community

June 18, 2021 - 1:56pm, 5356 views

LGA DevKit

Hi,

I am currently trying to set up QMI/RmNet on the PLS83-W module so following this tutorial (PLS63/83 QMI/RMNET Setup and Linux qmi_wwan / ModemManager Integration | Thales IoT Developer Community (thalesgroup.com) ). I first need to configure the module via GTKterm with AT commands.

Problem is, I want to send AT commands through the native USB port of the LGA Devkit but GTKTerm terminal doesn't detect any USB ports means I am unable to communicate with the module with AT commands.

On the other hand, when I send AT commands through ASC0 USB port (VCP USB), I am able to select an USB port and see the AT Terminal so I can send commands.

In short, I was wondering if there is a way to be able to send AT commands through native USB port via a terminal ?

Thank you in advance for your answer,

Best Regards

A Random Intern

Comment

Bartłomiej Gema...

Jun 18 2021 - 3:36pm

Hello,
In general it is possible to use native USB. Have you tried with Windows for comparison?
Did you check lsusb and dmesg outputs?
BR,
Bartłomiej

Like
0
Log in or register to post comments

Random Intern

Jun 21 2021 - 10:09am

Hi,

I just checked lsusb and dmesg output, here they are :*

lsusb :

~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader
Bus 001 Device 003: ID 04f2:b541 Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
Bus 001 Device 005: ID 03f0:1198 HP, Inc HID-compliant mouse
Bus 001 Device 006: ID 1e2d:006b Cinterion Wireless Modules PLSx
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg :

[  158.419749] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
[  158.420055] radeon 0000:03:00.0: WB enabled
[  158.420070] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x000000002ed02101
[  158.420078] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x000000003c047a43
[  158.420084] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x00000000e1aa8aae
[  158.420090] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x00000000dcbd866b
[  158.420095] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x000000001f572f44
[  158.420900] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x00000000762f3e52
[  158.521789] radeon 0000:03:00.0: failed VCE resume (-110).
[  158.774950] [drm] ring test on 0 succeeded in 1 usecs
[  158.774962] [drm] ring test on 1 succeeded in 1 usecs
[  158.774972] [drm] ring test on 2 succeeded in 1 usecs
[  158.774991] [drm] ring test on 3 succeeded in 4 usecs
[  158.775007] [drm] ring test on 4 succeeded in 4 usecs
[  158.951554] [drm] ring test on 5 succeeded in 1 usecs
[  158.951566] [drm] UVD initialized successfully.
[  158.951648] [drm] ib test on ring 0 succeeded in 0 usecs
[  158.951733] [drm] ib test on ring 1 succeeded in 0 usecs
[  158.951798] [drm] ib test on ring 2 succeeded in 0 usecs
[  158.951859] [drm] ib test on ring 3 succeeded in 0 usecs
[  158.951918] [drm] ib test on ring 4 succeeded in 0 usecs
[  159.611379] [drm] ib test on ring 5 succeeded
[  236.030956] usb 1-1: new high-speed USB device number 6 using xhci_hcd
[  236.181299] usb 1-1: New USB device found, idVendor=1e2d, idProduct=006b, bcdDevice= 0.00
[  236.181310] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[  236.181316] usb 1-1: Product: PLSx
[  236.181322] usb 1-1: Manufacturer: Cinterion Wireless Modules
[  236.181327] usb 1-1: SerialNumber: ff94bff1
[  526.314319] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled

I retried opening GTKTerm again to check if i can access to LGA DevKit's USB port but it still doesn't show any port I can use to send AT commands, here is a screenshot of the ports available (I tried them and none of them is connected to the DevKit) :

In comparison, when I plug the DevKit with its ASC0 (VCP) USB port, I can select it and I am able to send AT commands (as below) :

Thank you for your answer,

Best Regards,

A Random Intern

Like
0
Log in or register to post comments

rspmn

Jun 22 2021 - 12:22pm

USB PID 006b looks like an engineering sample or rather old firmware to me.

According to the kernel patch for the qmi_wwan driver the USB PID should be 006f and the serial
ports are available as /dev/ttyACM*:
[4567975.356067] usb 2-3.2: new high-speed USB device number 114 using ehci-pci
[4567975.438875] usb 2-3.2: New USB device found, idVendor=1e2d, idProduct=006f
[4567975.438878] usb 2-3.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[4567975.438880] usb 2-3.2: Product: PLSx3
[4567975.438882] usb 2-3.2: Manufacturer: Cinterion Wireless Modules
[4567975.438884] usb 2-3.2: SerialNumber: 12345678
[4567975.440933] cdc_acm 2-3.2:1.0: ttyACM0: USB ACM device
[4567975.442018] cdc_acm 2-3.2:1.2: ttyACM1: USB ACM device
[4567975.443320] cdc_acm 2-3.2:1.4: ttyACM2: USB ACM device
[4567975.444569] cdc_acm 2-3.2:1.6: ttyACM3: USB ACM device
[4567975.447285] qmi_wwan 2-3.2:1.8: cdc-wdm0: USB WDM device
[4567975.448313] qmi_wwan 2-3.2:1.8 wwan0: register 'qmi_wwan' at usb-0000:00:1d.7-3.2, WWAN/QMI device, f6:b9:9b:e1:95:2a

Regards,
Reinhard

Like
0
Log in or register to post comments

Bartłomiej Gema...

Jun 22 2021 - 12:58pm

Hello,

I connected mine to Ubuntu and it enumerated with idProduct 0x0069.
According to AT spec if the module is configured as ECM all USB devices of the UE enumerate
with PID 0x0069. If it's configured as WWAN device all USB devices of the UE enumerate with PID 0x006F.
Can you paste ATI1 and ATI8 replies?

BR,
Bartłomiej

Like
0
Log in or register to post comments

Random Intern

Jun 22 2021 - 1:17pm

Hello Bartłomiej,

Thank you for your answer.

Here are the ATI1 and ATI8 replies :

ATI1
Cinterion
PLS83-W
REVISION 00.024
A-REVISION 01.000.00

OK

ATI8
C-REVISION 00000.00

OK

Best Regards

A Random Intern

Like
0
Log in or register to post comments

Random Intern

Jun 22 2021 - 1:10pm

Thank you for your answer !

Actually, yes, it should be 006f as I set the AT^SSRVSET="actSrvset",11 command on the module... But it's not and I don't really know why.

I checked under /dev and I don't have any ttyACM file...

Do you have any idea about how I could send AT commands through native USB ? I currently tried ASC0 (VCP), both ports but native USB on itself won't allow me to send AT commands as my GTKTerm terminal can't detect its port when it's on native.

Best Regards,

A Random Intern

Like
0
Log in or register to post comments

Bartłomiej Gema...

Jun 22 2021 - 2:16pm

Hello,

How about ECM **** - is USB enumerated properly?
It seems that you have quite an old firmware - the first customer sample. The AT spec for this version states (for setting 11) that CDC5 (USB5) and nd CDC6 (USB6) enumerate as RmNet device. All USB devices of the UE enumerate with PID 0x006B.
I think that you need to update the firmware to a newer version. But for that purpose you have to contact your Thales technical sales person or module provider.

BR,
Bartłomiej

Like
0
Log in or register to post comments

Random Intern

Jun 22 2021 - 2:43pm

Hello Bartłomiej,

I think it is enumerated properly for ECM as I have this output :

[17469.156742] smsc95xx 1-1.2.3:1.0 enx000c900100b6: unregister 'smsc95xx' usb-0000:00:14.0-1.2.3, smsc95xx USB 2.0 Ethernet 
[18275.813473] usb 1-1.4: USB disconnect, device number 34
[18284.072441] usb 1-1.4: new high-speed USB device number 36 using xhci_hcd
[18284.279313] usb 1-1.4: New USB device found, idVendor=1e2d, idProduct=0068, bcdDevice= 0.00
[18284.279319] usb 1-1.4: New USB device strings: Mfr=4, Product=3, SerialNumber=5
[18284.279322] usb 1-1.4: Product: PLSx
[18284.279325] usb 1-1.4: Manufacturer: Cinterion Wireless Modules
[18284.279327] usb 1-1.4: SerialNumber: b3806075
[18284.293157] cdc_ether 1-1.4:1.4 eth0: register 'cdc_ether' at usb-0000:00:14.0-1.4, CDC Ethernet Device, 00:a0:c6:06:07:50
[18284.347693] cdc_ether 1-1.4:1.4 enx00a0c6060750: renamed from eth0
[18462.437454] usb 1-1.4: USB disconnect, device number 36
[18462.438080] cdc_ether 1-1.4:1.4 enx00a0c6060750: unregister 'cdc_ether' usb-0000:00:14.0-1.4, CDC Ethernet Device
[18479.142698] usb 1-1.4: new high-speed USB device number 37 using xhci_hcd
[18479.348689] usb 1-1.4: New USB device found, idVendor=1e2d, idProduct=0068, bcdDevice= 0.00
[18479.348694] usb 1-1.4: New USB device strings: Mfr=4, Product=3, SerialNumber=5
[18479.348697] usb 1-1.4: Product: PLSx
[18479.348699] usb 1-1.4: Manufacturer: Cinterion Wireless Modules
[18479.348702] usb 1-1.4: SerialNumber: b3806075
[18479.367568] cdc_ether 1-1.4:1.4 eth0: register 'cdc_ether' at usb-0000:00:14.0-1.4, CDC Ethernet Device, 00:a0:c6:06:07:50
[18479.415940] cdc_ether 1-1.4:1.4 enx00a0c6060750: renamed from eth0

I see, thank you for your help.

Best Regards,

A Random Intern

Like
0
Log in or register to post comments

Bartłomiej Gema...

Jun 23 2021 - 2:57pm

Hello,

Can you see the assigned interfaces like below:

[ 287.259160] cdc_acm 2-7:1.0: ttyACM0: USB ACM device
[ 287.285125] cdc_acm 2-7:1.2: ttyACM1: USB ACM device
[ 287.289685] cdc_acm 2-7:1.4: ttyACM2: USB ACM device
[ 287.292539] cdc_acm 2-7:1.6: ttyACM3: USB ACM device

Are you able to communicate?

BR,

Bartłomiej

Like
0
Log in or register to post comments

Random Intern

Jun 29 2021 - 4:24pm

Hi Bartłomiej,

Sorry for the delay. We sent back the modules to get them updated so here are the new AT1 and AT8 replies :

ati1

Cinterion
PLS83-W
REVISION 01.002
A-REVISION 01.000.05

OK
ati8

C-REVISION 00000.00

OK

Here is my new dmesg output and I can now see the interfaces below (along with some errors that I haven't solved yet :

~$ dmesg
[19238.648200] usb 1-2.3: new high-speed USB device number 17 using xhci_hcd
[19238.850368] usb 1-2.3: New USB device found, idVendor=1e2d, idProduct=006f, bcdDevice= 0.00
[19238.850372] usb 1-2.3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[19238.850374] usb 1-2.3: Product: PLSx3
[19238.850376] usb 1-2.3: Manufacturer: Cinterion Wireless Modules
[19238.850377] usb 1-2.3: SerialNumber: ff94bff1
[19238.860786] qmi_wwan 1-2.3:1.0: cdc-wdm1: USB WDM device
[19238.861329] qmi_wwan 1-2.3:1.0 wwan0: register 'qmi_wwan' at usb-0000:00:14.0-2.3, WWAN/QMI device, b6:e0:cd:ae:d0:cd
[19238.862814] qmi_wwan 1-2.3:1.2: cdc-wdm2: USB WDM device
[19238.863312] qmi_wwan 1-2.3:1.2 wwan1: register 'qmi_wwan' at usb-0000:00:14.0-2.3, WWAN/QMI device, b6:e0:cd:ae:d0:cd
[19238.865426] qmi_wwan 1-2.3:1.4: cdc-wdm3: USB WDM device
[19238.866061] qmi_wwan 1-2.3:1.4 wwan2: register 'qmi_wwan' at usb-0000:00:14.0-2.3, WWAN/QMI device, b6:e0:cd:ae:d0:cd
[19238.867704] qmi_wwan 1-2.3:1.6: cdc-wdm4: USB WDM device
[19238.868391] qmi_wwan 1-2.3:1.6 wwan3: register 'qmi_wwan' at usb-0000:00:14.0-2.3, WWAN/QMI device, b6:e0:cd:ae:d0:cd
[19238.870369] qmi_wwan 1-2.3:1.8: cdc-wdm5: USB WDM device
[19238.871040] qmi_wwan 1-2.3:1.8 wwan4: register 'qmi_wwan' at usb-0000:00:14.0-2.3, WWAN/QMI device, b6:e0:cd:ae:d0:cd
[19240.432423] qmi_wwan 1-2.3:1.4: unknown notification 32 received: index 4 len 2
[19240.432432] qmi_wwan 1-2.3:1.6: unknown notification 32 received: index 6 len 2
[19240.434460] qmi_wwan 1-2.3:1.0: unknown notification 32 received: index 0 len 2
[19240.434465] qmi_wwan 1-2.3:1.2: unknown notification 32 received: index 2 len 2
[19240.434466] qmi_wwan 1-2.3:1.6: unknown notification 32 received: index 6 len 2
[19240.932417] qmi_wwan 1-2.3:1.0: unknown notification 32 received: index 0 len 2
[19240.934413] qmi_wwan 1-2.3:1.2: unknown notification 32 received: index 2 len 2
[19240.936416] qmi_wwan 1-2.3:1.2: unknown notification 32 received: index 2 len 2
[19240.936425] qmi_wwan 1-2.3:1.4: unknown notification 32 received: index 4 len 2
[19240.938414] qmi_wwan 1-2.3:1.4: unknown notification 32 received: index 4 len 2
[19240.962416] qmi_wwan 1-2.3:1.0: unknown notification 32 received: index 0 len 2
[19241.934402] qmi_wwan 1-2.3:1.2: unknown notification 32 received: index 2 len 2
[19241.936404] qmi_wwan 1-2.3:1.4: unknown notification 32 received: index 4 len 2
[19241.962396] qmi_wwan 1-2.3:1.0: unknown notification 32 received: index 0 len 2
[19545.981732] qmi_wwan 1-2.3:1.0: nonzero urb status received: -71
[19545.981735] qmi_wwan 1-2.3:1.0: wdm_int_callback - 0 bytes
[19545.981738] qmi_wwan 1-2.3:1.2: nonzero urb status received: -71
[19545.981739] qmi_wwan 1-2.3:1.2: wdm_int_callback - 0 bytes
[19545.981740] qmi_wwan 1-2.3:1.4: nonzero urb status received: -71
[19545.981741] qmi_wwan 1-2.3:1.4: wdm_int_callback - 0 bytes
[19545.981764] qmi_wwan 1-2.3:1.6: nonzero urb status received: -71
[19545.981765] qmi_wwan 1-2.3:1.6: wdm_int_callback - 0 bytes
[19545.981766] qmi_wwan 1-2.3:1.8: nonzero urb status received: -71
[19545.981767] qmi_wwan 1-2.3:1.8: wdm_int_callback - 0 bytes
[19545.987760] qmi_wwan 1-2.3:1.0: nonzero urb status received: -71
[19545.987762] qmi_wwan 1-2.3:1.0: wdm_int_callback - 0 bytes
[19545.987764] qmi_wwan 1-2.3:1.2: nonzero urb status received: -71
[19545.987765] qmi_wwan 1-2.3:1.2: wdm_int_callback - 0 bytes
[19545.987767] qmi_wwan 1-2.3:1.4: nonzero urb status received: -71
[19545.987768] qmi_wwan 1-2.3:1.4: wdm_int_callback - 0 bytes
[19545.987769] qmi_wwan 1-2.3:1.6: nonzero urb status received: -71
[19545.987770] qmi_wwan 1-2.3:1.6: wdm_int_callback - 0 bytes
[19545.987771] qmi_wwan 1-2.3:1.8: nonzero urb status received: -71
[19545.987772] qmi_wwan 1-2.3:1.8: wdm_int_callback - 0 bytes
[19545.993728] qmi_wwan 1-2.3:1.0: nonzero urb status received: -71
[19545.993730] qmi_wwan 1-2.3:1.0: wdm_int_callback - 0 bytes
[19545.993733] qmi_wwan 1-2.3:1.2: nonzero urb status received: -71
[19545.993734] qmi_wwan 1-2.3:1.2: wdm_int_callback - 0 bytes
[19545.993735] qmi_wwan 1-2.3:1.4: nonzero urb status received: -71
[19545.993736] qmi_wwan 1-2.3:1.4: wdm_int_callback - 0 bytes
[19545.993737] qmi_wwan 1-2.3:1.6: nonzero urb status received: -71
[19545.993738] qmi_wwan 1-2.3:1.6: wdm_int_callback - 0 bytes
[19545.993755] qmi_wwan 1-2.3:1.8: nonzero urb status received: -71
[19545.993756] qmi_wwan 1-2.3:1.8: wdm_int_callback - 0 bytes
[19545.999759] qmi_wwan 1-2.3:1.0: nonzero urb status received: -71
[19545.999761] qmi_wwan 1-2.3:1.0: wdm_int_callback - 0 bytes
[19545.999763] qmi_wwan 1-2.3:1.2: nonzero urb status received: -71
[19545.999764] qmi_wwan 1-2.3:1.2: wdm_int_callback - 0 bytes
[19545.999765] qmi_wwan 1-2.3:1.4: nonzero urb status received: -71
[19545.999766] qmi_wwan 1-2.3:1.4: wdm_int_callback - 0 bytes
[19545.999767] qmi_wwan 1-2.3:1.6: nonzero urb status received: -71
[19545.999768] qmi_wwan 1-2.3:1.6: wdm_int_callback - 0 bytes
[19545.999769] qmi_wwan 1-2.3:1.8: nonzero urb status received: -71
[19545.999770] qmi_wwan 1-2.3:1.8: wdm_int_callback - 0 bytes
[19546.005771] qmi_wwan 1-2.3:1.0: nonzero urb status received: -71
[19546.005773] qmi_wwan 1-2.3:1.0: wdm_int_callback - 0 bytes
[19546.005775] qmi_wwan 1-2.3:1.2: nonzero urb status received: -71
[19546.005776] qmi_wwan 1-2.3:1.2: wdm_int_callback - 0 bytes
[19546.005778] qmi_wwan 1-2.3:1.4: nonzero urb status received: -71
[19546.005779] qmi_wwan 1-2.3:1.4: wdm_int_callback - 0 bytes
[19546.005780] qmi_wwan 1-2.3:1.6: nonzero urb status received: -71
[19546.005781] qmi_wwan 1-2.3:1.6: wdm_int_callback - 0 bytes
[19546.005782] qmi_wwan 1-2.3:1.8: nonzero urb status received: -71
[19546.005783] qmi_wwan 1-2.3:1.8: wdm_int_callback - 0 bytes
[19546.011759] qmi_wwan 1-2.3:1.0: nonzero urb status received: -71
[19546.011761] qmi_wwan 1-2.3:1.0: wdm_int_callback - 0 bytes
[19546.011763] qmi_wwan 1-2.3:1.2: nonzero urb status received: -71
[19546.011764] qmi_wwan 1-2.3:1.2: wdm_int_callback - 0 bytes
[19546.011766] qmi_wwan 1-2.3:1.4: nonzero urb status received: -71
[19546.011767] qmi_wwan 1-2.3:1.4: wdm_int_callback - 0 bytes
[19546.011768] qmi_wwan 1-2.3:1.6: nonzero urb status received: -71
[19546.011769] qmi_wwan 1-2.3:1.6: wdm_int_callback - 0 bytes
[19546.011770] qmi_wwan 1-2.3:1.8: nonzero urb status received: -71
[19546.011771] qmi_wwan 1-2.3:1.8: wdm_int_callback - 0 bytes
[19546.017728] qmi_wwan 1-2.3:1.0: nonzero urb status received: -71
[19546.017730] qmi_wwan 1-2.3:1.0: wdm_int_callback - 0 bytes
[19546.017732] qmi_wwan 1-2.3:1.2: nonzero urb status received: -71
[19546.017733] qmi_wwan 1-2.3:1.2: wdm_int_callback - 0 bytes
[19546.017734] qmi_wwan 1-2.3:1.4: nonzero urb status received: -71
[19546.017735] qmi_wwan 1-2.3:1.4: wdm_int_callback - 0 bytes
[19546.017736] qmi_wwan 1-2.3:1.6: nonzero urb status received: -71
[19546.017737] qmi_wwan 1-2.3:1.6: wdm_int_callback - 0 bytes
[19546.017755] qmi_wwan 1-2.3:1.8: nonzero urb status received: -71
[19546.017756] qmi_wwan 1-2.3:1.8: wdm_int_callback - 0 bytes
[19546.023767] qmi_wwan 1-2.3:1.0: nonzero urb status received: -71
[19546.023769] qmi_wwan 1-2.3:1.0: wdm_int_callback - 0 bytes
[19546.023771] qmi_wwan 1-2.3:1.2: nonzero urb status received: -71
[19546.023772] qmi_wwan 1-2.3:1.2: wdm_int_callback - 0 bytes
[19546.023773] qmi_wwan 1-2.3:1.4: nonzero urb status received: -71
[19546.023774] qmi_wwan 1-2.3:1.4: wdm_int_callback - 0 bytes
[19546.023775] qmi_wwan 1-2.3:1.6: nonzero urb status received: -71
[19546.023776] qmi_wwan 1-2.3:1.6: wdm_int_callback - 0 bytes
[19546.023777] qmi_wwan 1-2.3:1.8: nonzero urb status received: -71
[19546.023778] qmi_wwan 1-2.3:1.8: wdm_int_callback - 0 bytes
[19546.029776] qmi_wwan 1-2.3:1.0: nonzero urb status received: -71
[19546.029778] qmi_wwan 1-2.3:1.0: wdm_int_callback - 0 bytes
[19546.029781] qmi_wwan 1-2.3:1.2: nonzero urb status received: -71
[19546.029782] qmi_wwan 1-2.3:1.2: wdm_int_callback - 0 bytes
[19546.029783] qmi_wwan 1-2.3:1.4: nonzero urb status received: -71
[19546.029784] qmi_wwan 1-2.3:1.4: wdm_int_callback - 0 bytes
[19546.029785] qmi_wwan 1-2.3:1.6: nonzero urb status received: -71
[19546.029786] qmi_wwan 1-2.3:1.6: wdm_int_callback - 0 bytes
[19546.029787] qmi_wwan 1-2.3:1.8: nonzero urb status received: -71
[19546.029788] qmi_wwan 1-2.3:1.8: wdm_int_callback - 0 bytes
[19546.033899] usb 1-2.3: USB disconnect, device number 17
[19546.033974] qmi_wwan 1-2.3:1.0 wwan0: unregister 'qmi_wwan' usb-0000:00:14.0-2.3, WWAN/QMI device

I also tried checking if the module is ready but it returns the error below :

~$ sudo qmicli -d /dev/cdc-wdm1 -p --dms-get-operating-mode
error: couldn't open the QmiDevice: Transaction timed out

If you have any idea what those errors could be related to, could you let me know ?

Thank you for your help.

Best Regards,

A Random Intern

Like
0
Log in or register to post comments

You are here

LGA DevKit + PLS83-W Module / AT Commands problem | Thales IoT Developer Community

Pages

Pages