@nvd, Do you think the issue started after a specific upgrade path was taken? For the devices that had connectivity restored by re-running the tool, did they remain stable in terms of connectivity? I’ve rebuilt 18.04.0 with the toolchain from Release 15, and I did immediately see a failure to connect, with the same error codes show in @coastalbrandon’s image:
Aug 1 22:20:48 swi-mdm9x15 user.err Legato: =ERR= | modemDaemon[678]/swiQmi T=m ain | swiQmi.c swiQmi_CheckResponse() 813 | Sending QMI_WDS_START_NETWORK_INTERF ACE_REQ_V01 failed: rc=0 (), resp.result=1.[0x01], resp.error=14.[0x0e] Aug 1 22:20:48 swi-mdm9x15 user.err Legato: =ERR= | modemDaemon[678]/le_pa T=ma in | pa_mdc_qmi.c StartSession() 1903 | Data connection failure Call End provide d 45, Code 1 Aug 1 22:20:48 swi-mdm9x15 user.err Legato: =ERR= | modemDaemon[678]/le_pa T=ma in | pa_mdc_qmi.c StartSession() 1914 | Data connection failure Verbose Call End provided Type 2, Verbose 204 Aug 1 22:20:48 swi-mdm9x15 user.err Legato: =ERR= | modemDaemon[678]/modemDaemo n T=main | le_mdc.c le_mdc_StartSession() 1017 | Get Connection failure 45, 1, 2 , 204
One limitation of pairing the newer AVC agent in Legato 18.04.0 with the older firmware from Release 15 is that you can’t have concurrent data connections with a USB host and a Legato application over the same APN. In my case, my Windows 10 host was automatically starting a data connection, which blocked my AirVantage test. As soon as I disabled the Windows connection, my AirVantage connection was successful. That was Release 15 Generic Modem + Linux, with LE 18.04.0 rebuilt with R15 toolchain. Is it possible that the QMI Event Reports failure isn’t the root cause? I’m not seeing that error though, which is strange, and I’d still like to get to the bottom of that error.
Thanks,
Ryan