libqmi-devel Digest, Vol 77, Issue 3
gildeap at tcd.ie
Wed Feb 6 11:28:37 UTC 2019
That is correct about my system. The output is too much (correlationally at
least), but I think maybe just when I was using verbose mode.
For the second issue yes, the interface seemed fine afterward - I sent a
command one time to check.
On Sun, 3 Feb 2019 at 08:03, Aleksander Morgado <aleksander at aleksander.es>
> On Mon, Jan 14, 2019 at 4:03 PM Paul Gildea <gildeap at tcd.ie> wrote:
>> This report is from quite some time ago but as I hit this issue when
>> working with libqmi recently, maybe some of my debugging can help anybody
>> else if they get this issue. In my case the upgrade is failing whenever I
>> am using a slow baud rate. Each time I tried to upgrade an MC7455 with a
>> connection using baud 9600 I would get this error. On a hunch I thought
>> that this may be related to the issue. I redirected the upgrade output to a
>> file and the upgrade worked fine, I sshed in and that worked fine also.
> You mean the actual stdout of qmi-firmware-update is maybe too much if
> your connection is very slow? i.e. 9600bps is your remote connection to a
> system with the MC7455, right?
>> Another issue I noticed is that when upgrading is complete and the
>> updater is waiting on a reply using the cdc-wdm port, if the higher
>> enumerated of the two ports is used, the transactions will time out. For
>> instance if the modem comes back up with cdc-wdm0 and cdc-wdm1 then if
>> cdc-wdm1 is used this will happen 12 times and then the program will print
>> an error also (seen below):
>> [14 Jan 2019, 14:34:43] [Debug] [/dev/cdc-wdm1] sent generic request
>> <<<<<< QMUX:
>> <<<<<< length = 11
>> <<<<<< flags = 0x00
>> <<<<<< service = "ctl"
>> <<<<<< client = 0
>> <<<<<< QMI:
>> <<<<<< flags = "none"
>> <<<<<< transaction = 1
>> <<<<<< tlv_length = 0
>> <<<<<< message = "Sync" (0x0027)
>> [14 Jan 2019, 14:35:03] -Warning ** couldn't create DMS client after
>> upgrade: couldn't open QMI device: Transaction timed out
>> [14 Jan 2019, 14:35:03] -Error ** qmi_device_release_client: assertion
>> `QMI_IS_DEVICE (self)' failed
>> No functional error, the modem upgrades successfully, it just errors and
>> never returns to the linux prompt without user intervention. The lower
>> enumerated port works fine.
> Does the cdc-wdm1 work at all using QMI after the upgrade? i.e. do you get
> 2 working QMI ports after the upgrade or just cdc-wdm0 working?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libqmi-devel