Re: Telit FN990: MM 1.20.4: mmcli --location-enable-gps-nmea reporting error

2023-01-09 Thread Daniele Palmas
Hi Amol,

Il giorno mar 3 gen 2023 alle ore 06:36 Amol Lad  ha scritto:
>
> Hi,
>
> I get the following error when enabling NMEA in FN990 with MM 1.20.4 (It 
> comes with 1.18.6 as well). I do not recall seeing this with Telit LN920 so 
> looks like this is something FN990 specific. Please advise. (I'm using MBIM)
>
> # mmcli -m "$modem" --location-enable-gps-nmea
> error: couldn't setup location gathering: 
> 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.GeneralError: Couldn't 
> enable location 'gps-nmea' gathering: Couldn't start GPS engine: QMI protocol 
> error (46): 'GeneralError''

>  [1672723268.345371] [/dev/cdc-wdm0] sent generic request 
> (translated)...
> << QMUX:
> <<   length  = 19
> <<   flags   = 0x00
> <<   service = "loc"
> <<   client  = 1
> << QMI:
> <<   flags   = "none"
> <<   transaction = 4
> <<   tlv_length  = 7
> <<   message = "Set NMEA Types" (0x003E)
> << TLV:
> <<   type   = "NMEA Types" (0x01)
> <<   length = 4
> <<   value  = 0D:00:02:00
> <<   translated = gga, gsv, gsa
>
>  [1672723268.345445] [/dev/cdc-wdm0] sent message...
> << RAW:
> <<   length = 68
> <<   data   = 03:00:00:00:44:00:00:00:3A:00:00:00...
>
>  [1672723268.345621] [/dev/cdc-wdm0] sent message (translated)...
> << Header:
> <<   length  = 68
> <<   type= command (0x0003)
> <<   transaction = 58
> << Fragment header:
> <<   total   = 1
> <<   current = 0
> << Contents:
> <<   service = 'qmi' (d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3)
> <<   cid = 'msg' (0x0001)
> <<   type= 'set' (0x0001)
> << Fields:
> <<   QmiMsg = 
> '01:13:00:00:10:01:00:04:00:3e:00:07:00:01:04:00:0d:00:02:00'
>
>  [1672723268.376601] [/dev/cdc-wdm0] received message...
> >> RAW:
> >>   length = 68
> >>   data   = 03:00:00:80:44:00:00:00:3A:00:00:00...
>
>  [1672723268.376810] [/dev/cdc-wdm0] received message (translated)...
> >> Header:
> >>   length  = 68
> >>   type= command-done (0x8003)
> >>   transaction = 58
> >> Fragment header:
> >>   total   = 1
> >>   current = 0
> >> Contents:
> >>   status error = 'None' (0x)
> >>   service  = 'qmi' (d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3)
> >>   cid  = 'msg' (0x0001)
> >> Fields:
> >>   QMUX = '01:13:00:80:10:01:02:04:00:3e:00:07:00:02:04:00:01:00:73:00'
>
>  [1672723268.376877] [/dev/cdc-wdm0] received message...
> << RAW:
> <<   length = 20
> <<   data   = 01:13:00:80:10:01:02:04:00:3E:00:07...
>
>  [1672723268.376982] [/dev/cdc-wdm0] received generic response 
> (translated)...
> << QMUX:
> <<   length  = 19
> <<   flags   = 0x80
> <<   service = "loc"
> <<   client  = 1
> << QMI:
> <<   flags   = "response"
> <<   transaction = 4
> <<   tlv_length  = 7
> <<   message = "Set NMEA Types" (0x003E)
> << TLV:
> <<   type   = "Result" (0x02)
> <<   length = 4
> <<   value  = 01:00:73:00
> <<   translated = FAILURE: NoPermission
>
>   [1672723268.377384] [modem0] couldn't setup required NMEA traces: QMI 
> protocol error (115): 'NoPermission'

I can't check right now on the target, but this and the start error
are probably related to the control point not registered as the master
client.

I suggest to file a ticket with Telit technical support to deal with this.

Regards,
Daniele

>  [1672723268.377493] [/dev/cdc-wdm0] sent message...
> << RAW:
> <<   length = 38
> <<   data   = 01:25:00:00:10:01:00:05:00:22:00:19...
>
>  [1672723268.377685] [/dev/cdc-wdm0] sent generic request 
> (translated)...
> << QMUX:
> <<   length  = 37
> <<   flags   = 0x00
> <<   service = "loc"
> <<   client  = 1
> << QMI:
> <<   flags   = "none"
> <<   transaction = 5
> <<   tlv_length  = 25
> <<   message = "Start" (0x0022)
> << TLV:
> <<   type   = "Minimum Interval between Position Reports" (0x13)
> <<   length = 4
> <<   value  = E8:03:00:00
> <<   translated = 1000
> << TLV:
> <<   type   = "Intermediate Report State" (0x12)
> <<   length = 4
> <<   value  = 02:00:00:00
> <<   translated = disable
> << TLV:
> <<   type   = "Fix Recurrence Type" (0x10)
> <<   length = 4
> <<   value  = 01:00:00:00
> <<   translated = periodic-fixes
> << TLV:
> <<   type   = "Session ID" (0x01)
> <<   length = 1
> <<   value  = 10
> <<   translated = 16
>
>  [1672723268.377846] [/dev/cdc-wdm0] sent message...
> << RAW:
> <<   length = 86
> <<   data   = 03:00:00:00:56:00:00:00:3B:00:00:00...
>
>  [1672723268.378097] [/dev/cdc-wdm0] sent message (translated)...
> << Header:
> <<   length  = 86
> <<   type= command (0x0003)
> <<   

Re: ModemManager 1.20.4 - invalid cast

2023-01-09 Thread Aleksander Morgado
Hey Peter,

>
> (ModemManager:19419): GLib-GObject-WARNING **: 15:01:34.152: invalid cast from
> 'MMBroadbandModemQmiQuectel' to 'MMBroadbandModemMbim'
> **
> ERROR:../src/mm-broadband-modem-mbim.c:284:mm_broadband_modem_mbim_peek_port_mbim:
> assertion failed: (MM_IS_BROADBAND_MODEM_MBIM (self))
> Bail out!
> ERROR:../src/mm-broadband-modem-mbim.c:284:mm_broadband_modem_mbim_peek_port_mbim:
> assertion failed: (MM_IS_BROADBAND_MODEM_MBIM (self))
> Aborted
>

Any chance you can run this under gdb like this and get a backtrace?
$ sudo G_DEBUG=fatal-warnings gdb --args /usr/sbin/ModemManager --debug

Also, what modem is this?


Re: ModemManager 1.20.4 - invalid cast

2023-01-09 Thread Peter Naulls

On 1/9/23 06:11, Aleksander Morgado wrote:

Hey Peter,



(ModemManager:19419): GLib-GObject-WARNING **: 15:01:34.152: invalid cast from
'MMBroadbandModemQmiQuectel' to 'MMBroadbandModemMbim'
**
ERROR:../src/mm-broadband-modem-mbim.c:284:mm_broadband_modem_mbim_peek_port_mbim:
assertion failed: (MM_IS_BROADBAND_MODEM_MBIM (self))
Bail out!
ERROR:../src/mm-broadband-modem-mbim.c:284:mm_broadband_modem_mbim_peek_port_mbim:
assertion failed: (MM_IS_BROADBAND_MODEM_MBIM (self))
Aborted



Any chance you can run this under gdb like this and get a backtrace?
$ sudo G_DEBUG=fatal-warnings gdb --args /usr/sbin/ModemManager --debug


I will try; but as you recall, I've had problems with MM under GDB on this
platform since it greatly impacts the performance and affects timeouts, etc.

I'll get you a full log in any case; might be a day or two.


Also, what modem is this?


Quectel EM12-AW; it is pretty similar to other Quectel modems.

Obviously what I am doing is not "correct", but an error condition or whatever
would be much better here than a crash.

Thanks.