<div dir="ltr"><div dir="ltr"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div>Hi Aleksander, </div></div></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">tir. 31. mar. 2020 kl. 05:43 skrev Aleksander Morgado <<a href="mailto:aleksander@aleksander.es">aleksander@aleksander.es</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hey Tor,<br> <br> ><br> > I am experiencing a very strange problem with MC7304. Randomly (like in 1 of 3 instances), when initializing the WAN connection, the modem setup routine fails on the --wda-get-data-format command, and then the completion of the initialization just fails. For now, we have just been detecting this and then reset the usb port and rerun the whole procedure at regular intervals until it works, but that is not a permanent solution. The wda-set-data-format also fails when get does.<br> ><br> > Have been googling 'lightly' without any obvious success. I was hoping some of you experts on this list just pops up and say 'you need to do this' before we start spending to much on digging very deeply into the issue :)<br> ><br> > # qmicli -d /dev/cdc-wdm0 --wda-get-data-format<br> > error: couldn't create client for the 'wda' service: QMI protocol error (3): 'Internal'<br> ><br> > libqmi version: 1.22.2<br> ><br> > kernel 4.9.199<br> ><br> > MC7304 firmware:<br> > Model: MC7304<br> > Boot version: SWI9X15C_05.05.78.00 r34310 CARMD-EV-FRMWR3 2017/09/17 00:43:17<br> > AMSS version: SWI9X15C_05.05.78.00 r34310 CARMD-EV-FRMWR3 2017/09/17 00:43:17<br> > SKU ID: 1103054<br> > Package ID: 1103054_9906141_MC7304_05.05.66.00_00_Generic_005.000_000<br> > Carrier ID: 1<br> > Config version: 005.029_000<br> ><br> > Any hints or advises appreciated.<br> </blockquote><div><br></div><div>I have some further updates here. I read another thread about the '-p' option, </div><div>which, when added to all instances of qmicli invocation in the init.d file makes</div><div>the problem go away in at least more than 9 out of 10 cases. So it is </div><div>apparently a timing issue. Still have to test this on more than one </div><div>system, but I am optimistic. :)</div><div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Nothing from the top of my head really.<br> <br> Is this happening only during boot? Maybe you didn't wait long enough<br> to boot before sending the WDA command?<br></blockquote><div><br></div><div>It seems that it happens randomly both at boot and after boot. And 'boot' in this case</div><div>is actually a minute or so after power is applied.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Are you only sending the WDA command, or some other additional<br> commands as well? Are those commands failing or is it only the WDA<br> service?<br></blockquote><div><br></div><div>We check the output of the wda-get-data-format command, and depending on</div><div>that, other commands will run - like putting it into 802-3 mode. Other commands</div><div>seem to work anyway, like -w or <span style="color:rgb(0,0,0);font-family:monospace">--wds-get-packet-service-status. </span></div><div><span style="color:rgb(0,0,0);font-family:monospace"><br></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> When you say you're reseting the USB port, are you literally just<br> reseting the USB comm in your host forcing a re-enumeration of the<br> device? Or are you fully powering off the modem externally and<br> powering it back on? Or triggering a rdevice reboot with the DMS<br> service?<br></blockquote><div><br></div><div>We are sending an unbind and bind to the USB port the modem is connected</div><div>to, which forces re-enumeration. But after learning and testing with the -p option, </div><div>I cannot be sure that it really affects anything, or if it worked sometimes just</div><div>randomly as before. </div><div><br></div><div>BR, </div><div>Tor Rune Skoglund</div></div></div>