Modem reset issue

[Aleksander Morgado]

Hey,

>
> I'm resetting the modem (SIMCOM_SIM7600G-H) with mmcli (mmcli 1.16.10)
>
> The modem status was fully connected before running:
>
> $ mmcli -m 0 --reset
> successfully reseted the modem
>
> After the reset, the device does not connect anymore, and only power
> cycling put things back to normal.
>

Does the module fully reset? i.e. are the ports going away and coming back?

> Modem Manager output is this, after the reset:
>
> Nov 22 17:26:45 bd-curie ModemManager[309]: <warn>  [modem0/bearer21]
> connection attempt #1 failed: QMI protocol error (14): 'CallFailed'
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0] state
> changed (connecting -> registered)
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0/bearer21]
> connection #1 finished: duration 0s, tx: 0 bytes, rx :0 bytes
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0] simple
> connect started...
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0] simple
> connect state (4/8): wait to get fully enabled
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0] simple
> connect state (5/8): register
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0] simple
> connect state (6/8): bearer
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0] simple
> connect state (7/8): connect
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0] state
> changed (registered -> connecting)
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0/bearer22]
> couldn't start network: QMI protocol error (14): 'CallFailed'
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0/bearer22]
> call end reason (1): generic-unspecified
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0/bearer22]
> verbose call end reason (3,2500): [cm] offline
> Nov 22 17:26:45 bd-curie ModemManager[309]: <warn>  [modem0/bearer22]
> connection attempt #1 failed: QMI protocol error (14): 'CallFailed'
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0] state
> changed (connecting -> registered)
> Nov 22 17:26:45 bd-curie ModemManager[309]: <info>  [modem0/bearer22]
> connection #1 finished: duration 0s, tx: 0 bytes, rx :0 bytes
> Nov 22 17:26:47 bd-curie ModemManager[309]: <info>  [modem0] 3GPP
> registration state changed (home -> unknown)
> Nov 22 17:26:47 bd-curie ModemManager[309]: <info>  [modem0] state
> changed (registered -> enabled)
> Nov 22 17:26:47 bd-curie ModemManager[309]: <warn>  [modem0] couldn't
> load operator code: Current operator MCC/MNC is still unknown
> Nov 22 17:26:47 bd-curie ModemManager[309]: <warn>  [modem0] couldn't
> load operator name: Current operator description is still unknown
>
> Is this expected?
>

Not expected, but I'd like to understand if those logs you posted are
happening in the short time between you sending the reset request and
the module really doing the reset. i.e. when you run mmcli --reset,
you're just asking the modem to reset, the modem will get the request
and then after some seconds perform the reset completely, the modem
will fully go away from the system and re-appear. To me, it looks like
those logs you posted may be failed connection attempts triggered
before the modem applied the reset.

-- 
Aleksander
https://aleksander.es