Sierra HL7588

[Dan Williams]

On Tue, 2017-04-18 at 00:12 +0000, Paul Bartell wrote:
> Hello,
> 
> I've been trying to bring up a Sierra HL7588 modem on the latest
> version of
> ModemManager. The HL7588 seems to be based on the Sierra EM7345 with
> an
> Intel/Infineon chipset.
> 
> This modem has three different USB configurations:
> 
> 1. CDC-ACM and 4 NCM ports
> 2. CDC-ACM
> 3. MBIM and CDC-ACM

On these devices I think MBIM would be preferred.  MM's Intel XMM AT
command support is mostly absent, because these chipsets didn't show up
in consumer devices until they supported MBIM.

Some observations with this device:

1) it never replies to the sms+read command, instead it just lets MM
time out after 10 seconds.

2) as you've seen, it never allows bearer statistics, returning
OperationNotAllowed.

But also, it looks like you're disabling then re-enabling and
reconnecting the device each time?  Any reason why you're doing the
disable/re-enable step?  That shouldn't be necessary, unless you're
doing it for testing reasons...

Anyway, things seem to go well for the device until MM gets two
Simple.Connect() requests that run in parallel and end up requesting a
connection at about the same time.  That should be fine, usually,
except that MBIM can't support that without some additional kernel-side 
configuration that MM doesn't do.  So that's immediately suspect, and
the device seems to get into a bad state and return DeviceNotSupported.

First Simple.Connect() request is at 1491876941.001119.
Second is at 1491876948.689788.
Both start proceeding in parallel at 1491876951.018354.

This is probably a bug in ModemManager that it allows this to happen
without supporting multiple MBIM data streams.  Any idea if the tools
you're using to drive ModemManager are perhaps sending two connect
requests in parallel, and if you could modify those tools to not do
that for testing purposes?

Dan


> Only the second configuration works properly out of the box (standard
> ppp
> connection).
> 
> After patching ModemManager not check tx/rx byte counters, the modem
> sometimes connects in MBIM mode. Other times it fails when connecting
> to
> the bearer with an "OperationNotAllowed" or "NoDeviceSupport" error.
> I've
> attached a log of the ModemManager --debug for the modem in mbim
> mode.
> 
> It seems to connect reliably once per reset when specifying ip-
> type=ipv4v6
> instead of just ipv4. If I attempt to connect and then disconnect,
> the
> modem must be reset before it will connect again. Similarly, when
> connecting via mbimcli, it defaults to ipv4v6 and connects correctly
> the
> first time but disconnecting and reconnecting always returns
> OperationNotAllowed or NoDeviceSupport. Sometimes using mbimcli with
> --set-radio-state=off and then --set-radio-state=on resets it
> sufficiently
> to connect again.
> 
> I also attached a log for the HL7588 in NCM mode if that would be
> helpful
> as well.
> 
> Also here is a list of the device capabilities reported by mbimcli
> mbimcli -d /dev/cdc-wdm0 -p --query-device-caps
> [/dev/cdc-wdm0] Device capabilities retrieved:
> Device type: 'embedded'
> Cellular class: 'gsm'
> Voice class: 'no-voice'
> Sim class: 'removable'
> Data class: 'gprs, edge, umts, hsdpa, hsupa, lte'
> SMS caps: 'pdu-receive, pdu-send'
> Ctrl caps: 'reg-manual'
> Max sessions: '16'
> Custom data class: 'unknown'
> Device ID: '014284000026041'
> Firmware info: 'M2M_7160_MBIM_VERIZON_WW_01.15'
> Hardware info: 'XMM7160_V1.2_MBIM_NAND_VERIZON'
> 
> mbimcli -d /dev/cdc-wdm0 -p --query-packet-statistics
> error: operation failed: OperationNotAllowed
> 
> I would really appreciate any ideas on what my next steps should be.
> 
> Thanks,
> Paul
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel