<div dir="ltr"><div dir="ltr"> > Are you using the "Modem Reboot" command only? Or something else? <br></div>No, we added a new command.<div><br></div><div>The image file was sent to the module fragment by fragment.</div><div>Without the mbim-proxy, the transmission process is fluent.</div><div>But when using the mbim-proxy, it will return "MBIM protocol error: FragmentOutOfSequence" after sending the first request(fragment).</div><div>It is weird because we get the out-of-sequence error when we just try to send the first fragment.</div><div>Is it possible that the mbim-proxy is not correctly configured for such transmission ?</div><div><br></div><div>Thanks,</div><div>Edward Chang.</div><div> <br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 11, 2020 at 3:47 PM Aleksander Morgado <<a href="mailto:aleksander@aleksander.es">aleksander@aleksander.es</a>> wrote:<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 Edward,<br>
<br>
> We are now implementing qualcomm device update (qdu) MBIM device service on the libmbim currently used by the MM and fwupd.<br>
> It uses the MBIM_SERVICE_INTEL_FIRMWARE_UPDATE service.<br>
<br>
Are you using the "Modem Reboot" command only? Or something else?<br>
<br>
> We found the update process will succeed only if the modemmanager is stopped and the mbim port is opened without the proxy.<br>
> Probably the mbim interface could not be interfered during the update process.<br>
<br>
You need to investigate why that happens, because it doesn't make much<br>
sense. It is true that the MBIM session is kept open by the proxy, but<br>
other than that, there is no other interaction triggered by the proxy<br>
itself, the only interactions done by the proxy are triggered by<br>
connected clients.<br>
<br>
If your client connects to the proxy, you should be able to send<br>
messages without any problem.<br>
<br>
> Could we stop the mbim-proxy during update and restart it after update ?<br>
><br>
<br>
That is currently not possible, stopping the mbim-proxy will break<br>
other firmware upgrade processes, like the one for the DW5821e. If<br>
there is any issue triggered by the proxy itself, we should fix the<br>
proxy, not stop it<br>
<br>
-- <br>
Aleksander<br>
<a href="https://aleksander.es" rel="noreferrer" target="_blank">https://aleksander.es</a><br>
</blockquote></div></div></div>