Sierra MC7710 on embedded debian

[Aleksander Morgado]

On Tue, Jun 3, 2014 at 6:07 PM, reiner otto <augustus_meyer at yahoo.de> wrote:
> Thanx for fast response:
> My script to start the wan connection:
> #!/bin/bash
> #Dont need pppd any more
> killall pppd
> echo "Wait 30s for MC7710 to settle down"
> sleep 30
> #set -x
> qmicli -d /dev/cdc-wdm0  --dms-uim-verify-pin=PIN,2004
> sleep 10
> #Next one makes no difference: Also has problem after "soft boot"
> #qmicli -d /dev/cdc-wdm0 --wds-start-network=  --client-no-release-cid
> --device-open-sync
>

The --device-open-sync will reset ALL services; so all previously
allocated CIDs will be fully reseted. Hence, this option should be
executed only once and only during your *first* qmicli command,
whatever that is. For example, you could just run:
  # qmicli -d /dev/cdc-wdm0 --dms-noop --device-open-sync
And then run your other commands (e.g then the PIN unlock). If you're
seeing errors with mismatched CIDs, maybe that is an option to try.

> qmicli -v -d /dev/cdc-wdm0 --wds-start-network=  --client-no-release-cid
> sleep 10

Have you tried to use the "qmi-network" script that libqmi provides?
It makes it easier to handle the connection/disconnection routine.

Note that if you use --client-no-release-cid always in this command,
running the command multiple times may end up exhausing the number of
WDS clients that can be allocated to the device. So; if you use
--client-no-release-cid; make suret hat you have another WDS command
afterwards using --client-cid (without --client-no-release-cid) so
that the CID is released. Yes, bit messy, but that is why I wrote the
"qmi-network" script :)

> dhclient -nw  -lf /var/tmp/wan.leases wwan0
> echo "Waiting for dhclient to get a lease"
> sleep 10
> ip route delete default
> ip route add dev wwan0
> echo "waiting for IP on wwan0"
>

You may also want to make sure that WWAN0 is configured to use 802.3
(instead of raw-ip), before launching the --wds-start-network command.
You can do this either using the following option (e.g. in the
--wds-start-network command):
    --device-open-net="net-802-3|net-no-qos-header
Or otherwise with an independent command:
    --wda-set-data-format=802-3   (only in libqmi >= 1.10)

> I am puzzled about CID=2. Is it possible, that some data is init=0 after
> power cycle, set to "1" (on successful connection), but then keeps its "1"
> value thru soft boot ? May be, in the MC7710 itself ?

Not sure what you mean with the CID=2... that is a client ID number.
These are fully reseted upon power-cycle and also if you use
--device-open-sync.


-- 
Aleksander
https://aleksander.es