Re: [Quectel EM160R-GL] Various commands over mbim fail with 'Invalid transition'
> >> After upgrading an EM160R-GL modem via QFireHose from firmware version > >> EM160RGLAUR02A07M4G to version EM160RGLAUR02A07M4G, almost all functions > >> fail with ‘Invalid transition’. The modem power state is listed as "power > >> state: low” via mmcli. On the former firmware version everything was > >> working fine. > >> > >> This is currently happening with modemmanager 1.18.8 using mbim via the > >> qmi_wwan driver on openwrt with linux 4.4.60 and libmbim 1.28.4 > >> > >> I tried manually enabling it (in case it was FCC locked) via mbimcli > >> --device-open-proxy --device="/dev/cdc-wdm0" --quectel-set-radio-state=on, > >> but this also had no effect. > >> > >> What additional steps would I need to take to debug this? > > > > Very likely that they may have changed the FCC unlock algorithm in the > > newer firmware version :/ > > > > -- > > Aleksander > > > The same firmware version has worked on other modems of the same model. This > appears to be a problem with a specific batch of modems(?). Is this something > that is likely to occur? > > Also in my testing the modem is not FCC locked, its stuck in factory-test > mode, as verified by AT+QRFTESTMODE?. Attempting to leave factory-test mode > with AT+QRFTESTMODE=0 doesn’t seem to have any effect Ah, that could also be it, yes. Maybe ask for help in the Quectel forum, they may know what happened or how to solve it. -- Aleksander
Re: [Quectel EM160R-GL] Various commands over mbim fail with 'Invalid transition'
> On Jun 13, 2023, at 6:04 AM, Aleksander Morgado > wrote: > > On Tue, Jun 13, 2023 at 1:43 AM Alex Ballmer wrote: >> >> After upgrading an EM160R-GL modem via QFireHose from firmware version >> EM160RGLAUR02A07M4G to version EM160RGLAUR02A07M4G, almost all functions >> fail with ‘Invalid transition’. The modem power state is listed as "power >> state: low” via mmcli. On the former firmware version everything was working >> fine. >> >> This is currently happening with modemmanager 1.18.8 using mbim via the >> qmi_wwan driver on openwrt with linux 4.4.60 and libmbim 1.28.4 >> >> I tried manually enabling it (in case it was FCC locked) via mbimcli >> --device-open-proxy --device="/dev/cdc-wdm0" --quectel-set-radio-state=on, >> but this also had no effect. >> >> What additional steps would I need to take to debug this? > > Very likely that they may have changed the FCC unlock algorithm in the > newer firmware version :/ > > -- > Aleksander The same firmware version has worked on other modems of the same model. This appears to be a problem with a specific batch of modems(?). Is this something that is likely to occur? Also in my testing the modem is not FCC locked, its stuck in factory-test mode, as verified by AT+QRFTESTMODE?. Attempting to leave factory-test mode with AT+QRFTESTMODE=0 doesn’t seem to have any effect
Re: [Quectel EM160R-GL] Various commands over mbim fail with 'Invalid transition'
On Tue, Jun 13, 2023 at 1:43 AM Alex Ballmer wrote: > > After upgrading an EM160R-GL modem via QFireHose from firmware version > EM160RGLAUR02A07M4G to version EM160RGLAUR02A07M4G, almost all functions fail > with ‘Invalid transition’. The modem power state is listed as "power state: > low” via mmcli. On the former firmware version everything was working fine. > > This is currently happening with modemmanager 1.18.8 using mbim via the > qmi_wwan driver on openwrt with linux 4.4.60 and libmbim 1.28.4 > > I tried manually enabling it (in case it was FCC locked) via mbimcli > --device-open-proxy --device="/dev/cdc-wdm0" --quectel-set-radio-state=on, > but this also had no effect. > > What additional steps would I need to take to debug this? Very likely that they may have changed the FCC unlock algorithm in the newer firmware version :/ -- Aleksander
[Quectel EM160R-GL] Various commands over mbim fail with 'Invalid transition'
After upgrading an EM160R-GL modem via QFireHose from firmware version EM160RGLAUR02A07M4G to version EM160RGLAUR02A07M4G, almost all functions fail with ‘Invalid transition’. The modem power state is listed as "power state: low” via mmcli. On the former firmware version everything was working fine. This is currently happening with modemmanager 1.18.8 using mbim via the qmi_wwan driver on openwrt with linux 4.4.60 and libmbim 1.28.4 I tried manually enabling it (in case it was FCC locked) via mbimcli --device-open-proxy --device="/dev/cdc-wdm0" --quectel-set-radio-state=on, but this also had no effect. What additional steps would I need to take to debug this? Thanks Log snippet from logread on openwrt with LOG_LEVEL set to debug: Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.095984] [modem0] user request to connect modem Mon Jun 12 22:56:55 2023 daemon.info [10700]: [1686610615.096263] [modem0] simple connect started... Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096345] [modem0]profile ID: unspecified Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096402] [modem0]PIN: unspecified Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096447] [modem0]operator ID: unspecified Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096492] [modem0]allowed roaming: yes Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096537] [modem0]APN: Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096580] [modem0]APN type: unspecified Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096629] [modem0]IP family: unspecified Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096712] [modem0]allowed authentication: unspecified Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096806] [modem0]user: unspecified Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096866] [modem0]password: unspecified Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.096934] [modem0]multiplex: unspecified Mon Jun 12 22:56:55 2023 daemon.info [10700]: [1686610615.096982] [modem0] simple connect state (3/8): enable Mon Jun 12 22:56:55 2023 daemon.info [10700]: [1686610615.097158] [modem0] state changed (disabled -> enabling) Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.097834] [modem0] skipping initialization: not first enabling Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.097907] [modem0/ttyUSB2/at] device open count is 2 (open) Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.097957] [modem0/ttyUSB3/at] opening serial port... Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.099048] [modem0/ttyUSB3/at] setting up baudrate: 57600 Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.099138] [modem0/ttyUSB3/at] no flow control explicitly requested for device Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.099196] [modem0/ttyUSB3/at] port attributes not fully set Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.099295] [modem0/ttyUSB3/at] device open count is 1 (open) Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.099345] [modem0/ttyUSB3/at] running init sequence... Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.099459] [modem0/ttyUSB0/qcdm] opening serial port... Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.100476] [modem0/ttyUSB0/qcdm] device open count is 1 (open) Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.100563] [modem0] flashing primary AT port before enabling... Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.100721] [modem0/ttyUSB3/at] --> 'ATE0' Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [/dev/cdc-wdm0] sent message... << RAW: << length = 48 << data = 03:00:00:00:30:00:00:00:1D:00:00:00... Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [/dev/cdc-wdm0] sent message (translated)... << Header: << length = 48 << type= command (0x0003) << transaction = 29 << Fragment header: << total = 1 << current = 0 << Contents: << service = 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df) << cid = 'radio-state' (0x0003) << type= 'query' (0x) Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [1686610615.108400] [modem0/ttyUSB3/at] <-- 'OK' Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [/dev/cdc-wdm0] received message... >> RAW: >> length = 56 >> data = 03:00:00:80:38:00:00:00:1D:00:00:00... Mon Jun 12 22:56:55 2023 daemon.debug [10700]: [/dev/cdc-wdm0] received message (translated)... >> Header: >> length = 56 >> type= command-done (0x8003) >> transaction = 29 >> Fragment header: >> total = 1 >> current = 0 >> Contents: >> status error = 'None' (0x) >> service =
