Hi,
I used minicom directly on the TTY (0 and 2), the failures remain on both
models for the AT commands used during MM device init and they are systematic
(like MM).
On ttyUSB2 interface, I see periodically unsolicited responses such as:
^RSSI: 18
^CERSSI:0,0,255,-101,-12,7,32639,32639,32639,
^ANLEVEL:0,99,18,4,101,12
^HCSQ:"LTE",45,40,136,16
On both TTY, some other AT commands such as ^SYSCFGEX, ^SYSINFOEX or +CREG work
but most (even basic ones) don't.
AT^SYSINFOEX
^SYSINFOEX:2,3,0,1,0,6,"LTE",101,"LTE"
OK
AT+CSQ
+CSQ: 17,99
OK
ATI
ERROR
Louis-Alexis
________________________________
From: Aleksander Morgado <aleksan...@aleksander.es>
Sent: 29 July 2020 10:45
To: Louis-Alexis Eyraud <louis-alexis.eyr...@sigfox.com>
Cc: ModemManager (development) <modemmanager-devel@lists.freedesktop.org>
Subject: Re: Huawei MS2372h-158/518 initialisation issues
Hey,
My team and I tried multiples Huawei MS2372h variants and two of them (the 158
and 518) show similar initialisation errors.
Jul 28 15:04:44 raspberrypi ModemManager[416]: <info> [1595945084.395531]
[device /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3] creating modem
with plugin 'huawei' and '3' ports
Jul 28 15:04:44 raspberrypi ModemManager[416]: <warn> [1595945084.411342]
[plugin/huawei] could not grab port ttyUSB1: Cannot add port 'tty/ttyUSB1',
unhandled serial type
Jul 28 15:04:44 raspberrypi ModemManager[416]: <info> [1595945084.416027]
[base-manager] modem for device
'/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3' successfully created
Jul 28 15:04:44 raspberrypi ModemManager[416]: <warn> [1595945084.971664]
[modem0] modem couldn't be initialized: couldn't load current capabilities:
Failed to determine modem capabilities.
After init, the modems are in an unavailable state from Network Manager point
of view and of course they cannot establish a connection.
No info (model, firmware...) is present in mmcli output:
-------------------------
General | dbus path: /org/freedesktop/ModemManager1/Modem/1
-------------------------
System | device:
/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2
| drivers: option1
| plugin: huawei
| primary port: ttyUSB2
| ports: ttyUSB0 (at), ttyUSB2 (at)
-------------------------
Status | signal quality: 0% (cached)
-------------------------
Modes | supported: allowed: any; preferred: none
| current: allowed: any; preferred: none
In ModemManager debug logs, there are many AT command errors like this one:
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.962262]
[modem0/ttyUSB2/at] --> 'AT+CGMM<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.970688]
[modem0/ttyUSB2/at] <-- '<CR><LF>ERROR<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.971016]
[modem0/ttyUSB2/at] operation failure: 100 (Unknown error)
The attached debugs logs and lsusb output for the MS2372h-158 are from a test
done on a RPI3 with a ModemManager build from git on master branch (reproduced
with 1.10, 1.12 and 1.14 too).
Have you an idea where the issue could come from?
The modem is really reporting a ton of ERRORs on most AT commands we try to use:
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.421452]
[modem0/ttyUSB2/at] --> 'ATE0<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.908627]
[modem0/ttyUSB2/at] <-- '<CR><LF>OK<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.909130]
[modem0/ttyUSB2/at] --> 'ATV1<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.914240]
[modem0/ttyUSB2/at] <-- '<CR><LF>ERROR<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.914580]
[modem0/ttyUSB2/at] operation failure: 100 (Unknown error)
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.914776]
[modem0/ttyUSB2/at] --> 'AT+CMEE=1<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.925467]
[modem0/ttyUSB2/at] <-- '<CR><LF>ERROR<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.925801]
[modem0/ttyUSB2/at] operation failure: 100 (Unknown error)
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.925989]
[modem0/ttyUSB2/at] --> 'ATX4<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.931025]
[modem0/ttyUSB2/at] <-- '<CR><LF>ERROR<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.931517]
[modem0/ttyUSB2/at] operation failure: 100 (Unknown error)
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.931730]
[modem0/ttyUSB2/at] --> 'AT&C1<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.937987]
[modem0/ttyUSB2/at] <-- '<CR><LF>ERROR<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.938329]
[modem0/ttyUSB2/at] operation failure: 100 (Unknown error)
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.938526]
[modem0/ttyUSB2/at] --> 'AT+GCAP<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.946952]
[modem0/ttyUSB2/at] <-- '<CR><LF>ERROR<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.947296]
[modem0/ttyUSB2/at] operation failure: 100 (Unknown error)
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.947536]
[modem0/ttyUSB2/at] --> 'ATI<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.951462]
[modem0/ttyUSB2/at] <-- '<CR><LF>ERROR<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.951803]
[modem0/ttyUSB2/at] operation failure: 100 (Unknown error)
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.952049]
[modem0/ttyUSB2/at] --> 'AT+CPIN?<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.961680]
[modem0/ttyUSB2/at] <-- '<CR><LF>ERROR<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.962019]
[modem0/ttyUSB2/at] operation failure: 100 (Unknown error)
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.962262]
[modem0/ttyUSB2/at] --> 'AT+CGMM<CR>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.970688]
[modem0/ttyUSB2/at] <-- '<CR><LF>ERROR<CR><LF>'
Jul 28 15:04:44 raspberrypi ModemManager[416]: <debug> [1595945084.971016]
[modem0/ttyUSB2/at] operation failure: 100 (Unknown error)
Jul 28 15:04:44 raspberrypi ModemManager[416]: <warn> [1595945084.971664]
[modem0] modem couldn't be initialized: couldn't load current capabilities:
Failed to determine modem capabilities.
Would you be able to run these commands manually without MM using minicom, and
see if the commands keep on failing constantly? Also, do these commands fail if
they're run in ttyUSB0 instead of ttyUSB2?
--
Aleksander
https://aleksander.es<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Faleksander.es%2F&data=02%7C01%7Clouis-alexis.eyraud%40sigfox.com%7C6dffa8a8617940d910a708d8339bd476%7Cfcbc8bb1061e4b949f703ad917b0c8d3%7C0%7C0%7C637316091660335155&sdata=NSpyFg78wUE9RzYU4yt1%2FlAzsfOp3kwQ8o23Z1q1uT4%3D&reserved=0>
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
