Hi Amol and Aleksander, Il giorno lun 28 nov 2022 alle ore 12:19 Amol Lad <amol....@4rf.com> ha scritto: > > Attaching full log and relevant portion seems below. No it's not regression. > I just loaded 1.20.2 mainly for 5g support. >
I've got a bunch of changes fixing this and adding modes retrieval through QMI (which makes more sense than using AT commands when available), just need to find the time to polish and submit... Regards, Daniele > == > <debug> [1669633765.148778] [modem0] no carrier config currently selected > (default in use) > <debug> [1669633765.149038] [modem0] device identifier built: > 00001bc700001071359172390000176FN990TelitWirelessSolutions -> > d04794b2e195986e2087001f45f6a4b81d1e3f16 > <debug> [1669633765.149153] [ttyUSB2/at] device open count is 2 (open) > <debug> [1669633765.149226] [ttyUSB2/at] --> 'AT+WS46=?<CR>' > <debug> [1669633765.163992] [ttyUSB2/at] <-- '<CR><LF>+WS46: > (22,28,31,36-38,40)<CR><LF><CR><LF>OK<CR><LF>' > <debug> [1669633765.164170] [modem0] (shared-telit) device allows (3GPP) mode > combination: 3g > <debug> [1669633765.164198] [modem0] (shared-telit) device allows (3GPP) mode > combination: 4g > <debug> [1669633765.164230] [modem0] (shared-telit) device allows (3GPP) mode > combination: 3g, 4g > <debug> [1669633765.164253] [modem0] (shared-telit) device allows (3GPP) mode > combination: 5g > <debug> [1669633765.164281] [modem0] (shared-telit) device allows (3GPP) mode > combination: 4g, 5g > <debug> [1669633765.164312] [modem0] (shared-telit) device allows (3GPP) mode > combination: 3g, 4g, 5g > <debug> [1669633765.164341] [modem0] (shared-telit) device allows (3GPP) mode > combination: 3g, 5g > <debug> [1669633765.164366] [modem0] filtering 7 supported mode combinations > with 1 modes > <debug> [1669633765.164390] [modem0] device supports 3 different mode > combinations > === > <debug> [1669633765.212244] [ttyUSB2/at] device open count is 2 (open) > <debug> [1669633765.212331] [ttyUSB2/at] --> 'AT+WS46?<CR>' > <debug> [1669633765.225404] [ttyUSB2/at] <-- '<CR><LF>+WS46: > 37<CR><LF><CR><LF>OK<CR><LF>' > <warn> [1669633765.225529] [modem0] couldn't load current allowed/preferred > modes: Couldn't parse unexpected +WS46 response: '+WS46: 37' > > From the FN990 AT command guide: > AT+WS46=[<n>] > <n> integer 38 WDS-Side Stack to be used by the TA. > Values: > 22 : UTRAN only > 28 : E-UTRAN only > 31 : UTRAN and E-UTRAN > 36 : NG-RAN only > 37 : NG-RAN and E-UTRAN > 38 : NG-RAN, E-UTRAN and UTRAN > 40 : NG-RAN and UTRAN > > ________________________________ > From: Aleksander Morgado <aleksande...@chromium.org> > Sent: Monday, November 28, 2022 4:03 PM > To: Amol Lad <amol....@4rf.com> > Cc: Daniele Palmas <dnl...@gmail.com>; ModemManager (development) > <modemmanager-devel@lists.freedesktop.org> > Subject: Re: Telit FN990: All supported/current modes not reported (MM 1.20.2) > > Hey, > > > > > I'm trying Telit FN990 with MM 1.20.2 release and "supported" and "current" > > modes always report "4g" in MBIM mode. I believe it's reported correctly in > > QMI. It seems not all +WS46 combinations are supported in MBIM. > > > > Modes | supported: allowed: 4g; preferred: none > > | current: allowed: 4g; preferred: none > > > > Could you please run MM with debug logs to see what the modem is replying? > > Also, just to confirm, this is not a regression, right? > > -- > Aleksander > ________________________________ > The information in this email communication (inclusive of attachments) is > confidential to 4RF Limited and the intended recipient(s). If you are not the > intended recipient(s), please note that any use, disclosure, distribution or > copying of this information or any part thereof is strictly prohibited and > that the author accepts no liability for the consequences of any action taken > on the basis of the information provided. If you have received this email in > error, please notify the sender immediately by return email and then delete > all instances of this email from your system. 4RF Limited will not accept > responsibility for any consequences associated with the use of this email > (including, but not limited to, damages sustained as a result of any viruses > and/or any action or lack of action taken in reliance on it).
