RE: ublox SARA does not connect
Hi Since I sent you this, I made some progress- - Modified ublox plugin to identify this modem as 4g - found out that the AT+COPS=0 you always send, does not return or return some proprietary CME code. that is because the modem does auto-registration and sending COPS interferes with that. That is stated in the datasheet. So removed it and it everything started working. - I do have still problems with specific devices which return error [modem0] couldn't load UE mode of operation for EPS: Serial command timed out. I guess that’s serial port hung from some previous command? ron -Original Message- From: Aleksander Morgado Sent: Monday, September 4, 2023 11:28 PM To: ron Cc: modemmanager-devel@lists.freedesktop.org Subject: Re: ublox SARA does not connect Hey > So its been a few months, and now when we install the product in US, trying > to connect to Verizon and tmobile, I face problems again. > Modem is ublox sara r5, which works through serial port AT commands only. > The modem seems to be connected, when issuing AT+CGDCONT , but modem > manager +network manager do not go ahead to create a connection > Attached logs > The modem is indeed registered as we can see the initial EPS bearer IP address for the vzwadmin APN, but for some reason MM doesn't know about that. I can see MM trying +CREG? and +CGREG? but they both seem to return the reg state as idle. Could you run +CEREG? manually in the AT port to see what it returns? The modem is detected as a 1-port AT generic modem, and none of the capability queries we do end up telling us it may be 4G capable (which is why we don't try +CEREG to check) ModemManager[573]: [1692200059.641466] [device /sys/devices/platform/soc@0/3080.bus/3086.serial] creating modem with plugin 'generic' and '1' ports ... ModemManager[573]: [1692200059.704189] [modem0/ttymxc0/at] --> 'AT+WS46=?' ModemManager[573]: [1692200059.716311] [modem0/ttymxc0/at] <-- '+CME ERROR: 100' -- Aleksander
Re: ublox SARA does not connect
Hey > So its been a few months, and now when we install the product in US, trying > to connect to Verizon and tmobile, I face problems again. > Modem is ublox sara r5, which works through serial port AT commands only. > The modem seems to be connected, when issuing AT+CGDCONT , but modem manager > +network manager do not go ahead to create a connection > Attached logs > The modem is indeed registered as we can see the initial EPS bearer IP address for the vzwadmin APN, but for some reason MM doesn't know about that. I can see MM trying +CREG? and +CGREG? but they both seem to return the reg state as idle. Could you run +CEREG? manually in the AT port to see what it returns? The modem is detected as a 1-port AT generic modem, and none of the capability queries we do end up telling us it may be 4G capable (which is why we don't try +CEREG to check) ModemManager[573]: [1692200059.641466] [device /sys/devices/platform/soc@0/3080.bus/3086.serial] creating modem with plugin 'generic' and '1' ports ... ModemManager[573]: [1692200059.704189] [modem0/ttymxc0/at] --> 'AT+WS46=?' ModemManager[573]: [1692200059.716311] [modem0/ttymxc0/at] <-- '+CME ERROR: 100' -- Aleksander
RE: ublox SARA does not connect
Hi It’s a little difficult to collect logs as I do not have the board at the moment. However, the way I solved it eventually was to downgrade modem manager from 1.20 to 1.18 on ubuntu 22.04. that fixed the problem ron -Original Message- From: Aleksander Morgado Sent: Thursday, March 30, 2023 11:16 AM To: ron Cc: modemmanager-devel@lists.freedesktop.org Subject: Re: ublox SARA does not connect Hey! On Mon, Mar 27, 2023 at 11:00 AM ron wrote: > > Hi > > Im running a ublox SARA modem in an embedded system on ubuntu. > > It is connecting fine on ubuntu 20.04, but remains in “registered” state when > setup in ubuntu 22.04. > > It seems that NM doesn’t run pppd for some reason, or is it MM issue? > > > > root@ubuntu:~# mmcli -m 0 > > > > General | path: /org/freedesktop/ModemManager1/Modem/0 > >|device id: d4174b3552de7d45f5b0268aec1350664f7273c6 > > > > Hardware | manufacturer: u-blox > >|model: SARA-R510M8S > >|firmware revision: 03.15 > >|supported: gsm-umts > >| current: gsm-umts > >| equipment id: 352709570223149 > > > > System | device: > /sys/devices/platform/soc@0/3080.bus/3086.serial > >| drivers: imx-uart > >| plugin: generic > >| primary port: ttymxc0 > >|ports: ttymxc0 (at) > > > > Status | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), > sim-puk2 (10) > >|state: registered > >| power state: on > >| access tech: lte > >| signal quality: 41% (recent) > > > > Modes|supported: allowed: any; preferred: none > >| current: allowed: any; preferred: none > > > > IP |supported: ipv4, ipv6, ipv4v6 > > > > 3GPP | imei: 352709570223149 > >|operator name: Partner ISR > >| registration: home-sms-only > >| packet service state: detached These two previous lines are a bit suspicious. The home-sms-only could indicate that you are not allowed to setup a data connection, but that would collide with your previous statement that it worked fine in 20.04. Then, the packet service detached thing could indicate that we're not correctly handling that, but a bit unsure without looking at the logs. Could you gather MM debug logs (see https://modemmanager.org/docs/modemmanager/debugging/) with both Ubuntu 20.04 and Ubuntu 22.04 and open a new issue in gitlab? https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues > > > > SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 > > > > NM connection file: > > > > id=ttymxc0 > > uuid=c0a7c307-2657-4cf1-8913-b5a826594338 > > type=gsm > > > > [gsm] > > #apn=uinternet > > auto-config=TRUE > > > > [ppp] > > baud=921600 > > crtscts=true > > lcp-echo-failure=5 > > lcp-echo-interval=30 > > > > [ipv4] > > dns-search= > > method=auto > > > > [ipv6] > > addr-gen-mode=stable-privacy > > dns-search= > > method=ignore -- Aleksander
Re: ublox SARA does not connect
Hey! On Mon, Mar 27, 2023 at 11:00 AM ron wrote: > > Hi > > Im running a ublox SARA modem in an embedded system on ubuntu. > > It is connecting fine on ubuntu 20.04, but remains in “registered” state when > setup in ubuntu 22.04. > > It seems that NM doesn’t run pppd for some reason, or is it MM issue? > > > > root@ubuntu:~# mmcli -m 0 > > > > General | path: /org/freedesktop/ModemManager1/Modem/0 > >|device id: d4174b3552de7d45f5b0268aec1350664f7273c6 > > > > Hardware | manufacturer: u-blox > >|model: SARA-R510M8S > >|firmware revision: 03.15 > >|supported: gsm-umts > >| current: gsm-umts > >| equipment id: 352709570223149 > > > > System | device: > /sys/devices/platform/soc@0/3080.bus/3086.serial > >| drivers: imx-uart > >| plugin: generic > >| primary port: ttymxc0 > >|ports: ttymxc0 (at) > > > > Status | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), > sim-puk2 (10) > >|state: registered > >| power state: on > >| access tech: lte > >| signal quality: 41% (recent) > > > > Modes|supported: allowed: any; preferred: none > >| current: allowed: any; preferred: none > > > > IP |supported: ipv4, ipv6, ipv4v6 > > > > 3GPP | imei: 352709570223149 > >|operator name: Partner ISR > >| registration: home-sms-only > >| packet service state: detached These two previous lines are a bit suspicious. The home-sms-only could indicate that you are not allowed to setup a data connection, but that would collide with your previous statement that it worked fine in 20.04. Then, the packet service detached thing could indicate that we're not correctly handling that, but a bit unsure without looking at the logs. Could you gather MM debug logs (see https://modemmanager.org/docs/modemmanager/debugging/) with both Ubuntu 20.04 and Ubuntu 22.04 and open a new issue in gitlab? https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues > > > > SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 > > > > NM connection file: > > > > id=ttymxc0 > > uuid=c0a7c307-2657-4cf1-8913-b5a826594338 > > type=gsm > > > > [gsm] > > #apn=uinternet > > auto-config=TRUE > > > > [ppp] > > baud=921600 > > crtscts=true > > lcp-echo-failure=5 > > lcp-echo-interval=30 > > > > [ipv4] > > dns-search= > > method=auto > > > > [ipv6] > > addr-gen-mode=stable-privacy > > dns-search= > > method=ignore -- Aleksander